Every lab deals with billing errors. Incorrect codes, missing modifiers, timely filing issues: these are frustrating, but they're visible. Your billing team knows they exist and has workflows to address them.
The billing errors that do the most damage are a different category entirely. They're systematic, invisible to standard reporting, and often persist for months before anyone realizes something is wrong. By the time they surface, the financial impact has already compounded.
This page covers both: the common errors every lab should have controls for, and the less visible errors that tend to be far more expensive.
Errors Your Billing Team Is Already Watching
These are the billing errors most labs have some level of visibility into. They're worth reviewing, but they're rarely where the biggest losses are hiding.
Incorrect or unsupported diagnosis codes
Diagnosis codes that don't support medical necessity are one of the most common reasons lab claims are denied. Medicare and many commercial payors require specific ICD-10 codes to justify testing. Claims submitted with unsupported or unspecified codes are denied on receipt.
The fix: Regular audits of diagnosis code usage by test type and payor. LCD (Local Coverage Determination) compliance reviews for high-volume tests.
Missing or incorrect modifiers
Modifiers communicate additional information about a service: whether a test was repeated, performed under specific circumstances, or requires separate reimbursement. Missing or incorrect modifiers are a frequent source of denials and underpayments.
The fix: Modifier audits by CPT code and payor. Billing system configuration review to ensure modifiers are applied consistently.
Timely filing failures
Every payor has a filing deadline. Claims submitted after that deadline are denied regardless of medical necessity or coding accuracy. In high-volume lab environments, timely filing denials can accumulate quickly.
The fix: AR aging reports reviewed regularly. Claims approaching filing deadlines flagged for priority follow-up.
Duplicate claim submissions
Resubmitting a claim that's already been adjudicated, or is still in process, results in a duplicate denial and can trigger payor audits. Usually caused by manual resubmission workflows without adequate claim status checks.
The fix: Claim status verification before resubmission. Billing system duplicate-check configuration review.
The Errors That Are Actually Costing You the Most
The billing errors above are manageable because they're visible. The errors below are in a different category: systematic, invisible to standard reporting, and inclined to compound silently for months before anyone finds them. The list isn't exhaustive. It's a cross-section of the kinds of issues this work is designed to surface. For specific examples — how each was found and what was recovered — see the case studies page.
Payor underpayments with no visible flag
When a payor underpays a claim, most billing systems post the payment and move on, particularly if the claim carries a denial code that auto-clears on remit posting. The claim appears resolved. No error flag. No follow-up queue. The unpaid claims aren't on the “no activity” report (they have remit activity) and aren't on the error report (the denial cleared). They sit in a blind spot that no standard report is designed to catch.
The fix: Custom exception reporting that looks specifically for remit-posted, error-cleared claims with $0 payments. Payor-level payment trend analysis against contracted rates.
LIS-to-billing system transmission errors
Every lab has at least one integration between its lab information system and billing system. That integration is a potential point of failure, and transmission errors rarely present as transmission errors on the billing side. A field that exists correctly in the LIS gets dropped, truncated, or reformatted during transmission. Both systems appear to be working normally. The gap between them is invisible unless someone looks at both at once.
The fix: Systematic LIS-to-billing reconciliation. Field-level comparison of data across systems, not just claim-level audits.
HL7 transmission formatting errors
Labs that receive orders from multiple EMR or ordering systems are exposed to a specific category of risk: each vendor's HL7 configuration is slightly different, and those differences can introduce errors that look like ordinary claim rejections. From the billing team's perspective, every affected claim looks like a routine coding denial; there's no indication they all share a single vendor-side root cause.
The fix: HL7 log analysis comparing raw transmission output across vendors. Rejection rate analysis by ordering source. Root-cause isolation before individual claim rework begins.
Auto-clearing logic that creates blind spots
Billing systems use auto-clearing rules to manage claim workflows efficiently. The rules usually work as intended. They can also hide real problems: when a denial code clears automatically on remit posting, claims that should require follow-up disappear from the work queue. If a payor is exploiting that logic, those claims become permanently invisible to standard reporting.
The fix: Regular audits of auto-clearing configuration. Exception reporting designed specifically to surface claims that cleared automatically but were never paid.
Submission routing that fails silently at the clearinghouse
“Submitted” inside a billing system isn't the same as “accepted” at the clearinghouse, and isn't the same as “received” by the payor. When a routing or enrollment configuration is wrong for a subset of payors, claims can leave the billing system marked as submitted, get rejected at the gateway, and never come back as a denial. Internally everything looks active. Externally, the payor never received the claim.
The fix: Acknowledgment-level reconciliation against 277CA / clearinghouse reports: comparing what the billing system says was submitted against what the clearinghouse actually accepted.
Eligibility integrations selecting the wrong plan
Real-time eligibility doesn't always pick the right coverage when a patient has more than one active plan. Different vendors handle coordination of benefits differently, and the default behavior often isn't correct for how a lab actually bills. Claims go to the wrong primary, get denied or paid as secondary, and the resulting balance shifts to the patient, even though eligibility itself “succeeded.”
The fix: Audit how eligibility responses are being interpreted. Compare the plan billed against the plan returned as primary. Adjust selection logic to evaluate COB rather than defaulting to response order.
NCCI bundling that suppresses reimbursement quietly
NCCI procedure-to-procedure edits don't always look like denials. Sometimes they look like a $0 line on an otherwise paid claim. When commonly co-ordered tests are bundled without the appropriate modifier, the lab can be losing reimbursement it's contractually entitled to — without a single denial code triggering a review.
The fix: Line-level expected-vs-actual comparison against the contracted fee schedule. Modifier configuration review for procedure pairs that appear together routinely.
Stale LCD and medical-policy edit tables
LCDs, NCDs, and payor medical policies change. Edit tables that aren't actively maintained drift behind those changes — scrubbing out claims with diagnoses that are now valid under the live policy, or letting through claims that aren't. Denials climb on high-volume tests with no clear cause, and the root issue is internal configuration rather than ordering-provider behavior.
The fix: A recurring policy-refresh check tied to MAC bulletins and payor policy updates. Edit-table reconciliation against the current LCD text, not the version loaded at go-live.
Test codes that exist in the LIS but aren't linked to a CPT
New assays go live. Orders flow in. Results post on time. The billing impact never appears, because the test code has no CPT mapping in the billing system. The orders don't reject and don't error; they simply never produce a claim, because the billing system has nothing to bill. Volume in operations climbs while the corresponding revenue line stays flat.
The fix: Reconciliation between resulted-test volume in the LIS and billed-claim volume in the billing system, broken out by test code. Mapping verification on every new assay before it goes live.
Why These Errors Persist Even in Well-Run Labs
The labs where these errors exist aren't poorly managed. They typically have experienced billing staff, established workflows, and regular reporting reviews.
The problem is structural. Billing teams are built to process volume: submissions, denials, appeals, follow-up. There's rarely bandwidth for the kind of cross-system analysis that would surface a transmission error or a reporting blind spot.
Standard reports also aren't designed to find what they weren't built to look for. A payor underpayment that auto-clears won't appear on a denial report. A transmission error that drops an address field won't appear on a claim error report. An HL7 formatting problem won't appear on anything; it will just look like a slightly elevated rejection rate from certain ordering sources. A test that was never linked to a CPT won't appear in any billing report at all, because the billing system never saw it.
These errors persist because finding them requires a different kind of work: cross-system reconciliation, custom exception reporting, and root cause investigation rather than claim-level follow-up.
What to Do If You Suspect a Problem
A few indicators that something systematic may be happening in your lab's billing environment:
- AR aging that won't resolve despite active follow-up
- Write-off rates that have been climbing gradually
- Denial rates from a specific payor that seem higher than expected
- Reconciliation reports that never quite tie between systems
- A persistent sense that the numbers look slightly off, but nothing specific flags
None of these are proof of a problem. Any of them, however, is a reason to look more carefully than standard reporting allows.
The Most Expensive Billing Errors Are the Ones Nobody Is Looking For
Standard billing audits catch the errors your reporting is designed to surface. Revenue recovery work finds the ones it isn't. If your lab has AR that won't resolve, write-offs that seem high, or reports that don't quite add up — that's worth investigating beyond the standard workflow.