Billing operations guide
Design a payer contract rate variance review for the billing desk
A practical method for comparing allowed amounts to contracted rates, separating carve-outs, and routing underpayment findings to an owner.
On this page
What a rate variance review is meant to catch
A payer contract rate variance review compares the allowed amount on a paid claim with the rate the contract says should apply. The review looks for underpayments, but it also surfaces wrong fee schedules, missing escalators, and claims paid under an outdated product. Scope the first pass to high-volume codes and recently renegotiated contracts so the sample stays manageable. The output is a ranked list of variances with the contract clause and claim evidence attached.
A variance is not automatically an underpayment, because a contract may allow a different rate for a site of service, a modifier, or a bundled service. The reviewer must read the payment against the same clause the contract applies before raising a dispute. Separating a true rate error from a permitted adjustment protects the billing team's credibility with the payer. It also keeps the recovery queue focused on claims that can actually be corrected.
Build a rate card from the contract itself
Build the rate card from the executed contract, its fee schedule attachment, and any signed amendment, not from a summary someone typed into a spreadsheet. Record the effective dates, the product or plan type, the place of service rules, and the modifiers that change the rate. Note the carve-outs and case rates that intentionally sit outside the fee schedule. Version the rate card and keep the source page number next to each line.
When a contract has multiple schedules, label the claim population each schedule applies to before comparing payments. A Medicaid managed care line and a commercial line may share a code but not a rate, and mixing them produces false variances. Ask the contract owner to confirm any ambiguous clause in writing. The confirmation belongs in the rate card file so the next reviewer does not reopen the same question.
Match paid claims to the right rate line
Match each paid claim to one rate line using the code, modifier, place of service, date of service, and plan. Load the allowed amount, the paid amount, the patient responsibility, and the contractual adjustment into the review file. Calculate the variance against the expected allowed amount and keep the calculation visible. A variance without a visible calculation is difficult to defend in a payer dispute.
Sort the results by dollar impact and by repeat pattern rather than by claim count alone. One high-value surgical line may matter more than fifty small office visits, while a repeated small variance can signal a fee schedule that was never loaded. Flag any line where the paid amount exceeds the expected rate, because an overpayment creates a different obligation. Treat both directions as findings that need an owner.
Separate permitted adjustments from errors
Permitted adjustments include contractual bundling, multiple procedure reductions, site of service differentials, and patient responsibility shifts. Document the clause that supports each adjustment and remove the claim from the error queue. A claim that is correctly adjusted should still be counted so the review shows how much of the apparent variance was expected. This step prevents the team from chasing recoveries that the contract does not support.
Errors include a missing escalation, an old fee schedule, a wrong product mapping, or a rate applied to the wrong provider. Route each error to the contract owner, the credentialing team, or the payer relationship owner as appropriate. Set a response date and record the payer reference number when a dispute is filed. The billing specialist can prepare the packet, but the contract owner should approve the interpretation that goes to the payer.
Recover, report, and prevent the next variance
File recovery requests through the channel named in the contract and keep the submission proof with the claim. Track the recovery status separately from the original variance so the team can see how much was recovered, denied, or still open. Reconcile the recovered amount back to the payment posting record before closing the case. A recovery that never reaches the account is not a completed review.
Report the variance rate by payer, contract, and code family each month, with the dollar impact and the age of open items. Share the pattern with payment posting and billing reconciliation so future payments are checked against the same rate card. Ask for one preventive change, such as a fee schedule reload or a contract clarification, at every review. The goal is fewer variances next quarter, not a longer list of disputed claims.
Handle small variances without losing the pattern
A small per-claim variance can still be material when it repeats across hundreds of claims. Aggregate the low-dollar lines by payer and code before deciding to ignore them. If the total exceeds the review threshold, treat the group as one finding with a single owner. A variance policy that looks only at individual claim size will miss the most expensive pattern.
Rebuild the expected rate whenever a contract is amended or a fee schedule is loaded. Compare the new rate card with the old one and list the codes that changed. Send the list to the posting team so they know which payments to watch in the first month after the change. Most rate errors appear at the seam between an old contract and a new one, and a short watch list catches them early.
Authoritative references
Philippines staffing intake
Define the role before hiring begins.
Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.
Contact Us