Receiver Matching supports the use of operational allocation codes.

If you set up an operational allocation code for several GL accounts and then specify the allocation code on a purchase order, Receiver Matching splits the posting lines across the GL accounts, sub-accounts, cost centers, and projects in the allocation code.

If you set the Use Exp Item Var Accts field to Yes in Supplier Invoice Control, you can view the operational allocation code in Receiver Matching, but the code is not actually used in the matching process. This situation occurs because the system has already charged the expense to the allocation code. The expense posting was created during PO Receipt, and was offset by the posting to the Expensed Item Receipts account and posted using Operational Transaction Post. In Receiver Matching, the main posting is to the Expensed Item Receipts account, and other accounts (other than tax accounts, the supplier control account, and the unmatched invoices account) are only used if there are usage or rate variances for the memo item purchase. If usage or rate variances occur, these are charged to the Expensed Item Usage Variance account or to the Expense Item Rate Variance account defined in Domain/Account Control.

If you set the Use Exp Item Var Accts field to No in Supplier Invoice Control, any usage or rate variances that arise from the matching of a memo item receipt are instead charged to the expense account defined on the purchase order line. If you specify an allocation code instead of a GL account, the allocation code is used in Receiver Matching.

The Op Alloc Code field in the Receiver Matching grid displays an operational allocation code if one was specified on the purchase order for the memo item. For memo items only, you can also enter a new allocation code, even if one was not used on the purchase order line.