How Much Does It Cost to Outsource Medical Billing?
- Medical Billing
- OneMed Billing
Every system in your revenue cycle reports on events. A denial generates a denial. An aged claim appears on the aging report. A payment posts. But nothing in your billing software generates a record of a charge that was never captured, a service coded a level below what the note supported, or a payment that arrived under contract and was accepted as correct. Absence doesn’t raise an alert. That’s precisely why it persists.
A claim was denied
denial reportA claim is ageing
A/R agingA payment arrived
posting logA claim was rejected
clearinghouseA charge never captured
nothingA level never coded
nothingAn underpayment accepted
nothingA denial never worked
nothingWhich is why the only way to find the second column is for someone to go looking on purpose.
This is also why leakage tends to be found late and by accident. An audit is simply the decision to look deliberately, on a defined sample, against what the documentation and the contract say should have happened.
A structured review of claims, payments, adjustments and denials, run against what your documentation supports and what your payer contracts specify — to identify revenue leakage, compliance exposure, and the workflow gaps producing both.
Practices lose revenue to underpayments, incorrect adjustments, missed charges and coding errors without ever seeing a symptom, because none of those things announce themselves. The audit’s job isn’t to confirm what you already suspect. It’s to quantify what you can’t currently see, and to say plainly which findings are worth acting on first.
The gap between those four is the finding.
Each of these is recoverable in principle. What they have in common is that none of them generates an alert on its own.
Paid below the contracted or expected allowed amount. Identifying these requires the rate to compare against, which is why we ask for fee schedules upfront.
Wrong adjustment amounts or codes quietly reducing reimbursement, often applied consistently enough that they look correct.
Services delivered and documented but never captured, or entered too late to be billed. These produce no denial and appear on no report.
Incorrect bundling or modifier usage causing reduced payment or denial on claims that were otherwise clinically sound.
Claims denied for late submission or late follow-up — entirely preventable, and permanent once the window closes.
Denials never appealed or resolved before the payer’s deadline, usually because nobody had capacity rather than because they’d have failed.
Visits or procedures billed below the level the documentation supports — legitimate revenue lost through caution rather than error.
Authorization required but not obtained, expired, or not matched to the service billed.
Notes that don’t fully support medical necessity, coding levels or the procedures billed — a compliance exposure as much as a revenue one.
Code sets, payer edits and contract terms change. Every finding is assessed against the rules in force for that payer and date of service.
Both are audits, but they sit on opposite sides of submission and answer different questions. Most practices need some of each — one stops next quarter’s losses, the other reclaims last quarter’s.
Internal audits are genuinely useful, and we’d encourage any practice to run them. The limitation isn’t competence — it’s that a team auditing workflows it designed is looking for problems it doesn’t expect to find.
| Dimension | Internal billing audit | Independent external audit |
|---|---|---|
| Typical focus | Routine checks and compliance monitoring | Systemic issues, leakage and payer behaviour |
| Familiarity with the workflow | Can mask issues that look normal | No assumptions about how things are done |
| Payer underpayment detection | Rarely in scope | Paid vs expected compared directly |
| Contractual adjustment review | Seldom checked | Adjustments verified against contract |
| Time available to do it properly | Competes with daily billing | Dedicated to the review |
| Willingness to report uncomfortable findings | Varies by culture | Reported plainly, including over-coding |
The strongest arrangement is usually both: internal review for ongoing monitoring, an external audit periodically to catch what routine has normalised.
Scoped to what your practice actually needs, rather than a single fixed package.
Coding, modifiers, documentation and charge accuracy reviewed before claims go out, to reduce denials and rework at source.
Submitted and paid claims analysed for underpayments, incorrect adjustments and recovery opportunities.
Top denial reasons and trends identified across payers, so repeat denials get fixed at the cause rather than one claim at a time.
Paid amounts compared against expected or contracted rates to detect payer underpayments and reimbursement variance.
Aging, follow-up workflow and payer response patterns reviewed to find where collections are stalling.
Coding and modifier usage evaluated for accuracy and compliance, including over-coding as well as under-coding.
Structured, transparent, and scoped so you know what's being reviewed and why.
We agree what's being reviewed and why, then collect EOBs, ERAs, claims data, denial reports and secure PM or EHR access. Fee schedules too, where underpayment review is in scope.
Claims and payment data reviewed line by line to detect discrepancies and variance against what was expected.
Claims paid below the expected or contracted amount identified, with the comparison basis stated for each.
We establish why the pattern exists — a coding habit, a workflow gap, a payer behaviour — rather than only listing symptoms.
A targeted plan covering what can still be recovered and what needs changing so it stops recurring.
Findings delivered with revenue impact, priority order, and clear owners for each recommended fix.
Summary of findings and risk areas
Claim-by-claim results with corrections
Revenue impact of each finding
Denial root-cause and error trends
Action plan with owners
Illustrative report contents.
A findings report is only useful if someone can act on it. Ours is written to be handed to a billing manager and worked through, not filed.
Revenue impact figures are estimates based on the sample reviewed and the rates available to compare against. They indicate scale and priority — they are not a guarantee of recovery, because recovery depends on filing windows, payer response and documentation.
The leaks differ by structure — so the scope does too.
Catch missed charges, coding errors and preventable denials without hiring additional billing staff or an in-house auditor.
Billing accuracy compared across multiple providers and departments, with consistent review and clear correction guidance.
Specialty-specific coding issues, modifier mistakes and documentation gaps that drive rejections in one department but not another.
Reduced payer scrutiny and stronger compliance, with claims checked against that specialty's particular billing rules.
Workflow breakdowns between sites that cause delayed charges, missed follow-ups and inconsistent results.
Issues fixed early, before rising patient volume turns a small error rate into a large one.
Tell us what’s prompting the question — rising denials, unexplained write-offs, or revenue that stopped tracking volume — and we’ll scope an audit around it rather than selling you a fixed package.
We'll reply within one business day to scope it with your team.
A detailed review of claims, payments, adjustments and denials to identify where revenue is being lost. It evaluates coding and modifier accuracy, payer reimbursement against expected rates, denial trends, write-offs and A/R follow-up workflows — then reports the errors, inefficiencies and compliance risks found, with a recommendation attached to each.
Underpayments from payers, incorrect contractual adjustments, missed or unbilled charges, recurring denial patterns, documentation and coding gaps, and aging A/R that isn’t being followed up. Most of these produce no alert of their own, which is exactly why they persist.
Common signals are rising denials, delayed payments, growing A/R, unexplained write-offs, or inconsistent reimbursement for the same service. Audits are also worth running after a system change, after staff turnover, or whenever revenue stops tracking patient volume.
Yes — where we have something to compare against. Identifying a contractual underpayment requires the contracted rate or fee schedule for that payer. Where those are available, paid amounts are compared line by line against expected reimbursement. Where they aren’t, we identify variance by payer pattern instead and tell you which basis was used, because the two differ in how conclusive they are.
Yes. Denials are analysed by payer, reason code, procedure and workflow step to establish why claims are being denied — covering eligibility, authorization, coding, documentation and submission process issues.
Typically claim data, denial reports, remittance files (ERA or EOB) and an AR aging report, plus fee schedules or contracted rates if underpayment review is in scope. Most audits take one to three weeks depending on claim volume, data availability and scope.
Sometimes. An independent audit can find over-coding as well as under-coding, and where it does we report it plainly — knowing early is considerably better than a payer finding it during a post-payment review. An audit that only ever returns good news isn’t an audit.