Configure Business Unit Derivation

Configure how Payables Agent assigns invoices to Business Units.

Business Unit derivation affects invoice ownership, accounting, routing, approvals, user visibility, and exception management. Only one Business Unit derivation method can be active at a time.

Derivation method How it works Recommended use
Standard Business Unit Derivation Uses existing Oracle Payables logic. For matched invoices, the Business Unit is derived from the purchase order. For unmatched invoices, the Business Unit is derived from the supplier site. If neither source is available, the Business Unit is derived from the DEFAULT_ORG_ID profile option. Use when purchase order and supplier-site setup reliably determine the Business Unit.
Email Routing Attribute Derives the Business Unit from information embedded in the email subject. Use when suppliers submit invoices for multiple Business Units, the organization operates only a few Business Units, or email mapping isn’t practical.
Sender Email Address Mapping Derives the Business Unit from the sender’s email address. Use when supplier sender addresses consistently map to Business Units.
Recipient Email Address Mapping Derives the Business Unit from the recipient email address. Use when the organization maintains multiple invoice mailboxes for different Business Units, regions, or operating groups.

To configure Business Unit derivation:

  1. Go to Navigator > My Enterprise > Setup and Maintenance > Financials > Payables > Manage Intelligent Document Recognition Options.
  2. Review the Business Unit derivation options.
  3. Select the required email-based Business Unit derivation mode.
  4. Open Configuration > Capture > Streams.
  5. Select Invoice Image Documents.
  6. Open Email-to-Business Unit Mapping from the stream actions menu.
  7. Create the sender or recipient email mappings required by the selected derivation mode.
  8. Save and test the mappings.

Submit test invoices for the selected derivation method and confirm that Business Units are assigned correctly, routing behavior matches expectations, and invoices appear under the appropriate Business Unit.