Every clinic owner who's done a full year of TPA work knows the story. Twelve patients on cashless mediclaim on a Tuesday. By Friday the pre-auth letters are back and three of them have been short-settled. The billing software has the original claim and the receipt but no native concept of a partial settlement, so the receptionist enters a write-off line and the difference disappears into the month-end. Multiply that by fifty weeks and the leakage is somewhere between mildly annoying and the difference between profitable and not.
This is a field guide for Indian clinic owners, practice managers, and finance partners picking billing software in 2026. The argument is straightforward: the packaged products in this category are competent and competitively priced, and most single-doctor and two-doctor clinics should buy and stop. The interesting question opens up at multi-doctor practices, clinics with meaningful TPA exposure, and chains — where billing has to do four jobs, not one, and where the packaged tools quietly leak money on three of them.
What "clinic billing software" actually means in 2026
The phrase "billing software" hides a stack of distinct workflows. A useful disaggregation looks like this.
The first job is point-of-care billing speed. A consult ends; a receptionist or the doctor herself closes the visit, captures consultation fees, any procedure, any consumable, any in-clinic injection, applies the right GST treatment per line, and prints or sends the bill — all in under 60 seconds. This is the primitive that gets demoed. Practo Ray, Cliniify, MocDoc, Drlogy, Halemind, Doctors App, DocPulse, Easy Clinic, and free options like Vyapar all do this well. At single-doctor and two-doctor scale this is roughly the whole problem.
The second job is package and rate-plan enforcement. A single patient on a single Tuesday might be on a cash rate for consultation, on a corporate rate negotiated with their employer for diagnostics, on a TPA tariff for an in-clinic procedure, and on a clinic-package rate for a follow-up bundled into a prior visit. The billing software has to route each line item to the right ledger automatically. Most packaged products handle two or three rate plans cleanly. The fourth — usually the package logic that mixes exempt and taxable items — is where errors compound.
The third job is the TPA and insurance claim cycle. Pre-authorisation request, claim document preparation, submission tracking, denial routing, partial settlement handling, write-off discipline, resubmission queue. Indian clinics with even modest TPA exposure see 15–25 percent first-submission denial and another 8–15 percent short-settlement on approved claims. A serious chunk of this is recoverable with a disciplined resubmission workflow, and the packaged billing tools mostly don't ship one. The TPA workflow is where most of the leakage in clinic billing actually lives.
The fourth job is the multi-doctor revenue cockpit. Consultation share by doctor, procedure share, lab and pharmacy attach by referring doctor, day-of-week patterns, doctor-wise collection net of TPA write-offs. This is the screen the founder lives in monthly and the screen most packaged products ship thinly. It usually exists as a couple of static reports that don't reconcile against the front-office collection number and don't survive a doctor moving between branches.
A packaged product in this category is good when it does jobs one and two cleanly and acceptable when it does job three at a basic level. It becomes inadequate when the clinic's TPA share, doctor count, or branch count is large enough that jobs three and four start moving real money.
Where the off-the-shelf products converge and where they diverge
A useful exercise before signing anything: demo five screens, in this order. The OPD consult bill at the counter. The package and rate-plan setup. The TPA claim queue with a partial settlement on it. The month-end doctor-share report. The journal entry that lands in Tally or Zoho Books at end of day.
By the time you've watched those five screens across three vendors, the differences are clear. MocDoc is one of the strongest on the bundled OPD+IPD+pharmacy story and on rate plans for corporate and insurance clients; their cockpit screens are honest. Drlogy and CureNearMe lean hard on the TPA workflow and tend to do well for clinics where insurance is more than a third of revenue. Practo Ray has the strongest patient-facing layer and a competent biller behind it, but the TPA cockpit is shallower than the others. Cliniify, Halemind, and Easy Clinic do the EMR-billing integration cleanly because they were built from the EMR side outward. Vyapar and Doctorsapp's free tools are honest options for very small clinics or single-doctor practices that mostly bill cash.
None of them, in our experience, ship a partial-settlement workflow and a resubmission queue that a clinic with 40+ percent TPA exposure can lean on without bolting something on. That bolt-on is where most of the custom-billing conversations open up.
When buying is enough
Most clinics in India should buy and stop. Honest cutoffs:
- 1–2 doctors, single location, cash and UPI mostly. Pick any of MocDoc, Practo Ray, Cliniify, Drlogy, Doctors App, or Easy Clinic. The variance between these products at this scale is smaller than the variance in how disciplined the front desk is about closing every consult on the system. Spend the budget on a better receptionist and a clean rate plan rather than on enterprise features you won't use.
- Specialist solo practice (paediatrics, derma, ortho, gynae) with low TPA exposure. Same answer. The leverage is in capturing every consumable and every follow-up at point of care, not in the billing engine. Pick something that handles GST treatment cleanly and that you can leave alone.
- 3-doctor clinic, single location, low TPA exposure (below 20 percent). Still buy. Look harder at the doctor-share report and the rate-plan setup because those quietly stop working at 3 doctors. MocDoc, Cliniify, and Halemind tend to be the stronger options here.
For the broader question of which clinic management system to buy at this scale, we've made the case in detail in our field guide to multi-doctor clinic software — for most Indian clinics, the packaged products are honestly good and getting cheaper.
When a thin custom layer is the right answer
The custom-billing conversation opens up at four signals, in this order.
Signal one: TPA share is above 30 percent and the denial-and-resubmission queue lives in a spreadsheet. This is the most common signal and the highest-return one. A clinic doing INR 4–8 crore a year with 35 percent TPA exposure typically has INR 15–30 lakh of recoverable claim leakage sitting in denied, short-settled, or never-resubmitted claims. A thin custom layer — a claim cockpit on top of the packaged biller that owns the pre-auth stage, the submission queue, the denial reason taxonomy, the partial-settlement reconciliation, and the resubmission timer — pays back inside the first quarter. India's claim denial discipline has tightened under IRDAI's 2024 health insurance guidelines and the cashless framework, which makes the resubmission workflow more important, not less.
Signal two: rate-plan complexity is breaking package billing. Clinics running a mix of cash, corporate, TPA, and clinic-package rates routinely overbill some patients and underbill others — usually underbill, because the receptionist defaults to the lower line when she's not sure. A thin enforcement layer at point of care, fed by a clean rate matrix, removes the discretion and tightens collections by 3–5 percent of revenue. This is the layer that also fixes the GST line-item treatment problem at audit — exempt healthcare services, taxable diagnostics, mixed package billing, and pharmacy sale under the same GSTIN, each routed to the right ledger.
Signal three: multi-doctor revenue cockpit and doctor-share reconciliation. Owners of 3–6 doctor clinics with revenue-share or hybrid compensation arrangements need a monthly view that no packaged product ships well — consultation share, procedure share, lab attach, pharmacy attach, all net of TPA write-offs, reconciled against actual cash collection. We've seen month-end discrepancies of INR 1.5–3 lakh between the packaged tool's doctor-wise report and the front-office collection number, and most of it is just bad attribution logic. A thin BI layer on top of the packaged biller, owned by the clinic, removes the argument.
Signal four: chain-level finance cockpit. Across branches the picture gets harder. Cross-branch patient identity, shared doctors moving between locations, owned versus partner-clinic revenue split, central pharmacy and lab attribution. We've discussed the broader pattern in our field guide for clinic chains — the billing piece of that surface is typically a thin custom layer above the packaged EMR and pharmacy POS, not a wholesale replacement.
What about the EMR, pharmacy, and Tally integration
Billing is the middle of the clinic stack, not the front of it. The cleanest pattern for a 3+ doctor clinic in 2026 looks like this. EMR (Cliniify or MocDoc or Halemind) owns the clinical record and pushes line items into billing. Pharmacy POS (which can be the same packaged product or a separate one like Marg) owns dispensing and inventory and pushes its line items in. The billing layer computes the right total per ledger, lands the patient receipt, and produces the journal. Accounting (Tally for most Indian clinics, Zoho Books for newer ones) receives the GST-treated journal nightly. We've written about the reconciliation pattern in detail in our Tally–Zoho–GST automation playbook.
The thing that breaks most often is the journal hand-off. Packaged clinic systems will write a daily summary journal to Tally, but the line-item GST treatment is frequently wrong on the edges — TPA write-offs hitting the wrong ledger, pharmacy GST collapsed into a single line, exempt-services mislabelled as zero-rated. The custom layer's job at month-end is to validate the journal and produce a clean GSTR-3B-ready reconciliation. That's a small piece of code with a large impact at audit.
Worked example: a 4-doctor clinic in Bengaluru
Concrete numbers. A 4-doctor multi-specialty clinic in Bengaluru. One branch, a small in-house pharmacy, a tie-up with an external diagnostic chain for samples. INR 5.4 crore annual revenue. Existing stack: Cliniify for EMR and OPD billing, Marg for pharmacy POS, Tally for accounting. TPA mix at 38 percent of revenue across five TPAs. Cash and UPI at 52 percent. Corporate at 10 percent.
Where the leakage was. First-submission TPA denial at 21 percent, of which about 60 percent was clinical-coding fixable. Short-settlement at 11 percent of approved value, never reconciled. Pharmacy GST collapsed into a single line in the Tally journal causing a two-day reconciliation exercise every month. Doctor-wise revenue share off by INR 2.1 lakh in the last audit because procedure attribution wasn't tracked.
The build. An 8-week, INR 11.5L fixed-price thin custom layer on top of Cliniify and Marg, plus an INR 40k per month retainer. Three components:
- TPA claim cockpit with pre-auth queue, denial taxonomy, partial-settlement reconciliation, resubmission timer, monthly recovery dashboard.
- Rate-plan enforcement at point of care with a clean matrix of cash, TPA, corporate, and package rates feeding into Cliniify via API.
- Tally journal validator that ingests the daily summary from Cliniify and Marg, reapplies the right GST treatment per line, and lands a clean entry into Tally with a GSTR-3B-ready monthly view.
Outcome at six months. First-submission denial down to 12 percent. Short-settlement recovery added about INR 18L annualised. Month-end close shortened from three days to half a day. The doctor-share argument disappeared.
Y1 economics: INR 11.5L build + INR 40k × 12 retainer = INR 16.3L. Recovered revenue from denial-and-short-settlement work alone: INR 22–26L annualised. The other levers (rate-plan enforcement, GST reconciliation discipline) added on top of that. Net positive in the first six months.
Two traps worth naming
Trap one: rip out the packaged biller to fix the TPA workflow. This is the most expensive mistake in this category. Cliniify, MocDoc, Drlogy, and Halemind have spent years on the OPD billing primitive and on the EMR integration. Replacing them with a custom build to fix the claim workflow buys you a worse front office and an unfinished back office. The right pattern is to build the thin layer above, leave the biller in place, and let the packaged product keep getting better at the things it's already good at. This mirrors the pattern we've described in our CA firm client portal and law firm document vault field guides — the leverage almost always sits in the seams.
Trap two: build the patient-facing payment surface before the back-office is honest. It's tempting to start with the consumer side — UPI payment links in WhatsApp, an in-app wallet, a family-account view. None of that pays back until the back-office reconciliation is clean. Build the TPA cockpit and the rate-plan enforcement first. The patient-facing surface is a Phase 2 conversation.
Where to take this next
If you run a clinic doing more than INR 3 crore a year and TPA is more than a quarter of revenue, the first useful exercise is a 90-minute reconciliation walk. Open last month's TPA claim register next to last month's bank statement. Match every claim to its receipt and flag everything that's short, denied, or missing. If the gap is more than INR 1.5L for the month, the custom-layer conversation is worth having. If it's smaller, the packaged tool is doing its job and the leverage is elsewhere — usually in the reminder loop or in patient experience rather than in billing.
If you want a second pair of eyes on the reconciliation walk or on whether a thin custom layer makes sense for your setup, we're happy to do that as a paid scoping exercise. Book a discovery call and we'll come back with an honest read.