Converter

EOB PDF to JSON Converter

JSON is the format software speaks: nested, typed, and directly consumable by any modern language or API. Converting a PDF to JSON turns a document into a machine-readable object your code can validate, transform, and store without any parsing gymnastics.

Every extraction here is JSON-native — the CSV and Excel downloads are derived from it. Upload in the browser and copy the JSON, or skip the browser entirely and call the REST API from your own pipeline: same schema, same field names, every time.

EOB conversions structure the money trail per service line: CPT code, billed, allowed, plan paid, and patient responsibility in adjacent columns, making reconciliation and denial tracking a filter instead of a reading exercise.

How it works

1. 1

   Upload the EOB

   PDF (including scanned), PNG, JPG, or WEBP — from any source, with no template setup.

2. 2

   AI extracts the fields

   Patient & provider name, Claim number, Service date, Procedure (CPT) codes, and more — each with a confidence score so you know what to double-check.

3. 3

   Download the JSON output

   A structured JSON object with stable, snake_case field names, nested arrays for repeating rows, and a per-field confidence score — identical whether you download it from the browser or receive it from the API.

What lands in your JSON output

• ✓Patient & provider name
• ✓Claim number
• ✓Service date
• ✓Procedure (CPT) codes
• ✓Billed vs allowed amount
• ✓Insurance paid
• ✓Patient responsibility
• ✓Denial codes

Example column layout

A converted EOB produces consistent, labeled columns:

patient_name,provider_name,claim_number,billed_amount,allowed_amount,patient_responsibility…,…,…,…,…,…

When to use JSON

• →Building document upload into your own product via the REST API
• →Feeding automation pipelines, webhooks, and workflow tools
• →Storing structured document records in a database
• →Validating extracted values in code before they enter your system

FAQ