EDI system — how a modern electronic data interchange system works
In short: An EDI system is the combined software, protocols and processes that let two organizations exchange structured business documents automatically. This guide explains the components of a modern EDI system (translator, communications, mapping, monitoring), what it costs, and how it compares to legacy on-premise systems.
Key capabilities
- Translator / mapper: Converts your internal format (CSV, JSON, ERP export) to and from EDIFACT, X12, UBL, XML per partner spec.
- Communications layer: AS2, OFTP2, SFTP, PEPPOL, VAN. Handles signing, encryption, MDN receipts and retries.
- Partner directory: Trading partner profiles: GLN/GTIN, protocol endpoints, certificates, message specs, contact matrix.
- Monitoring & alerting: Real-time dashboard on message flow, exceptions, MDN pending, error queues, SLA tracking.
- Archive & audit: Encrypted, tamper-evident 10-year archive with search and export for tax and reconciliation.
- ERP interface: REST API, native ERP connectors, or file-drop into ERP staging tables.
How an EDI system processes a purchase order end-to-end
A retailer's ERP emits a purchase order. The retailer's EDI system converts it to EDIFACT ORDERS and transmits it over AS2 to the supplier's endpoint. The supplier's EDI system receives the message, validates the envelope and signature, sends back an MDN receipt, then translates the ORDERS to the supplier's internal format and drops it into the ERP.
The supplier's ERP generates a confirmation (ORDRSP), then a dispatch advice (DESADV) when goods ship, then an invoice (INVOIC). Each document is translated, signed, transmitted and archived by the EDI system. Every state change (sent, received, MDN OK, rejected) is visible in the monitoring dashboard.
Frequently asked questions
What is an EDI system?
An EDI system is the combined software, network protocols and business processes that let two organizations exchange business documents (orders, invoices, shipment notices) in structured, machine-readable format directly between their IT systems, without email, PDF or manual entry.
What are the main components of an EDI system?
A modern EDI system has five components: a translator/mapper (converts formats), a communications layer (transport protocols like AS2/OFTP2/SFTP), a trading partner directory (specs, certificates, endpoints), a monitoring and alerting layer, and an archive with audit trail. Cloud EDI bundles all five in a single SaaS product.
How much does an EDI system cost?
Cloud EDI systems (SaaS) start at €24/month for low volume. Managed EDI: €200-500/month. On-premise EDI systems (IBM Sterling, OpenText Trading Grid, Cleo Clarify) require €15,000-100,000 upfront plus €5,000-20,000/year in maintenance and IT ops.
Cloud EDI system or on-premise?
Cloud is the right default in 2026 for anyone under ~10,000 documents/month and under ~50 trading partners: 10× faster to deploy, 10-20× lower cost, no infrastructure to maintain. On-premise remains justified for very high volumes, extreme customization, or industries with strict data residency requirements beyond EU hosting.
Which EDI systems support global compliance standards?
A modern EDI system should support EDIFACT (Europe), ANSI X12 (US), UBL 2.1 (PEPPOL and EU e-invoicing), ODETTE (automotive), plus tax-specific formats like ANAF e-Invoice in Romania. EDIconnect supports all of these natively.