The EOB
ends here.
Argus turns paper and PDF dental EOBs into reviewed, balanced payment data—then posts to Open Dental only when a human says go.
- Billed
- $1,200.00
- Write-off
- $350.00
- Plan pays
- $400.00
- Patient
- $450.00
Live product concept Hover or tap the panel to inspect the workflow.
ERAs solved most of payment posting.
Most is not all.
Even efficient practices still receive a stubborn remainder of insurance payments as paper or PDF EOBs. Each one has to be read, interpreted, balanced, and keyed into the practice management system.
Estimates reflect the operating context Argus is being designed around; results vary by payer mix, enrollment, and workflow.
Eyes. Calculator.
Judgment. Keyboard.
Argus separates the work into deliberate stages. Extraction and auditing remain read-only. Posting is a distinct, human-triggered act.
Upload
Bring in a PDF, scan, image, pasted text, or structured 835.
Document enters ArgusExtract
AI reads unstructured documents; structured 835 files take a deterministic path.
Data is organizedAudit
Exact decimal math re-derives line totals and reconciles the check.
Every dollar accounted forReview
A person inspects the source beside the extracted fields and can correct anything.
Human judgment stays centralPost
Only an explicit click begins the Open Dental posting workflow.
Human-triggered writeAI reads it.
Math proves it.
Extraction can be probabilistic. Financial reconciliation should not be. Argus uses exact decimal arithmetic to test the accounting identity for every service line and the payment as a whole.
Contractual adjustment + plan payment + patient responsibility = billed amount
Automation with
a hard stop.
The central design rule is simple: nothing is written to Open Dental until a human explicitly chooses to post.
Human-in-the-loop
Source document and extracted data stay together for fast, accountable review.
Duplicate defenses
Argus checks its event history and Open Dental payment records before posting.
Rollback-aware posting
Records are snapshotted before changes so a failed multi-step post can be restored.
Tamper-evident history
Transitions are recorded in a hash-chained event trail with short-lived PHI fields.
A working prototype.
Not a finished promise.
Argus is running in a secure cloud environment, connected to an Open Dental development system, and backed by an extensive automated test suite. It has not yet processed real patient EOBs.
Purpose-built foundation
Cloud-hosted, access-controlled, and designed around the sensitivity of dental payment workflows.
224 offline tests
Pipeline, security, tenant isolation, posting safety, audit history, and 835 parsing.
Real-world validation
Extraction accuracy, production Open Dental credentials, and carefully supervised pilot data.
For dental operators who still touch paper EOBs
Help shape
what comes next.
We’re looking for thoughtful conversations with practices and dental groups that understand this workflow firsthand.
Discuss an Argus pilot Prototype only · Not currently offered as generally available software