If you manage billing at a hospital, you already know that collecting ₹500 from an OPD patient at the front desk and settling a ₹1.2 lakh IPD bill after a ten-day admission are completely different operations. Yet many hospitals run both on the same generic billing screen and wonder why revenue leaks. Understanding the structural difference between outpatient billing and inpatient billing is the first step toward fixing that. This article breaks down op ip billing at the hospital level, explains where one-size-fits-all systems fail, and shows what a purpose-built HMS must do instead.
OP billing is transactional: collect payment at the counter before or after a single visit. IP billing is a running ledger where charges accrue daily across departments, estimates are given upfront, advances are collected periodically, and final settlement happens at discharge. Both flows need different screens, different controls, and different reports.
| Billing Dimension | Outpatient (OP) | Inpatient (IP) |
|---|---|---|
| Transaction type | One-time, closed at visit end | Running ledger, open until discharge |
| Charge posting | Manual at counter | Auto-posting from clinical orders |
| Payment timing | Before or during visit | Advance + periodic top-ups + final settlement |
| TPA / insurance | Cashless OPD or reimbursement | Pre-auth, interim claims, final claim |
| Package logic | Rarely applicable | Core requirement |
| Advance reconciliation | Not required | Mandatory at discharge |
| Audit trail (NABH) | Basic receipt | Full charge-edit history required |
OP Billing Flow
Outpatient billing is a point-of-sale transaction. A patient registers, sees a doctor, gets investigations done, buys medicines, and walks out, all within a few hours. Your billing team has one job: close the encounter cleanly before the patient leaves the premises.
In a busy OPD of 200-plus patients a day, speed is everything. A billing screen that needs four clicks to add a single service line becomes a bottleneck. In tier-2 and tier-3 hospitals, one person often handles both registration and billing simultaneously. That person needs consultation charges, lab requisitions, radiology charges, and pharmacy items all on one screen with one-click posting.
A proper outpatient billing system must have:
- Single-screen consultation and service billing with real-time tariff lookup
- Integrated pharmacy billing with automatic GST line-item computation (5%, 12%, or 18% as applicable)
- Cashless TPA processing for CGHS, ESI, Ayushman Bharat, and state-scheme OPD visits
- ABHA-linked patient records for ABDM-compliant encounter documentation
- Instant receipt generation with digital delivery via SMS or WhatsApp
None of these need to be complex. They need to be fast. See how eMedHub structures this in its outpatient management module.
IP Accrual and Estimates
The moment a patient is admitted, a running account opens in your system. Every ward round generates nursing charges. Every lab order generates investigation charges. Every blood unit, every surgical consumable, every physiotherapy session, every meal from the diet kitchen: all of it posts to that account. This is accrual billing, and it is the defining feature of inpatient billing.
The total is not known until the patient is ready for discharge. That creates two practical problems your billing team faces every day.
The first is charge capture. If your clinical and billing modules are not tightly integrated, charges posted in the nursing station or the OT never reach the billing ledger. Doctors write orders and billing staff re-key them manually. In a 30-bed ward with 20 active patients, that re-keying gap is where leakage compounds daily.
The second is pre-authorisation. Ayushman Bharat (PM-JAY), CGHS, and most private TPA policies require an itemised cost estimate before the procedure begins. Without a system that generates a credible estimate from the IP tariff automatically, your TPA coordinator is guessing. Wrong estimates delay approvals and can trigger claim denials at final settlement.
Put a number on the risk. A 120-bed hospital billing ₹4 crore a month with 5% IP charge leakage loses ₹20 lakh every month. At 15% leakage, that figure crosses ₹60 lakh. Those rupees are not being stolen. They are simply not being captured because the billing engine was designed for receipts, not accruals.
Advances and Packages in IP Billing
Two features separate IP billing from OP billing more than anything else: advances and surgical packages. Both are everyday practice in Indian hospitals, and both expose the limits of generic billing software.
Advances
For a planned surgery or a long admission, you collect an advance at the time of admission, typically 50 to 100% of the estimated cost. That advance must sit as a liability against the patient's IP account until discharge, when it is adjusted against the final bill. Any excess goes back to the patient; any shortfall is collected at the counter.
A generic billing system often records the advance as a separate receipt with no structural link to the IP ledger. Your billing staff then reconcile manually at discharge. Repeated across 10 to 30 discharges a day, that manual step is a steady source of arithmetic errors and patient disputes at the billing counter.
Packages
Surgical packages are standard in Indian hospitals. A laparoscopic cholecystectomy package at ₹65,000 might include OT charges, surgeon and anaesthesia fees, two days of ICU, five days of ward stay, routine investigations, and implants up to a specified ceiling. When actual costs exceed that ceiling, you must bill the excess separately. When costs fall short, a refund must trigger cleanly.
Generic billers handle this poorly. Some break the package into line items and lose the ceiling logic entirely. Others treat it as a flat amount and hide actual costs, leaving excess charges uncaptured. Either way, you lose money or lose transparency with the patient.
A proper IP billing engine manages packages by:
- Defining package components and ceiling values at the tariff level
- Tracking actual consumption of each component in real time
- Flagging excess items for supervisor approval before billing
- Generating a discharge summary that clearly separates package items from chargeable add-ons
Where Generic Hospital Billing Software Fails
Most generic hospital billing software is designed around the simplest case: an invoice in, a payment out. That model works for a single-doctor clinic. It does not scale to a multi-specialty hospital where one IP patient's account spans 15 departments over 12 days.
Here is where the failures show up in practice:
- No automatic charge posting. Doctors and nurses post orders in a clinical module, but billing staff must re-enter every item manually. Missed charges are systematic, not accidental.
- No package ceiling enforcement. The system cannot flag when actual costs exceed the agreed package limit, so supervisors have no visibility until the patient is at the discharge counter.
- Advance not linked to the IP ledger. Settlement staff reconcile advances at each discharge by hand, creating errors and slowing patient throughput at the billing counter.
- TPA estimate generation is manual. Your TPA coordinator exports a draft bill and fills in pre-auth fields by hand, introducing errors that delay Ayushman Bharat, CGHS, and private TPA approvals.
- OP and IP share one queue. The fast OP counter and the careful IP reconciliation work at different speeds. Forcing them onto the same screen penalises both workflows.
- No NABH-ready audit trail. NABH standards require every charge edit in an IP bill to be logged with the user ID and timestamp. Generic systems rarely maintain this record.
The result is a billing team working harder than necessary, with errors that surface only at month-end or during a TPA audit.
How eMedHub Handles Both
eMedHub runs two purpose-built billing engines on a shared patient master. Your OPD counter and your IP finance desk each get a screen designed for their specific workflow, with no compromise forced on either side.
The outpatient management module is built for speed: one screen, one-click service addition, integrated pharmacy with automatic GST computation, and cashless TPA handling for CGHS, ESI, Ayushman Bharat, and state schemes from day one.
The inpatient management module opens a dedicated accrual ledger at admission. Charges flow in automatically from the nursing station, the OT, the lab, the pharmacy, and the diet section. Your finance team can pull a live estimate at any point during the stay. Advances are booked against the IP account and auto-adjusted at discharge. Package billing enforces ceiling limits and routes excess charges to a supervisor queue before the patient reaches the billing counter.
Both engines feed the same MIS dashboard and NABH-ready audit reports, so your finance head gets a unified picture without stitching data from two separate systems.
If your current billing setup forces your team to reconcile manually, book a demo to see eMedHub in a hospital setting similar to yours.
Frequently asked questions
What is the difference between OP and IP billing in a hospital?
OP billing closes at the end of a single visit: the patient pays and leaves. IP billing is a running account open from admission to discharge, with charges posted daily from multiple departments. The two processes need different screens, different reconciliation steps, and different TPA handling to prevent revenue leakage.
Why do hospitals need separate billing software for OPD and IPD patients?
OPD billing prioritises speed: a single screen to post services, collect payment, and print a receipt in under two minutes. IPD billing requires accrual logic, advance management, package ceiling enforcement, and pre-auth estimate generation. Running both on the same interface forces compromises that slow one or both counters and introduce billing errors.
How does TPA billing work differently for OPD and IPD patients?
For OPD, a cashless TPA case requires a pre-auth for the visit and medicines, resolved at the counter on the same day. For IPD, the process involves an admission pre-auth, interim claims for long stays, and a final claim at discharge. The IP billing engine must generate itemised estimates automatically to support each stage cleanly.
What is accrual billing in hospital inpatient management?
Accrual billing means charges are recorded as they occur throughout the admission, not when payment is collected. Bed charges post daily, investigation charges post when tests are ordered, pharmacy charges post when medicines are issued to the ward. The total bill is known only at discharge, which is why IP billing requires a live ledger and not a simple invoice screen.
How should a hospital billing system handle surgical package deals?
A surgical package must be defined at the tariff level with ceiling values for each component: OT time, surgeon fee, anaesthesia, ward days, ICU days, investigations, and implants. The billing engine should track actual consumption against each ceiling in real time, flag excesses for supervisor approval, and produce a discharge bill that separates package items from chargeable add-ons.