Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/OrderManagement/PricingRules/PaymentTermsRule.htm

## Payment Terms

Payment Terms pricing rules define when the product is to be paid for. Payment Terms can be negotiated between the end user and the pharmacist. Payment Terms can be defined on the product (SKU), total order, brand, or product group level.

Payment Terms are defined using Payment Terms pricing rules and the value of the payment\_values\_\_v Veeva Setting.

**Who can use this feature?**

* End Users - iPad, Windows
* [Using Payment Terms Pricing Rules](#Using)
* Order Admins
* [Setting Payment Term Entry via Pricing Rules - iPad, Windows](#Creating)
* [Setting Payment Term Entry via Free Text - Browser, iPad, Windows](#Setting)
* [Setting Payment Term Entry via Picklist - Browser, iPad, Windows](#Setting2)
* Users do not require an additional license

### Configuring Payment Terms Pricing Rules for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)All Users](#)

Payment Terms pricing rules are not required to use payment terms. The payment\_values\_\_v Veeva Setting can be used to set payment term values across all products and conditions. Free Text payment terms can be entered if the payment\_values\_\_v Veeva Setting does not contain a value. Browser only supports Free Text payment terms.

To configure this feature:

1. Ensure [Configuring Order Management](../OM_Config.htm) is complete.
2. Navigate to **Business Admin > Objects > Veeva Settings (veeva\_settings\_\_v)**.
3. Set the Payment Terms entry to free text or a picklist:

* **Free Text entry** - Leave the payment\_values\_\_v field empty

* **Picklist entry** - Populate the payment\_values\_\_v field with values separated by a semicolon in the order they should display, for example, 30 Days;60 Days; 90 Days

4. Select the payment\_priority\_bottomtotop\_\_v check box to set Payment Term priority:
   * **Selected** - Priority order is set to product level, brand level, product group level, then order level
   * **Unselected** - Priority order is set to order level, product group level, brand level, then product level
5. Select **Save**.

### Creating Payment Terms Pricing Rules as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Order Admins](#)

When payment\_values\_\_v is populated, the Payment Term fields on the order and order lines display a defined picklist. If payment\_values\_\_v is not populated, the Payment Term field displays a free text field.

#### Setting Payment Term Entry via Pricing Rules

Creating a Payment Terms Pricing Rule sets the payment terms on the line, order, brand, and product group level.

To create a Payment Terms Pricing Rule:

1. Navigate to **Home > Pricing Rules**.
2. Select **Create**.
3. Select **Payment Terms** in the Object Type Selector.
4. Select **Continue**.
5. Complete the following fields:
   * name\_\_v
   * product\_\_v (must be null, or product\_type\_\_v is order\_\_v, detail\_\_v, product\_group\_\_v)
   * start\_date\_\_v
   * end\_date\_\_v
   * comparison\_type\_\_v
   * minimum\_quantity\_\_v
   * maximum\_quantity\_\_v (optional)
   * payment\_terms\_\_v
   * payment\_terms\_max\_\_v (optional) (values separated by a semicolon)
6. Select **Save**.

If there is a matching Payment Terms pricing rule, Payment Term is set based on the pricing rule:

* If the payment\_max\_\_v field for the Payment Terms pricing rule contains a value, the user is able to edit the set value to one of the values listed in the field
* If the payment\_max\_\_v field for the Payment Terms pricing rule, does not contain a value but the payment\_values\_\_v Veeva Setting contains a value, the user is able to select a Payment Term from the values listed in the Veeva Setting
* If the payment\_max\_\_v field for the Payment Terms pricing rule, does not contain a value and the payment\_values\_\_v Veeva Setting does not contain a value, the user is able to enter free text value as the Payment Term

If there is not a matching Payment Terms pricing rule, Payment Term is not set:

* If the payment\_values\_\_v Veeva Setting contains a value, the user is able to select a Payment Term from the values listed in the Veeva Setting

* If the payment\_values\_\_v Veeva Setting does not contain a value, the user is able to enter free text value as the Payment Term

| Payment Terms Pricing Rule applied? | Payment Terms Pricing Rule applied has Payment Max defined? | Veeva Settings Payment Value is defined? | Default Payment Term | Available Payment Terms |
| --- | --- | --- | --- | --- |
| Yes | Yes | n/a | payment\_\_v field on the pricing\_rule\_\_v object | payment\_max\_\_v field on the pricing\_rule\_\_v object |
| Yes | No | Yes | payment\_\_v on the pricing\_rule\_\_v object | payment\_values\_\_v Veeva Setting |
| Yes | No | No | payment\_\_v on the pricing\_rule\_\_v object | Free text |
| No | n/a | Yes | None | payment\_values\_\_v Veeva Setting |
| No | n/a | No | None | Free text |

The payment\_priority\_bottomtotop\_\_v Veeva Setting determines the priority of choosing a winning payment term to set as total\_payment\_\_v when payment terms are set on the product, total order, brand, and product group level.

* If the payment\_priority\_bottomtotop\_\_v checkbox is deselected, Payment Term priority is set to order level, product group level, brand level, and then product level
* If the payment\_priority\_bottomtotop\_\_v checkbox is selected, Payment Term priority is set to product level, brand level, product group level, and then order level

#### Setting Payment Term Entry via Free Text

Free text entry is available when the payment\_values\_\_v field on the Veeva Settings record is empty.

To set Payment Term entry via free text:

1. Navigate to **Business Admin > Objects > Veeva Settings (veeva\_settings\_\_v)**.
2. Select the appropriate Veeva Settings record.
3. Ensure the **payment\_values\_\_v field** is empty.
4. Select **Save**.

#### Setting Payment Term Entry via Picklist

Populating the Veeva Settings record displays a defined picklist of Payment Term options for end users.

To set Payment Term entry via picklist:

1. Navigate to **Business Admin > Objects > Veeva Settings (veeva\_settings\_\_v)**.
2. Select the appropriate Veeva Settings record.
3. Enter the picklist options in the **payment\_values\_\_v field** in the order they should display, for example, 30 Days; 60 Days; 90 Days.
4. Specify the Payment Term priority via the **payment\_priority\_bottomtotop\_\_v** checkbox:

   * **Enabled** - Payment Term priority starts at the product level, brand level, product group level, then order level
   * **Disabled** - Payment Term priority starts at the order level, product group level, brand level, then product level
5. Select **Save**.

### Using Payment Terms Pricing Rules as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

After all discounts are calculated and applied, Payment Terms pricing rules can set the payment terms on the line level, order level, brand level, and product group level. If payment terms are not set by Payment Terms pricing rules, users can select from the values in the payment\_values\_\_v Veeva Setting. If the payment\_values\_\_v Veeva Setting does not contain any values, users can enter free text.

If the payment\_\_v, payment\_brand\_\_v, and/or payment\_group\_\_v fields are on the layout for order\_line\_\_v and/or the payment\_\_v field is on the layout for order\_\_v, the user can manually override the payment terms determined by the pricing rules with values either from the payment\_terms\_max\_\_v field on the pricing rules, values from the payment\_values\_\_v Veeva Setting, or with free text.

If payment\_brand\_\_v is edited, the override value is applied to payment\_brand\_\_v for all products in the brand.

The payment\_group\_\_v field can only be edited if a product group is defined for the order line in the product\_group\_\_v field. The override value is applied to payment\_group\_\_v for all products with the same product\_group\_\_v value defined on the order line.

#### Comparison Type

* If Payment Term comparison\_type\_\_v equals the product\_quantity\_\_v, quantity\_\_v is considered to determine if the payment term applies
* If Limit Rule comparison\_type\_\_v equals the list\_value\_\_v, quantity\_\_v multiplied by list\_amount\_\_v is considered to determine if the payment term applies
* If Limit Rule comparison\_type\_\_v equals the net\_value\_\_v, quantity\_\_v multiplied by net\_amount\_\_v is considered to determine if the payment term applies

#### Product Type

* If Payment Term product product\_type\_\_v equals order\_\_v, only the product is considered to determine if the payment term applies. The Payment Term pricing rule sets the payment\_\_v field on the order line.
* If Payment Term product product\_type\_\_v equals null, all products on the order are considered to determine if the payment term applies. The Payment Term pricing rule sets the payment\_\_v field on the order.
* If Payment Term product product\_type\_\_v equals detail\_\_v, all products in the brand are considered to determine if the payment term applies. The Payment Term pricing rule sets the payment\_brand\_\_v field on the order line.
* If Payment Term product product\_type\_\_v equals group\_\_v, all products in the product group are considered to determine if the payment term applies. The Payment Term pricing rule sets the payment\_group\_\_v field on the order line.
* If a product group is defined for the order line in the product\_group\_\_v field, only Payment Term pricing rules for that product group are considered
* If a product group is not defined for the order line in the product\_group\_\_v field and there is only one Payment Term pricing rule that could apply to the product on the product group level, that Payment Term pricing rule is considered
* If a product group is not defined for the order line in the product\_group\_\_v field and there are multiple Payment Term pricing ruless that could apply to the product on the product group level, no Payment Term pricing rules are considered and payment\_group\_\_v is not set for the order line

A product is considered towards all Product Groups it belongs to, even if a Product Group is defined on the product order line.

### Related Topics

[List Price Rules](ListPriceRule.htm)

[Limit Pricing Rules](LimitPriceRule.htm)