Where Practices Lose Billing Revenue

A practice can post charges every week and still lose revenue quietly. The symptom is not one dramatic payer refusal. It is a widening difference between net collectible charges and payments, an accounts-receivable aging report nobody has reviewed this quarter, and encounters that never became clean claims.

Measure the practice with its own numbers. For the last ninety days, reconcile completed encounters, charges entered, claims accepted by the clearinghouse, payer and patient payments, contractual adjustments, denials, refunds and current receivables. If a five-provider group averages $300,000 in monthly net collectible charges but receives $260,000, the operating question is where the $40,000 difference sits: normal timing, unbilled work, rejected claims, denied claims, patient balances, underpayments or an invalid expectation. These numbers are illustrative only; replace them with the practice ledger and payer contracts.

The diagnostic follows four checkpoints: eligibility, supported documentation and coding, claim scrubbing, and denial ownership. Software can validate fields and transmit data; it cannot resolve an unclear note, call a payer or pursue the next action.

The number that tells you billing is broken

No single percentage diagnoses every practice. Start with:

Opening AR + net charges − payments − valid adjustments − refunds/transfers = closing AR.

Reconcile encounter, charge and claim counts. A clean-claim rate can look strong while completed encounters remain unbilled outside its denominator. Payment rate can look weak when the period ignores normal adjudication. Gross charges can exaggerate the gap when contractual adjustments are absent.

Build one monthly control table with:

• completed encounters and encounters not closed;
• charges by date of service and posting date;
• claims submitted, accepted, rejected and pending;
• payments by payer and patient responsibility;
• contractual and non-contractual adjustments with authorization;
• denials by reason and status;
• AR by age, payer, provider, location and balance type;
• unapplied cash, credit balances and refunds.

The cost is what remains collectible but unworked, plus labor and cash-flow consequences—not a generic percentage. Trace it to claims before buying another dashboard.

Leak one: eligibility and benefits were not verified before the visit

Coverage can be active but still unsuitable for the planned service. The practice may have the wrong member ID, an expired plan, an out-of-network benefit, an unmet deductible, a coordination-of-benefits issue, a referral requirement or a service needing prior authorization. Discovering that after care shifts work into claim correction and patient collection, when expectations are harder to reset.

A pre-visit routine begins several working days before the appointment, with higher-risk services reviewed earlier:

1. Match patient name, date of birth, member and group identifiers to the payer response.
2. Confirm active coverage for the service date and relevant plan.
3. Check provider, location and service-network status through the approved source.
4. Record benefit details relevant to the planned service, including deductible, copay or coinsurance information as available.
5. Identify referral, authorization or medical-necessity requirements without assuming verification is an authorization.
6. Resolve conflicting or incomplete responses through the documented payer route.
7. Communicate an estimate or payment expectation under the practice’s approved policy, with clear limits because benefits are not a guarantee of payment.
8. Store source, date, time, representative or transaction reference and result in the designated system.

Assign a named owner and a deadline. The front desk should see a concise action status, not interpret a long payer response at check-in. Complex authorization belongs in a separate prior authorization support workflow. Eligibility work should not delay clinically necessary care without the practice’s authorized decision.

Leak two: the documentation does not support the code

The clinician performed work, but the record may omit the element required to support the selected code, level, modifier, diagnosis relationship or medical necessity under the applicable rule. A cautious coder may choose a lower supported code. An aggressive process may submit more than the note supports. Neither should be solved by asking a biller to infer clinical facts.

This is a documentation and query workflow problem:

• Define which encounters are ready for coding and which are incomplete.
• Run edits for missing signatures, dates, required fields and internal inconsistencies.
• Route a neutral, non-leading query to the authorized clinician or coding owner.
• Record the query, response, amendment and final code decision according to policy.
• Track recurring gaps by provider, service and cause; use them for education, not retrospective invention.
• Prevent billing staff from changing clinical documentation or selecting unsupported codes to clear a queue.

Modifier rules, coding updates and payer policies change. The practice needs qualified coding oversight and current authoritative references. A remote support team can identify missing administrative elements, manage the query queue and maintain status; it should not make clinical judgments outside its defined competence and authority.

Leak three: claims were submitted without effective scrubbing

Claim scrubbing checks the claim against structural, code-set, payer and practice rules before transmission. It can catch missing demographics, invalid identifiers, inconsistent dates, absent referring-provider information, invalid payer IDs, required modifiers, impossible code combinations and missing authorization references.

