← Elevate Aura  ·  Plain-language guides to healthcare software Chennai, India · WhatsApp
Guide

What is a TPA in hospital billing? The middle party that pays you.

TPA stands for Third Party Administrator. It is the company an insurer appoints to run claims between itself and your hospital: approving admissions, checking bills and releasing payment. This guide explains the process as the front office experiences it.

Written for Indian hospital front officesProcess explained, not soldUpdated September 2026
The short answer

TPA in two paragraphs

A TPA, or Third Party Administrator, is a company appointed by a health insurer to administer claims on its behalf. It is not the insurer and it is not the hospital. It issues the patient's card, approves the cashless admission, reviews the bill against the policy, queries what it does not accept and instructs the insurer to release payment to you.

For a hospital that means the patient in the bed is not the payer. The paperwork is the payer, and the money arrives weeks or months later depending on how well that paperwork was assembled on the day of admission.

The process

What actually happens between admission and payment

Every cashless admission runs through the same sequence. Knowing where it usually stalls is most of the job.

1. Identify the payer at the desk

Before anything clinical happens, the front office establishes which policy is being used, which insurer issued it, which TPA administers it and whether your hospital is inside that TPA's network. If the hospital is out of network, the admission is a reimbursement case: the patient pays and claims later, and the hospital's role is limited to supplying documents.

2. Pre-authorisation

The hospital sends a request stating the provisional diagnosis, the proposed treatment or procedure, the expected length of stay and the estimated cost, signed by the treating doctor. The TPA approves a figure, partly approves, asks a question or declines. Nothing about this is automatic, and an emergency admission proceeds while the request is in flight.

3. Enhancement during the stay

If the patient stays longer, moves to intensive care or needs an additional procedure, the approved amount no longer covers the admission and a further request is raised. Enhancements are one of the commonest causes of a shortfall at discharge, because the treatment changed and nobody told the TPA on the day it changed.

4. The claim file at discharge

This is the document set the TPA pays against. It typically includes the signed claim form and policy or card details, the pre-authorisation and every enhancement, the discharge summary, the itemised bill with charge codes, pharmacy and consumable bills, investigation reports, the operation notes where there was surgery, and the patient's identity and address proof.

5. Query, settlement and the shortfall

The TPA either settles, deducts items it considers non-payable or raises a query. Deductions commonly fall on items excluded by the policy, consumables that are not itemised, or charges that do not match the treatment described in the summary. Whatever is deducted is either written off, billed to the patient under your own policy, or disputed. That decision is a commercial and contractual one, so confirm it with your advisers rather than taking a rule from a web page.

Why payment is slow

The delay is mostly information, not goodwill

Hospitals tend to blame TPAs for slow payment, and TPAs tend to blame hospital paperwork. Both are describing the same failure from different ends: the claim file does not agree with itself. Where the bill, the discharge summary and the pre-authorisation describe three slightly different admissions, someone has to reconcile them, and the file goes into a queue while that happens.

  • Approval taken late. A planned admission where pre-authorisation was raised after the patient was already on the ward.
  • Enhancement never raised. The stay extended or the patient moved to ICU and the approved amount was never revised.
  • Unitemised consumables. A single line for consumables invites a deduction; a list of what was used does not.
  • Bill typed separately from the record. Charges re-entered by hand at discharge drift away from what the notes say was done.
  • Documents missing at submission. An investigation report or an operation note absent from the file restarts the clock.
  • Nobody owns follow-up. Claims submitted and then not tracked until the month-end receivables report.

The practical fix is not a harder negotiation. It is to make the bill a by-product of the treatment record, so the itemised bill, the summary and the claim form are three views of the same admission rather than three separate acts of typing.

At the counter

What the front office must capture, and when

Almost every deduction traces back to something not asked for at the desk. This is the minimum an insured admission needs before the patient leaves registration.

CaptureWhenWhy it matters later
Policy number, insurer and TPA nameAt registrationDecides whether the case is cashless or reimbursement.
Card or e-card and patient identity proofAt registrationIdentity mismatch is a standard query.
Network status of your hospital with that TPABefore admissionAn out-of-network cashless promise cannot be kept.
Provisional diagnosis and planned procedureWith pre-authorisationThe approval is written against this, not against the final bill.
Expected length of stay and estimateWith pre-authorisationSets the approved amount you must stay inside.
Any change in treatment or stayThe day it happensTriggers the enhancement request before discharge, not after.
Itemised charges as they occurThroughout the stayRemoves the discharge-day reconstruction of the bill.
Attendant's contact numberAt registrationThe person who answers when a query arrives weeks later.

Where this sits in software: in HIMS TPA and insurance billing the payer and approval sit on the admission, charges accumulate on the encounter as treatment happens, and the cash portion, the insured portion and the claim are drawn from the same record. What the software cannot do is decide your policy on shortfalls or read a contract for you.

Questions

Common questions about TPAs

What does TPA stand for?

Third Party Administrator. It is a company licensed to administer health insurance claims on behalf of an insurer, handling cards, pre-authorisation, bill review and settlement with the hospital. The insurer carries the risk; the TPA runs the process.

Is the TPA the same as the insurance company?

No. The insurer issues the policy and pays the claim. The TPA administers it. One insurer may use several TPAs, and one TPA may serve several insurers, which is why the card and the policy can carry different names.

What is pre-authorisation?

A request the hospital sends before or at the start of treatment stating the diagnosis, the planned procedure, the expected stay and the estimated cost. The TPA approves an amount against it. Treatment that goes beyond that amount needs an enhancement request.

Why do TPAs deduct part of the bill?

Usually because an item is excluded by the policy, because consumables were not itemised, or because the charge does not match the treatment described in the discharge summary. Whether a deduction is disputed or absorbed is a commercial decision for your hospital and its advisers.

How long does a TPA claim take to settle?

It varies by insurer, TPA and the state of the file. What a hospital can control is the file: complete documents, an itemised bill drawn from the record, enhancements raised on the day treatment changed, and someone tracking submitted claims rather than discovering them in ageing.

Can software make TPA claims faster?

It can remove the part that is self-inflicted. When the bill is generated from the treatment record and the payer sits on the admission from registration, the claim file agrees with itself. Approval times and insurer policy remain outside your control.

Keep reading

Next in this series

Still deciding what you need?

Tell us how your centre or business works today and we will tell you plainly which parts of this apply to you, and which do not.

Founder-led · Chennai, India · Built and supported by the person who wrote it