EDI compliance — becoming EDI-capable for retailers and regulators
In short: EDI compliance means meeting a trading partner's specification for structured document exchange (EDIFACT/X12 messages, transport protocol, GS1 identifiers, acknowledgments) and — for e-invoicing — the local tax authority's format (ANAF e-Factura, PEPPOL). This guide covers how to become EDI capable and pass compliance testing.
Key capabilities
- Retailer spec review: We analyze the partner's EDI spec (message versions, mandatory segments, business rules) and build a compliant mapping.
- Certificate & GLN setup: AS2/OFTP2 certificates provisioned; GLN and GTIN registered with GS1; trading partner directory populated.
- End-to-end testing: Full test cycle with the retailer's test environment: ORDERS in, ORDRSP + DESADV + INVOIC out, all validated.
- Acknowledgment (997/CONTRL): Automated functional acknowledgments per spec — a hard requirement for compliance in most retail programs.
- ANAF e-Factura compliance: UBL 2.1 conversion, ANAF signature, error-free submission and audit trail.
- Ongoing spec updates: When the retailer or regulator publishes a new spec version, we upgrade transparently before the deadline.
The two categories of EDI compliance in 2026
The first category is commercial compliance — meeting a retailer's EDI spec because it's a contract requirement. Every major EU retailer publishes a supplier EDI guide (Kaufland, Carrefour, Lidl, Mega Image, Metro etc.) and refuses to onboard non-compliant suppliers. Being EDI capable is a prerequisite, not a bonus.
The second category is regulatory compliance — meeting the tax authority's format for electronic invoicing. In Romania, ANAF e-Factura (UBL 2.1) is mandatory for B2B invoicing since 2024. In the EU broadly, PEPPOL BIS Billing 3.0 is the standard. A modern EDI platform handles both categories on one contract.
Frequently asked questions
What is EDI compliance?
EDI compliance means meeting the specification a trading partner or regulator requires for electronic document exchange. This includes the message format and version (e.g. EDIFACT D96A ORDERS), the transport protocol (AS2, OFTP2, SFTP, PEPPOL), the acknowledgments required (CONTRL, MDN, 997), and the business rules (mandatory fields, GS1 identifiers, cross-references).
What does EDI capable mean?
'EDI capable' is a supplier status: it means the supplier can send and receive the specific EDI documents a customer requires, in the customer's specific format, over the customer's required protocol, and pass the customer's compliance test. Being 'EDI capable' is usually a contract prerequisite for supplying large retailers.
How to become EDI capable?
Contract an EDI provider that already has a template for the retailer you need to serve. Steps: (1) provide your ERP export format, (2) provide your GLN, (3) provider does the mapping and configuration, (4) test cycle with retailer's UAT environment, (5) go-live. Typical timeline: 5-10 business days with an experienced provider.
How do EDI providers ensure compliance with industry standards?
By maintaining a library of pre-built templates for each partner (updated when specs change), running automated compliance validation on every outbound message before transmission, and having a certified operations team that handles exceptions before they become partner-facing failures.
How does EDI compliance testing work?
The retailer provides a test (UAT) environment mirroring production. Your EDI provider sends test messages (ORDRSP, DESADV, INVOIC), the retailer validates format, business rules and acknowledgments. Once all test scenarios pass (typically 5-15 scenarios), the retailer signs off and moves you to production.