Tracing Financial Discrepancies and Strengthening Internal Controls
Revenue integrity investigations begin when an amount, transaction pattern, system behavior, or operational outcome doesn't make sense. A contract may be configured incorrectly, a claim may be missing expected charges, a posting rule may conceal payment variances, or a recurring payer recovery may be handled repeatedly without resolving its cause. Each deserves investigation, but not every unusual transaction represents lost revenue or a compliance violation.
The challenge is to move from an initial signal to a supported finding. That means preserving the source evidence, defining the affected population, reconstructing the financial sequence, testing competing explanations, and assigning corrections to the teams authorized to make them. Recovering money is one possible result. Preventing another faulty transaction may be equally consequential.
The first job is to establish what really happened. Pull the claim, remittance, configuration, or ledger evidence into a defensible sequence before assigning a cause or describing the financial impact.
First, Establish What Happened
Revenue integrity sits at the intersection of documentation, coding, charge capture, contracts, claim processing, payments, and account resolution. It looks for breaks between what should have happened under applicable rules and what actually happened in the systems. Investigations can arise from routine reconciliation, audit samples, staff observations, trend reports, patient complaints, or payer correspondence.
A good lead describes the variance without declaring its cause. “Forty claims have a pricing variance” can be supported immediately; “the payer underpaid forty claims” requires contract and payment validation.
Define the Problem Before Pulling Thousands of Records
Start with a specific investigation statement: which process, population, time frame, observable behavior, and possible financial outcome are at issue? Identify who raised the concern, when it appeared, whether a recent system or contract change occurred, and whether urgent containment is warranted.
Different dates answer different questions. A claim’s date of service may determine the applicable contracted rate, while adjudication, remittance, posting, and deposit dates determine when financial activity appears. Mixing these fields can create false trends. Preserve the query filters and report version so someone else can reproduce the population.
Establish Evidence and Reconstruct the Transaction
An investigation is only as strong as the records behind its conclusion. Use approved, access-controlled systems and the minimum information needed for the assignment. Protect PHI in exports, retain the original extracts where permitted, and avoid changing live accounts merely to test a theory.
Trace representative transactions end to end before widening the query. Verify record grain: a single EFT can pay many claims, one claim can contain many service lines, and provider-level adjustments can affect a deposit without belonging to the current claim lines. Joining an EFT total to each service line will overstate cash unless the relationship is handled deliberately.
Use stable identifiers such as claim control number, encounter ID, payment or EFT trace, account ID, service-line sequence and adjustment identifiers. Reversals and replacement claims may resemble duplicates but can be legitimate independent events. Do not delete them based only on matching amounts.
Classify the Financial Exposure Correctly
Financial findings need consistent labels so exploratory reporting does not become a misleading recovery claim. A variance is the beginning of analysis, not the final financial impact.
Revenue impact may take the form of underpayment, avoidable denial, unsupported adjustment, missing charge, refund liability, patient overbilling, or processing cost. Gross billed charges are not automatically a valid estimate of lost collections. Investigations may also uncover overpayments that must be escalated for repayment review rather than counted as an opportunity for additional revenue.
Investigating Contract and Reimbursement Variances
A reliable expected payment calculation uses the appropriate executed agreement, payment methodology, amendments, fee schedule, date of service, payer product, site, modifiers, units, and claim-specific rules. An analyst may spot a candidate discrepancy using standard reports or Excel, but contract interpretation and formal rate confirmation may require managed care, contracting, compliance, or legal review.
Save the rate source, calculation formula, tested claim examples and reason an exception was included or removed. A sound escalation package gives the receiving department something it can act on, not merely a spreadsheet of red numbers.
Investigating Posting, PLBs, and Automation Failures
Revenue integrity can be compromised after a payer correctly adjudicates a claim. An automatic rule may assign money to the wrong account, write off patient balances prematurely, reapply a recovered payment that is no longer due, or post a zero-dollar informational remit as a financial transaction. The batch may balance even though individual accounts are inaccurate.
CMS explains that remittance adjustments may occur at service-line, claim or provider level. Provider-level adjustments (PLBs) can increase or decrease a payment independently of the current claim adjudications. A correctly balanced EFT does not demonstrate that every related account, receivable or adjustment was posted correctly. CMS remittance guidance provides the foundational distinction.
When PLB recoveries and reapplications repeat, construct a transaction timeline across remittances. Determine whether the amounts relate to the same recovery, a corrected claim, a payer offset against a new claim, or a local automation rule. Check whether source control numbers, payer notices, and original payments connect. Automatically reapplying each recovery can hide an unresolved cause and compound the exposure.
Find the Cause, Not Just the Transaction That Failed
Root-cause analysis moves beyond naming a person or a symptom. A recurring write-off may follow one analyst’s action but originate in a defective mapping table or unclear approval rule. Test several explanations using timelines, sample expansion, change logs, controlled comparisons, and documented replay or test-environment behavior where authorized.
A timeline and correlation do not alone prove causation. Label findings suspected, validated, or unresolved, and identify the supporting evidence. If a problem spans several workflows, it may have multiple contributing causes rather than a single fix.
Containment, Correction, and Escalation
When a control failure may still be active, the first decision is whether to contain it: pause an automation job, quarantine affected files, hold a suspicious claim batch or temporarily increase review. These actions require the appropriate authority and should be weighed against operational disruption, claims deadlines, patient access, and cash-flow consequences.
Some cases need prompt referral to compliance, privacy/security, managed care, patient financial services or legal counsel. Regulatory repayment obligations, mandatory notifications, interest, appeals, and patient billing corrections can depend on payer, program, jurisdiction and specific facts. An investigative analyst should not infer a universal legal deadline or unilaterally apply a write-off simply because an amount looks wrong.
Build Corrective Controls That Match the Failure
A corrective action that repairs only the sampled accounts is incomplete when the rule producing the error remains active. Controls should interrupt the failure where practical and provide independent evidence when prevention cannot be guaranteed. The 2025 GAO Green Book provides a useful internal-control framework, although it establishes federal agency standards and is not a blanket binding regulation for private provider billing departments.
A strong control specifies its owner, trigger, population, threshold, action on failure, evidence retained, review frequency and escalation path. “Staff will be more careful” is not a measurable control without clear procedures and verification.
Test Whether the Fix Works
Define success before releasing the change. Retest known failed cases, normal valid transactions and edge cases such as reversals, duplicates, secondary payments, negative PLBs and changed contract rates. Where possible, use a comparison period or stable denominator, and record any volume or population changes that limit interpretation.
Monitor for unintended consequences, too. A strict hold rule may reduce incorrect postings but delay valid cash application. Track the accuracy measure alongside exception backlog, time to resolve, claim filing deadlines and staff workload. Reopen the issue if error patterns recur or the process can't sustain normal volume.
Document the Investigation for Independent Review
A complete investigation workpaper lets someone unfamiliar with the case reproduce the logic and distinguish evidence from judgment. A versioned file and clear notes matter more than elaborate formatting.
Separate the workpaper from the executive summary. Leadership may need the size of the validated issue, whether the failure is ongoing, the required decisions, and the date for next verification. The underlying working files should retain the detail needed to defend those conclusions.
Common Investigation Traps
- Declaring the payer wrong based on payment alone: reconcile allowed amounts, patient cost sharing, coordination of benefits and actual contract methodology.
- Calling all credits refundable: validate ownership, reversals, prior payer recoveries and applicable refund requirements before disbursement.
- Confusing a balanced batch with accurate account posting: test the transaction destination, adjustment type and historical receivable.
- Extrapolating a targeted sample: 10 errors in a handpicked set of 20 suspicious accounts do not establish a 50% system-wide error rate.
- Using gross charges as collections impact: contract allowances, realistic recoverability and subsequent financial adjustments may differ substantially.
- Fixing account exceptions while leaving a defective bot rule untouched: validate root cause, configuration ownership and regression tests.
- Assuming every repeated PLB is invalid: trace payer recovery identifiers and historical activity before deciding that an offset is duplicated.
- Closing an issue when the correction ticket is marked complete: verify new transactions, independent reconciliations and downstream effects.
Revenue integrity is strengthened when investigation results change the conditions that allowed a discrepancy to occur. A closed claim, corrected journal entry or recovered payment addresses the transaction; a tested control addresses the risk of the next one. Both belong in a defensible resolution.
References and Further Learning
The resources below establish general remittance interpretation, healthcare compliance and internal-control principles. Payer-specific dispute rights, contract rates, state requirements and organizational approvals must be checked against their own controlling materials and effective dates.
References
Additional Learning
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.