EDI: electronic data interchange explained for SMEs
EDI means that orders and invoices go straight from system to system without retyping. Here is when it makes sense, which standards you'll meet, and what drives the price.
Table of contents
In short: EDI stands for Electronic Data Interchange. It is a method of exchanging business documents such as orders and invoices in a structured format directly between companies' IT systems, so nobody has to key them in again. For most smaller businesses, it becomes relevant when a large customer requires it, or when invoices to the public sector have to be sent electronically.
If you've ended up here, you may have received a letter from a retail chain or a wholesaler saying that future orders will come via EDI, or you may be tired of keying in the same order lines from PDFs. Here you get a down-to-earth explanation of what EDI is, which standards are used in Denmark, and how to get started without making it bigger than necessary.
What is EDI, and what does it do?
With EDI, two companies' systems send documents directly to each other in an agreed format. When a customer sends an order, it lands as an order in your order or ERP system, and when you invoice, the invoice lands as an invoice in the customer's accounting system. GS1 describes the purpose as the companies speaking the same digital language in the supply chain.
Typical documents that are exchanged:
- Orders and order confirmations: what has been ordered, at what price and for what delivery.
- Despatch advice notes: what has been sent, and when.
- Invoices and credit notes: in a format the recipient's system can read automatically.
- Master data on products and locations, so both parties are talking about the same thing.
For it to work, both parties must agree on three things: the format (how the document is structured), the address (who it is going to) and the transport (how it gets there). The address is often a GLN (Global Location Number), a 13-digit number from GS1 that works as a digital address for e-invoices and EDI. The transport can go through the Danish Nemhandel infrastructure or the international Peppol network, where you send and receive through an approved Peppol service provider following the so-called four-corner model. The buyer and the supplier therefore don't need to use the same provider.
The gain, according to the Danish Business Authority, is that the document is loaded automatically at the recipient's end. That removes scanning and manual keying, and with it both time and the risk of errors.
A PDF attached to an email is not EDI. The Danish Business Authority states directly that image files and PDF documents are not electronic invoices, because the recipient can't process them automatically.
When do you need EDI?
Signs that the time has come:
- A large customer requires it as a condition of trading with you.
- You invoice the public sector. Nemhandel has been mandatory by law for e-invoices to Danish public authorities since 2005.
- Many order lines are keyed in manually from emails and PDFs, and errors lead to wrong deliveries or credit notes.
- You trade in other EU countries. Under the EU's VAT rules from 2025 (ViDA), member states must require e-invoicing for trade between businesses in different countries by 1 July 2030 at the latest.
Signs that it's too early: you have few orders a week, no customers are asking, and your invoicing is done from a registered accounting system. The Danish Business Authority states that all registered accounting systems are ready for e-invoicing, and that businesses that use them will be able to send and receive e-invoices from spring 2027 without doing anything themselves.
The standards you'll meet
| Standard | What it is | Where you typically meet it |
|---|---|---|
| OIOUBL | The Danish standard for e-invoices | Invoicing the public sector and between businesses via Nemhandel |
| Peppol BIS | The European standard in the Peppol network, for example for e-invoices and e-orders | Cross-border trade and trade with businesses that use Peppol |
| GS1 EANCOM | GS1's version of the UN standard UN/EDIFACT | Orders and invoices in the supply chain |
| GS1 XML | GS1's XML-based format for the same kind of data | Supply chains where the parties prefer XML |
| PDF by email | An image of a document | Is not EDI and not an e-invoice |
What does it cost?
The price depends more on your set-up than on the standard itself. The most important cost drivers are:
- Access to the network. A subscription or a price per document at an EDI or Peppol provider, or a module in your existing system.
- Connection to your system. The fields in the EDI message must match the fields in your ERP or order system. The more special the system, the more work.
- Start-up per trading partner. Each customer often has its own variant and its own test process.
- Master data. Item numbers, location numbers and prices must be right, otherwise the messages are rejected.
- Operations and exceptions. Somebody has to handle the messages that fail and update the set-up when a partner changes something.
- Training of those who will handle the exceptions.
Buy a standard system or build your own?
Most often, standard is the right choice. An e-invoice module in the accounting system, or an EDI provider that handles formats and transport, covers most needs. Never build your own version of a standard.
Ask a provider about five things: which formats and networks they support, whether the price is per document or a subscription, who is responsible for testing with your trading partners, how rejected messages are displayed, and how data gets into your own system.
A custom integration layer makes sense when you have an older system without an EDI module, when you have many trading partners each with their own variant, or when some of your customers use EDI while the rest still send orders by email. Then the task is to get all orders to land in the same way in your system, however they come in. Read more about this type of task under enterprise integration.
Where does an AI layer fit in?
EDI solves the problem for the customers that use EDI. An AI layer can take care of the rest and of the exceptions:
- Read orders from email and PDF from customers without EDI and turn them into structured orders that are validated against the product catalogue and prices before they land in the system.
- Explain rejected messages in plain language: which field, which order, and what needs to be corrected.
- Compare order, order confirmation and invoice and flag differences in price or quantity.
- Follow up on missing replies, such as an order without an order confirmation or a delivery without an invoice, and notify the right person.
- Help map a new partner's specification against your fields, which a developer then tests.
What AI can't do: replace the standard or the transport itself, guarantee that a connection is correct without testing, or take responsibility for the content of an invoice. See also how CRM and ERP work together, if the order starts in sales.
How to go about it
- Gather the requirements from your trading partners: format, transport and which documents.
- Check what your current system can already do, especially e-invoicing in the accounting system.
- Clean up master data: item numbers, prices and location numbers.
- Choose your access to the network: a module in the system or a provider.
- Start with one partner and one document, typically the order or the invoice, and test thoroughly.
- Agree who handles exceptions before you expand to more partners.
If you have a mix of EDI, email and PDF orders, Agent360 can help you choose or build the integration layer, write to us here.
Sources
- GS1 Denmark, GS1 glossary (EDI, GLN, GS1 XML, EANCOM): https://www.gs1.dk/om-gs1/gs1-ordbog (accessed 6 October 2026)
- GS1, GS1 EANCOM: https://www.gs1.org/standards/eancom (accessed 6 October 2026)
- The Danish Business Authority, Nemhandel: common digital infrastructure: https://erhvervsstyrelsen.dk/nemhandel-faelles-digital-infrastruktur (accessed 6 October 2026)
- The Danish Business Authority, E-invoicing (updated 5 October 2026): https://erhvervsstyrelsen.dk/e-fakturering (accessed 6 October 2026)
- The Danish Business Authority, Guidance on the Danish Bookkeeping Act, section 2.15 on e-invoices: https://erhvervsstyrelsen.dk/vejledning-bogfoeringsloven (accessed 6 October 2026)
- OpenPeppol, About Peppol: https://peppol.org/about/ (accessed 6 October 2026)
Frequently asked questions
What is a GLN number?
A GLN (Global Location Number) is a 13-digit number from GS1 that works as a digital address for e-invoices and EDI. It tells you who the document is going to, and together with the format and the transport it is one of the three things both parties must agree on.
Must invoices to the public sector be sent electronically?
Yes. Nemhandel has been mandatory by law for e-invoices to Danish public authorities since 2005, and the Danish standard for e-invoices is called OIOUBL. A PDF attached to an email doesn't count as an electronic invoice, because the recipient can't process it automatically.
When does e-invoicing become a requirement when trading with other EU countries?
By 1 July 2030 at the latest. Under the EU's VAT rules from 2025, known as ViDA, member states must by then require e-invoicing for trade between businesses in different countries. If you trade in other EU countries, that is a sign it's time to look at EDI.
Tags: EDI, e-invoice, Peppol, OIOUBL, integration
Contents
Which of your manual steps could disappear?
We map where data is moved by hand between your systems, and what can realistically be automated.
Book a mapping sessionRelated articles

MFA: multi-factor authentication for your business – how to get started
Learn how to implement MFA securely in your organisation. Guidance on methods, costs and best practices for protecting company data.

English-language invoices: requirements for invoices to foreign customers
Invoice in English to foreign customers legally. Danish regulations, EU and international VAT rules, zero-rating, reverse charge, and automation.

Drawing programme (CAD): 2D, 3D, licences and file formats
What is CAD? Learn about 2D and 3D design programmes, file formats, licensing models, and how to choose the right tool for technical drawings.