Evaluating Interface Activity

Before the Billing Interface process evaluates interface activity to determine whether new bill headers are required, it evaluates the customer, bill source, bill type, and business unit characteristics to send the appropriate bill-by to the interface staging area by default. The Billing Interface process then uses the bill-by identifiers to determine which new bill headers need to be generated.

If, for example, you have a different bill-by identifier defined for each bill type, the Billing Interface process selects by default the bill-by identifier for each bill type. It groups the interface data for each bill type by using the bill-by criteria of that type.

You must define some fields together as part of the bill-by in order for the functionality of the fields to process correctly. For example, to use the user-defined currency rate functionality, you must define three fields together in the bill-by: CUR_RT_SOURCE, RATE_MULT, and RATE_DIV. If you define only one or two of these fields in the bill-by criteria, the system creates a bill with erroneous rate information.

Other fields that work as a group are listed in the following table:

Functionality	Fields to Add to Bill-By
User-Defined Currency Rate	CUR_RT_SOURCE, RATE_MULT, RATE_DIV
Direct Invoicing	RANGE_SELECTION_ID, DIRECT_INVOICING
Override Defaults for Consolidated Billing	(CONSOL_KEY) and (CONSOL_SETID, CONSOL_CUST_ID)
OM_BILL to Billing interface	ADDRESS_SEQ_NUM, PAYMENT_METHOD, PYMNT_TERMS_CD

You should include SHIP_FROM_BU as a bill-by field for transactions from Order Management or Inventory that will be subject to VAT.