Yearly running cost Assuming 12,000 remittances a year
By hand $140K / year 4,000 hours of work
Subscription n.a.
This workflow $518 / year Machine usage only; setup, hosting and review are extra. How should payments reach your practice system? Match insurer payments to dental claims and prepare checked entries for your practice software.
One remittance includes up to 25 claim payment lines.
Review from exports Reviewed posting batch $1,440 – 4,080 setup Approved practice-system posting Add an authorized system connection $1,872 – 5,520 setup
Which system should it connect to?Open Dental authorized API Other documented practice-system API A biller approves every posting batch. No funds transfers, patient balance write-offs, treatment decisions or guessing ambiguous patient matches.
What is included Begin with structured remittance and claim exports, not scanned EOBs. Check payment totals, contractual adjustments and previously posted identifiers before preparing entries.
Begin with structured remittance and claim exports, not scanned EOBs. Check payment totals, contractual adjustments and previously posted identifiers before preparing entries.
Practice scope: up to 1 practice-system connection.
Model input budget: up to 7,000 tokens across the reference run.
Model output budget: up to 1,000 tokens across the reference run.
Standard independent test set: at least 100 remittances.
Strict independent test set: at least 200 remittances.
Reference application CPU: 2 cores.
Reference application memory: 4 GB.
What standard do you need? Choose the acceptance targets your provider must demonstrate on your own test material.
Standard Test the defined workload and controls. Correct patient and claim matches: ≥99% Posting exceptions caught: ≥95% Included Strict Tighter targets and a larger independent test set. Correct patient and claim matches: ≥99.5% Posting exceptions caught: ≥98% Setup +$360 – 1,200 My own requirements Agree different targets and scope with your provider. Quote separately
How these standards are measured Split by remittance and insurer. Include name collisions, reversals, partial payments, already-posted payments and duplicate delivery of the same approved batch. Agree the holdout set before tuning. Report each metric with its numerator, denominator and exclusions; abstentions count against coverage. Test all inputs, including failures, rather than only accepted results.
Targets for your selected standard What is checked Target Correct patient and claim matchesCorrect suggested matches divided by all suggested matches; ambiguous identifiers must remain unposted. ≥99% Posting exceptions caughtDuplicate, unmatched and unbalanced cases held divided by all independently labeled posting exceptions. ≥95% Exact payment and adjustment totalsCorrect cent-level totals divided by all totals in approved batches; any unbalanced released batch fails. ≥100% Approval and data controlsPassed control cases divided by all independently tested unauthorized-action, stale-input and sensitive-data cases; any critical failure rejects delivery. ≥100%
Targets apply to the agreed independent test set, not every possible future input. During the pilot, a person reviews every result. Any unauthorized action or sensitive-data exposure fails acceptance.
How quickly do you need each remittance? Choose the time from accepted input to a reviewable remittance. Human review and waiting for source access are separate.
Within 60 seconds Included Within 30 seconds Setup +$144 – 480 Within 15 seconds Setup +$288 – 840
Timing details Measure wall-clock time including queueing, model calls, validation and permitted retries. Report failures and deadline misses. Faster targets need pilot testing; they are not vendor benchmarks.
The target applies to at least 95% of agreed test runs, with 1 in progress at a time.
How much should each remittance cost? Choose a machine-cost target per remittance. A lower cap may limit model calls and iterations.
Up to $0.15 Included Up to $0.12 Setup +$144 – 480 Up to $0.10 Setup +$288 – 840
Cost details Includes reference model usage, a retry allowance and allocated hosting at the stated volume. Human review, source-system subscriptions and paid connector access are separate. A tighter target must preserve the selected standards in the pilot.
Reference machine cost: $0.07 – 0.10 per remittance at 1000 remittances a month. The selected cap is a target to test, not a replacement for this estimate.
Where do you want it to run? Run the workflow in your cloud or on your own machine. Choose separately whether it may use an external AI model.
Run it onYour cloud Local environment AI model accessApproved model API No external model calls
Data and access details Run in your controlled cloud environment with scoped access and retained review records.
Use an approved external model with the agreed data-processing terms and minimum necessary input.
Local hosting does not itself keep data offline. Connected business systems may still use the network. Private inference needs suitable hardware and a separate measured running cost; access and retention rules must be agreed before real data is used.
How do you want to use it? Choose a browser interface, an MCP tool for your current agent, or a standalone agent.
Web page Review each remittance in a private browser interface. Included Your AI agent Call the workflow through MCP; the same access and approval rules apply. Setup +$72 – 360 Standalone agent Use a dedicated agent with the agreed triggers and controls. Setup +$144 – 480