Hospital Chain Multi-Location Revenue Reconciliation: A CFO Guide for Indian Healthcare

Most hospital chain CFOs in India do not have a revenue reconciliation problem at the chain level. The chain total ties. The problem shows up when the auditor asks why the Bengaluru unit’s pharmacy revenue grew 18 percent in a quarter when footfall grew 6 percent, and the answer is buried four systems deep — somewhere between the HIS pharmacy module, the unit’s bank sweep, the central GL, and an inter-unit stock transfer that was never reversed.

What Multi-Location Hospital Revenue Reconciliation Covers

Multi-location revenue reconciliation in an Indian hospital chain is the process of taking the unit-level revenue feeds from each hospital information system, splitting them by service line, mapping them to the consolidated general ledger, and reconciling each slice against bank deposits, TPA settlements, and inter-unit transfer entries. The output is a unit-by-unit P&L that ties to the chain total and exposes variance at the granularity central finance needs to act on.

Five service lines drive nearly all the variance: in-patient (IPD), out-patient (OPD), pharmacy, diagnostics and radiology, and doctor consultation revenue share. Each has its own collection pattern, its own TDS and GST treatment, and its own reconciliation pitfalls.

Quick-Reference: Revenue Streams in a 14-Unit Hospital Chain

How Central Billing Differs from Unit Billing in Hospital Chains

Most Indian hospital chains operate a hybrid billing model. Corporate clients, group health insurance contracts, and TPA empanelments sit with the parent entity, so the billing happens centrally — a single GST registration, a single PAN, a single corporate bank account that receives TPA batch settlements. Cash patients, walk-ins, OPD consultations, and over-the-counter pharmacy sales bill at the unit, against the unit’s GST registration (where applicable for taxable supplies), and the receipts land in the unit’s current account.

This split breaks every clean revenue-to-bank reconciliation. The HIS at the unit records the service. The GL books the revenue at central. The bank credit may land at either entity depending on the payer’s instruction. The reconciliation has to handle three different join keys — patient ID at the HIS, claim reference at the TPA, and batch reference at the bank — and reconcile them to a single revenue line per unit per service line per day.

How HIS-to-GL Reconciliation Works Across Units

Each unit’s HIS produces a daily revenue feed broken down by department, doctor, service code, and payment mode. Central finance pulls these feeds — typically into a staging schema — and runs three reconciliations in sequence.

The first reconciliation matches HIS daily revenue to the unit’s bank deposit. Cash collections at the OPD counter and pharmacy counter should land in the bank sweep within 24 to 48 hours. Card and UPI collections should appear in the merchant settlement file from the payment processor. Variance here usually traces to cash custody handoffs, settlement timing differences, or a pharmacy module that booked the sale before the cash drawer was reconciled.

The second reconciliation matches central billing revenue (corporate, TPA, group health) to TPA batch credits and corporate receipts. This is the slowest stream — TPA settlement cycles run 21 to 60 days, partial settlements are common, and a single batch credit may cover claims from multiple units. The reconciliation has to disaggregate the batch credit back to the originating unit before any unit-level P&L is final.

The third reconciliation reattributes inter-unit transfers. A patient admitted at the Whitefield unit and transferred to the Indiranagar unit for cardiac surgery generates revenue at both — the originating unit for the initial admission, the receiving unit for the procedure. The HIS books the entire episode at the originating unit by default. Central finance reverses the originating-unit revenue for the procedure portion and books it at the receiving unit, with a netting entry that ensures the chain total does not double-count.

Worked Example: A ₹220 Crore Monthly Consolidation Across 14 Units

Consider a hospital chain operating 14 units across South India, ranging from 50-bed nursing homes to 350-bed tertiary care hospitals. Monthly gross revenue runs at ₹220 crore. The split:

• IPD: ₹127.6 crore (58%)
• OPD: ₹26.4 crore (12%)
• Pharmacy: ₹30.8 crore (14%)
• Diagnostics and Radiology: ₹22.0 crore (10%)
• Doctor Consultation: ₹13.2 crore (6%)

The central finance team pulls 14 unit HIS feeds into the SAP staging schema on the first working day after month-end. Each feed is normalised into the five-service-line taxonomy and mapped to the chain’s GL account structure. Initial consolidation ties at ₹220.1 crore against the GL’s ₹217.7 crore — a ₹2.4 crore variance.

The variance does not show up at the chain-total level by service line: IPD, OPD, diagnostics, and consultation all tie within ₹5 lakh tolerance. Pharmacy shows the gap. Drilling from chain pharmacy to unit pharmacy, twelve units tie. Two units show variance — one of them, a 200-bed unit in Hyderabad, shows ₹2.3 crore of the ₹2.4 crore total.

Drilling further, the unit’s HIS pharmacy module shows ₹4.8 crore of pharmacy sales for the month. The bank deposit ledger for the unit’s pharmacy collection account shows ₹2.5 crore. The card and UPI settlement file from the payment processor shows ₹1.9 crore. Total bank-side: ₹4.4 crore. Gap: ₹2.3 crore at the cash collection layer of the pharmacy counter, not in any of the other service lines or units.

