Claims & Billing

Move claims forward and keep payment follow-up organized.

Build a clear path from reviewed clinical documentation to a submitted claim, a posted EOB, and a resolved balance. Every claim and patient balance gets an accurate status, an owner, and a next action.

Book a Free Consultation

Situation

Is this your problem?

The revenue is earned. The follow-through is not reliable.

Claims sit unsubmitted because an attachment, narrative, or reviewed code is missing and no one owns the exception.
The clearinghouse says accepted, the payer says not on file, and the practice has no dated follow-up trail.
Denials repeat for the same reason because corrections and appeal outcomes never become a reusable rule.
EOBs are posted late or inconsistently, so insurance balances, patient balances, and adjustments cannot be trusted.
Patient statements go out without a clear review step, and balance questions bounce between the front desk and billing.
The aging report grows every month, but the team cannot see which dollars are collectible, disputed, pending, or approved for write-off or refund.

Scope

What this workstation owns.

This is the starting scope. We adapt it to your practice, hours, systems, payer mix, and team.

Claim preparation & submission

Create claims from completed procedures after the clinical team has reviewed coding and documentation
Scrub required claim fields against fixed practice rules before submission
Match required radiographs, periodontal charts, narratives, and other supporting documents to the claim
Route missing or unclear clinical documentation back to the clinical team without making coding decisions
Submit clean claims through the approved clearinghouse and record the submission reference

Status & exception follow-up

Confirm clearinghouse acceptance and separate rejections from payer denials
Check claim status at agreed aging intervals by portal, clearinghouse, or approved payer channel
Record payer status, reference numbers, requested information, and the next follow-up date
Correct nonclinical submission errors within approved rules and resubmit
Escalate stalled, missing, duplicate, or coordination-of-benefits claims with a complete history

EOBs, denials & appeals

Post reviewed insurance payments, contractual adjustments, and patient responsibility from EOBs or ERAs
Reconcile each EOB or ERA to the claim and deposit record before closing the item
Classify denials by reason, deadline, dollar amount, and required owner
Assemble appeal packets from approved templates and reviewed supporting records
Track appeal submission, acknowledgment, response, and final disposition through closure

Patient balances & payments

Review balances against posted insurance activity before releasing a statement
Send approved statements and follow-up messages on the practice's cadence and consent rules
Record patient questions, disputes, promises to pay, and agreed next actions
Set up only manager-approved payment plans and route exceptions for approval
Prepare refund requests with the payment trail and reason for authorized review

Aging, controls & handoff

Maintain insurance and patient aging queues by age, value, payer, status, and next action
Produce a weekly exception view for claims or balances without a current owner or follow-up date
Surface repeated denial, attachment, posting, or statement failures for process correction
Hand off accounting-ready payment and adjustment records to Bookkeeping without changing the books

Metrics

How do we measure success?

Targets agreed from your practice's baseline.

Clean submission rate: Share of reviewed claims accepted by the clearinghouse without a preventable rejection, tracked by rejection reason.
Time to first submission: Time from completed, reviewed clinical documentation to initial claim submission.
Claims with a next action: Share of open claims with a current status, named owner, and dated next step.
Denial turnaround: Time from denial receipt to corrected claim, appeal submission, approved write-off review, or other documented disposition.
Accounts receivable aging: Insurance and patient balances by age band, with the over-90-day share and collectible dollars tracked separately.

Automation

AI agents and automations for this workstation.

We assess the workflow before recommending a hire or a build. These are possible improvements, not features already installed in your practice.

Claim-prep agentassemble → check → queue

Built forThe practice submits enough claims that manual preparation creates a daily backlog or repeated preventable rejections.

47%
Reported reduction in unpaid claims: 6 months
Period measured: 2 offices
Locations in the case

Vendor-reported example: DentalXChange describes two specialty practices using its billing service for claim submission, follow-up, payment posting, and reconciliation. It reports a 47% reduction in unpaid claims over six months. The result covers the combined service, not claim preparation alone. It is not independently verified or a forecast for this build.

