Skip to content
Knowledge centre

Technical guides: e-invoicing and EDI

Technical explanations of the mechanics that make a flow fail. Written to be useful without contacting us — and to be checkable.

The questions these guides answer

Each guide opens with a direct answer that reads on its own.

E-invoicing

Why is my electronic invoice being rejected?

An electronic invoice is rejected because the structured data accompanying it fails a check by the recipient or the platform, not because the document is unreadable. The most frequent causes are a mandatory field that is missing or wrongly formatted, a business rule not honoured (amount consistency, VAT, identifiers), content that does not match the profile the channel expects, or an incorrect recipient identifier. The PDF can be perfectly correct and the invoice still be refused.

EDI / EDIFACT

How do I identify the cause of a rejected EDIFACT message?

To identify the cause of an EDIFACT rejection, start from the raw message actually transmitted rather than how the integration tool displays it, then read the technical acknowledgement — a CONTRL, where one is sent, usually names the offending segment and data element. Compare that segment against the partner specification currently in force, then determine whether the gap comes from the mapping (the data exists but is misplaced or miscoded) or from the source data (the mapping is correct but receives a wrong value). Those two cases are fixed in different places.

ERP integration

What should we check in our ERP before an e-invoicing project?

Before an e-invoicing project, check that the ERP genuinely holds every piece of data the target format requires — not only what appears on the current PDF — that customer master data contains usable, current identifiers, that the system can receive inbound documents and not only send, and that it can store and report each invoice’s lifecycle statuses. In most cases the ERP already holds the essentials: what is missing is the layer that extracts, formats and handles the responses.

Does this guide describe your situation?

The guides explain the mechanics. The diagnostic establishes which one applies to your flows, on your messages.