INVOIC is the EDIFACT/EANCOM message for the electronic invoice sent to a retailer. It carries the parties, references to the order and the despatch advice, items, quantities, prices, VAT and totals. In Romania, INVOIC and the ANAF e-Invoice coexist: INVOIC goes to the retailer, the e-Invoice goes to ANAF.
INVOIC is the EDIFACT message for the electronic invoice, carrying party tax data, items, quantities, prices, VAT and totals. In Romania it coexists with ANAF e-Invoice (UBL 2.1 XML sent via SPV): EDIconnect automatically converts between INVOIC (required by retailers) and e-Invoice (required by ANAF), eliminating double entry.
An INVOIC repeats the data from the order and the delivery and adds the financial part. The main segments:
| Segment | Role in the message |
|---|---|
| UNH | Message header: type (INVOIC) and version. |
| BGM | Beginning of the document: type (380 = commercial invoice) and the invoice number. |
| DTM | Invoice date (137) and other relevant dates. |
| RFF | References: the order (ON), the despatch advice (DQ), the party's VAT number (VA). |
| NAD | Supplier (SU), buyer (BY), invoicee (IV) and delivery party (DP). |
| CUX | The invoice currency. |
| LIN, QTY, PRI | The item (GTIN), the invoiced quantity (47) and the net price. |
| MOA | Amounts: the line amount (203) and the summary totals (77, 79, 125, 176). |
| TAX | Tax: the VAT and the rate applied. |
| UNT | End of the message. |
The example is illustrative and simplified: 118 units invoiced, the ones received in the RECADV example, at 4.35 each. The amounts and the VAT rate are illustrative and do not replace the tax rules in force.
UNH+1+INVOIC:D:96A:UN:EAN008'
BGM+380+INV-2026-1234+9'
DTM+137:20261120:102'
RFF+ON:PO-2026-0451'
RFF+DQ:DES-2026-0187'
NAD+SU+2000001000014::9'
NAD+BY+2000002000020::9'
NAD+IV+2000004000042::9'
NAD+DP+2000003000036::9'
CUX+2:RON:4'
LIN+1++5940000000011:SRV'
QTY+47:118'
MOA+203:513.30'
PRI+AAA:4.35'
UNS+S'
MOA+77:621.09'
MOA+79:513.30'
TAX+7+VAT+++:::21'
MOA+125:513.30'
MOA+176:107.79'
UNT+21+1'INVOIC closes the commercial flow: ORDERS → ORDRSP → DESADV → RECADV → INVOIC. It is issued after delivery and, as a rule, after the quantities have been confirmed by RECADV.
EDIconnect converts automatically between INVOIC, required by retailers, and the e-Invoice, required by ANAF, with no double entry. You can issue the invoice from the Web EDI portal or from your ERP, and the platform generates the e-Invoice from the INVOIC and submits it to ANAF using the company's digital certificate.
EDIconnect sends INVOIC to the retailer and generates the e-Invoice for ANAF from the same flow, with no double entry.
Last updated: November 2026. The example is illustrative and simplified; mandatory segments and codes differ from one retailer to another, so follow the partner's implementation guide.