EDI INVOIC — the EDIFACT electronic invoice message
In short: The EDI INVOIC message is the electronic invoice in EDIFACT format: the supplier sends the retailer an invoice after delivery, referencing the original ORDERS and DESADV, with VAT, line items and payment terms. It is the EDIFACT equivalent of X12 810 and can be converted to UBL for Romania's ANAF e-invoicing system.
Key capabilities
- Full EDIFACT structure: Header (invoice identifiers), TAX (VAT per rate), MOA (amounts), LIN (line items with price, quantity, VAT), TOD (payment terms).
- Linked to ORDERS + DESADV: Every INVOIC references the original order and dispatch advice — the retailer runs automatic 3-way matching (PO ↔ ASN ↔ INVOIC).
- Convertible to UBL for ANAF: The same invoice is issued as EDIFACT INVOIC to the retailer and as UBL 2.1 for Romania's ANAF e-invoicing system — one ERP export, two channels.
- Compliant 10-year archiving: Digital signature, encrypted archive, full audit trail — meets both Romanian tax requirements and retailer contracts.
INVOIC plus ANAF e-invoicing: one architecture
The most efficient pattern for suppliers selling into Romanian retail: the ERP exports the invoice once → EDIconnect converts it simultaneously into (a) EDIFACT INVOIC to the retailer via AS2, (b) UBL 2.1 to ANAF's e-invoicing system via API, (c) optionally UBL PEPPOL to B2B customers in the EU. Zero duplication, zero risk of mismatch between channels.
The result: accounting has a single source of truth (the ERP), the retailer receives the invoice in its required format, the tax authority receives it as UBL, and audits are simple — all three versions are archived in EDIconnect under the same invoice number.
Frequently asked questions
What is the EDI INVOIC message?
INVOIC is the standard EDIFACT message for a B2B electronic invoice. The supplier sends it to the retailer after delivery, referencing the original ORDERS and DESADV, including VAT, payment terms and all invoice lines.
Does INVOIC replace ANAF e-invoicing?
No — they are separate channels. INVOIC goes to the retailer over EDI (AS2/OFTP2). Romania's ANAF e-invoicing (UBL 2.1) goes to the ANAF e-invoicing platform via API. EDIconnect issues both from the same ERP export, in parallel.
How does the retailer perform 3-way matching?
The retailer automatically compares the purchase order (ORDERS), the quantities received (RECADV) and the invoice (INVOIC). If all three match, the invoice is approved for payment automatically; if not, it goes into a dispute queue.
What happens if my invoice is rejected?
The retailer can send an APERAK (application response) stating the rejection reason. EDIconnect displays the rejection in the portal and lets you correct and resend the invoice within minutes.
Does INVOIC need a digital signature?
It depends on the retailer and local tax regulation. Most large retailers require INVOIC to be signed with a qualified digital certificate or sent via AS2 (which embeds a signature). EDIconnect signs automatically according to each retailer's requirements.