Field notes
EDI knowledge from real integration projects
Articles on EDIFACT, ANSI X12, XRechnung, Peppol, mapping architecture and AI-assisted document analysis — written for teams who run integrations.
XRechnung rejection checklist: the ten rules that fail most often
German public-sector invoices are rejected for a small set of recurring reasons. Here is the list, with the business rule behind each one.
Read articleWhy AI should explain EDI, never validate it
A language model is excellent at describing what a segment means and useless as a source of truth for compliance. Here is how we keep the two layers apart.
Read articleMapping projects that survive the second partner
The first EDI mapping is easy. The tenth is only easy if the first was built as a canonical model instead of a point-to-point translation.
Read articleReading your first EDIFACT file without a manual
A short walkthrough of an ORDERS message, segment by segment, so the wall of apostrophes turns into a purchase order.
Read articlePeppol in practice: what changes when you leave the direct connection
Peppol is a network, not a file format. Understanding the four-corner model explains most of the surprises during onboarding.
Read article