How does accounting information populate on non-purchase order (PO) invoices sent by suppliers from the SAP Business Network?

Accounting information populates based on the requester's default accounting information. The following information demonstrates how the fields are related:

• The requester (On Behalf Of field) is derived from the Sold To Email address that the supplier specifies when creating the non-PO invoice.
• When the supplier creates a non-PO invoice on the SAP Business Network, the Email field within the Additional Fields section of the invoice header corresponds to the Sold To Email address. This Email field is a free-form text box and not a chooser field, which allows the supplier to specify any email address in this field.

The supplier must match the exact email address that is defined in your Ariba Procurement and Invoicing Solution for the user (including case sensitivity), or else the email address validation fails when the invoice reaches your site.

To clarify how the supplier-entered information corresponds to your Ariba Procurement and Invoicing Solutions, consider the following example:

• If the supplier specifies jdoe@ariba.com for the Sold To Email address on the non-PO invoice, when the invoice reaches your site, the site looks within the master data to find a match for that user's email address.
• If a match is found, that user is set as the requester of the invoice.
• If the requester is successfully set based on the email address lookup, then the invoice line-item accounting values default based on the requester's default user profile accounting data.
• If no match is found, aribasystem is set as the requester.

Invoicing > Non-PO Invoice