A failed EDI transaction becomes a chargeback or a short-paid invoice. We catch it first.
Every transaction is validated field by field before it moves — and when something is wrong, the engine corrects the common cases itself instead of parking the document in an error queue.
- Field-by-field, every transaction
- Auto-correction built in
- Field-level audit trail
The problem
An EDI error is never just an error
A failed document doesn’t announce its cost up front. It shows up later — as a late order, a chargeback, a short-paid invoice, or an afternoon of two teams comparing screenshots.
What a failed transaction becomes
- A transposed item ID ships the wrong product — and the return, restock, and reorder are all on you.
- A wrong unit of measure turns an order for eaches into an order for cases.
- A price mismatch surfaces weeks later as a short-pay you have to dispute line by line.
- The usual fix — re-sending the file — sends the same broken data twice.
What the validation engine does instead
- Validates every transaction field by field before it moves, comparing X12 files against templates.
- Auto-corrects the common failures: transposed item IDs, wrong UOMs, missing addresses.
- Runs price tolerance checks and cross-references original data against mapped values as documents flow.
- Rebuilds failed transactions from your current ERP data — not from the file that already failed.
The engine
Nine things the engine does to every document
Validation isn’t a checkbox stage at the door — it’s a set of corrections and cross-checks running on every transaction, in both directions.
Field-by-field validation
Every transaction is validated at the field level before it moves — not sampled, not spot-checked.
Field-level audit trail
Every ship-to, bill-to, item, price, and UOM stored at field level — the record that settles partner disputes.
Auto-correction of common errors
Transposed item IDs, wrong UOMs, and missing addresses are fixed automatically instead of queued for a human.
Original-vs-mapped cross-reference
Original data is cross-referenced against mapped values, so translation errors can’t hide.
X12 template comparison
Incoming and outgoing X12 files are compared against templates to catch structural drift early.
Price tolerance checks
Prices outside tolerance are flagged in flight — before they become short-pays and disputes.
Consolidated invoice splitting
Consolidated invoices are split automatically so each document lands the way your ERP expects it.
Line number backfilling
Missing line numbers are backfilled automatically — a small fix that prevents a failed import.
Item ID correction
Item identifiers are corrected against known catalog data, so a keying slip doesn’t stop an order.
Smart resend
We don’t re-send broken files. We rebuild them.
When a transaction fails on most platforms, “retry” means transmitting the same broken file again. Comparatio soft-deletes the failed transaction and rebuilds it from your current ERP data — so the document that goes back out is generated from what your system says now, not from the file that already failed.
FAQ
Validation, in practice
What happens when a transaction fails validation?
Common errors — transposed item IDs, a wrong unit of measure, a missing address — are corrected automatically. Anything that can’t be auto-corrected is flagged with the exact field that failed, so the fix is a lookup, not an investigation.
How is smart resend different from just re-sending the file?
Re-sending a broken file sends the same broken data twice — which is what most platforms do. Comparatio soft-deletes the failed transaction and rebuilds it from your current ERP data, so what goes back out reflects reality, not the error.
What does the audit trail actually store?
Every ship-to, bill-to, item, price, and unit of measure — stored at the field level on every transaction, with original data cross-referenced against mapped values. When a partner disputes a document, you can show exactly what was sent and why.
Can validation catch pricing problems before they become disputes?
Yes — price tolerance checks run on transactions as they flow, and original values are cross-referenced against mapped ones, so a price that drifts outside tolerance is flagged before it turns into a short-pay or a chargeback.
Find out what your failed transactions actually cost.
See the validation engine against your own document flows — including the errors it would have caught and fixed this week.