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 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.

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.

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.