Invoice Message
UN/EDIFACT INVOIC is the electronic invoice message, the EDIFACT counterpart to the X12 810, used to bill for goods or services delivered.
In this guide
EDIFACT INVOIC moves from Supplier to Buyer (Seller → Buyer) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT INVOIC Works
Sender
Supplier
Receiver
Buyer
Direction
Seller → Buyer
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Finance
Sender — Supplier
EDI Transmission
INVOIC
Invoice Message
UN/EDIFACT D.96A / D.01B
Receiver — Buyer
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT INVOIC workflow. Steps: Generate Billing Detail, Build INVOIC, Send to Buyer, Buyer AP Gateway, Automated Matching, Approve for Payment. Transmitted from Supplier to Buyer via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Automates accounts payable matching and drives faster, more accurate supplier payment across EDIFACT trading relationships.
Sender
Supplier
Receiver
Buyer
Direction
Seller → Buyer
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Invoice number and document type. |
| RFF | Reference | References the original order number. |
| LIN | Line Item | Billed item. |
| MOA | Monetary Amount | Line and document total amounts. |
| TAX | Duty/Tax/Fee Details | VAT or other tax detail. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+INVOIC:D:96A:UN'
BGM+380+INV-90210+9'
DTM+3:20230925:102'
RFF+ON:PO-2024-88213'
NAD+BY+BUYERCORP::92'
NAD+SU+ACMESUPPLY::92'
LIN+1++SKU-10293:BP'
QTY+47:100'
PRI+AAA:25.00'
MOA+203:2500.00'
TAX+7+VAT+++:::20+S'
UNS+S'
MOA+79:2950.00'
UNT+13+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| ERP Billing Document | invoice.line_amount | MOA+203 (Monetary Amount) |
| ERP Billing Document | invoice.vat_rate | TAX/5278 (Duty/Tax/Fee Rate) |
Validation rules
- RFF+ON must reference a valid, previously received ORDERS document.
- Sum of LIN-level MOA+203 amounts plus tax must equal the document-level MOA+79 total.
- TAX segments must use valid country-specific tax type and rate codes.
Common errors & troubleshooting
Invoice held for tax discrepancy
Cause: VAT rate on the invoice doesn't match the rate configured for that product/country combination in the buyer's tax engine.
Fix: Synchronize tax rate tables between trading partners, especially after regulatory rate changes.
Related articles
Frequently asked questions
The message carries currency qualifiers alongside MOA segments, and cross-border invoices commonly specify both invoice currency and, where required, the tax point currency.
Still have questions about INVOIC?
Ask EDI AI →