Self-Billing and ERS: Buyers Invoice Themselves

Self-billing flips invoicing on its head: the buyer, not the supplier, creates the invoice. The buyer already knows the price from the purchase order and knows what arrived from the goods receipt, so it computes the amount owed and pays, no supplier invoice required. Automotive and large retail run on this model because it strips out an entire class of invoice-matching disputes. It is tightly coupled to scheduling agreements and to the EDI 856 ship notice that confirms receipt.

The mechanics confuse people for two reasons: the naming is inconsistent across standards and ERPs, and ASC X12, unlike EDIFACT, never defined a self-billed invoice transaction at all. That second point clears up most of the confusion, so it comes first.

There Is No X12 "Self-Billed Invoice" Transaction

Here is the under-explained fact: ASC X12 has no dedicated self-billed invoice transaction set. People search for one and never find it, because it does not exist. Self-billing in the X12 world rides on transactions that already exist, driven by the buyer's ERS or pay-on-receipt program:

• EDI 861 Receiving Advice records what the buyer received, the trigger for settlement
• EDI 810 Invoice carries the invoice, generated by the buyer internally rather than sent by the supplier
• EDI 812 Credit/Debit Adjustment handles corrections, short-pays, and adjustments after settlement

The 810 you see in a self-billing flow was not keyed by the supplier. The buyer's system produced it from the PO and the goods receipt. Nothing in the transaction set itself signals "self-billed"; the context is the buyer's ERS program.

Oracle states this equivalence directly. In its documentation, Pay on Receipt, ERS, and Self-Billing are the same feature: an invoice generated internally from the purchase order and the goods receipt, not from a supplier submission (docs.oracle.com, Pay on Receipt / ERS).

How ERS Actually Runs

Evaluated Receipt Settlement pays the supplier by matching the goods receipt to the purchase order and pricing from the PO, with no supplier invoice in the loop. The sequence looks like this:

1. The supplier ships against a scheduling agreement or PO and sends an ASN (856 or EDIFACT DESADV).
2. Goods arrive and the buyer posts a goods receipt, matched to the ASN.
3. The buyer's ERS run picks up the receipt, prices each line from the PO, calculates tax, and creates the settlement document.
4. The buyer pays on terms and, in EDI relationships, transmits the settlement to the supplier so the supplier can clear its receivable.

Because pricing comes from the agreed PO and quantity comes from the verified receipt, the classic three-way-match failure, invoice versus PO versus receipt, cannot happen. The invoice is derived from the two documents it would otherwise be matched against. For the matching problem this replaces, see three-way match explained.

EDIFACT Does Have Self-Billing Codes

Unlike X12, EDIFACT carries self-billing explicitly inside the INVOIC message through the BGM document-name code. The BGM segment's document-name code (data element 1001) distinguishes a self-billed document from an ordinary one:

BGM 1001 code	Document
389	Self-billed invoice
261	Self-billed credit note
527	Self-billed debit note

These codes are defined in the GS1 EANCOM guidelines for the INVOIC message (gs1.org EANCOM) and the underlying UN/EDIFACT directories (unece.org UN/EDIFACT). So an EDIFACT partner can send a single INVOIC and flag it as self-billed, where an X12 partner would use a plain 810 whose self-billed nature is understood from the ERS program context.

How SAP and Oracle Implement It

SAP runs ERS through transaction MRRL and treats certain scheduling agreements as invoiceable only via self-billing. MRRL performs the evaluated receipt settlement run: it reads goods receipts flagged for ERS, prices from the PO or scheduling agreement, and posts the settlement without a supplier invoice. SAP documents ERS as part of its logistics invoice verification (help.sap.com, Evaluated Receipt Settlement).

For automotive, SAP's scheduling agreement type LZS (external service, self-billing) is invoiceable only through the self-billing IDoc, transmitted as SBINV / GSVERF. The supplier posts the buyer's self-billing document to clear its receivable rather than issuing its own invoice. That is the technical expression of "the buyer invoices themselves."

Oracle, as noted, folds all of this into one feature. Whether you call it Pay on Receipt, ERS, or Self-Billing, the engine generates the invoice from the PO plus the goods receipt.

When Self-Billing Makes Sense

Self-billing pays off when volume is high, pricing is stable and contract-driven, and receipts are reliably captured, which is exactly the profile of a scheduling agreement relationship. The prerequisites are real: prices must be locked in the PO or agreement, tax handling must be agreed in advance, and the buyer's goods receipt must be accurate, because the supplier is now trusting the buyer's count.

Where those conditions hold, it removes supplier invoicing labor, compresses the payment cycle, and cuts disputes. Where they do not, spot pricing, frequent price changes, unreliable receiving, conventional invoicing is safer. It also depends on clean ASN and receiving data, which is why the 856 ship notice and 861 receiving advice are the documents that make or break an ERS program.

You can validate the 810, 856, and 861 files in a self-billing flow with our free EDI Inspector before wiring them to your ERP. To connect settlement documents to your back office automatically, see ERP integration.

Frequently Asked Questions

What is self-billing in EDI?

Self-billing is an arrangement where the buyer generates the invoice from the purchase order and goods receipt, rather than the supplier sending one. It is also called Evaluated Receipt Settlement (ERS) or Pay on Receipt. The buyer prices the verified receipt from the agreed PO and pays automatically.

Is there a dedicated X12 transaction for self-billed invoices?

No. ASC X12 has no dedicated self-billed invoice transaction set. Self-billing rides on existing transactions: the 861 receiving advice triggers it, the 810 carries the buyer-generated invoice, and the 812 handles adjustments. EDIFACT differs, flagging self-billing inside the INVOIC message with BGM code 389.

What is the difference between ERS and self-billing?

They describe the same thing. Evaluated Receipt Settlement (ERS) is the technical term for settling payment from the goods receipt and PO without a supplier invoice. Self-billing is the commercial term. Oracle explicitly equates Pay on Receipt, ERS, and Self-Billing as one feature.

How does SAP handle evaluated receipt settlement?

SAP runs ERS through transaction MRRL, which reads goods receipts flagged for ERS, prices from the PO or scheduling agreement, and posts settlement without a supplier invoice. Automotive scheduling agreement type LZS is invoiceable only through the self-billing IDoc, transmitted as SBINV or GSVERF.

Why does self-billing reduce invoice disputes?

Because the invoice is derived from the purchase order and the verified goods receipt, the usual three-way-match failure between invoice, PO, and receipt cannot occur. Pricing comes from the agreed PO and quantity from the confirmed receipt, so there is nothing to mismatch, provided the receipt data is accurate.