DentalXChange claims-management case study ↗

The manual way

Find completed procedures that have not been billed.
Open the chart and claim screen one patient at a time.
Check demographic, payer, provider, and procedure fields.
Search for the right radiograph, chart, or narrative.
Ask the clinical team about anything missing.
Submit and hope the exception is not rediscovered days later.

With AI agents & automation

Completed, reviewed procedures enter one preparation queue.
Fixed checks find blank, mismatched, or out-of-range fields.
Required attachments are matched by documented rules.
Missing clinical items return to the clinical team with context.
A person reviews the completed claim before submission.

Systems needed

Practice management system
Imaging or document source
Clearinghouse
Exception queue

Human control

A person approves submission. The clinical team handles code selection, chart corrections, clinical narratives, and any question about treatment or necessity.

Full build specification

Trigger / problem: A completed procedure is ready for billing after the clinical team has reviewed the codes and chart. Today those items are found through memory, reports, or rejected claims.
What it reads: The reviewed ledger entry, patient and subscriber fields, payer data, provider identifiers, procedure details, and available supporting documents.
What it decides: Whether required administrative fields and rule-based attachments appear present. It does not decide which code is correct or whether treatment was medically necessary.
What it does: Creates or updates the claim draft, applies fixed scrub rules, matches available supporting documents, and places complete claims in a human-review queue. Incomplete claims get a named exception.
Human approval / takeover: A person approves submission. The clinical team handles code selection, chart corrections, clinical narratives, and any question about treatment or necessity.
Systems needed: Read and draft access in the PMS, access to approved imaging or document repositories, and a clearinghouse connection that exposes submission status.
Privacy / access: Minimum necessary access, role-based permissions, and a Business Associate Agreement where required. Patient information stays in approved practice accounts and connected systems.
Logging & failure handling: Every source record, check result, attachment match, exception, reviewer, and submission decision is logged. If a source is unavailable or a match is uncertain, the claim remains unsent and enters the exception queue.
Success metric: Time to first submission, clean clearinghouse acceptance rate, and claims delayed by missing documentation.
What the practice owns at handoff: The scrub rules, attachment matrix, review queue, exception reasons, configured workflow, and operating guide in the practice's accounts.
Good fit when: The practice submits enough claims that manual preparation creates a daily backlog or repeated preventable rejections.
Not a fit when: Clinical documentation and coding are not reviewed consistently. Fix that clinical control first rather than automating around it.

Claim-status agentcheck → record → escalate

Built forAging reports are large enough that staff cannot reliably work every claim or reconstruct the follow-up history.

47%
Reported reduction in unpaid claims: 6 months
Period measured: 2 offices
Locations in the case

Vendor-reported example: DentalXChange reports a 47% reduction in unpaid claims across two specialty offices over six months after its billing service handled submission, follow-up, payment posting, and reconciliation. The result reflects the whole service, not status follow-up alone. It is not independently verified or a forecast for this build.

DentalXChange claims-management case study ↗

The manual way

Run an aging report.
Sign into several payer portals.
Search one claim at a time.
Copy status notes back into the PMS.
Set a personal reminder to check again.
Discover later that a deadline passed or the payer never received it.

With AI agents & automation

Open claims enter follow-up windows set by payer and status.
Available electronic statuses are collected into one queue.
Each claim gets a dated note and next action.
Missing, stalled, or deadline-sensitive claims rise to the top.
A person handles calls, portal questions, and disputed statuses.

Systems needed

Practice management system
Clearinghouse or payer portals
Claim-status queue
Task or notification layer

Human control

A person handles phone calls, conflicting payer responses, filing-limit risk, corrected claims, appeals, and any request for clinical records not already approved.

Full build specification

