Most practices track whether a claim was paid. Far fewer track whether it was paid correctly, at the rate the contract actually specifies. That distinction matters more than it sounds like it should. A claim that pays is easy to mistake for a claim that paid right, and payer underpayments are built to be easy to miss: a few dollars off here, a bundled code paid at the wrong rate there, a fee schedule update that never made it into the payer’s system correctly.
This isn’t about denials, and it isn’t about the revenue cycle basics covered in our guide to revenue cycle management in Dallas-Fort Worth. It’s about a narrower, frequently overlooked question: when a payer does pay a claim, is it paying the amount your contract actually says it should? For many DFW practices that have never run this specific check, the answer is no, and the gap is larger than expected.
Why Contract Compliance Is a Different Problem Than Denial Management
Denial management catches claims that didn’t get paid at all. Contract compliance auditing catches something quieter: claims that got paid, just not correctly. A denied claim shows up clearly on an aging report. An underpaid claim looks exactly like a paid claim, unless someone is comparing the amount received against the actual contracted rate for that code, that payer, and that date of service.
Fee Schedules Change More Often Than Practices Track
Payer fee schedules update annually, sometimes more often, and practices frequently continue billing and reconciling against a rate table that’s a year or more out of date. Without a current, code-level fee schedule to check against, there’s no way to catch an underpayment even if someone is looking.
Bundling and Multiple-Procedure Rules Are a Common Source of Error
Payer systems frequently misapply multiple-procedure reduction rules, bundle codes that shouldn’t be bundled, or apply the wrong modifier logic. These errors are systematic, meaning if it happened once for a given code combination, it’s probably happening every time that combination is billed.
Manual Payment Posting Hides the Problem
When staff post payments quickly to keep up with volume, without comparing the posted amount to the contracted rate, an underpayment gets recorded as “paid” and disappears from anyone’s radar. The claim is closed, the balance is zero, and nothing flags it for review again.
What a Contract Compliance Audit Actually Involves
A payer contract compliance audit is a structured comparison between what a payer actually paid on a sample of claims and what the contract says it should have paid for those same codes, modifiers, and dates of service.
Building a Current Fee Schedule Reference
The audit starts with the practice’s actual signed contracts and current fee schedules for its top payers, not assumptions or last year’s numbers. This reference becomes the yardstick every claim gets measured against.
Sampling Claims Across High-Volume Codes and Payers
Rather than reviewing every claim ever billed, an audit typically samples a representative set of claims across a practice’s highest-volume procedure codes and payers, where systematic underpayment errors have the biggest cumulative impact.
Identifying Patterns, Not Just One-Off Errors
A single underpaid claim might be a fluke. The same code underpaid by the same amount across dozens of claims from the same payer is a systematic error, and it’s the pattern that matters, because it means every future claim with that same combination will likely be underpaid again until it’s corrected.
What DFW Practices Typically Find
Underpayment patterns show up in a fairly consistent set of places across independent and specialty practices in the DFW market:
- Evaluation and management codes paid at an outdated fee schedule rate after an annual update
- Bundled procedures paid as a single unit when the contract specifies separate reimbursement
- Multiple-procedure reductions applied at the wrong percentage or to the wrong line item
- Modifier-25 or modifier-59 claims paid as if the modifier weren’t present
- Contracted rates for newer or less common codes that were never correctly loaded into the payer’s system in the first place
Why This Gets Missed Even at Well-Run Practices
Contract compliance auditing isn’t a sign that a billing team is doing a bad job. It requires a specific comparison, actual payment against actual contracted rate, at the individual code level, that most billing workflows simply aren’t built to perform as a matter of routine. Billing staff are focused on getting claims out clean and following up on denials; checking whether a paid claim was paid at the right rate is a separate, more granular exercise that competes for the same limited time.
It’s also easy to assume a payer’s system is applying the contract correctly because the payer built and maintains it. In practice, payer systems make configuration errors at the same rate any large system does, and those errors don’t announce themselves. They just quietly persist until someone checks.
Recovering Past Underpayments
Most payer contracts include a timely filing window for corrected claims and appeals, often 12 to 24 months from the date of service, which means a compliance audit can typically recover underpayments going back further than most practices assume, not just catch errors going forward.
Recovery usually involves submitting a corrected claim or a formal appeal referencing the specific contract language and fee schedule rate, with documentation showing the discrepancy. Payers don’t volunteer this correction on their own; it requires the practice, or a partner acting on its behalf, to identify the error and make the case.
Turning a One-Time Audit Into an Ongoing Safeguard
A single audit recovers what’s already been lost, but without an ongoing process, the same underpayment patterns simply start accumulating again the day the audit ends. Practices that get lasting value from contract compliance work build a recurring check into their normal reconciliation process, comparing a sample of payments against current fee schedules on a quarterly basis rather than treating it as a one-time cleanup project.
This is also where fee schedule updates need a home. When a payer issues a new fee schedule, someone needs to load it, verify it against a sample of claims, and flag discrepancies immediately, rather than discovering months later that an entire category of codes has been paid at the wrong rate since the update took effect.
Someone on the leadership team also needs to own this quarterly cadence, not just the billing staff running the comparison. For practices without a dedicated financial executive, that ongoing oversight is a natural fit for fractional financial leadership: reviewing findings each quarter, deciding which discrepancies are worth pursuing, and making sure fee schedule updates don’t slip through the cracks between audits.
How 4th Season Consulting Supports Contract Compliance for DFW Practices
4th Season Consulting’s revenue cycle management team runs payer contract compliance audits for DFW practices as a complement to standard denial management and claims follow-up, comparing actual payments against contracted rates across a practice’s highest-volume codes and payers to identify systematic underpayment.
Where audits identify recoverable underpayments, the team manages the corrected claim or appeal process directly with the payer, and where a practice wants ongoing protection rather than a one-time check, contract compliance monitoring can be built into the regular reconciliation cadence covered in our broader revenue cycle management approach.
Frequently Asked Questions
How far back can a practice recover underpaid claims?
It depends on the specific payer contract’s timely filing and appeal window, but many contracts allow corrected claims or appeals within 12 to 24 months of the date of service. This is why it’s worth auditing sooner rather than later, recoverable windows close over time.
How common are payer underpayments, really?
More common than most practices assume, because they’re built to be invisible. A claim that gets paid, just at the wrong rate, looks identical to a correctly paid claim unless someone specifically compares the payment against the contracted rate for that code and payer.
Do we need a new contract to fix this, or can existing contracts be enforced?
In most cases, existing contracts already specify the correct rates, the problem is that the payer’s payment system isn’t applying them correctly. A compliance audit typically works within the existing contract, using its language to support a corrected claim or appeal rather than requiring a renegotiation.
Is this the same thing as denial management?
No. Denial management addresses claims that were rejected outright. Contract compliance auditing addresses claims that were accepted and paid, just at an incorrect amount. Both matter, but they require different processes to catch.
How often should a practice run a contract compliance check?
A full audit is a good starting point, but ongoing value comes from a recurring check, ideally quarterly, comparing a sample of recent payments against current fee schedules, especially after any payer fee schedule update.
Find Out What You’re Actually Owed
If no one has specifically checked whether your top payers are paying at the contracted rate, there’s a good chance revenue is sitting uncollected in plain sight. 4th Season Consulting can run a payer contract compliance audit for your DFW practice and manage recovery on anything found.
Learn more about our Revenue Cycle Management services, or get started with a consultation today.
