EDI & EDIFACT

One failing EDIFACT mapping stops an entire chain. We rework it.

EDI mapping remediation, correction of data transformations and recovery of failing exchanges with your customers, suppliers and carriers.

Fix my EDI mapping See how we work

At a glance

The subject: EDI exchanges that fail: EDIFACT mappings, data transformations and messages refused by a trading partner.
What we do: We read the rejected message, trace it back to the rule or segment responsible, correct the mapping and replay the flows until exchanges resume in full.
Who it is for: Companies whose exchanges with customers, suppliers or carriers are standardised and high-volume: transport and logistics, distribution, manufacturing, food and beverage.
What we do not do: We do not replace your EDI platform and we do not push a migration. We repair what is there.
Starting point: A diagnostic: the cause is established and quantified before anything is corrected.

What we are most often called in for

A partner changed their specification and your messages stopped going through.
Your INVOIC messages are rejected while your ORDERS pass normally.
An expected segment or qualifier is missing, and nobody knows which one.
The transformation produces correct data in the wrong place.
The message leaves, but the acknowledgement never arrives.
Your long-standing EDI provider can no longer act on it.

EDI & EDIFACT

What we take on

A broken mapping is not a configuration problem: it is two systems disagreeing about what a piece of data means. We settle it at the source.

Mapping remediation
Analysing the rejected message, comparing it against the partner specification, fixing the mapping and replaying the flow.
Data transformations
Conversions between EDIFACT, X12, XML, CSV, JSON and your ERP’s internal structures, with the business rules that go with them.
New partner onboarding
Integrating a new customer, supplier or carrier: reading their specification, mapping, testing, go-live.
Taking over existing flows
Picking up a poorly documented or unmaintained mapping estate, and straightening out what fails.
Connectivity & transport
Setting up and troubleshooting the channels: AS2, OFTP2, SFTP, APIs, with acknowledgement and retry handling.
Exchange monitoring
Knowing in real time what was sent, what is stuck and what failed — without opening five interfaces.

How an engagement runs

01
Rejection analysis
Reading the raw message and the partner response, assuming nothing.
02
Specification comparison
The precise gap between what you send and what is expected.
03
Mapping fix
Fixed at the source, including the upstream rules that produced the data.
04
Partner testing
Validation on real messages, with the partner where available.
05
Back to production
Replaying the pending flows and watching the first exchanges.

The messages and channels involved

These are the building blocks of your trading exchanges: one broken block stops the chain.

ORDERS / ORDRSP: The order and its response: the start of the chain. An error here propagates everywhere.
DESADV: The despatch advice: what the recipient needs to prepare their goods receipt.
INVOIC: The invoice: the message whose rejection hits your cash directly.
RECADV / CONTRL: The acknowledgements: what tells you your message was received and understood.
AS2 / OFTP2: The long-standing transport channels, still mandated by many large customers.
ANSI X12: The North American standard, when your exchanges reach beyond Europe.

Anumerik works on the technical implementation: mappings, data transformations, connectivity and integration. We do not provide legal or tax advice — your own advisers remain your reference on how the rules apply to you.

Frequently asked questions

Can you work on a mapping you did not write?

Yes — that is most of our work. We start from the rejected message and the partner specification; the mapping’s history is useful but not required to find the gap.

Do we have to replace our EDI platform to fix this?

Usually not. Most failures come from the mapping or from upstream data, not from the platform. If replacement genuinely becomes the best option, we will say so — after the diagnostic, not before.

Do you work alongside our current EDI provider?

Yes. We regularly work alongside an incumbent provider, on a specific flow they cannot address within the required timeframe.

Sources

References to the specifications themselves. Anumerik is not affiliated with any of these bodies and does not interpret their texts.

Introducing UN/EDIFACT — UNECE / UN/CEFACT
UN/EDIFACT directories (UNTDID) — UNECE / UN/CEFACT
GS1 EDI standards — GS1

The logical next step

Fixing one broken process usually reveals another, right next to it.

E-invoicing

ERP integration

Integration