Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →

Tariff mismatch: the deduction that repeats every month

Contracts get revised. Rate cards do not. The difference is deducted silently until someone reconciles the two.

BLOG · PAYER MECHANICS
● Format mechanism table
● Invented stats 0
● Figures worked arithmetic
✓ no figure without its working

Payer mechanicsHospital sideUpdated Aug 2026

In short

Billing above the contracted rate is the most mechanical deduction there is, and the most recoverable. It usually means a contract revision never reached the rate card, so every claim since then carries the same error.

What sets it off.

A payer revises rates. The revision arrives as an email or an annexure. Nobody loads it. Billing continues against the superseded card.

Because it repeats, the total is large even when the per-claim amount is small. It also looks like a payer problem when it is a data problem.

What you need in the file.

The signed contract with its effective date, against the rate card version your billing actually runs on. If those two dates differ, every claim in between is affected.

Payers will generally accept a correction and reprocess where the error is theirs. Where it is yours, the deduction stands — which is why finding it quickly matters more than arguing it.

The minute where it is still fixable.

Import rate cards by pasting from the spreadsheet the payer sent, rather than retyping. Retyping is where transcription errors enter.

Then a standing check: billed rate against contracted rate, flagged before the claim goes out. One correction clears every future claim on that line.

Why it compounds quietly

A tariff error on one claim is small enough to write off. The same error on every claim for that procedure, for a quarter, is not. Because each instance looks trivial, nobody escalates it, and because it looks like a payer deduction, nobody looks at the rate card.

The pattern is easiest to see in aggregate: the same deduction reason, the same procedure, repeating. One line in a monthly report showing repeated deduction reasons ranked by total value would surface it in the first month.

This is also the ground most worth aggregating before querying. One instance is a phone call. Forty instances is a contract conversation, and a much better one, because you are no longer arguing about a single patient.

Keeping rate cards current

Import by pasting the payer's own spreadsheet rather than retyping. Transcription is where most errors enter, and a retyped rate card is a second source of truth that will diverge.

Record the effective date against every version. When a deduction arrives, the first question is which version was in force on the date of service — and without effective dates that question cannot be answered.

For groups, compare the same payer and procedure across branches. Divergence between your best and worst branch rate is what fragmented negotiation has cost you, and it is usually a bigger number than the deductions.

The patient-facing version of this ground, for handing to a family: claim help. The mechanism in full: every way an Indian payer reduces a claim.

Questions we get asked

Is tariff mismatch recoverable?

Often yes, where the error is the payer's. Where the rate card was simply not updated, the deduction generally stands — so speed matters more than argument.

How do you find it?

Compare the effective date of the signed contract against the version your billing runs on. A gap means every claim in between is affected.

Find these in your own settled claims

Twenty claims you have already settled, classified by ground, split into predictable and unexplained. About an hour of your team’s time.

The mechanism above, on your own numbers.

Nothing on this page is a promise. Bring a month of settlements and we will read them with you.