Line amounts
Billed, allowed, contractual write-off, plan-paid, and patient-responsibility amounts for every service line—the numbers your posting lives or dies on.
Dental EOB extraction software · Built for Open Dental
Dental EOB extraction
software.
Pegasus reads paper and PDF dental EOBs, extracts every field into clean structured data, audits the math to the penny, and posts reviewed payments to Open Dental. AI-powered EOB extraction with a human approving every posting.
01 / The problem
The EOBs that never became an 835.
Electronic remittance solved most of payment posting. What remains is a stubborn stream of paper and PDF explanation-of-benefits documents that still have to be read, interpreted, balanced, and keyed into the practice management system by hand.
Dental EOB extraction closes that gap. Instead of a team member squinting at a scanned paper EOB and typing figures into Open Dental, Pegasus reads the document, pulls every field into structured data, and checks that the money reconciles before a person posts it.
02 / What gets extracted
Posting becomes review, not re-keying.
Every field on the EOB, structured: Pegasus turns an unstructured document into the exact fields your billing workflow needs—ready to review and post.
Patient & plan
Patient name, member ID, provider, claim number, and date of service captured from every claim on the EOB.
CDT codes
Each dental procedure line read with its CDT/procedure code and tooth or surface context where present.
Denial & adjustment codes
Denied lines flagged with their adjustment and denial reason codes so appeals and follow-up are one click away.
Structured data
Clean structured fields ready for human review and posting to Open Dental—not a blob of OCR text.
Check reconciliation
The check total and per-claim totals extracted and reconciled against the sum of the line items.
03 / Inputs
Any EOB format you receive.
Paper that got scanned, a PDF from a payer portal, a phone photo, or a structured remittance file—Pegasus takes the EOB as it arrives.
PDF & scanned PDF
Digital and scanned PDF EOBs, including multi-claim and multi-page documents.
PNG & JPG
Photographed or imaged EOBs are read with AI extraction, no clean text layer required.
Pasted text
Copy an EOB's text straight in when that is what you have.
835 / ERA
Structured electronic remittance takes a deterministic parsing path—no guessing where the data is exact.
Any dental payer
Layouts vary by carrier; AI extraction reads every carrier's format—national and regional alike—without per-payer templates.
One or a stack
Built for the daily remainder of paper EOBs a practice or group still works by hand.
04 / How it works
Extract, audit, review, post.
Extraction and auditing are read-only. Posting to Open Dental is a distinct, human-triggered act—never automatic.
- Upload the EOB. PDF, scan, image, pasted text, or a structured 835.
- AI extraction. Unstructured EOBs are read into structured fields; 835 files parse deterministically.
- Exact-math audit. Decimal arithmetic re-derives line totals and reconciles the check to the penny.
- Human review. A person inspects the source beside the extracted data and corrects anything.
- Post to Open Dental. Only an explicit click writes the reviewed payment—with duplicate defenses.
- Audited history. Every step is recorded in a tamper-evident audit trail.
05 / Security & HIPAA
HIPAA-compliant EOB extraction.
EOBs are PHI. Pegasus treats them that way—built by dental IT operators who implement HIPAA controls for a living, with a Business Associate Agreement provided to every practice.
Every service in the data path—including the AI extraction layer—operates under a signed Business Associate Agreement. PHI is encrypted in transit and at rest, access is scoped per office, and raw EOB content is automatically purged within seven days. The full posture—access layers, PHI-redacted logging, incident readiness—is documented on the Argus security section.
06 / Questions
Dental EOB extraction, answered.
What dental teams ask most about extracting EOBs and posting the payments.
What is dental EOB extraction?
Dental EOB extraction reads a dental Explanation of Benefits document—paper, PDF, or scan—and converts it into structured data: patient, member ID, provider, claim number, date of service, CDT procedure codes, billed, allowed, write-off, plan-paid and patient-responsibility amounts, denial codes, and the check total. That structured data can then be posted to a practice management system like Open Dental.
How is EOB extraction different from ERA (835) processing?
ERAs (835 files) are already structured and post automatically. EOB extraction handles the remainder—the paper and PDF EOBs that never arrive as an 835 and still have to be read and keyed by hand. Pegasus extracts those with AI, while structured 835 files take a separate deterministic parsing path. See our EOB vs ERA guide for the full comparison.
What fields can be extracted from a dental EOB?
Patient name, member ID, provider, claim number, date of service, procedure (CDT) codes, billed amount, allowed amount, contractual write-off, plan-paid amount, patient responsibility, denial and adjustment reason codes, and the check total—every field needed to post a payment.
Which EOB file formats are supported?
PDFs including scanned PDFs, images such as PNG and JPG, and pasted text for AI extraction. Structured 835 / ERA files are parsed deterministically.
Can I try it?
We're onboarding a small first group of founding practices and dental groups who work paper and PDF EOBs by hand today. Book a founding call. Product and posting questions—Open Dental, accuracy, HIPAA—are answered on the Argus page.
For dental teams that still key EOBs by hand
Put dental EOB
extraction to work.
Tell us about your current EOB and payment-posting workflow and we'll show you how Pegasus fits.
Book a founding call Now onboarding founding practices · Built for Open DentalPrefer email? support@pegasusdentalit.com