Hospital Billing Software in India: OPD, IPD, Cashless

Hospital billing in India is not one job. It’s three, and they barely resemble each other. The OPD counter needs speed and UPI. The IPD ward needs a running account, package rates, and a discharge settlement that ties out to the rupee. And the insurance desk runs a separate track entirely: TPA pre-auth, queries, and a final claim that has to clear against IRDAI timelines. Buy software that only does one well and the other two end up on spreadsheets.

This guide sorts what hospital billing software actually has to handle across those three worlds, what GST really applies (most clinical services are exempt, room rent isn’t always), what to look for in a package and TPA engine, and where clean clinical documentation quietly makes billing easier without pretending to be a billing engine.

Key takeaways

• Hospital billing spans three worlds: high-volume OPD (cash/UPI), IPD (bed charges, packages, interim bills, discharge settlement), and cashless claims (TPA pre-auth, IRDAI timelines, NHCX direction). One tool has to carry all three or your desks fragment.
• Health care services by a clinical establishment are GST-exempt under CBIC Notification 12/2017, but room charges above ₹5,000/day carry 5% GST since July 2022. Your billing engine has to apply the split correctly.
• The billing features that matter: a package and tariff master, an interim-bill and discharge-settlement flow, a TPA pre-auth and claims queue, and a tight audit trail.
• Clean documentation feeds cleaner claims. A complete discharge summary means fewer TPA queries. That’s where an ambient scribe helps, upstream of billing.
• When IPD, packages, and cashless are daily work, a dedicated billing/HIS module usually beats bolting billing onto a clinical EMR.

Sources: CBIC Notification 12/2017-CT(Rate); CBIC Notification 04/2022-CT(Rate); IRDAI Master Circular, 29 May 2024.

If your OPD billing already runs clean and the pain is IPD reconciliation or a TPA queue that never empties, jump to the sections on those. If you’re buying fresh, start with the three worlds and be honest about which two you’re weakest on today.

OPD billing: fast, high-volume, cash and UPI

Picture the front desk at a mid-size Pune hospital at 8pm. The OPD has cleared two hundred patients since morning, the queue still has thirty, and the cashier is switching between a UPI QR, a card machine, and a cash drawer without missing a beat. OPD billing lives or dies on that speed.

What OPD billing actually needs is short:

• A bill that closes in seconds: consult fee, a lab line, a pharmacy line, done.
• Every payment mode at the counter: cash, UPI, card, and a running tab for corporate or credit patients.
• A queue and token flow so the counter isn’t the bottleneck.
• GST applied right, which for most clinical services means nil (more on that below).

Most billing tools handle OPD counter billing competently. It’s the simplest of the three. The mistake buyers make is judging a whole hospital system on a slick OPD demo, then discovering the IPD and cashless sides are thin. OPD is table stakes, not the deciding factor.

IPD billing: bed charges, packages, interim bills, discharge

This is where billing software earns its price, and where a manual ledger leaks money. IPD billing is a running account, not a transaction. A patient admitted for a surgery accrues charges over days, and the bill has to hold all of it together.

The pieces that matter:

• Daily accruals. Bed and nursing charges by category, ICU rates, doctor visit charges, each posting automatically per day rather than being keyed in at discharge from memory.
• A package and tariff master. Surgeries are often billed as packages with defined inclusions and exclusions. The software has to hold the package rate, apply it, and flag what falls outside so the ward isn’t arguing with the billing desk at discharge.
• Interim bills. For a long stay the family needs to pay against a running total. The system should generate an interim bill any day, net it against the advance deposit, and keep the account current.
• Discharge settlement. The hard part. At discharge the final bill nets deposits, package inclusions, any cashless approval, and the patient’s own share. If this reconciliation isn’t automatic, someone does it by hand under time pressure, and that’s exactly where revenue slips.

A hospital running a real IPD load without proper package and settlement handling is doing arithmetic that should be automated. If your IPD desk keeps a parallel Excel sheet to “check” the software, the software isn’t doing the job. Our wider hospital revenue cycle guide walks the same accrual-to-settlement flow end to end.

