Product · Billing & Revenue Cycle

Hospital Billing Software That Handles How Indian Hospitals Actually Get Paid

L.K. Monu Borkala, Founder, OneCity Technologies · Published 6 September 2026 · Updated on 6 September 2026

Hospital billing in India is not the same as billing in any other business, and generic billing software fails at the exact points where the differences matter. A hospital issues both Tax Invoices and Bills of Supply on the same day for the same patient depending on which services are GST-exempt and which are taxable. It runs a cashless insurance workflow where the TPA pre-authorises an amount at admission that may bear no relation to the final bill at discharge. It submits PMJAY claims through NHCX where a mismatched patient name or an incorrect package code means a rejected claim and weeks of resubmission. And it loses revenue to charges that never make it onto the bill at all, because the consumable was used in the ward but the nursing station had no way to post it to billing in real time. OneCity's billing module is built inside the hospital ERP, connected to the same database where clinical events happen, so that every chargeable action posts to billing the moment it occurs rather than at discharge when someone tries to reconstruct it from memory.

The revenue leakage problem most hospitals know about but cannot quantify

Revenue leakage in Indian hospitals is not a vague concept. It has specific, identifiable sources, and each one is fixable with software that connects billing to clinical operations in real time. The first source is unbilled consumables: a ward nurse uses a dressing kit, a suture set, or an IV cannula during a procedure, and the charge never reaches the bill because the nursing station has no real-time link to billing. In a busy 100-bed hospital, unbilled consumables alone can account for Rs 3 to 5 lakh per month. The second source is incorrect GST classification: a billing clerk manually classifying a room charge as taxable when it should be exempt, or vice versa, creates either a revenue loss (if the hospital absorbs the wrongly-charged tax) or a compliance liability (if the wrong classification is submitted to the GST portal). The third source is insurance claim denials: Indian hospitals see first-submission denial rates of 15% to 25% on cashless claims, and each denied claim enters a resubmission cycle that consumes staff time and delays payment by weeks or months.

A hospital billing Rs 2 crore per month that loses 10% to these three sources is writing off Rs 20 lakh monthly, or Rs 2.4 crore annually. That is not a billing inefficiency; it is a structural failure that no amount of staff overtime can fix, because the root cause is disconnected systems where clinical events and billing entries happen in different databases at different times.

Why generic billing software fails in a hospital

Generic billing and accounting software (Tally, Zoho Books, even SAP) handles invoicing, GST filing, and accounts receivable perfectly well for a trading or manufacturing business. It fails in a hospital because hospital billing has four structural features that generic systems are not designed for. First, charges originate in clinical events, not in purchase orders or sales transactions: a doctor ordering a blood test in OPD generates a billable event that must post to the patient's folio automatically, not wait for a billing clerk to manually add it. Second, the same patient encounter produces both exempt and taxable charges: room rent below the threshold is exempt, the diagnostic tests ordered during the stay are taxable, the pharmacy drugs dispensed may be either depending on context, and the billing system must classify each line correctly and produce the appropriate document (Bill of Supply or Tax Invoice) without manual intervention.

Third, insurance billing is a parallel workflow with its own lifecycle: pre-authorisation at admission, enhancement requests during the stay if the approved amount is exceeded, final claim submission at discharge, and a denial-resubmission cycle that can run for weeks. This workflow must run alongside the patient billing workflow without duplicating data or requiring separate entry. Fourth, package billing for procedures (Rs 1,20,000 for a knee replacement, Rs 35,000 for a normal delivery) must coexist with itemised billing, and the billing system must handle cases where actual costs exceed the package rate, where the patient's insurance covers the package but not the extras, and where the hospital needs to track the margin per package to evaluate whether the rate is commercially viable. None of these are edge cases. They happen in every Indian hospital every day, and a billing system that treats them as exceptions to be handled manually is the system that causes the leakage.

GST for hospitals: what the billing system must handle correctly

