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.
Tell us what would make this more useful — or report a wrong result by email; you choose what to include, nothing is sent automatically.
Corrected interchange
Copy puts the corrected 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.
Runs of spaces in the ISA header are correct: ISA is a fixed-width
record, so every element is padded to an exact size (ISA05/07 to 2,
ISA06/08 to 15, and so on). VAN services and fixed-offset parsers read
the ISA by byte position, so the padding is required — see the
isa.* findings below.
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
- fatal
- A conforming parser will reject the interchange. x12-tidy flags it but cannot make it valid.
- error
- A real conformance violation. x12-tidy repaired what it could; the value or structure was wrong.
- warning
- Advisory — a trust or QA signal worth a look, not a conformance failure.
x12-tidy's classification. Every finding's code, title, and explanation
come straight from its
diagnostic code registry — the same
source as the full code reference 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.
Click a pass (▶) to open or close it. Click a severity chip on a pass to show only those findings — click more than one to combine.