A single hospital with clean billing can become a multi-branch group with chaotic billing almost overnight. Each location grows its own habits, fee schedules drift apart, reports stop being comparable, and a consultant working across three branches gets three partial pictures of what they are owed. Consolidation is how you regain control.
The multi-branch challenge
The core problem is that each branch optimises locally. One uses a different fee schedule, another a different payout cycle, a third a different way of recording collections. Individually each is defensible; together they make group-level reporting impossible and consultant payouts inconsistent. The challenge is standardising without crushing legitimate local differences.
Standardising fee schedules
Start with the fee schedules. A consultant's rate should not depend on which branch happened to record the visit. Define group-level fee schedules, allow controlled local variations only where genuinely justified (cost-of-living, speciality demand), and make the standard the default everywhere else.
- A group-default fee schedule applied unless explicitly overridden.
- Documented, approved exceptions for genuine local differences.
- A single definition of "collection" used across every branch.
- One payout cycle and cut-off, group-wide, for each consultant.
Consolidated vs per-branch reporting
You need both views, not one. Branch managers need per-branch performance to run their location, while group finance needs consolidated numbers to see the whole picture. The trap is maintaining these as two disconnected reporting systems; they must be two views of the same underlying data, or they will never agree.
Consultants who work across branches
A consultant who serves multiple branches is where fragmentation hurts most. If each branch tracks them separately, the consultant gets multiple partial statements, the threshold and TDS are computed wrong, and reconciliation is a nightmare. They need one consolidated statement showing every visit and collection across every location.
A cross-branch consultant whose ₹30,000 threshold is calculated per branch will have their TDS under-deducted. The Section 194J threshold is per payee, per year, across the whole group, not per location.
Centralised TDS and compliance
TDS is where decentralisation becomes a genuine compliance risk. The Section 194J threshold and 10% deduction apply to the consultant's total payments across the group, so deductions, 26Q filing, and Form 16A must be coordinated centrally. Treating each branch as an island means thresholds are missed and the same consultant appears in multiple returns inconsistently.
Multi-branch billing is not a technology problem first; it is a standards problem. Agree the fee schedules, the collection definition, and the payout cycle, and the consolidation follows.
One source of truth
The endgame is a single system where every branch records into the same model, every consultant has one consolidated ledger, and TDS is computed on group totals. With one source of truth, branch-level and group-level reports always reconcile, cross-branch consultants are paid correctly, and compliance is centralised by design rather than stitched together after the fact.
Growth should not mean losing control of your billing. Standardise the fee schedules and definitions, give cross-branch consultants a single consolidated view, centralise TDS, and run everything off one source of truth, and a multi-location group can bill as cleanly as a single hospital ever did.