The GST treatment of hospital services is more complex than most billing systems acknowledge. Healthcare services provided by a clinical establishment are exempt under GST, but the exemption has boundaries that create mixed-supply situations on almost every inpatient bill. Room charges above the specified per-day threshold attract GST. Diagnostic services (lab tests, imaging) provided to outpatients who are not admitted are taxable. Pharmacy sales to outpatients are taxable. Food supplied to inpatients as part of treatment is exempt, but canteen sales to visitors are taxable. Ambulance services are exempt, but ambulance hire for non-emergency transport may not be. Cosmetic procedures that are not medically necessary are taxable regardless of the setting.

A billing system that gets this wrong creates two problems simultaneously. If it classifies an exempt service as taxable, the hospital either absorbs the wrongly-charged GST (reducing revenue) or passes it to the patient (creating disputes and regulatory risk if audited). If it classifies a taxable service as exempt, the hospital has a GST compliance liability that surfaces during an audit. The billing module must classify each charge line automatically based on the service category, the patient's admission status, and the applicable threshold, then generate the correct document type: Bill of Supply for exempt, Tax Invoice (with e-invoice integration for eligible turnover) for taxable. The GST hospital billing guide covers the specific rules and thresholds in detail.

TPA cashless and insurance claims: where billing and clinical data must converge

Cashless insurance billing is where the gap between disconnected systems and integrated billing becomes most expensive. The workflow starts at admission: the front desk sends a pre-authorisation request to the TPA with the patient's policy details, expected diagnosis, and estimated cost. The TPA approves an amount. During the stay, if the actual cost exceeds the approved amount, an enhancement request must go to the TPA with supporting clinical documentation. At discharge, the final claim is submitted with the complete bill, procedure codes, discharge summary, and supporting documents.

Each of these steps fails when billing and clinical data live in separate systems. The pre-auth request requires clinical information (provisional diagnosis, planned procedures) that the billing team does not have until the doctor enters it. The enhancement request requires an updated cost estimate that the billing system cannot produce in real time if charges are still being posted manually. The final claim requires a discharge summary and procedure codes that must match the billing entries exactly, and a mismatch between the clinical documentation and the bill is the single most common reason for first-submission denials. A billing system integrated with the hospital management software pulls all of this from the same database: the clinical data, the charges, and the documents are already linked because they were created as part of the same patient encounter.

For PMJAY claims through NHCX, the integration is even more specific: the system must look up the applicable package rate, verify the patient's eligibility, submit the pre-authorisation in the NHCX format, and handle the claim lifecycle entirely within the billing workflow. A hospital submitting PMJAY claims through a separate portal, re-entering data from the billing system, is doing double work and introducing the data mismatches that cause denials.

Package billing versus itemised billing

Most Indian hospitals offer package rates for common procedures, and the billing system must handle both packages and itemised billing within the same patient encounter. A patient admitted for a caesarean section on a Rs 45,000 package may need additional blood products, an extended ICU stay, or medications not included in the package. The billing system must track the package items separately from the extras, calculate what the insurance covers under the package versus what becomes a patient liability, and produce a final bill that shows the breakdown clearly enough that neither the patient nor the TPA disputes it.

The less visible problem with packages is margin tracking. A hospital offering a knee replacement package at Rs 1,20,000 needs to know whether the actual cost of delivering that package (surgeon fee, OT time, implant cost, post-op care, medications) is Rs 90,000 or Rs 1,30,000. Without real-time cost tracking integrated into billing, the hospital discovers it is losing money on a package only when the quarterly accounts are closed, by which point many patients have been billed at the loss-making rate. OneCity tracks actual cost against package rate per case, so the finance team sees margin erosion as it happens rather than three months later.

What OneCity's billing module does specifically

OneCity's billing module is not a standalone billing system bolted onto the side of an ERP. It reads the same database where every clinical event is recorded, which means charges post to the patient folio the moment they occur: when a doctor orders a test, when the pharmacy dispenses a drug, when a nurse records a consumable, when the OT logs a procedure. By the time the patient reaches discharge, the bill is already complete rather than being assembled from department-by-department printouts. The GST classification is automatic per line item, with the correct document type (Bill of Supply or Tax Invoice) generated based on the service category and admission context. TPA pre-auth, enhancement, and final claim submission happen inside the billing workflow with clinical documentation attached from the same patient record. NHCX submission for PMJAY is native, not a separate portal.

