Key Points
- A claim can be paid in full while a coding omission leaves reimbursement for documented care unclaimed.
- Source-to-bill reviews should compare care records with codes, charges and payer rules before assigning a financial benefit.
- Independent review needs clear ownership, escalation rights and separate reporting for corrections, payment differences and cash recovered.
Consider an illustrative case in which the procedure and payer rules require a bilateral modifier for additional reimbursement. A surgeon documents the bilateral procedure. The submitted claim omits the required modifier, and the contract engine calculates expected payment from that claim. If the payer pays the calculated amount, the variance report can show zero and the account can close as paid in full.
Clean-claim, denial, and collection-timing measures may give the CFO no reason to revisit that encounter. The payment matches the submitted claim, while the coding omission leaves the additional reimbursement for documented care unclaimed.
Before the next automation investment, I want executives to ask: how do we know the bill represents the documented care under the applicable billing rules? Collection results show how effectively payment was received against the bill. Establishing whether the bill was correct requires a check against the underlying records and rules.
Connected Systems Can Carry the Same Error Forward
As providers connect documentation, coding, charge capture, and billing, each stage relies on information from the one before it. The resulting claim supplies the expected payment calculation. If an error carries through those stages unchecked, their outputs can agree while preserving the original mistake.
The same risk applies to a charge mapped to the wrong revenue code or a contract term loaded incorrectly in the payment model. A check that repeats the configured calculation can reproduce the result while leaving the underlying assumption untested.
Revenue integrity therefore needs access to the original care records and billing rules. Professional guidance already calls for comparing medical records with charges and claims, including prospective coding review before submission [1]. HFMA’s performance measures for the revenue cycle draw on submitted claims, recorded charges, payments, and receivables [2]. I would pair those measures with source-to-bill checks that test whether documented care was represented correctly.
For AI-based workflows, NIST’s AI Risk Management Framework recommends assessment by independent assessors or internal experts outside front-line development [3]. I would apply that principle to revenue-cycle automation more broadly, with controls suited to each workflow. Alongside speed and accuracy targets, require two answers before funding: which source records and rules can the verification process test, and who has authority to challenge an automated decision?
Start From the Record of Care, Then Validate the Money Separately
In the bilateral example, the operative note provides evidence needed to test the assigned code and modifier. A review confined to the claim may miss the discrepancy. Examine whether the documentation supports the procedure, diagnosis, modifiers, and units, and reconcile documented services to the charges that reached the bill. Where documentation is incomplete or contradictory, use the appropriate clinical clarification process.
When the error sits in a charge item, price, unit, or system mapping, establish the affected population and the period involved. Correct the configuration and review the related encounters. Chart-to-bill audits are an established method for finding missing, duplicate, and incorrect charges [4]. Follow approved corrections through the affected accounts and verify that the change worked.
Then determine the reimbursement the corrected claim supports under the payer contract, coverage rules, and authorization requirements. Compare that amount with what was paid and what the patient was billed. Validate the financial consequence separately from the billing correction. Under Medicare, inpatient payment may be based on the case, and certain outpatient services are packaged into another payment [5]. A corrected packaged-supply charge may improve billing accuracy without changing payment for that encounter. Check the applicable payment rules, including any outlier effect, before assigning a financial benefit. Reporting a charge correction as recovered cash before payment is received overstates the result.
Independence Has to Be Written Into the Operating Model
Who owns the review of a paid claim against the care record? Clean-claim rate and days in A/R alone provide an incomplete answer. Someone needs explicit responsibility for investigating coding and charge accuracy even after the account closes.
Revenue integrity needs a defined route to challenge coding, charging, contract configuration, and payment decisions: access to source evidence, an escalation path for disputed interpretations, and qualified approval for changes. Assess reviewers on accuracy and completed corrections as well as financial results.
The test has to run in both directions. A credible program pursues missed reimbursement and addresses unsupported charges, excess payments, and inaccurate patient balances. Following the evidence wherever it leads is what earns the authority to correct.
This applies to a provider’s own coding and billing teams, and it applies with equal force to an outsourced partner. Where the same organization produces and reviews the bill, review ownership and escalation rights need to be explicit and in writing. Unresolved findings need a route to the client that allows them to be considered independently of the team whose work is under review.
What Sutherland Does with the Responsibility
Sutherland Revenue Integrity covers U.S. hospitals, health systems, and physician groups, from patient access and authorization through documentation, coding, charge capture, billing, payment review, and post-payment follow-up, drawing on our revenue-cycle services. Our payer operations work informs the review of payment decisions: we know how adjudication logic and contract configuration produce a number, so we know where to test it.
The expectations above bind us too. Where Sutherland performs both production and review, clients should know who can challenge a coding or billing decision, how that challenge is escalated, and how an approved correction reaches the affected accounts. We would rather be asked that question during the sales process than after go-live.
The Report the CFO Should Ask For
Report four categories separately: confirmed billing errors and their assessed financial impact, validated payment differences, cash actually recovered, and amounts still under correction or investigation. Link each category back to the underlying findings so the same benefit is counted once. This gives the CFO a clear view of completed corrections and work still open.
As more revenue-cycle work becomes automated, improved collection results still need to be backed by checks on the original bill. Someone must be able to examine the record of care, question the billing decision, and carry an approved correction through the affected accounts. That is a responsibility for revenue integrity. Fund it with the authority to do the job.
If your clean-claim and payment reports cannot show whether the original bill reflects documented care, talk to Sutherland’s revenue-cycle team. We can help you examine where errors enter the process, establish who can challenge them, and separate billing corrections from cash actually recovered.
Rajesh Reddy
VP, Healthcare Vertical
