How to read a 997 reject, segment by segment
A 997 tells you exactly what your trading partner rejected and why, if you know where to look. Here is how to read AK3, AK4 and AK5 without guessing.
Learning EDI in public
I fell into EDI by accident. Now I write down everything I work out.
X12 and EDIFACT reference, reject codes decoded, platform notes, and the e-invoicing mandates nobody explains properly. Written from public standards as I work through them.
ErrorsReject codes, acknowledgement failures and interchange problems, decoded. What the code means, what causes it, and how to fix it.1 pageX12ANSI X12 transaction sets, segments, qualifiers and the implementation details the introductory pages skip.Nothing published yetEDIFACTUN/EDIFACT messages, the X12 crosswalk, and what changes when you cross the Atlantic.1 pageTrading partnersRetailer and carrier requirements as published, onboarding sequences, and what tends to trigger chargebacks.Nothing published yetPlatformsSterling, Gentran, Axway B2Bi, Cleo, Boomi and the rest. Mapping, debugging and migration, from their public documentation.Nothing published yetConnectivityAS2, SFTP, VANs and API bridges. Certificates, MDNs, and the handshake failures that look like nothing is wrong.Nothing published yetComplianceE-invoicing mandates, ViDA, Peppol and EN 16931, plus the X12 release cycle. What changes, when, and what it means for existing EDI flows.Nothing published yetFundamentalsWhat EDI actually is, how an interchange is put together, and how a transaction moves. For people starting where I started.Nothing published yet
From the notebook
All notesStart here
All sectionsRecent
RSSX12 to EDIFACT: the crosswalk that actually matters
The transaction set mappings between X12 and EDIFACT are the easy part. The differences that break integrations are in structure, qualifiers and acknowledgement behaviour.