Pricing follows the same model as the rest of OneCity: free for up to 5 doctors, paid plans from Rs 999 per month scaling by bed count and active doctors, every price on the pricing page. Billing is included in the ERP, not sold as a separate module with its own license fee. For a detailed comparison of how different vendors handle billing, see the 10-system comparison which scores each on billing depth alongside other dimensions.

Revenue cycle management: beyond the bill

Billing generates the invoice. Revenue cycle management (RCM) tracks what happens after: was the invoice paid, partially paid, disputed, or written off? For cash-paying patients, the cycle is short. For insurance patients, the cycle extends weeks or months through the claim-adjudication-payment pipeline. For PMJAY, the payment timeline depends on state-level processing speeds that vary from 30 days to 90+ days.

A billing system without RCM visibility tells the hospital how much it billed. It does not tell the hospital how much it collected, how much is stuck in the denial pipeline, how much was written off, or what the average days-to-collection is by payer type. OneCity's RCM dashboard tracks each of these by payer (cash, TPA, PMJAY), by department, and by time period, so the finance team can see that TPA X has Rs 12 lakh in pending claims older than 45 days and take action before those claims age out of the submission window.

Where billing connects to the rest of the hospital

Billing does not exist in isolation. Medical records retention rules govern how long billing records must be kept (and they differ by record type). DPDP Act compliance applies to the patient financial data the billing system processes. NABH accreditation assessors check billing accuracy and documentation as part of their review. AERB-licensed equipment generates billable procedures that must be tracked per device. The compliance overview maps all of these connections, and the implementation timeline guide covers how to sequence a billing system migration alongside other compliance projects.

For hospitals evaluating the broader system: what a hospital management system is covers how billing fits into the full HMS/ERP picture, and how to choose hospital management software includes billing depth as one of the six evaluation dimensions. Vendor lock-in and data ownership covers what to check in the billing system's data export terms before signing.

This page is general product information, not financial or tax advice. GST rules, TPA processes, and PMJAY claim procedures change; verify current requirements with your chartered accountant or the relevant authority before acting.

Frequently Asked Questions

How billing connects to clinical documentation under NABH

NABH assessors check billing accuracy as part of their quality review, specifically whether the charges on the bill match the clinical documentation in the patient record. A bill showing five days of ICU charges when the clinical notes show the patient moved to a general ward on day three is a non-conformity that assessors flag. This is not a billing error in the traditional sense; it is a disconnect between two systems that should be reading the same data. When billing and clinical documentation share a database, this disconnect cannot occur because the bed-transfer record that updates the nursing view also updates the billing view in the same transaction.

The NABH 6th edition added specific requirements for digital audit trails on billing changes: who modified a charge, when, and why. A billing system that allows a clerk to change a line item without logging the original amount, the new amount, the reason, and the user ID is not NABH-compliant under the 6th edition, and an assessor can see this in the system logs within minutes of sitting down.

Billing for multi-location hospital groups

Hospital groups with multiple locations face a billing complexity that single-site hospitals do not: each location may have its own GST registration (required if locations are in different states, sometimes even within the same state if they are separate legal entities), its own TPA agreements with different cashless rates, and its own PMJAY empanelment status. The billing system must handle per-location GST, per-location TPA rates, and consolidated financial reporting across all locations without requiring each location to run a separate billing instance. OneCity's multi-location features handle this with a shared patient record and per-location financial configuration, so a patient who visits one location and is billed there can be seen at another location without re-registration, and the group CFO sees all locations' billing and collections on one dashboard.

For hospitals also handling medical records retention, billing records fall under the general three-year NMC retention rule for case sheets, but financial records (invoices, credit notes, GST returns) must be kept per the Income Tax Act and GST rules, typically for six to eight years. A billing system that deletes records when a patient file is archived creates a compliance gap the hospital discovers only during a tax audit.

Sources and further reading

GST healthcare exemption provisions are per CBIC-GST. NHCX claim processing details are from the ABDM portal. TPA claim denial rates are based on published industry analyses by the IRDAI. Verify current GST rates and claim procedures with your CA or the relevant authority.