A scrubber is only as good as its rules, source data and follow-up. Passing an edit does not prove coverage, documentation or payment eligibility. The clean-claim measure should describe the first submission’s acceptance under a defined denominator; it does not include encounters never billed or denials after acceptance.

A rejection occurs before payer adjudication when the transaction or claim cannot be accepted for processing. A denial occurs after adjudication. Rejections are often faster to correct, but only when someone monitors the clearinghouse and payer acknowledgements daily. “Sent” is not the same as “accepted.”

The daily control should reconcile:

1. claims exported from the practice system;
2. files received by the clearinghouse;
3. payer acceptance or rejection acknowledgements;
4. rejected claims assigned by reason and owner;
5. corrections resubmitted and re-acknowledged;
6. transactions still missing an expected response.

Use a control total by claim count and charge amount. Without that reconciliation, a file-level failure can disappear between systems while every individual dashboard appears calm.

Leak four: denials were never worked

A denial queue needs an owner, category, next action and deadline. Common operational categories include eligibility, authorization, coding or modifier, medical necessity, duplicate, coordination of benefits, timely filing, non-covered service, bundling, demographic or provider enrollment, and information requested from patient or practice.

Do not treat every denial as an appeal. Some require corrected information and resubmission; some need a corrected claim with the payer’s required indicator; some need records or a formal appeal; some are valid contractual adjustments; and some are not collectible after review. The worker follows the payer’s current instruction, contract and approved practice policy.

Timely filing, corrected-claim and appeal windows are payer-, plan-, program-, contract-, claim- and sometimes state-specific. There is no safe single number. Record the controlling source and calculate the internal due date with a buffer. When a claim is already near deadline, escalate it above newer low-risk work.

For each denial, preserve the remittance code and narrative, payer communication, supporting records, submission proof, decision, next due date and final disposition. Analyze causes separately from recovery. A corrected claim may recover revenue today; preventing the same demographic error protects tomorrow’s queue.

Read the AR aging report like a billing manager

What each aging bucket is telling you

Age claims from the correct origin and label it: date of service, first billing date or last payer action. These dates answer different questions. Use standard buckets such as 0–30, 31–60, 61–90, 91–120 and over 120 days, but preserve the underlying date so work is not distorted by bucket boundaries.

• 0–30 days: confirm submission, acceptance and normal payer processing. Watch unbilled encounters and missing acknowledgements.
• 31–60 days: identify claims past the payer’s normal status point, requests for information, missing posting and patient-balance transfers.
• 61–90 days: escalate stalled or repeatedly corrected claims, underpayments and coordination issues; verify every next deadline.
• 91–120 days: triage by collectibility and deadline, with documented evidence of prior actions. Management attention is warranted.
• Over 120 days: conduct a structured collectibility review. Do not automatically write off age alone; determine payer status, documentation, contract, patient policy and legal constraints.

Segment insurance AR from patient AR, credits and unapplied cash. A total aging balance can hide a single payer processing issue or an old batch of unposted payments.

Which balances to chase first and which to adjust

Score each account on collectible amount, days to filing or appeal deadline, probability of recovery, effort, evidence available and compliance risk. Work high-value, high-probability claims near deadline first. Then clear quick corrections that release many claims or prevent repeat errors.

For a small balance, compare expected recovery with the documented cost of the next action. The practice can use automated statements, batch portal work or a policy-based threshold when lawful and contractually permitted. No worker should invent a write-off to make aging look better. Adjustments need reason codes, approval authority and periodic review for patterns or improper waiver.

A same-day triage:

1. Filter claims with a known filing or appeal deadline inside the next thirty days.
2. Sort by collectible balance and recoverability, not gross charge alone.
3. Separate missing-information items the practice can resolve today.
4. Identify payer-wide patterns that can be escalated as a batch.
5. Place unsupported, non-covered or exhausted claims into authorized review rather than endless follow-up.

Book a billing operations review with the current aging export, denial categories, clearinghouse rejection log and payer mix.

In-house biller, billing company or dedicated support team

An experienced in-house biller can be the best fit for a small, complex practice with close clinical coordination—provided absence and succession are covered. A full billing company can suit a practice wanting broader responsibility and willing to govern the commercial model. A dedicated team can suit recurring queues where the practice wants system visibility and provider-side supervision without rebuilding every role internally.

Compare the complete requirement: eligibility, charge lag, submission, rejection, denial, payment posting, patient balance, reporting, coding oversight, management, cover and transition. Do not compare an employee salary with a vendor percentage while ignoring the work each leaves behind.

