Executive summary. Reconciliation confirms that two records agree. Revenue integrity confirms that the amount received matches what the contract and the claim actually support.
Definition
Revenue integrity is the practice of measuring the gap between expected and realized revenue, then resolving each gap under a documented rule.
Where the two diverge
Reconciliation compares records that already exist: an adjudication response, a remittance, a bank deposit, a general-ledger entry. A perfectly balanced reconciliation can still sit on top of an underpaid claim, because nothing in the comparison asks what the claim should have paid.
Revenue integrity builds that expectation first, from the claim, the governing contract terms, acquisition cost, service evidence, and any program rules that apply. A reconciled transaction can be closed. A revenue-integrity case stays open until its variance is explained, corrected, appealed, accepted, or written off under a rule someone can point to.
The case model
A durable case keeps source events immutable and records conclusions separately, so a later adjustment cannot overwrite the facts that created the case. The fields that carry the work are expected value, realized value, variance, reason classification, evidence links, owner, deadline, and outcome.
Expected reimbursement is rarely one number. It may come from a contract formula, a published schedule, a negotiated rate, a prior authorization decision, or an estimate made under time pressure. Record which basis was used and how confident it is. Those two facts decide which cases a reviewer works first.
From variance to recovery
Detection opens a reviewable work item. The reviewer confirms the source data, reads the controlling agreement and the clinical documentation, then picks a path: correct and resubmit, appeal, open a payer inquiry, or accept the variance.
Traceability is what makes the loop worth running. Every recovery should point back to the variance that started it and the evidence used to resolve it. Patterns in closed cases then become the detection rules for the next quarter.
Frequently asked questions
Can reconciliation software detect underpayments?
It can surface a discrepancy. Turning that discrepancy into recovered money takes an explicit expectation model and a resolution workflow with owners and deadlines.
Should every variance become a case?
No. Set thresholds for materiality, confidence, filing deadlines, and cost to recover, and keep them visible so a reviewer can challenge them.
Referenced standards and further reading
- CMS: Medicare claims processing manuals ↗Centers for Medicare & Medicaid Services
Related articles
Choose the expected reimbursement basis first →