The orders EDI never reached.
eventsEDI 850s flow through; PDFs and free text get the same treatment. Your top 20 customers send EDI — Corin makes the other 400 equal.
EDI automation with AI agents — 850 to 820
on the wire: X12 850 · X12 855 · X12 856 · X12 810 · X12 820
01One network partner
Documents flow through a single EDI network connection in the SPS Commerce / TrueCommerce class. Corin rides rails that already exist; it doesn't ask you to become an EDI shop.
02Inbound 850 becomes a validated order
A purchase order arrives as X12 850. Corin maps it against the item master, checks credit, availability, and price, and stages the sales order — after a dry run shows what will post.
03Exceptions become decisions, not tickets
A failed map, a part-number alias, a partial — each lands as a decision card with the full brief: the line, the mismatch, the proposed fix. Nobody opens an IT ticket to release an order.
04Outbound 855, 856, 810
Acknowledgements, advance ship notices, and invoices are generated from ERP state and released on the gates you set — the documents enterprise buyers score you on.
05820 closes the loop
Remittance advices arrive as X12 820 and match to open invoices — cash application for your largest accounts stops being a manual reconcile.
Two lanes in. One rail out.
The 850 and the emailed PDF merge into the same validated, dry-run, gated commit — and the commit files into the ledger — a record of every decision: what changed, who approved it, when.
Sample rail — representative data, not a customer record.
Raw interchange in. ERP-ready out.
X12 from the trading network, ATA SPEC 2000 from aviation — the agent reads the wire format, repairs what a fixed mapper would bounce, and stages a clean document in the ERP. The wire format becomes the agent’s problem — not your team’s.
ISA*00*…*ZZ*PARTNER*ZZ*CORIN*260830~
ST*850*0001 · BEG*00*NE*PO-55231~
PO1*1*150*EA*152.00**BP*XX-4420-B~
N1*ST**92*____~
CTT*14~
+ resolve: XX-4420-B → AX-4420 · cross-reference
+ repair: empty N1 ship-to → plant from the partner profile
+ validate: 14/14 lines against the item master
+ dry run: pricing + availability confirmed — nothing posted
Sales order — staged
- order
- PO-55231 · X12 850
- lines
- 14 — 13 matched, 1 alias resolved
- checks
- credit OK · ATP confirmed · 2 lines split-ship
staged · awaiting approval
Illustrative interchange — sample records built on the shared demo cast, not customer data. SPEC 2000 is the ATA e-Business standard aviation trades in; Corin's production proof runs in that world.
Documents in, acknowledgements out.
ST*850*0001 — BEG*00*NE*PO-55231 — DTM*002*20261015
14 lines mapped against the item master: 13 matched, 1 part-number alias resolved from the cross-reference table.
Credit OK · available-to-promise confirmed for 12 lines · 2 lines split-ship from the second DC.
The sales order stages in the ERP — nothing posts until the gate clears.
Sample documents — representative data, not a customer record.
Not an EDI network.
Not a VAN. Corin rides one network partner; your maps and mailbags stay with the provider.
Not an EDI replacement. For the long tail of customers not worth an EDI project, email intake covers the gap — EDI stays for the accounts that mandate it.
Not a mapping project per partner. New trading partners are configuration against an existing network connection.