Trigger / problem: An accepted claim reaches its next agreed follow-up date without payment, denial, or a final disposition.
What it reads: Claim number, payer, member and provider identifiers, billed amount, service date, submission history, clearinghouse response, prior payer notes, and next-action date.
What it decides: Which approved status channel to use, whether the result is routine or exceptional, and the next follow-up interval under fixed rules.
What it does: Retrieves available status, writes a dated status note, updates the queue, sets the next action, and escalates missing, rejected, stalled, or deadline-sensitive claims.
Human approval / takeover: A person handles phone calls, conflicting payer responses, filing-limit risk, corrected claims, appeals, and any request for clinical records not already approved.
Systems needed: Reliable claim identifiers in the PMS, clearinghouse status access, approved payer portal access, and a task queue. We verify which payers expose usable electronic status before scoping.
Privacy / access: Access is limited by payer and task. Credentials remain in practice-controlled accounts or an approved credential manager. No patient data is copied into unapproved tools.
Logging & failure handling: Every inquiry, response, reference number, status change, and next-action date is logged. Portal failures and unmatched responses stay open and route to a person.
Success metric: Share of open claims with a current status and dated next action, plus aging by payer and procedure type.
What the practice owns at handoff: The follow-up windows, payer routes, status taxonomy, escalation rules, queue, and operating guide.
Good fit when: Aging reports are large enough that staff cannot reliably work every claim or reconstruct the follow-up history.
Not a fit when: Claim records lack stable identifiers or the practice has not chosen one source of truth for status notes.

Denial-workflow agentclassify → assemble → route

Built forThe same denial types recur or the team loses time rebuilding packets and searching for deadlines.

20–30% → nearly 0%
Vendor-reported denial-rate change: $25,000
Reported first-month collection increase: 5 hrs / wk
Reported staff time saved

Vendor-reported example: a Dentrix success story says Oakdale Smiles moved from a 20% to 30% denial rate to nearly zero, increased collections by $25,000 in the first month, and saved five staff hours per week after adopting Eligibility Pro and eClaims. The result covers the combined products and the practice's process changes, not denial routing alone. It is not independently verified or a forecast for this build.

Dentrix Oakdale Smiles success story ↗

The manual way

Read each EOB from scratch.
Decode the denial reason.
Search for the payer's deadline and requirements.
Ask several people for records or context.
Rewrite a familiar appeal.
Track the result in a spreadsheet or memory.

With AI agents & automation

Denials enter a queue by reason, value, and deadline.
Similar denials use an approved checklist and packet template.
Available records and claim history are assembled for review.
Clinical or coding questions return to the clinical team.
A person approves every correction, appeal, write-off, or resubmission.

Systems needed

PMS and claim history
EOB or ERA source
Document repository
Appeal template library
Deadline queue

Human control

A person approves all corrected claims and appeals. The clinical team resolves clinical coding, necessity, and documentation questions. A manager approves write-offs, refunds, and disputed balances.

Full build specification

Trigger / problem: A denial, rejection, underpayment, or information request arrives and needs a documented disposition before a filing or appeal deadline.
What it reads: The claim and submission history, payer response, EOB or ERA codes, approved payer rules, prior notes, available attachments, and practice approval limits.
What it decides: Which administrative denial category and approved checklist appear to apply, who must review it, and how urgent it is. It does not decide clinical coding or final appeal strategy.
What it does: Creates a denial record, extracts the deadline and reason, assembles available supporting items, drafts an internal summary or approved-template response, and routes it to the right reviewer.
Human approval / takeover: A person approves all corrected claims and appeals. The clinical team resolves clinical coding, necessity, and documentation questions. A manager approves write-offs, refunds, and disputed balances.
Systems needed: EOB or ERA access, claim history, document storage, payer-rule references, and a queue with deadlines and approval states.
Privacy / access: The workflow reads only the records needed for the denial. Appeal packets are sent only through approved payer channels after review.
Logging & failure handling: The denial reason, extracted deadline, source document, packet contents, approver, submission proof, and payer outcome are logged. Unclear reasons or missing deadlines are treated as exceptions, not guessed.
Success metric: Denial turnaround, repeat-denial rate by reason, appeal outcomes, and dollars resolved before deadline.
What the practice owns at handoff: The denial taxonomy, checklists, approved templates, deadline rules, approval map, queue, and documented workflow.
Good fit when: The same denial types recur or the team loses time rebuilding packets and searching for deadlines.
Not a fit when: The practice wants software to make unsupervised coding or clinical-necessity decisions. Those remain with qualified people.

