An underpayment is not simply the difference between the amount billed and the amount received. It is a shortfall against the payment due under the applicable contract after legitimate adjustments. If that expected amount is wrong, the team creates a false recovery case. If it is never calculated, genuine gaps can pass unnoticed.
01 / THE BASELINE
Calculate the expected amount first
Start with the insurer and plan, the contract version effective on the service date, the facility or rendering provider, the service and any applicable modifiers or units. A fee schedule quoted for a different provider, location or period is not a reliable baseline. Keep the contract clause beside the calculation so another reviewer can reproduce it.
Separate billed charge, allowed amount, insurer responsibility and patient responsibility. The insurer may correctly pay less than the charge. A short payment exists only after the contracted method, coverage, patient share and agreed adjustments have been applied.
- Version: which agreement and effective date controlled this service?
- Method: fixed fee, percentage, package, tier or other agreed basis?
- Scope: which clinician, facility, service, unit and plan does the rate cover?
02 / CONTRACT INTERPRETATION
Different contract methods create different expectations
A fixed service fee, percentage of a schedule, case package and tiered rate do not produce the same expected payment. Before calculating a variance, identify the governing method and whether the service is bundled, capped, subject to a provider tier or adjusted for units. The effective date matters when rates changed during a quarter. Store the source clause and each input so a reviewer can reproduce the number from the agreement and claim.
Patient share and insurer liability also need separating. A BHD 50 allowed amount with BHD 10 properly assigned to the patient can yield BHD 40 from the insurer without any underpayment. Conversely, an insurer's BHD 40 payment may still be wrong if the contracted insurer share was BHD 50 and the remittance assigned an unsupported adjustment. The audit question is not 'Was cash lower than charge?' but 'Which party owed what under this agreement?'
03 / THE REMITTANCE
Compare like with like at line level
Match each remittance line to the original claim line and account for partial denials, offsets, reversals and later payments. The useful equation is expected insurer payment minus actual insurer payment after valid adjustments. A claim can contain a denied line and an underpaid approved line; those require different recovery paths.
When a remittance is missing or cannot be matched confidently, show it as an exception rather than manufacturing a variance. Reconciliation should also catch overpayments, duplicate payments and a claim marked 'paid' while a balance remains unexplained.
BHD 7 is a question, not yet a finding
Suppose a service has a contracted allowed amount of BHD 50 and the insurer is responsible for all BHD 50. The remittance shows BHD 43. The apparent variance is BHD 7. Confirm no valid patient share, package adjustment, later payment or contract exception applies before classifying it as an underpayment.
04 / VALIDATION
A variance should survive the obvious alternative explanations
Check for secondary payments, later remittance cycles, reversals and replacement claims before opening a recovery case. Then test legitimate contractual exclusions, coordination of benefits, patient share, package logic, quantity limits and agreed discounts. A payment posted to the wrong claim can appear as both an underpayment and an overpayment until reconciliation is fixed.
Set a confidence state for each finding: confirmed, likely, or unresolved because a contract or remittance is missing. Do not silently classify an unmatched payment as zero. When a rate engine produces repeated false alerts, record the reason and update the rule with an effective date. Otherwise the recovery team spends its time disproving its own software instead of pursuing real differences.
- Confirmed: contract, claim and remittance are matched; no valid adjustment explains the shortfall.
- Likely: the pattern is plausible but a clause or subsequent payment needs review.
- Unresolved: key evidence is missing; do not state a recoverable BHD amount as fact.
05 / FROM ONE TO MANY
A repeated small gap may be the real issue
A single BHD 7 discrepancy may be worth checking but not enough to establish a payer pattern. If the same service, provider and insurer show that gap on 2,000 otherwise comparable claims, the arithmetic suggests BHD 14,000 in potential variance. That figure still needs line-by-line validation; it is not recovered revenue.
Group the affected claims by payer, service, dates, contract version and adjustment reason. Look for a coding or place-of-service mismatch, an outdated rate, a contract interpretation difference or a downcoding pattern. The group helps a human decide whether to correct internal billing, ask the insurer to reprocess, or raise a contract question.
06 / FROM BHD 7 TO BHD 14,000
Test the sample before multiplying the difference
If a dashboard shows a BHD 7 gap on 2,000 claims, begin with a stratified sample across service dates, facilities, provider types and remittance reason codes. Confirm that each sampled claim uses the same contract version and reimbursement logic. If 20 sample claims include five valid patient-share adjustments, the headline BHD 14,000 figure is already overstated and the cohort must be split before any payer inquiry.
After validating the cohorts, calculate exposure as the sum of individual expected insurer payments minus actual insurer payments, not simply a single average multiplied by the total count. Preserve the claims excluded as duplicates, reversals or valid adjustments. This makes the payer packet defensible and prevents a dramatic example from becoming a misleading financial claim.
Take the BHD 14,000 signal down to claim level
sehaXG can compare each paid line with the rate applicable on its service date and group the apparent BHD 7 differences by insurer, service and contract version. The reviewer can inspect sample remittances, exclude valid patient-share or later-payment cases and keep the remaining claims as a defensible investigation cohort.
Each validated case then has the contract clause, expected and actual payment, inquiry deadline and owner beside it. The dashboard separates potential exposure from BHD actually recovered after a new remittance is posted.
Explore sehaXG Intelligence07 / THE RECOVERY FILE
Send evidence, then confirm the money
A recovery file should include the claim and remittance identifiers, affected lines, the relevant contract clause, a reproducible expected-payment calculation and the exact BHD difference. Check the insurer's inquiry or appeal window before sending it. Prioritize by validated amount, likelihood of correction, time limit and effort—not by the largest raw billed charge.
After the inquiry, record the insurer response and reconcile any adjustment or additional payment. If the insurer confirms its interpretation, the team may need a contract discussion rather than repeated identical appeals. If the original calculation was wrong, correct the rate logic so future false alerts stop.
08 / OPERATIONAL ROUTINE
Make payment review a recurring control
Each cycle, ingest new remittances, match them to claim versions, apply the contract effective on each service date and queue only unexplained variances. Have a contract owner review new amendments and a revenue owner review high-value exceptions. Record the inquiry deadline, payer response and final posted payment for every pursued case. A recovered claim without a corrected rate rule can leave the next month's claims exposed.
Report validated variance BHD, amount queried, amount acknowledged by the insurer, cash actually recovered, unresolved aging and false-alert rate. Break the numbers down by payer and contract rule, not just by staff member. That shows whether the problem is adjudication, ambiguous contract wording, internal posting or the audit model itself—and whether a process fix is worth more than another individual appeal.
THE NEXT STEP
Make paid claims auditable
The practical value of an underpayment process is a traceable answer: what should have been paid, what was paid, why they differ and what happened after follow-up. sehaXG's revenue-intelligence direction puts that question beside the claim, remittance and payer pattern.