The problem to investigate
A single payment line may not represent the final reimbursement. Later adjustments, patient responsibility, or related payment events can explain part of an apparent variance.
Common causes to check
- Payment events reviewed in isolation
- Claim revisions not linked to the original
- Expected amounts based on incomplete terms
What your organization should review
- Identify the claim and version under review
- Assemble the available payment and adjustment history
- Document the basis for expected reimbursement
Verification and supporting evidence
Keep the claim reference, applicable agreement evidence, payment records, and calculation assumptions. Record unresolved inputs separately from verified differences.
Synthetic review example
In a synthetic example, a claim receives an initial payment and a later adjustment. Reviewing both events resolves part of the apparent shortfall before any remaining difference is evaluated.
How this fits the AuditRes workflow
Use the Medical reimbursement-recovery workflow to organize the variance and supporting evidence for review, retaining the QA-only data restriction.
AuditRes Medical brings reimbursement analysis, underpayment review, evidence, and resolution workflows together. Examples in this guide are synthetic. A payment variance needs a supported expectation and human review; it is not, by itself, a verified underpayment or realized recovery.
Frequently asked questions
Does a payment below the billed amount prove underpayment?
No. The comparison needs a supported expected reimbursement, not simply the charge amount. Contractual and payment context matter.
Are these examples based on real patients or recovery results?
No. All examples are synthetic educational scenarios. Medical remains in its QA phase; no real PHI should be submitted and no production compliance certification is claimed.