Definition
The INVOIC transmits an invoice in structured form. The header carries invoice number and date, issuer and recipient, and payment terms. Each line then carries the article identifier, delivered quantity, unit price and line value, plus discounts and surcharges. The trailer holds the tax breakdown and totals. What matters most are the references: the INVOIC points to the order number from the ORDERS and normally to the despatch advice from the DESADV. Only with those references can the recipient run the three-way match between purchase order, goods receipt and invoice without human intervention.
Why it matters
Invoice verification is one of the most expensive manual processes on the recipient's side, and every discrepancy creates an exception that costs both parties time. An INVOIC whose references and values reconcile cleanly against the order and the shipping notice posts automatically. One that does not lands in exception handling — and in the Amazon vendor model that is a frequent cause of deductions and delayed payment. The value of the INVOIC therefore lies less in sending the invoice than in staying consistent with the rest of the message chain.
How it works
In practice: the INVOIC may only reflect what was actually delivered, and must rest on the same references as the DESADV and ORDERS. Prices must match those transmitted in the order — discrepancies belong resolved before invoicing, not after. Partial deliveries need one invoice per delivery with the matching delivery reference. Credit notes and corrections travel as INVOIC messages with the appropriate message function, not as informal corrections outside the EDI channel. Mandatory fields and deadlines come from the partner's implementation guideline; for Amazon vendors, from Amazon's EDI specification.
Real-world examples
• A vendor sends the day's invoices as INVOIC messages each evening; each references its purchase order and its despatch advice, and verification runs through untouched on the recipient's side. • One order ships in two consignments and produces two DESADV and two INVOIC messages sharing an order reference but carrying different delivery references. • An invoice price differs from the order price by a few cents; automatic matching stops and the transaction moves to manual clearing.
Common pitfalls
• **Missing references:** without order and delivery references no automatic match is possible and the invoice will land in exception handling. • **Invoicing before the shipping notice:** an INVOIC that arrives before its DESADV cannot be allocated by the recipient. • **Price deviations:** even tiny differences from the order stop automatic posting. The fix belongs upstream in price maintenance. • **Confusing it with ZUGFeRD:** ZUGFeRD and XRechnung are separate e-invoicing formats with a different purpose. They do not replace an INVOIC inside an existing EDI chain.
Frequently asked
What is an INVOIC message?+
INVOIC is the EDIFACT message for an invoice. It transmits header, lines, tax details and totals in structured form and references the underlying purchase order and despatch advice so that invoice verification can run automatically.
What is the X12 equivalent of INVOIC?+
Transaction 810 (Invoice). EDIFACT INVOIC and X12 810 serve the same purpose in different standards — EDIFACT is common in Europe, X12 in North America.
What is the difference between INVOIC and ZUGFeRD?+
INVOIC is part of an EDI chain between trading partners and links directly to the purchase order and despatch advice. ZUGFeRD and XRechnung are German e-invoicing formats aimed at electronic invoicing towards public authorities in particular, and work without any upstream EDI process. They do not replace one another.
Why is my EDI invoice being rejected?+
The usual causes are missing or incorrect references to the purchase order and despatch advice, price or quantity deviations from the order, an invoice with no matching goods receipt, or missing mandatory fields from the partner's implementation guideline. In each case the root cause normally sits upstream in the process rather than in the invoice itself.