Explanation of Benefits Extractor

Pull claim numbers, patient and provider details, billed, allowed and paid amounts, and service lines out of EOB PDFs. Free, no signup, exports to CSV.

The full guide: Allowed amount and patient responsibility on an EOB

How should we start?

Build with Talonic

Need to scale? Create an API key, then run this from your own code or an agent.

Create an API key

Free account required

Start with a document

Upload a file or pick a sample, and see the fields come back.

No signup · nothing stored

Questions about Explanation of Benefits Extractor.

What is an EOB and what does this tool extract from it?

An explanation of benefits is the statement a health insurer sends after adjudicating a claim. The extractor reads the claim number and date, patient name, member ID and date of birth, payer, provider name and NPI, service dates, claim status, and the money fields: billed, allowed, deductible, copay, coinsurance, payer paid, and total patient responsibility.

Are service lines itemized?

Yes. Each service line returns the CPT or HCPCS code, service date, quantity, billed amount, allowed amount, paid amount, patient responsibility, and diagnosis pointers. Adjustments come back in their own table with reason and amount.

Can this handle EOBs from any payer?

It is payer-agnostic. The schema follows FHIR ExplanationOfBenefit and X12 835 conventions rather than one insurer layout, so national and regional payers both parse.

Is uploading PHI here a problem?

The document is processed via the Talonic API for extraction only; it is not retained for training and is not shared. For workflows that require a BAA, ask Talonic about the platform product rather than using the free tool with identified PHI.

What are the technical limits?

PDF format, up to 10MB and 100 pages per document.

How do I export?

CSV, XLSX, or JSON, including the service-line and adjustment tables.

Doing this to one file, or to ten thousand?

The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.

See document data extraction if you run this for clinical and billing teams, or the extraction API if you are building it in.