Extract EOB to Excel — Pull Claim Numbers, CPT Codes & Patient Responsibility from Any Payer
Manually typing claim data from an EOB takes 3 minutes per page. This reads any payer's format — Blue Cross, Aetna, Medicare, Medicaid — in 5–10 seconds, with the column names and layout you define.
5–10 seconds per EOB · Up to 99% accuracy on digital PDFs · Encrypted processing
Every Field a Billing Team Pulls From an EOB
An EOB carries the same logical fields across every payer — claim number, procedure codes, four money columns (what the provider billed, what the plan allowed, what insurance paid, what the patient owes), and adjustment reason codes — but no two payers label or arrange them the same way. With Custom Column Extraction, you type the column names you want and the AI locates each value by understanding what the field means, not where it sits — one definition works across every payer format.
| Claim # | Service Date | CPT | Billed | Allowed | Insurance Paid | Patient Responsibility | Network |
|---|---|---|---|---|---|---|---|
| 78214563 | 03/14/2026 | 99213 | $180.00 | $120.00 | $96.00 | $24.00 | In-Network |
Why EOB Extraction Breaks Template-Based Tools
EOBs carry four semantically-adjacent money columns — billed, allowed, paid, and patient responsibility — but payers swap their names and order freely. "stuck trying to balance something that's usable... vs something that can actually track everything but has 50 columns and nobody wants to fill out" is how one healthcare software builder on r/HealthInsurance described the EOB tracking problem. The data entry, not the data, is the bottleneck — and template tools that map fields by position make it worse.
Payer-specific templates multiply with every insurer. A practice billing Blue Cross, Aetna, UHC, Cigna, and Medicare juggles five layouts minimum. Template-based tools demand per-payer setup: mark where each field sits, then maintain those zones whenever a payer redesigns its statement.
Column-position mapping silently fails on reordered money columns. If a payer puts "Patient Responsibility" where "Insurance Paid" was last month, a position-based tool maps the wrong number into the wrong column — and a wrong-but-plausible dollar figure is harder to catch than a blank one.
CARC codes carry operational meaning that a flat "Code" column loses. CO (contractual adjustment), PR (patient responsibility), and OA (other adjustment) each trigger different downstream actions — submit an appeal, bill the patient, or write off the balance.
One set of column names extracts every payer's EOB. Type "Claim Number" once and the AI finds it whether the label reads "Claim #," "Claim ID," "ICN," or "Reference Number" — because it matches by the field's meaning, not its label or position. That's Custom Column Extraction: you define the output columns, the AI reads any layout to fill them.
Semantic mapping means a payer format change is a non-event. When a payer redesigns its EOB, there's no template to update. The AI re-reads the new layout the same way it read the old one — by understanding what each amount represents — so the redesign costs you zero maintenance time.
CARC codes land in their own columns, each actionable independently. Define separate columns for distinct code types and the AI routes each code accordingly. A CO-29 timely-filing denial, a PR-2 patient coinsurance, and an OA adjustment each arrive in a column your team can filter and act on — instead of one jumbled text field you have to re-parse.
From a Mixed-Payer Stack of EOBs to One Reconciliation Spreadsheet
Upload the stack as it arrives
A monthly batch mixes digital PDFs downloaded from payer portals, emailed EOB attachments (forwarded to your dedicated Email Inbox address — each account gets one, so forwarded attachments land in your processing queue without logging in), and scanned paper copies. All go into one batch with no pre-sorting by payer, plan type, or format.
Define your columns — and let the AI do the math
Type the output columns once: Claim Number, Date of Service, CPT Code, Billed Amount, Allowed Amount, Insurance Paid, Patient Responsibility. Add a computed column like Balance (Billed − Allowed − Insurance Paid) and the AI runs the calculation during extraction — you get the result, not the raw numbers to reconcile later in Excel.
One row per claim, every payer aligned
Download a single Excel file with aligned columns across every payer. Denied claims carry their CARC codes in a dedicated column — filter and act on CO-29 timely-filing denials without reading each document. Export as XLSX, CSV, or JSON, or push results straight into Google Sheets with the add-on.
When EOB Extraction Is Reliable — and When to Double-Check
Handles reliably
Digital PDFs from payer portals. Native digital documents have clean labels and sharp amounts — portal-download EOBs extract at up to 99% field accuracy.
Mixed-payer batches with one column definition. A stack spanning ten or more payers extracts into one aligned spreadsheet without per-payer configuration.
Paid and denied claims in the same document. Payers sometimes use different layouts for each on the same EOB — the AI reads each section independently and routes both into your output.
Verify these cases
Faded scanned paper EOBs. Low-contrast scans may misread a CPT digit or dollar amount. Spot-check any document that appears washed out.
Handwritten margin notes. Manual annotations on the EOB add information the AI reads less reliably than printed text. Review the remark column for documents with pen marks.
Multi-code denials on one line. When a denied service line carries several CARC codes at once, verify the code grouping maps as expected.
Frequently Asked Questions
Can it extract the claim number when every payer labels it differently — "Claim #," "Claim ID," or "ICN"?
Yes. Name a column "Claim Number" and the AI finds the value by meaning, not by matching a label. Whether the EOB prints "Claim #" in the top-right corner (Blue Cross), "Claim ID" in a left header block (Aetna), or "ICN" buried in Medicare service details, the identifier lands in the same column — no per-payer rule required.
Can I pull CPT codes and all four money columns — billed, allowed, paid, patient responsibility — into separate columns?
Yes. Define one column per field — "CPT Code," "Billed Amount," "Allowed Amount," "Insurance Paid," "Deductible," "Coinsurance," "Patient Responsibility" — and the AI maps the correct value to each by understanding what the field represents. The same definitions work across every payer because column matching is semantic, not positional. Paid and denied claims stay in one spreadsheet, each with the amounts that apply to it.
Can I process EOBs from many different payers in one batch without sorting by payer first?
Yes. Upload a batch that mixes Blue Cross, Aetna, UnitedHealthcare, Medicare, and Medicaid EOBs together. Define your columns once and the AI reads each document's unique layout independently, mapping values to the right columns and consolidating everything into one spreadsheet with a row per claim. No pre-sorting and no per-payer template setup — that's what makes batch processing practical at volume.
Does it extract CARC remark codes — and can I get them in their own column?
Yes. Name a column "Remark Code" and the AI pulls Claim Adjustment Reason Codes from each line — CO for contractual adjustments, PR for patient responsibility, OA for other adjustments. Define separate columns for different code types to route each to its own column, so your team can filter for specific codes (like CO-29 timely-filing denials) instead of reading through every document to find them.
How accurate is the extraction — do I still need to verify every field?
For digital PDFs from major payer portals, printed-text accuracy reaches up to 99%. The review burden depends on your documents: hover any extracted cell in the review screen to see exactly where the value came from on the original EOB — checking a batch takes seconds per page, not minutes. For high-stakes posting, verify amounts on faded or annotated documents; for routine reconciliation, the extraction is reliable enough to use as-is.