Service · Web development

Custom EDI integration development for your trading partners.

EDI (Electronic Data Interchange) is how businesses exchange orders, invoices, deliveries and stock updates with each other in a structured way. We build custom EDI integrations between your ERP and your retailers, suppliers or logistics partners (UN/EDIFACT, UBL, Peppol, ANSI X12 or XML), all from a single integration layer.

EDIFACT & UBLPeppol Access PointAS2 / SFTP / OFTP2ERP mapping

An EDI integration isn't a file drop, it's a trading protocol.

EDI has existed since the 1980s and is still the way large retailers, automotive OEMs and logistics companies communicate with their suppliers. If you supply Albert Heijn, Jumbo, IKEA or a German car manufacturer, you don't get a choice: you connect via EDI or you don't get invoiced. At the same time, "EDI" isn't one single thing. It's a collection of standards (UN/EDIFACT, ANSI X12, UBL, VDA, TRADACOMS, XML variants such as cXML), a collection of transport protocols (AS2, OFTP2, SFTP, Peppol) and a collection of business rules per trading partner. For one company, an "EDI integration" means one XML file a day via SFTP; for another, it's a real-time AS2 feed of thousands of ORDERS messages with functional acknowledgements sent back.

Since 2015 we've been building custom integrations between ERP systems and the outside world. For EDI, that means a mapping engine between your own data model and the messages your trading partners require, a transport layer that handles both classic AS2 and modern Peppol, and archiving that meets the ten-year statutory retention requirement for tax records. We don't replace large EDI providers such as Babelway, Comarch or OpenText at enterprise volume, but we do build smaller stacks, add-ons to existing providers, and specific integrations that standard products simply don't include.

Our role doesn't end at "the message gets through". We think along with you about what happens when a supplier adds a field tomorrow, how rejected messages avoid getting stuck in a queue, and how your finance or operations team can see discrepancies without having to read raw EDIFACT. A well-built EDI integration is largely about catching exceptions: the standard case is done in a single sprint, and the deviations are where the real work lies.

The standards we work with most often are: UN/EDIFACT for classic retail and logistics; UBL for modern e-invoicing via Peppol; ANSI X12 for US trading partners in retail and healthcare; VDA for German automotive; cXML and xCBL for B2B marketplaces; HL7 for healthcare communication; SBR for Dutch tax reporting; and XBRL/EBR for energy reporting. We don't pick a standard in advance. We choose what your trading partners require and build the stack around it.

Three flavours of EDI integration.

Which option suits you depends on your trading partners, your invoice and order volumes, and how much control you want to keep yourself. We'll advise on the best fit in the first conversation.

Compact project · fixed sprint budget

One-to-one EDI integration with a single trading partner

You need to deliver to one large retailer or OEM and have received their EDI specification. We build the direct integration from your ERP to their gateway: UN/EDIFACT ORDERS / DESADV / INVOIC, or the XML variant they prescribe. This includes mapping, AS2 or SFTP transport and the first rounds of test messages in their acceptance environment.

EDIFACTAS2 / SFTPAcknowledgmentsTest rounds
Mid-sized project · fixed sprint budget

Mapping engine for multiple trading partners

You connect to five, ten or more customers or suppliers, and each has slightly different segments, codes or business rules. We build a central mapping engine: one source format from your ERP, multiple recipient mappings. Adding a new partner then becomes a configuration change rather than a new project. This includes routing, monitoring and a dashboard for your operations team.

Mapping engineRoutingPartner onboardingMonitoring
Larger project · fixed sprint budget

Your own Peppol access point or AS2 server

You want to keep control of your e-invoicing flow to the government (Peppol BIS, SBR), or you run an AS2 server for your automotive flow. We build a production stack with your own access point or AS2 server, qualified signatures, ten-year archiving and a self-service portal for your trading partners. A true enterprise-grade EDI layer, in your own cloud.

Peppol access pointAS2 serverE-archivingPartner portal

What you get at the end.

