Interunit Pairs

You must define ChartFields and other options used for interunit transactions on the InterUnit Pairs page when you choose to use the Pairs Method. The Direct or Indirect Method does not apply to pairs.

An InterUnit Pairs definition is keyed by the from business unit, the to business unit and Transaction Code. For each of these combinations you specify the interunit receivable and interunit payable ChartFields. Separate InterEntity and IntraEntity definitions are not necessary because any given pair of business units can only be one or the other.

All ChartField validation is based on the SetIDs associated with the business units. The business unit used as the Set Control Value for ChartField prompting and validation depends on the Accounting Entry Type. When maintaining interunit pair data, refer to the following table to determine which entry types belong to which business unit.

From Business Unit	To Business Unit
Receivables	Payable
Revenue (for Billing Invoices)	Expense (for Billing Invoices)
In Transit (for interunit transfers if the Source is the Ownership Unit	In Transit (for interunit transfers if the Destination is the Ownership Unit)
Cost of Goods (for interunit transfers)	Accrued Payables (for interunit transfers) Customer Shipments (for interunit transfers)