The root cause traces to a pharmacy counter where the cash drawer reconciliation was being closed against the HIS pharmacy module total rather than against the cash physically deposited at the bank. The HIS was booking sales correctly; the cash deposit slip was being prepared from a different report; the gap had been compounding for six weeks before consolidation surfaced it. Without the unit-by-unit, service-line-by-service-line drill-down, the variance would have stayed buried in the chain total.

Pharmacy Revenue Carve-Out and GST Treatment

Healthcare services provided by a clinical establishment are exempt from GST under Sl. No. 74 of Notification 12/2017 — Central Tax (Rate). The exemption covers diagnosis, treatment, and care for illness, injury, deformity, or abnormality, including services by an authorised medical practitioner.

Pharmacy sales sit on the boundary. Medicines dispensed to inpatients as part of their treatment fall within the composite healthcare supply and are treated as exempt. Medicines sold to outpatients, walk-ins, and over-the-counter customers are taxable supplies of goods — 5% on most life-saving drugs, 12% on most formulations, and 18% on selected categories.

For a 14-unit chain, this means every pharmacy transaction has to be tagged at the point of sale with the patient type (inpatient versus outpatient or walk-in) and the drug GST rate. The reconciliation system has to extract the taxable pharmacy slice from the HIS pharmacy feed, aggregate it by GST rate and by unit, and produce the line items for the GSTR-1 outward supplies return. The exempt slice is reported separately under exempted supplies, and input tax credit on common inputs has to be reversed proportionally under Rule 42 of the CGST Rules.

A chain that does not run this carve-out correctly either underreports taxable pharmacy revenue and faces a GST demand on audit, or overreports it and pays GST on what should have been exempt inpatient supply. Both fail at consolidation.

Doctor Consultation Revenue Share and the New TDS Payment Code 1002

Most hospital chains run revenue-share arrangements with visiting consultants. The patient pays the hospital’s consultation fee at the OPD counter. The hospital retains a facility fee — typically 20% to 40% — and pays the balance to the consultant.

Under the 2026 TDS migration, professional services payments to consultants fall under payment code 1002 in the new 1001-1092 series. The hospital deducts TDS on the consultant’s share at the applicable rate, files the quarterly return under the new payment code, and issues Form 16A reflecting the migrated code structure. For chains running revenue-share arrangements with hundreds of consultants across multiple units, the reconciliation system has to:

• Disaggregate consultation revenue at the HIS by consultant, by unit, and by date
• Apply the revenue-share split per the consultant’s contract
• Compute TDS on the consultant share under payment code 1002
• Produce the quarterly TDS return data with the new payment code
• Reconcile the consultant payout register against the bank disbursement file

Hospital chains that consolidate this across 14 units using spreadsheet exports from the HIS routinely miss consultant payments, double-pay on transferred patients, and file TDS returns under the wrong payment code post-migration. The reconciliation infrastructure has to do all of this as a structured workflow against the consolidated revenue feed.

Cash vs Digital Collection Variance Per Unit

The cash-versus-digital mix varies sharply by unit, by city, and by service line. In tier-2 cities, pharmacy and OPD cash share can still run above 50%. In metro tertiary units, cash share at the IPD counter is often under 10%, with the rest split between TPA settlement, corporate billing, and digital patient payments.

The variance per unit shows up at three layers. The first is the cash custody chain — handover from the counter cashier to the unit cashier to the bank deposit slip. Any break here surfaces as a gap between HIS reported cash sales and bank deposited cash. The second is the digital settlement timing — card payments settle on T+1, UPI on T+0 or T+1, and the merchant settlement file from the acquirer has to be matched line by line to the HIS payment records. The third is the TPA settlement layer covered separately in TPA settlement reconciliation.

A chain reconciliation infrastructure that lands the bank feed, the merchant settlement file, the HIS payment register, and the TPA settlement sidecar into the same matching engine resolves variance at all three layers in one pass.

Why Hospital Chains Need Purpose-Built Reconciliation Infrastructure

Hospital chains running reconciliation in spreadsheets against monthly close cycles see two patterns repeat. First, the chain total ties because the spreadsheet pulls a single GL extract — but unit P&Ls are wrong because inter-unit transfers were not reattributed. Second, variance surfaces weeks after the month it occurred, by which time the source documents at the unit are harder to retrieve and the corrective action loses its window.

A purpose-built reconciliation software India deployment for a multi-unit hospital chain runs the HIS-to-bank and HIS-to-GL matches daily, exposes variance at the unit and service-line level the morning after the transaction, and feeds a structured exception queue rather than a month-end fire drill. Pharmacy carve-out, doctor revenue-share TDS, and inter-unit transfer netting are built into the matching configuration rather than maintained as separate spreadsheet workflows.

The GST side of the reconciliation — pharmacy taxable carve-out, inpatient exemption mapping, input tax credit reversal under Rule 42 — runs against the same matched data using a GST reconciliation software layer that consumes the carved-out pharmacy feed and the exempt healthcare service feed separately.

The compliance framework for hospital empanelment and TPA settlement norms is set by IRDAI, the Insurance Regulatory and Development Authority of India.

Continue Reading

For the upstream TPA settlement layer that feeds central billing, see TPA settlement reconciliation. For the patient-billing-to-collection workflow at the unit level, see hospital billing reconciliation. For the preauthorisation-to-discharge cashless workflow that drives most IPD revenue, see cashless claim settlement reconciliation.

The five most common questions about hospital chain multi-location revenue reconciliation in India are answered below.