Electronic Data Interchange (EDI)
When one computer does not merely send a business document, but creates a message that another computer can understand, validate and act upon.
- Structured data
- System-to-system exchange
- Legal and evidentiary consequences
Begin with the distinction
Electronic does not always mean EDI
EDI is the direct interchange of structured business data between computer systems according to an agreed message standard, with little or no manual re-entry.
Invoice attached to an email
- A person opens the attachment.
- The person reads the invoice.
- Data is entered again into the receiving system.
Delivery is electronic; processing is still largely manual.
Standard purchase-order message
- The buyer’s system generates the order data.
- The data is translated into an agreed standard.
- The supplier’s system validates and imports it.
Both delivery and routine processing can occur system to system.
EDI does not merely remove paper. It removes repeated human handling by turning business information into a standardised message that software can interpret.
Exchange occurs between business applications, not only between users.
Orders, invoices, shipment details and other transactional information.
Fields, segments, codes and syntax carry a shared meaning.
The receiving application can validate and process the message automatically.
The business problem
Why commerce moved beyond paper, fax and email
Business transactions repeatedly carry the same data: party names, product codes, quantities, prices, taxes, shipment details and payment references. Re-entering that data at every organisational boundary creates delay, cost and error.
Paper trade
Post, courier and physical files
Slow movement, storage burden and repeated data entryElectronic document
Fax, email and PDF attachment
Faster delivery, but a person still reads and processes itIntegrated EDI
Structured messages between applications
Requires standards, mapping, secure integration and partner rulesLess re-keying
Data generated in one system is imported by another, reducing transcription mistakes.
Faster cycles
Orders, acknowledgements and invoices can move within minutes rather than days.
Process integration
Procurement, inventory, logistics, invoicing and payment can operate as one flow.
Traceability
Timestamps, acknowledgements and audit logs help establish what was sent, by whom and when.
System anatomy
EDI is an arrangement, not a single software program
An operational EDI environment combines business applications, message standards, translation tools, communication facilities, security controls and rules agreed between trading partners.
Defines equivalence
It decides that the internal field supplier_code, for example, corresponds to a particular element in the selected EDI standard.
Applies the map
It converts mapped internal data into a complete standard message and converts incoming messages back into the receiver’s internal format.
Value Added Network
A VAN is a managed intermediary that can receive, store, route and track EDI messages. It may provide electronic mailboxes, delivery reports, security controls and audit facilities.
The message journey
How an EDI transaction moves from one system to another
Partner arrangement
Agree on document types, standard, protocol, identifiers, security, acknowledgements, error handling and retention.
Transaction created
A user or automated process creates an order, invoice or other business transaction.
Data extracted and mapped
Relevant fields are linked to their equivalent elements in the chosen EDI standard.
Translated and validated
The translator builds the message and checks mandatory fields, syntax, codes and format.
Transmitted securely
The message travels directly or through a VAN using an agreed protocol and security controls.
Received and checked
The receiving gateway checks the sender, envelope, communication status, syntax and duplication.
Translated inward
The standard message is converted into the format required by the receiving application.
Business process updated
The receiver creates or updates the order, shipment, inventory, invoice or payment record.
Acknowledgement returned
A technical or functional response reports whether the message was received and structurally accepted.
Records preserved
Messages, timestamps, validation results, acknowledgements and audit logs are retained.
Receipt — the message reached the designated communication system.
Functional acknowledgement — the structure was processed or an error was reported.
Contractual acceptance — legal assent depends on the parties’ agreement, message type, law and circumstances.
A common electronic language
EDI standards make different systems interoperable
A standard specifies how messages are arranged into envelopes, headers, segments and data elements; which codes are permitted; and how each transaction type is identified. Trading partners still need an implementation guide for the exact version, fields, code lists and validation rules they will use.
| Standard | Primary use | Typical sectors | Distinctive point |
|---|---|---|---|
| ANSI X12 | Widely used in North America | Retail, transport, finance, healthcare, supply chains | Numeric transaction sets, such as 850 for purchase orders and 810 for invoices |
| UN/EDIFACT | International trade framework | Cross-border trade, transport, customs | Message names such as ORDERS, INVOIC and DESADV |
| TRADACOMS | Historically prominent in UK retail | Retail ordering and invoicing | Older sector-specific standard still present in legacy systems |
| GS1 EANCOM | UN/EDIFACT subset for GS1 use | Retail, logistics, consumer goods | Uses GS1 identification and coding practices |
| XML / ebXML | Internet-oriented structured messaging | Web-integrated and service-oriented exchange | Readable tags and flexible integration with modern platforms |
Successful exchange also requires agreement on the standard’s version, mandatory and optional fields, code lists, character sets, validation rules, communication method and exception handling.
The commercial sequence
Each EDI message represents a stage of the transaction
Purchase order
May communicate a buyer’s offer or an order under an existing framework contract.
Advance shipping notice
Provides packaging, carrier and expected-delivery information before the goods arrive.
Receiving advice
Confirms quantity and condition of goods and identifies discrepancies.
Inventory report
Communicates stock position, availability or inventory movement.
Transport messages
Carry bookings, consignment details, bills of lading and transport status.
Regulatory declarations
Submit structured customs, tax, import-export, health or compliance information.
Across sectors
EDI is used where structured transactions recur at scale
Retail and manufacturing
Orders, acknowledgements, invoices, inventory reports, production schedules and replenishment.
Transport and logistics
Bookings, manifests, shipment notices, delivery status, bills of lading and freight invoices.
Banking and finance
Payment instructions, remittance advice, account reports and trade-finance messages.
Healthcare and pharmaceuticals
Procurement, claims, product and batch data, traceability and regulatory reporting.
Government and customs
Tax filings, import-export declarations, licences, permits and public procurement.
A retailer’s system detects low stock, sends an EDI order, receives an acknowledgement and shipping notice, updates expected inventory, records the goods receipt, and later matches the invoice against the order and receipt.
The cyber-law layer
Every technical event may carry a different legal meaning
EDI is legally significant because rights and obligations are created, communicated and proved through electronic records. The system must therefore answer not only what happened technically, but also what the event means in law.
| EDI event | Possible legal significance | Question to ask |
|---|---|---|
| Purchase order | May be an offer or an order under a pre-existing framework contract. | What did the interchange agreement and prior relationship provide? |
| Communication receipt | May prove that transmission reached the designated system. | Does receipt alone have any agreed commercial effect? |
| Functional acknowledgement | Confirms structural processing or reports syntax errors. | Was the message merely processable, or was the proposal accepted? |
| Order response | May accept, reject, qualify or vary the order and may operate as a counter-offer. | Did the response mirror the order or introduce new terms? |
| Shipping notice | Supports proof of dispatch preparation, packing and expected delivery. | Does it prove actual dispatch, delivery, or only planned shipment? |
| Invoice / remittance | May evidence the amount claimed, performance and allocation of payment. | Can the message be attributed and linked to the underlying transaction? |
Who sent it?
Authentication and attribution must connect the message to an authorised person or system.
Could the system bind the party?
Automated transmission does not eliminate questions of authority, access and internal controls.
Was it altered?
Hashes, signatures, validation records and tamper-evident logs support reliability.
When was it dispatched and received?
System designation, timestamps and agreed rules may become crucial to formation and performance.
Who bears a mapping or system error?
The interchange agreement should allocate responsibility for failure, duplication and incorrect processing.
What survives for court?
The native message, metadata, acknowledgements and system records matter more than a bare printout.
Trust must be designed
Security controls create evidentiary reliability
EDI record
Authentication
Verify identity and authority through controlled accounts, certificates or electronic signatures.
Integrity
Use hashes, signatures, validation rules and tamper-evident logs.
Confidentiality
Encrypt sensitive information and restrict access by role.
Availability
Maintain backups, redundancy, disaster recovery and incident response.
Duplicate control
Use unique references, sequence checks and replay protection.
Auditability
Preserve messages, timestamps, mapping versions, validation reports and access logs.
Preserve the record in the form in which reliability can be tested
Under the Bharatiya Sakshya Adhiniyam, 2023, electronic or digital records are subject to the statutory method of proof. Admissibility does not by itself establish persuasive weight.
- Native EDI message
- Readable rendering
- Message envelope and metadata
- Acknowledgements and timestamps
- Validation and error reports
- Mapping and standard version
- Access and transmission logs
- Chain-of-custody records
A record may be admitted yet remain weak if its origin, integrity, completeness or the reliability of the generating system is not established.
See the difference at a glance
Paper, email and EDI do not create the same process
| Point | Paper system | Email / PDF | EDI |
|---|---|---|---|
| Form | Physical document | Human-readable electronic document | Structured electronic message |
| Processing | Manual | Human reads and often re-enters | Application processes automatically |
| Consistency | Depends on forms and staff | Format may vary | Agreed standard and implementation guide |
| Speed | Hours or days | Fast delivery, slower processing | Seconds or minutes for both transfer and routine processing |
| Error pattern | Transcription and duplicate entry | Re-entry error remains | Less manual error, but incorrect mapping can scale rapidly |
| Evidence | Document, signature and delivery proof | Email headers and attachment | Message, metadata, acknowledgements, validation and audit logs |
- Shorter business cycles
- Fewer transcription errors
- Better supply-chain visibility
- Automated validation and audit trails
- High-volume and cross-border scalability
- Implementation and integration cost
- Different standards and partner requirements
- Dependence on networks and providers
- Cybersecurity and confidentiality risk
- Unclear authority or liability unless agreed
EDI does not remove human responsibility. It moves responsibility from repetitive data entry to system design, security, exception handling and legal governance.
Place it within the larger subject
EDI is part of e-commerce, but it is not the whole of e-commerce
Online marketing · platforms · consumer ordering · payments · digital services
Structured, recurring exchanges between business or government systems
A customer may place an order through a web interface. The seller may then use EDI at the back end for procurement, fulfilment, logistics and invoicing.
Retrieval practice
Check whether the central distinctions are clear
What is EDI?
The direct exchange of structured business data between computer systems using an agreed message standard, with minimal human re-entry.
Why is an emailed PDF usually not EDI?
Because the attachment is primarily designed for a human to read; the receiving application may not be able to interpret and process its contents automatically.
What is the difference between a mapper and a translator?
The mapper defines correspondence between internal fields and standard elements. The translator applies that map to generate or interpret the complete EDI message.
Does a functional acknowledgement prove acceptance of an offer?
Not necessarily. It commonly establishes technical receipt or structural processing. Contractual acceptance depends on the agreement, message type, law and circumstances.
What should be preserved if an EDI dispute reaches court?
The native message, readable rendering, metadata, acknowledgements, timestamps, mapping/version information, validation records, access logs and chain of custody.
What are the main legal issues?
Contract formation, attribution, authority, dispatch and receipt, integrity, confidentiality, retention, evidence and allocation of liability.
EDI is a standardised method of carrying legally significant business data directly from one application to another; its reliability depends on interoperable standards, secure systems, clear partner rules and preservation of trustworthy electronic records.
Read the page. Keep the complete notes.
The downloadable PDF contains the full lecture discussion, comparison tables, standards, legal meaning of EDI events and quick revision material.