Nothing you paste is stored, logged, or sent anywhere. The repair runs in memory on this server and is gone the moment the response is returned — no database, no files, no analytics.
Wrong result, or missing something? Tell us by email — the verdict, version, and stop reason are filled in for you; you add the detail and decide what to include. Nothing is sent automatically.
Corrected interchange
Copy puts this interchange on your clipboard. Use this drops it back into the form above, so you can re-run the repair on it or hand-edit and re-check. Neither is saved anywhere — it stays in your browser.
Read it segment by segment
The same corrected bytes, one segment per line, indented by envelope
level, with the segments inside each transaction set numbered (that
count is what SE01 must match). A reading aid — not a
different result.
This is expected, not an error: ISA is a fixed-width
record, so x12-tidy pads short elements with spaces to their exact
size (ISA05/07 to 2, ISA06/08 to 15, and so on) — the runs of spaces
you see are correct output. VAN services and fixed-offset parsers
rely on that exact byte alignment, which is also why the
isa.* findings below flagged the original short values.
Envelope
No envelope facts — no payload was produced.
The top five are read straight from the corrected ISA header. The three counts are tallied by walking the cleansed payload — not taken from IEA01 / GE01 / SE01, which are instead checked against them (see the findings). Each value's source is noted beside it.
Repair passes
Each pass runs x12-tidy once. Pass 1 works on the interchange you submitted and does the structural repairs. Pass 2 (and any later pass) runs on the previous pass's output, so it shows only what is still wrong after those repairs — usually things x12-tidy can flag but not safely fix on its own. The loop stops when a pass changes nothing or finds nothing; most interchanges settle in one or two passes.
Every finding's code, title, and explanation come straight from
x12-tidy's diagnostic code registry —
the same source as the full code reference (every
severity, always) and x12-tidy codes.
The Byte column is the offset into the text you submitted where the flagged structure begins. Findings about the ISA line all point at the start of that line, so they share a number; a dash means the finding isn't tied to one spot.
Hover a severity chip for what it means. Click a pass (▶) to open or close it; click a chip on a pass to show only those findings — click more than one to combine.
Full report — every pass, every finding, the envelope facts, and the corrected interchange, in one file. View it here first, or download it to keep.