A production-ready EDI integration, plus everything your team needs to manage it yourselves and extend it to new trading partners.

  • The integration layer itselfProduction and acceptance environments, connected to both your ERP (SAP, Exact, AFAS, Dynamics) and your trading partners' gateways or a Peppol access point.
  • Mapping tables per message typeDocumented mapping between your ERP fields and the relevant EDI messages (ORDERS, DESADV, INVOIC, ORDRSP, RECADV), including fallback rules for missing data.
  • Transport and acknowledgmentsImplementation of AS2, SFTP, OFTP2 or Peppol, with CONTRL and functional acknowledgment flows so you know when a message has actually arrived.
  • Validation and business rulesXSD or EDIFACT schema validation, plus the partner-specific business rules you've provided, so rejections are caught before sending.
  • Compliant e-archivingEncrypted, immutable storage of all inbound and outbound EDI messages for the ten-year statutory retention period, suitable for international invoices and audits.
  • Operations dashboardVisibility for your finance and logistics teams into sent, accepted, rejected and pending messages, with one-click resending for failed transmissions.
  • Codebase + runbookFull source code, build instructions and an incident runbook, so your IT team can handle escalations itself without depending on an external supplier.
  • Support contract (optional)Monitoring, certificate rotation, security patches and ongoing development for a fixed monthly fee, useful when Peppol or a retailer releases a new schema version.

When an EDI integration is the right choice.

Four situations in which we support organisations. If you recognise one of them, we'd be glad to talk through the scope with you.

Retail / wholesale

Supplier to major retailers

You supply Albert Heijn, Jumbo, Hema, Bol or a large international retailer. They require EDI orders (ORDERS), delivery note confirmations (DESADV) and e-invoices (INVOIC or UBL) via their prescribed gateway. Without a working integration, payments stall or orders don't get through.

Automotive / VDA

Tier supplier in the automotive chain

You supply parts or just-in-time deliveries to a German or international OEM. VDA messages via OFTP2, with tight timing for delivery confirmations and stock positions, are the norm. One missing DELJIT confirmation and the production line feels it.

Government & B2G

Peppol requirement for e-invoices

You invoice government bodies, hospitals or educational institutions that require UBL via Peppol BIS. Or you fall under the forthcoming EU-wide e-invoicing mandate and want to run your own AccessPoint instead of paying an external provider per invoice.

Logistics & customs

Transport orders and customs declarations

You coordinate multimodal transport with IFTMIN consignment notes, customs declarations (Customs / NCTS) and stock notifications to clients. The combination of EDI with API gateways and track-and-trace systems is where we have built the most.

Healthcare

ZorgMail, Vecozo and claims flows

Healthcare providers, pharmacies and insurers exchange claim files, return messages and authorisations via HL7 and EDIFACT variants. We integrate practice software or your own platform with ZorgMail, Vecozo and Vecozo-like hubs, with the right authentication and compliance requirements.

E-commerce to wholesale

Bol, Amazon or marketplace flow to your WMS

You sell via Bol, Amazon or another marketplace, but your stock and invoicing run on your own WMS or ERP. An EDI or cXML integration between the marketplace and your own system prevents duplicate administration, missed orders and manual re-keying.

How an EDI project works.

1

Introduction & partner scoping

A conversation in which we establish which trading partners need to be connected, which messages they require (ORDERS, DESADV, INVOIC, ORDRSP, RECADV, or others) and which transport they prescribe. We ask for their message implementation guides and review them together.

2

Source data from your ERP

We compare your outbound data (order confirmations, deliveries, invoices) with what the partner expects. Fields that don't match get mapping rules, lookup tables or fixed fallbacks. The result: a mapping document your team can maintain itself when your ERP changes.

3

Build in sprints, sandbox first

A working build every sprint. We start in the partner's acceptance environment, testing the mapping, transport and acknowledgments there, and work through the rejected scenarios together before going to production. Getting a retailer on board early for a test batch saves a lot of pain on go-live day.

4

Validation and exception flow

Every message goes through pre-validation against the schema and the business rules. Rejected messages get a clean retry flow with an audit log; messages that fail structurally are escalated to your operations team rather than a dead queue.

5

Setting up go-live & archiving

A phased transition from acceptance to production, archiving set up for the statutory retention period, and knowledge transfer to your IT and operations teams. Dashboards are ready for finance, supply chain and any audits.

6

Management & new partners