Cashless insurance claims: TPA pre-auth to final settlement

The third world is the one that frustrates admin heads most, because part of it is outside your control. Cashless claims run on the insurer and the TPA, and your billing software has to speak their process fluently.

A TPA (Third Party Administrator) processes claims on behalf of an insurer (IRDAI policyholder portal). The flow for a planned admission runs like this: the hospital sends a pre-authorisation request with the estimate, the TPA or insurer approves an amount, the desk manages queries and enhancement requests during the stay, and at discharge the hospital submits the final claim with the discharge summary and itemised bills. The approved amount settles with the insurer; the patient pays only the uncovered part.

IRDAI’s Master Circular on Health Insurance Business, dated 29 May 2024, sets the clock the desk works against: cashless pre-authorisation within one hour of request, and final authorisation within three hours of the discharge request, with a stated direction toward 100% cashless (IRDAI). What your software has to do is give the cashless desk a queue: which pre-auths are pending, which have queries open, which claims are submitted and awaiting settlement, and which have been paid or short-paid. Without that queue, the desk tracks it in a notebook, and short-payments go unnoticed.

Worth knowing where this is heading: the National Health Claims Exchange (NHCX), run by the National Health Authority, is building a standard rail for claims between hospitals, TPAs, and insurers, with insurers and TPAs coming live and hospitals ramping (PIB, 21 July 2024). It won’t replace your billing software, but a tool that can eventually submit claims in a standard digital format rather than by portal upload and PDF is buying you future ease. Ask vendors where they stand on NHCX, and treat vague answers as a “not yet.”

For the documentation side of a clean claim, what a cashless claim actually needs from the note is a useful companion read.

GST on hospital billing: exempt, mostly

Here’s a rule a surprising number of billing setups get wrong. Health care services by a clinical establishment are exempt from GST (nil-rated) under CBIC Notification No. 12/2017-Central Tax (Rate), Sl. No. 74 (CBIC). Consultations, procedures, diagnostics tied to treatment: no GST on the clinical service.

But “mostly exempt” isn’t “always exempt,” and the room-rent carve-out is the one to get right. Since 18 July 2022, room charges above ₹5,000 per day attract 5% GST (without input tax credit), and ICU, CCU, ICCU, and NICU are excluded from this, under CBIC Notification No. 04/2022-Central Tax (Rate) (CBIC). So a deluxe room at ₹8,000 a night carries 5% GST on the room charge; the ICU bed does not; the surgery itself stays exempt.

Your billing engine has to apply this split automatically: exemption on clinical services, 5% on eligible room rent, and the standard GST rates on any non-clinical retail lines like a cafeteria or a paid attendant meal. Confirm the tool handles the room-rent rule specifically, because it’s the item most legacy setups miss. We’re not tax advisers, and thresholds and rules do change, so run your exact billing categories past your CA before you finalise a setup.

What to look for when you buy

Skip the feature count on the brochure. Five things separate a real hospital billing engine from a glorified OPD counter till.

Capability	Why it matters	Question to ask the vendor
Package / tariff master	IPD surgeries bill as packages with inclusions and exclusions	”Show me a package bill with an exclusion applied at discharge”
Interim bill + discharge settlement	Long stays need running bills; discharge must reconcile automatically	”Run an interim bill, then a final settlement netting a deposit and a cashless approval”
TPA pre-auth + claims queue	Cashless is a workflow, not a document	”Show the queue: pending pre-auths, open queries, submitted claims, short-payments”
GST split (exempt vs 5% room rent)	Legal requirement; commonly misconfigured	”Bill a ₹6,000 room and an ICU night, show the GST on each”
Audit trail	Every bill edit, discount, and write-off must be traceable	”Who changed this bill, when, and can I lock it after settlement?”

