Outbound invoices from billing

Great Lakes Fleet Services buys alternators from Contoso Motor Co. by EDI: its purchase orders arrive as X12 850s and become sales orders (sap-edi-203), and it wants invoices back as X12 810s so its accounts payable system can match them without retyping. This lesson sets up that outbound invoice. The running example is billing document 90001877 for sales order 1000457 and delivery 80001234: 50 alternators CMC-ALT-100 at 240.00 USD, 12,000.00 USD net, no sales tax because Great Lakes Fleet Services holds an exemption.

Two output frameworks, one choice for all of billing

Billing in SAP S/4HANA can run on output determination (SD-BF-OC), the condition-technique message control known from ECC, or on SAP S/4HANA output control (CA-GTF-OC). SAP's billing documentation states a rule that shapes every design: you cannot combine the two frameworks within billing, so the choice applies to all billing apps. Which one is active by default depends on the release and on whether the system was converted, so check the activation setting rather than assuming. The Fiori apps Create Billing Documents, Manage Billing Documents and Schedule Billing Output send output only with output control.

Contoso runs billing on output control: invoice 90001877 was first sent to Great Lakes as a PDF by email (sap-sd-207 shows that rule). For EDI, Theo's team adds a Channel rule for output type BILLING_DOCUMENT, role RE and channel EDI, restricted to Great Lakes Fleet Services. Both channels stay active for role RE: the 810 is the document Great Lakes' accounts payable system processes, and the PDF copy goes to its AP mailbox for reference. If Great Lakes ever wants EDI only, marking the EDI rule exclusive stops the email without touching the 810. For the IDoc side of the EDI channel, follow SAP Note 2228611 and the billing documentation for your release; under SD-BF-OC the equivalent is the well-known V3 / RD00 / SD09 setup.

The partner profile

Why collect rather than send immediately? A billing run in the evening creates hundreds of invoices for fleet customers. Collecting them into 30-minute batches keeps the load on Process Orchestration smooth and gives Great Lakes a predictable number of interchanges a day. The cost is that every invoice IDoc waits in status 30 for up to half an hour, which monitoring must treat as normal (sap-edi-208 covers status 30).

Credit and debit memos

Credit memos (billing type G2) and debit memos (L2) go out through the same message type INVOIC. The IDoc header tells the receiver which document it is, and the mapping turns a credit memo into an 810 flagged as a credit or, for EDIFACT, an INVOIC with a credit note document code. Agree with Great Lakes whether credit memos travel as 810s at all; some customers want credits only on paper or as remittance adjustments, and that decision changes the output rules.

Testing the outbound invoice

A first test of outbound EDI invoicing is more than "the IDoc is green". In CMQ, Priya's team bills a delivery for Great Lakes and checks four points: the EDI output item is processed on the billing document; the INVOIC IDoc carries the expected values (invoice number, PO reference, items, tax exemption, total); Process Orchestration in XQ1 produced an 810 that passes Great Lakes' test translator with a positive 997; and Great Lakes' AP team confirms that the test invoice matched their PO in their system. The last step is the one that proves the business value, and the one most often skipped.