What dedicated billing support does each day

Before visits: work the eligibility queue, document responses and escalate authorization or network exceptions. After encounters: monitor unsigned or incomplete records, manage approved queries and enter authorized charges. At submission: run edits, transmit, reconcile acknowledgements and correct rejections. After adjudication: post or reconcile payments, classify denials, follow payer status, prepare approved appeal packages and update patient responsibility. At close: report control totals, unresolved exceptions, deadlines and workload aging.

A team lead assigns work, reviews quality samples, monitors deadlines and escalates outside-policy questions. The practice names owners for clinical documentation, coding, refunds, adjustments, patient hardship, payer contracting and compliance. A support specialist should never decide a clinical fact or waive a balance because the operational queue is old.

The weekly report should show encounters not billed, charge lag, acceptance and rejection, denials received and resolved, AR movement, top root causes, upcoming deadlines, underpayments or credits, and decisions required. It should permit claim-level traceability without placing unnecessary patient information into unsecured email or general project tools.

A high clean-claim rate can coexist with unbilled encounters and ignored post-adjudication denials. Use measures from the entire control chain. For deeper calling and status workflow, see AR follow-up for medical billing.

Security, access and compliance expectations

Billing commonly involves protected health information. HHS’s current business-associate guidance specifically lists billing and claims processing among activities that can make a service provider a business associate when PHI is involved. A covered entity generally needs the required written business associate agreement before disclosing PHI, and subcontractors that create, receive, maintain or transmit PHI on behalf of a business associate must be addressed.

Ask any partner, including OVELITHUB:

• Will it sign an agreement containing the required uses, safeguards, incident reporting, subcontractor and termination terms?
• Where will PHI be created, received, maintained or transmitted, including backups and support tools?
• Are users individually named, authenticated and granted role-based, minimum-necessary access?
• Can the practice approve and revoke access promptly, and are dormant accounts reviewed?
• Are system activity and material billing actions logged and reviewed?
• How are workstations, transmissions, downloads, printing and removable media controlled?
• What training records, sanctions, incident process, continuity plan and risk analysis are maintained?
• Which subprocessors or locations are involved, and how are equivalent obligations applied?
• How are PHI returned or destroyed at termination where feasible?

HHS’s current Security Rule summary describes risk analysis, workforce authorization, access control, audit controls, authentication, integrity and transmission safeguards for regulated entities. Its minimum-necessary guidance generally requires reasonable steps to limit PHI use, disclosure and requests to the intended purpose. These are requirements to assess and implement according to the actual relationship and risk; this article does not claim any OVELITHUB certification.

A thirty-day plan to stop the biggest leak first

Week 1: measure and reconcile

• Export encounter, charge, claim, remittance, denial and aging data for a consistent period.
• Reconcile control totals between practice system, clearinghouse, payer and bank posting.
• Sample claims from every aging bucket and map the actual stall point.
• Record the largest collectible leak and its root cause without changing production yet.

Week 2: stabilize eligibility

• Create a pre-visit worklist, proof standard and exception categories.
• Prioritize services and payers with high administrative risk.
• Assign unresolved issues to named practice decision owners.
• Measure completion before visit and downstream eligibility denials.

Week 3: stand up denial ownership

• Load open denials with reason, amount, source, next action and deadline.
• Separate corrected claims, formal appeals, information requests and valid adjustments.
• Work the deadline and high-collectibility order.
• Feed the leading preventable causes to eligibility, documentation and claim edits.

Week 4: attack the oldest workable AR

• Apply the collectibility score to insurance and patient balances separately.
• Resolve batch payer issues and claims with ready evidence.
• Route exhausted or unsupported balances through the authorized adjustment review.
• Set weekly reporting and a rolling ninety-day prevention plan.

Do not launch every fix simultaneously. The first thirty days should identify and control the largest recoverable leak while preserving submission and patient service. Outsourced support requires real onboarding: payer rules, access, work examples, escalation, adjustment authority and quality calibration. A partner promising zero practice effort is overselling.

Keep the practice’s revenue visible

Billing improves when every completed encounter has a traceable path to charge, accepted claim, adjudication, patient responsibility and final disposition. Eligibility, documentation, claim edits and denial follow-up are separate controls; one attractive clean-claim number does not replace them.

OVELITHUB’s medical billing support services can be scoped around defined queues while the practice retains policy, clinical and coding authority. Start with the aging report and the largest reconciled leak, then build the management and security controls required for continuing work.