Is EDI the same as e-invoicing?
Both are electronic and both carry invoices, but they are not the same thing. A company often needs both, and confusing them leads to an integration plan that is wrong from the start.
The basic difference: mandatory for whom?
E-invoicing is a legal obligation. It uses a format the state defines (UBL in most European schemes, UBL-TR in Türkiye) and a channel the state defines. Its purpose is tax oversight.
EDI is a commercial agreement. The parties choose the format and the channel. Its purpose is to automate operations.
| E-invoicing | EDI | |
|---|---|---|
| Obligation | Legal | Contractual |
| Format | UBL (XML) | EDIFACT, X12 |
| Channel | Via the tax authority or a certified network | Between the parties (AS2, SFTP, VAN) |
| Scope | Invoices only | Orders, despatch, invoices, payment… |
| Validated by | The state | Your trading partner |
The real distinction: scope
The most important difference is the second-to-last row. E-invoicing concerns only the invoice. EDI carries the whole commercial process:
ORDERS -> purchase order
ORDRSP -> order response
DESADV -> despatch advice
RECADV -> receiving advice
INVOIC -> invoice
REMADV -> remittance advice
So "we moved to EDI" usually means "we now receive orders electronically too", whereas e-invoicing covers only the last step of the process.
Why do you need both?
Because they answer to different parties.
If you supply a retail chain, the chain may require an EDIFACT INVOIC so that it can post the invoice automatically. You will still have to issue the same invoice through the legal e-invoicing channel, because that is where legal validity comes from.
The same commercial event goes to two places in two formats. The duplication looks odd, but the systems exist for different reasons.
Practical consequences
The numbers must agree. The document number on the EDI invoice and on the e-invoice must be identical. Otherwise reconciliation shows two invoices and nobody knows which is real.
The amounts must agree. Systems that round differently in the two formats produce penny differences, and those differences raise questions in an audit.
Timing matters. If the EDI invoice reaches your partner before the e-invoice has been issued, they may be unable to pay. The order of the two steps needs to be explicit in your process.
The European picture
In Europe the same distinction is drawn through Peppol. Peppol works as the cross-border counterpart of national e-invoicing: a standard network and format (Peppol BIS, again UBL-based). EDIFACT continues to carry the commercial flow.
So the table looks similar there too: the legal layer rests on a UBL-based network, the operational layer on EDIFACT.
The point not to confuse
"We issue e-invoices, so we do not need EDI" is wrong. E-invoicing does not receive your orders, announce your shipments or record your goods receipts. If your trading partner asks for EDI, the reason is not to receive the invoice but to automate the process.
The reverse holds as well: using EDI does not remove your legal obligation.
Where to start
If you have samples of both formats, putting them side by side and comparing how the same invoice looks is instructive. Making the EDIFACT file readable is the first step towards seeing which field corresponds to which UBL element.