Payment-posting agentmatch → draft → reconcile

Built forPosting volume causes delays or preventable balance corrections, and the practice has documented adjustment authority.

47%
Reported reduction in unpaid claims: 6 months
Period measured: 2 offices
Locations in the case

Vendor-reported example: DentalXChange describes two specialty offices using billing support across claim submission, follow-up, payment posting, and reconciliation, with unpaid claims reduced 47% over six months. The result is for the combined service and cannot be attributed to posting alone. It is not independently verified or a forecast for this build.

DentalXChange claims-management case study ↗

The manual way

Open an EOB or ERA.
Find each matching claim and payment.
Enter payment, adjustment, and patient responsibility lines.
Check the deposit separately.
Leave unusual items for later.
Discover the mismatch when a patient calls or the month closes.

With AI agents & automation

EOB or ERA lines are matched to candidate claims.
Posting entries are drafted from the source document.
Unapproved adjustments and mismatches become exceptions.
A person reviews and posts the batch.
Patient statements release only after balance review.

Systems needed

PMS ledger
EOB or ERA source
Deposit or remittance reference
Approval queue

Human control

A person approves the posting batch. A manager handles unusual adjustments, refunds, write-offs, disputes, and balances outside the documented threshold.

Full build specification

Trigger / problem: An EOB, ERA, or payer payment arrives and needs to be matched, reviewed, posted, and reconciled before the balance moves forward.
What it reads: The remittance, claim and ledger history, payment reference, billed amount, allowed amount, patient responsibility, adjustment codes, and practice approval thresholds.
What it decides: Which claim appears to match and whether the proposed payment and adjustment lines fall within fixed rules. Uncertain matches remain exceptions.
What it does: Drafts payment and adjustment entries, links the source remittance, flags mismatches or nonstandard adjustments, and queues the batch for review. After approved posting, it updates the balance workflow.
Human approval / takeover: A person approves the posting batch. A manager handles unusual adjustments, refunds, write-offs, disputes, and balances outside the documented threshold.
Systems needed: PMS ledger access, electronic or scanned remittance access, payment references, and an approval queue that preserves source documents.
Privacy / access: Financial and patient data stay inside approved practice accounts. Access is separated so drafting, approval, and refund authority can remain with different people.
Logging & failure handling: Every match, draft line, source document, exception, approval, and posted result is logged. Totals that do not reconcile cannot close automatically.
Success metric: Posting turnaround, batch reconciliation rate, correction rate, and statements released with a reviewed balance.
What the practice owns at handoff: The matching rules, adjustment thresholds, approval map, exception queue, configured workflow, and reconciliation guide.
Good fit when: Posting volume causes delays or preventable balance corrections, and the practice has documented adjustment authority.
Not a fit when: The ledger itself is unreliable or adjustment and refund authority are undefined. Establish those controls before automating drafts.

Hiring

We help you hire for this workstation.

One role. Two hiring routes.

Role for this workstation

Claims & Billing coordinator

Prepare reviewed claims, work status and denial queues, post reviewed EOB information, follow approved balance workflows, and keep every open item tied to a next action.

Reports to your billing lead or office manager. Clinical coding stays with clinicians. Adjustments, refunds, write-offs, disputes, and payment-plan exceptions stay with authorized managers.

EmployeeBest when the role also handles in-office payments, physical mail, deposits, or high-context coordination with the clinical team.

Remote human virtual assistantBest when claims, remittances, payer access, statements, and queues can be handled securely through practice systems with written approval limits.

How we help