The EDI landscape keeps moving: retailers release new schema versions, Peppol introduces new BIS profiles, automotive OEMs switch portals. We monitor those changes and extend the integration as you onboard more partners. For partners you onboard yourself, we provide a self-service portal with a test environment, so a new supplier or customer can send a first batch of messages themselves before production goes live.

Frequently asked questions.

What clients usually want to know before we start.

Which EDI standard do we need?
That depends on your trading partners and your sector. Retail and wholesale mostly run on UN/EDIFACT (ORDERS, DESADV, INVOIC) or UBL; automotive on VDA with OFTP2; government and B2B e-invoicing on UBL via Peppol BIS; US retail and healthcare on ANSI X12. With your first trading partner, we look at which message implementation guide you have received and use that to determine which standards your stack needs to support.
What is the difference between EDI and an API integration?
EDI is a standardised batch protocol for trade documents, with fixed message formats and formal acknowledgments. APIs are more flexible but company-specific and rarely standardised across suppliers. In practice, the two coexist: a retailer requires EDI for INVOIC while also offering a REST API for stock positions. We often build an integration layer that handles both and routes per partner.
What is UBL and how does it fit into Peppol?
UBL (Universal Business Language) is an open XML standard for trade documents: orders, invoices, deliveries. Peppol BIS is an EU-wide set of agreements built on top of UBL that prescribes which fields are mandatory and how they are exchanged between Access Points. For e-invoices to governments within the EU, Peppol BIS has effectively become the standard, and it is increasingly mandated for B2B too. Our page on Exact Online integration covers the accounting side of this flow.
Should we set up our own Peppol Access Point or hire a provider?
That depends on your invoice volume, your need for control and your sensitivity to per-invoice costs. For lower volumes, an external Access Point (Storecove, Tradeshift, Pagero) works well and is cheaper. For higher volumes, international flows or a requirement for maximum control, we build your own Access Point in your cloud. In the first conversation, we walk through both scenarios so the choice is made on substance, not ideology.
What about e-archiving for international invoices?
Tax legislation requires invoice data to be retained for many years: ten years in the Netherlands and most EU countries. For international invoices, the strictest requirement of the countries involved applies. We set up encrypted storage with immutable (write-once) logging and an audit trail showing who viewed, exported or resent which invoice, and when. Access runs through your IdP, so it falls within your existing security policy.
Do you work with our IT department and existing EDI provider?
Almost always. Many clients already run partly on Babelway, Comarch, Cleo or OpenText/GXS. We don't replace those enterprise stacks for high volumes, but we build add-ons or the specific integrations missing from standard products. We connect to your existing provider via webhooks or a lightweight broker of our own, and hand over knowledge in the final sprint.
Can you also help migrate from EDIFACT to modern APIs?
Yes. More and more supply chains are setting up parallel APIs alongside their EDIFACT flows, with UBL or REST/JSON as the new norm. We build a translation layer that leaves your existing ERP output unchanged, but can output classic EDIFACT (for partners who don't switch over) as well as modern APIs or UBL. That way you migrate at your own pace without forcing all your partners to move at once.
Which retail-specific flows are most common?
For Dutch retail this is usually the ORDERS-DESADV-INVOIC chain via EDIFACT: the retailer places an order, the supplier confirms with ORDRSP, announces the delivery with DESADV and invoices via INVOIC or UBL. A RECADV from the retailer completes the chain. International retailers and marketplaces often also use XML variants (cXML, xCBL) or their own API portals. We implement both sides: outbound to the retailer and the return flow back to your ERP.
What determines the cost of an EDI integration?
Three things: the number of trading partners and message types, the number of source systems on your side (a single ERP is quicker than SAP plus AFAS plus a platform of your own), and whether you run your own AccessPoint or AS2 server or work through an external provider. In the first conversation we go through the scope and then come back to you with a sprint budget. No open-ended hours; fixed budgets per sprint.

Talk to us about your EDI integration.

An introductory call of half an hour, with no obligation. We listen to your trading partner landscape, ask follow-up questions about the messages you need to exchange and give direction on scope, transport choice and any Peppol overlap. If you already have an EDI provider, we will look at how an additional stack can work alongside it. In the meantime, read our page on smart API integrations, and if you want to tackle your operational flows more broadly, our pages on a custom order management system or a custom ERP system. For purchasing-side automation: procurement-automation-platform.

Edit content