Convert X12 820 Payment/Remittance Files to CSV
Turn a raw 820 payment order/remittance advice file into a spreadsheet-ready CSV — invoice-level remittance detail, payment amounts, and adjustment reasons. Runs entirely in your browser; nothing is ever uploaded.
Drag & drop your 820 file here
Up to 50MB — parsed entirely in your browser
or try it instantly with a free example 820 file — no upload needed:
No file parsed yet — upload an 820 file or load the sample above to see results here.
Parsed 820 Preview
Standard Detected
—
Delimiters
—
Segments
—
Record Groups
—
| Group | Segment ID | Segment Description | Element # | Value |
|---|
What Is an X12 820 File?
The 820 (Payment Order/Remittance Advice) is the ANSI X12 transaction set used to instruct a bank to make a payment and/or to tell the payee which specific invoices a payment covers. It's the accounts-payable/accounts-receivable counterpart to the 835 (which is specific to healthcare claim remittances) — the 820 is used across general commerce, insurance premium payments, and B2B invoice settlement. It carries payment amount and method, payer/payee identification, and per-invoice remittance detail with any deductions or adjustments applied.
Read the Full Guide: Why Convert 820 Files, Key Segments, and More
Why Convert an 820 to CSV?
Accounts receivable teams need to reconcile incoming 820 remittances against open invoices in their ERP or accounting system. A CSV export makes it fast to match payment amounts to invoice numbers, spot short-pays or deductions, and confirm every line item that a customer's payment run says it settled — without manually decoding delimited EDI text.
Key Segments You'll See in an 820 Export
- BPR — Financial Information: total payment amount, payment method, and banking details.
- TRN — Reassociation Trace Number: links the payment to its bank transaction.
- N1 — Party Name: identifies the payer and payee.
- RMR — Remittance Advice Accounts Receivable Open Item Reference: the invoice number and amount paid against it.
- ADX — Adjustment: the reason and amount for any deduction from the invoiced amount.
820 vs. 835 — What's the Difference?
Both are remittance-advice transaction sets that share a similar BPR/TRN/N1 structure, but the 835 is healthcare-specific (claim payment and adjudication detail via CLP/SVC/CAS segments), while the 820 is the general-purpose version used for invoice payments, insurance premiums, and other B2B settlements via RMR/ADX. If you're working with a healthcare claim payment file, use our 835 to CSV converter instead.
Also Known As
People also search for this as an "X-12 820 to CSV converter," "AP remittance edi csv convertor," or "820 edi file won't open" — all land on the same structural parser here.
Related Pages
For general EDI background, read What Is an EDI File? and X12 EDI Viewer.
Frequently Asked Questions
Does this show which invoices a payment covers?
Yes — the RMR segments (one per invoice referenced) are parsed and shown along with every other element in the record.
Can this handle deductions and adjustment reasons?
Yes, ADX adjustment segments are parsed the same way as every other segment, structurally, from the file's own data.
Is my remittance file uploaded anywhere?
No. Parsing happens entirely in your browser; the file is never transmitted to a server.
Is this a subscription?
No — a one-time payment (currently 50% off at $29.99) unlocks unlimited full-file exports, with no recurring fees.
Does this support both 4010 and 5010 versions, and can I batch-convert multiple files?
Yes on versions — the parser reads structurally from the file's own delimiters, so 4010, 5010, and other X12 versions of the 820 all work. It currently processes one file at a time; there's no bulk/batch upload feature yet. It runs on any device with a modern browser, including Mac and Chromebook.