Invoice fails with the error: INV-15: This customer does not accept invoices for orders sent outside of Ariba SN.

Invoice failed with error : INV-13: Order reference xxxxxxxxxxx is an obsolete, duplicate, or replaced order.

The error may be due to one or more of the following reasons

• No Purchase Order(PO) exists on the SAP Business Network with the referenced PO number from the same buyer.
• The PO reference date included in the invoice does not match the one that exists on the SAP Business Network.
• The PO referenced in the invoice contains an extra space: [xxxxxxxxxxx] versus [xxxxxxxxxxx ].
• The invoice was created after the referenced PO version was obsoleted or cancelled
• The PO is being referenced only with the purchase order number, when this happens will not always link the order to the document and this is expected by Business Network.

Ensure you reference a matching and valid PO when creating an invoice.

This solution applies to invoices sent in all formats:

• PO-flip
• Commerce Extensible Markup Language (cXML)
• Electronic Data Interchange (EDI)

cXML:

Insert one of the following elements in the invoice to reference pre-existing purchase orders.

• OrderReference — (preferred method) A DocumentReference element containing the purchase order/master agreement payloadId.
• OrderIDInfo—The purchase order's orderID and its orderDate.

You can use either of the following:

Option 1:

<InvoiceDetailOrderInfo>

<OrderReference orderID = "xxxxxxxxxxx">

<DocumentReference payloadID = "PO Payload_id"></DocumentReference>

</OrderReference>

</InvoiceDetailOrderInfo>

Option 2:

<InvoiceDetailOrderInfo>

<OrderIDInfo orderID = "xxxxxxxxxxx" orderDate = "order date time"></OrderIDInfo>

</InvoiceDetailOrderInfo>

Copy the order date from the PO, and use the same format. For example: YYYY-YY-YYTyy:yy:yy-yy:yy

EDI:

The date within the BIG03 segment of the EDI invoice matches the date in the BEG05 segment of the EDI PO.

The BIG03 segment contains the date assigned by the buyer to the original PO, which is copied from the EDI850 PO's BEG05 date element. This is used on standard invoices that reference a single PO.

If you build a standard invoice that references a single PO and its line items, the BIG04 segment is required. The BIG03 segment is recommended to clarify the PO date. If the PO number (BIG04) for the buyer is unique, then, the BIG03 segment is not required.

The SAP Business Network works and processes invoices as follows:

1. When you send an invoice to your buyer, the SAP Business Network performs initial validation of the invoice details.
2. The SAP Business Network checks for details such as invoice number, the PO number against which the invoice was sent, the date of the PO included in the invoice document, etc.
3. Based on such data values, the SAP Business Network cross references the database to see if a PO sent by the same buyer (to whom you intend to send the invoice) contains the sending date of the mentioned PO.
4. A mismatch in this data (either an incorrect PO number or an incorrect PO date on the invoice) causes the SAP Business Network to tag these types of invoices as external PO invoices (also known as non-PO invoices).
5. After this validation, when the SAP Business Network reviews your buyer's invoicing rules, if your buyer has disabled the invoicing rule, Allow suppliers to send non PO invoices, this explains the rejection of the invoice.

You can verify buyer's transaction rules within your supplier account on the SAP Business Network.

In case you submit invoices via cXML, check this example that can help: Sample cXML for a PO-based invoice.

Here you can see the official documentation of how Business Network performs the match: Purchase Order Matching.

SAP Business Network for Procurement & Supply Chain > Transaction Documents > Transaction (Invoicing)