Pre-Bill vs. Post-Bill Coding Audits: What Each One Catches
A pre-bill coding audit reviews accounts before the claim goes out, so coding errors can be fixed before they lead to a coding-related denial or an overpayment. A post-bill audit reviews claims after submission, usually by sampling, to measure accuracy, spot patterns, and find compliance risk. Pre-bill audits help reduce coding problems on individual claims but can delay billing. Post-bill audits reveal trends and coder performance but find errors after the fact. Many organizations use both, with pre-bill audits focused on high-risk accounts and post-bill audits used for ongoing monitoring.Coding errors are expensive in both directions. Under-coding leaves money on the table, while over-coding creates denials, repayment obligations, and audit exposure. A coding audit is a systematic review of coded records against clinical documentation to measure accuracy and identify risk. The important decision is when to audit. This article explains how the two approaches differ, what each is best at catching, and how to combine them.
What Is a Pre-Bill Audit?
A pre-bill (also called prospective) audit reviews the coded account before the claim is submitted. Reviewers check the codes against the documentation and correct problems on the spot.
What it tends to catch:
Missing or incorrect diagnosis and procedure codes
Incorrect modifiers or code combinations that trigger edits
Documentation gaps that leave a code unsupported
Missed charges or codes that reduce reimbursement
DRG assignment that does not match the clinical picture
Strengths: Helps prevent coding errors from turning into coding-related denials or overpayments. It cannot prevent denials caused by eligibility, authorization, medical necessity, or payer processing issues. Gives coders immediate feedback.
Limits: Adds time before billing, which can increase DNFB days and slow cash. It is resource-intensive, so reviewing every account is often not practical. Targeted reviews of higher-risk accounts are a recognized approach.
What Is a Post-Bill Audit?
A post-bill (also called retrospective) audit reviews a sample of claims after they were submitted and, often, paid. The goal is to measure accuracy and find patterns.
What it tends to catch:
Error rates by coder, specialty, facility, or code type
Patterns of over-coding or under-coding
Compliance exposure that could draw payer or government scrutiny
Education needs for coders and physicians
Weaknesses in claim edits and documentation practices
Strengths: Provides a measurable accuracy rate and helps target training. It does not delay the original claim submission. Accuracy can be calculated per code or per record, with or without weighting, so define your method before comparing rates with other organizations.
Limits: Errors are found after submission, so correcting them may mean rebilling or refunding. For Medicare, an identified overpayment generally must be reported and returned by the later of 60 days after identification or the date the related cost report is due. Commercial payer requirements depend on contracts, state law, and payer policy, so involve compliance or legal counsel.
Side-by-Side Comparison
| Factor | Pre-Bill Audit | Post-Bill Audit |
|---|---|---|
| Timing | Before claim submission | After submission or payment |
| Main purpose | Reduce coding errors before billing | Measure accuracy and find patterns |
| Scope | Targeted, high-risk accounts | Sample of claims |
| Best at catching | Individual coding, DRG, and documentation errors | Trends, coder performance, compliance risk |
| Effect on cash flow | May delay billing | No delay to the original claim |
| Cost profile | Varies with scope, volume, and automation | Varies with sample size, method, and who performs the review |
| Correction path | Fix before billing | May require rebilling or refunds |
| Best used for | High-dollar, complex, or error-prone accounts | Ongoing monitoring and education |
Which Should You Choose?
For many hospitals and physician groups, the answer is both, for different purposes.
Use pre-bill audits for high-dollar inpatient cases, accounts with known error patterns, new coders in training, and service lines with recent denial spikes.
Use post-bill audits for routine monitoring, coder accuracy scoring (many organizations use 95 percent as a benchmark), and compliance risk reviews. Rotate the sample across coders, payers, and code types.
Connect the two. Feed post-bill findings back into education, claim edits, and pre-bill audit targets. If post-bill audits keep finding the same problem, add it to your pre-bill review list.
A Practical Starting Framework
Baseline first. Run a post-bill audit on a representative sample to learn your current accuracy rate and top error types.
Target pre-bill reviews at the areas where errors cost the most.
Set a cadence. Common patterns are monthly or quarterly post-bill samples, with pre-bill reviews on defined account types.
Track results. Follow accuracy rate, denial rate by coding-related reason, DNFB days, and rebilling volume.
Educate and re-audit. Use findings for coaching, then confirm improvement in the next cycle.
In-House vs. Outside Audit Partners
Internal teams know your workflows, but independent reviewers offer objectivity and added capacity. Many organizations use both. When comparing partners, ask about auditor credentials, sampling methods, turnaround time, how findings are reported, and whether they support education. Our guide on autonomous coding vendor questions is helpful if automation is part of your coding plan, and CDI Specialist vs. Medical Coder explains how documentation and coding roles work together.
Where to Find Audit and Coding Partners
RCR|HUB lists Business Partners across medical coding audit and accuracy services, audit services, coding software, CDI, and billing compliance. For outsourced coding, see onshore and offshore coding services. Business Partners can subscribe to RCR|HUB's RFP Access Network for access to researched, live RFP opportunities and the hospital and healthcare organization directory.
-
Neither is inherently more accurate. They answer different questions. Pre-bill audits fix individual claims, and post-bill audits measure overall performance.
-
It depends on volume, risk, and your compliance policy. Many organizations sample per coder and per code type so results are meaningful, and increase samples where errors appear.
-
They can if applied too broadly. Focus them on high-risk accounts and set turnaround targets to protect DNFB days.
-
Look at webinars and virtual education. RCR|HUB is expanding its webinar series beginning with ZYNC Tech Group, with additional Revenue Cycle topics and conversations to follow.
-
Certified auditors or experienced coders with strong knowledge of coding guidelines and payer rules. Independent auditors add objectivity.