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

Your rate card changed. Did your billing system find out?

A tariff revision that nobody loaded produces a deduction on every claim until somebody notices.

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

Hospital sideHospital sideUpdated Aug 2026

In short

A rate card is not a document, it is a document with a date. Billing against last year’s version is not a dispute you can win, because you agreed to the current one.

What has to be recorded

What a hospital records per payer contract so a rate revision cannot silently drift
FieldWhy it matters
Payer and planRates differ by plan under one insurer
Version referenceWhich notified or agreed list this is
Effective fromThe treatment date decides the version, not the billing date
Effective toBlank until superseded; set when the next version loads
Loaded by, loaded onSomebody is accountable for the version in force
Claims priced under itSo a retrospective correction has a defined scope

The date that governs is the treatment date

This is the detail most often got wrong. A claim for treatment in March, billed in May, is priced under the March version. A system that prices against “current” silently misprices every claim that straddles a revision.

Why the last row matters most

When a revision is discovered late, the only useful question is which claims were priced under the superseded version. Without that list the choice is between reviewing everything and reviewing nothing, and hospitals reliably choose nothing.

Questions we get asked

Which rate card version applies to a hospital claim?

The version in force on the date of treatment, not the date of billing or submission. A claim for care delivered before a revision is priced under the earlier list even if it is billed afterwards, which is why a rate card has to be stored with effective-from and effective-to dates rather than simply replaced.

How do rate card revisions cause repeat deductions?

A revision that nobody loads means every subsequent claim is priced against a superseded list, and each one is disallowed down to the agreed rate. Because the cause is identical every time, the deductions look like a payer pattern rather than a data problem, and often run for months before anyone connects them.

On the figures in this piece. Every rupee amount above is arithmetic on the assumptions stated beside it, not a market statistic. Where you need published Indian claim data with its source named, that sits on claim data. We publish no figure we cannot show the working for.

Read the mechanism. Now check your own numbers.

Bring twenty settled claims, advices only, patient details redacted. We name the clause behind each reduction and you keep the findings.