EDI vs Romanian e-Invoice (e-Factura) — real differences, when you need each and how they work together
Clear guide for Romanian companies supplying modern retail who also have the e-Factura ANAF obligation: what EDI is, what RO_CIUS e-Invoice is, why they don't replace each other, and how a single platform (EDIconnect) generates both from the same ERP invoice.
The most common 2024-2026 confusion: "we have e-Factura, so we don't need EDI anymore"
Since RO_CIUS e-Factura became mandatory in Romania (B2B from January 1, 2024, plus B2C extension in 2025), many suppliers think EDI with retailers became redundant. The logic is tempting: if I'm already sending the invoice through ANAF's SPV, why also send it via EDI? Short answer: because they solve different problems, for different recipients, at different stages of the commercial flow.
e-Factura ANAF is a fiscal system. EDI is a commercial system. e-Factura confirms ANAF received the invoice — a legal requirement. EDI confirms the retailer received the order, confirmed receipt, commercially accepted the invoice and will pay it — an operational requirement.
Good news: you don't have to choose. EDIconnect generates EDIFACT INVOIC for the retailer and UBL 2.1 RO_CIUS for ANAF in parallel, from the same ERP invoice. One click, two destinations, two obligations satisfied at once.
The 6 fundamental differences between EDI and Romanian e-Invoice
Before deciding "do we need one or both", look at what each actually does.
- Purpose — e-Factura is fiscal (VAT validation, fiscal transparency). EDI is commercial (the invoice being accepted as a payable document in the retailer's system).
- Format — e-Factura is UBL 2.1 RO_CIUS (XML, European EN 16931 syntax). EDI with major retailers is EDIFACT D96A (global B2B standard). Completely different formats; they don't substitute.
- Recipients — e-Factura: ANAF + the client via SPV. EDI: the retailer's system (Carrefour, Auchan, Lidl etc.), who doesn't read SPV — they use their own commercial processing flow.
- Message types — e-Factura covers only invoices (and certain notes). EDI covers the full flow: orders (ORDERS), shipping notice (DESADV), invoice (INVOIC), receipt confirmation (RECADV), catalog (PRICAT) etc.
- Commercial acceptance — e-Factura validates the invoice fiscally, but does NOT tell you if the retailer accepted it for payment. EDI receives RECADV / APERAK with commercial acceptance or rejection.
- Direction — e-Factura is one-way (only invoices from you to ANAF). EDI is bidirectional: retailer sends you orders, you send notices and invoices, retailer confirms receipts. Missing EDI = you keep typing orders manually.
EDI vs RO_CIUS e-Invoice — full comparison table
Common source: same invoice generated in your ERP. Two destinations, two formats, two obligations.
| Feature | e-Factura ANAF (RO_CIUS) | EDI with retailers (EDIFACT) |
|---|
| Requirement type | Legal (fiscal) | Contractual (commercial) |
| Message format | UBL 2.1 / RO_CIUS XML | EDIFACT D96A (INVOIC, ORDERS, DESADV...) |
| Transport channel | ANAF SPV (REST API) | AS2 / OFTP2 / SFTP / X.400 to the retailer |
| Documents covered | Invoices (and credit / debit notes) | Orders, dispatch notices, invoices, receipt confirmations, catalogs |
| Direction | One-way (supplier → ANAF / client) | Bidirectional (retailer ↔ supplier) |
| Commercial acceptance | No (fiscal validation only) | Yes (RECADV / APERAK) |
| Eliminates manual order entry? | No (e-Factura doesn't carry orders) | Yes (ORDERS flows straight into ERP) |
| RO major retailers requirement | Doesn't solve (they want EDIFACT INVOIC) | Yes (Carrefour, Auchan, Kaufland, Lidl, Mega Image, Metro require EDI) |
| Penalty if missing | ANAF fine | Missed orders / non-compliance penalties / contract loss |
| Who validates | ANAF (fiscal system) | Retailer (commercial system) |
How they work together in a real EDIconnect flow
Same invoice generated in ERP, two destinations in parallel, zero manual duplication.
- Carrefour order arrives via EDI — Retailer sends ORDERS in EDIFACT. EDIconnect receives, validates, maps and injects it into your ERP as a sales document.
- Your team processes the order in ERP — Normal workflow: stock allocation, picking, shipping. No internal process change.
- DESADV leaves to the retailer — On shipping, EDIconnect auto-generates the EDIFACT dispatch advice with pallets and SSCC. The retailer uses it for fast receipt.
- Invoice is generated in ERP — You generate the invoice as usual, in your ERP. One fiscal document.
- EDIconnect transmits in PARALLEL — Same invoice leaves simultaneously: EDIFACT INVOIC to Carrefour's system + UBL 2.1 RO_CIUS to ANAF SPV. Zero manual duplication.
- Confirmations come back — Retailer confirms acceptance via APERAK / RECADV. ANAF confirms receipt on SPV. EDIconnect correlates them in the same dashboard.
Common 2024-2026 mistakes — and how to avoid them
- Common mistake: "We implemented e-Factura, so we're fine with Carrefour and Auchan." How to avoid it: No. Carrefour, Auchan, Kaufland, Lidl, Mega Image, Metro do NOT read ANAF's SPV for commercial receipt. They want EDIFACT INVOIC straight into their system.
- Common mistake: "We generate e-Factura from ERP, then manually upload to the retailer's portal." How to avoid it: Useless duplication. EDIconnect generates both formats from the same ERP invoice, automatically, in parallel.
- Common mistake: "We don't want another platform, e-Factura is enough." How to avoid it: EDIconnect IS the platform that does both. You're not adding two systems; you consolidate everything into one.
- Common mistake: "We pay a separate software for e-Factura ANAF." How to avoid it: With EDIconnect you get e-Factura, retail EDI, catalog (PRICAT), dispatch advice (DESADV) — in a single SaaS subscription from €12/user/month.
- Common mistake: "We confuse ANAF rejection with retailer rejection." How to avoid it: Separate dashboard per channel: e-Factura ANAF (SPV status) vs retailer INVOIC (APERAK status). See exactly where the problem appeared.
- Common mistake: "We need separate retransmissions for each channel." How to avoid it: EDIconnect replays messages after correction on both channels, automatically or manually, from the same place.
EDIconnect — the only platform that does both
Built for the Romanian market. e-Factura RO_CIUS + EDIFACT EDI with major retailers, from the same ERP invoice.
- EDIconnect since 2014 — We've operated EDI with Romanian retailers since 2014. e-Factura RO_CIUS was added in 2022 on the same infrastructure, with ANAF UAT alongside.
- Legal + commercial synthesis — Same team that understands EDIFACT D96A also understands RO_CIUS UBL 2.1. No juggling between two vendors.
- Universal ERP connectors — SAP, Oracle, Dynamics, Charisma, Senior, WinMentor, NetSuite, Odoo. Same invoice, two formats, one flow.
- Local RO support — Romanian-speaking team, understanding of ANAF jurisprudence, retailer specifics and legislative changes in real time.
Details for those who want to dig deeper
What exactly is UBL 2.1 / RO_CIUS
UBL 2.1 is an XML standard for business documents developed by OASIS. RO_CIUS (Romanian Core Invoice Usage Specification) is the Romanian profile based on the European EN 16931 standard. Contains additional mandatory fields for ANAF (CAEN code, VAT-on-receipt indicator, etc.).
What exactly is EDIFACT D96A
EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) is the UN standard for B2B exchanges. D96A is the message directory published in 1996, semester A — the most widespread in European retail including Carrefour, Auchan, Kaufland.
Can I use PEPPOL instead of RO_CIUS?
PEPPOL is a UBL-based transport network widely used in the EU. In Romania, the mandatory fiscal flow goes through ANAF SPV with RO_CIUS. EDIconnect supports both if you have European partners who prefer PEPPOL.
What happens if ANAF rejects my UBL?
EDIconnect catches the rejection, alerts you with the exact reason (e.g. missing CAEN code, invalid GLN, wrong total), allows correction in ERP and retransmits. Same logic applies to APERAK from retailer.
Message volume an EDIconnect-class platform handles
Hundreds of thousands of messages per month at platform level. A single mid-sized supplier typically sends 50-500 invoices/month to retail + ANAF, plus dozens of orders/day received via EDI.
How to interpret APERAK
APERAK (Application Error and Acknowledgement) is the message where the retailer says: "I received it, syntactically validated" or "rejected for reason X". Different validation level from ANAF e-Factura — checks compliance with retailer commercial requirements.
FAQ
- Can I drop EDI if I have e-Factura?
- Not if you supply major retailers (Carrefour, Auchan, Kaufland, Lidl, Mega Image, Metro). They do NOT receive invoices from ANAF SPV — they want EDIFACT INVOIC directly. e-Factura solves your fiscal obligation; it does NOT solve commercial receipt.
- Can I drop e-Factura if I have EDI?
- No. e-Factura is a legal obligation in Romania starting 2024. Regardless of commercial system, the invoice must reach ANAF SPV in UBL 2.1 RO_CIUS format.
- Are EDI and e-Factura competing?
- No — they are complementary. EDI solves the commercial flow (orders, notices, invoices, receipts) with the retailer. e-Factura solves the fiscal flow with the state. Same invoice goes in two formats to two recipients.
- Can I generate both from the same ERP invoice?
- Yes. EDIconnect does exactly that: one ERP invoice → EDIFACT INVOIC to retailer + UBL 2.1 RO_CIUS to ANAF, in parallel, no manual duplication.
- What's the difference between UBL and EDIFACT?
- Both are B2B exchange formats. UBL is XML (modern, easy to read, EU-chosen). EDIFACT is positional text (older, more compact, universal standard in global retail). Coexist because retailers use EDIFACT and the EU chose UBL.
- How much does it cost to run both?
- With EDIconnect, both are included in the same SaaS subscription from €12/user/month. You don't pay two platforms.
- How do I handle rejections on both channels?
- EDIconnect dashboard shows separately: ANAF SPV status (accepted / rejected with reason) and retailer status (APERAK / RECADV). Correct in ERP, retransmit from EDIconnect.
- Are there Romanian retailers that only want e-Factura, no EDI?
- A few smaller chains or independent stores accept only e-Factura. Major chains (Carrefour, Auchan, Kaufland, Lidl, Mega Image, Metro, Profi, Dedeman, Hornbach, Leroy Merlin) require EDI for full commercial integration.
- What is PEPPOL and do I need it?
- PEPPOL is a European document transport network. In Romania, fiscal obligation is via ANAF SPV (not PEPPOL). If you have European partners who prefer PEPPOL, EDIconnect supports it as an additional option.
- How many messages can I send simultaneously?
- Modern EDI platforms handle hundreds of thousands of messages per month without issues. No practical ceiling for a typical supplier.
Continue with the dedicated retailer pages
EDIconnect handles both e-Factura ANAF and EDI with every major Romanian retailer.
Want to solve e-Factura + EDI from a single system?
2-minute demo: see an invoice leave simultaneously as EDIFACT to Carrefour and as UBL RO_CIUS to ANAF, without touching it twice.