The audit trail deserves its own line. In a hospital, bills get edited, discounts get given, and write-offs happen. A billing system without a tamper-evident trail of who did what is a governance hole, and it’s the first thing an auditor or a suspicious CFO asks about. Make the vendor show you the edit history, not just tell you it exists.

When a dedicated billing module beats bolting billing onto an EMR

Here’s our honest take, and it cuts against selling you anything. If IPD, packages, and cashless are daily work, buy a dedicated hospital billing or HIS module, not billing bolted onto a clinical EMR.

The reason is design intent. An EMR is built to document care: the note, the orders, the results. A billing engine is built to price care: a package master, a discharge settlement, a TPA queue, a GST split. A billing bolt-on inside an EMR usually handles OPD counter billing acceptably and then strains the moment an IPD interim bill or a pre-auth query shows up. You can force it, the way you can force any tool past its purpose, but the friction compounds across a busy ward.

There’s a narrower case where a bolt-on is fine: a small clinic or day-care setup that’s mostly OPD, with light or no IPD and little cashless volume. There, an EMR with decent OPD billing may be all you need, and running two systems would be overkill. The test is simple. Count your monthly IPD admissions and cashless claims. If both are meaningful, the billing engine is a separate, deliberate purchase. If both are near zero, the EMR bolt-on will do.

Where documentation feeds cleaner billing

This is the part people miss, so we’ll be plain about it. Better clinical documentation produces cleaner claims. A TPA query is usually a documentation gap: a discharge summary missing a diagnosis, a procedure note that doesn’t justify the package, a date that doesn’t line up. Fewer gaps, fewer queries, faster settlement.

That’s where an ambient scribe sits, and it’s important to be exact about scope. Our AI Scribe drafts the clinical note and the discharge summary for the doctor to review and sign. The doctor pastes or exports that draft into whatever system you run. It is documentation, upstream of billing. It is not a billing engine: it does not price a bed, run a package master, apply GST, or file a claim.

A few scope points, stated straight, because the market oversells this category:

• The scribe drafts; the doctor signs. Any prescription it suggests is a draft the clinician reviews and signs, never something sent on its own. The scribe doesn’t screen the draft for interactions or dosing; that clinical check stays with the doctor.
• Any diagnosis code it offers is a suggestion, not automated claim coding. It does not set the claim’s coding for you.
• The note comes back in clinical English regardless of whether the consult happened in Hindi, English, or a mix. It captures the mixed speech; the output is English.
• The visit audio is processed in memory and discarded once the note drafts. Nothing is stored.
• ABDM integration is on our roadmap, not shipped, and we won’t badge a status we don’t hold.

The value chain is straightforward: a cleaner note means a cleaner discharge summary, which means the cashless claim meets fewer queries and settles faster. The scribe doesn’t do your billing. It makes the paperwork your billing depends on faster and more complete. Under India’s IRDAI cashless rules, where documentation timelines are tight, that upstream cleanup is worth more than it looks.

The buying advice we’d give a friend

Sort your three billing worlds by how much pain each causes you today. OPD billing is almost certainly solved. IPD reconciliation and the cashless queue are where the money and the frustration are, so weight your evaluation there, and make every vendor demo an IPD discharge settlement and a TPA queue on your own numbers, not a slide.

Buy the billing engine for the billing job. Then, separately, decide whether the documentation feeding those bills is slow and gappy, because that’s a different tool with a different job. If your discharge summaries are late and thin and your TPA queries pile up because of it, a scribe on top of your existing systems fixes the upstream, not the billing itself.

If that upstream is your pain point, book a short demo and watch a real consult turn into a signed note and a clean discharge summary. We offer a 7-day full-featured trial, no card. See where the documentation piece lands before you change anything about your billing stack.

Sources: CBIC Notification 12/2017-CT(Rate), Sl. No. 74; CBIC Notification 04/2022-CT(Rate); IRDAI Master Circular, 29 May 2024; PIB / NHCX update, 21 July 2024; IRDAI policyholder portal (TPA).