FBR POS Integration for Hospitals & Labs: Workflow

A different scale of the same counter problem

A single-doctor clinic runs one counter and a handful of daily transactions. A mid-size hospital runs an outpatient desk, an inpatient billing office, a pharmacy counter and a lab reception at once, often across shifts and sometimes across buildings. The receipt is the same idea (an FBR invoice number and a QR code); the workflow around it is bigger.

Whether and how FBR's POS integration rules apply to your hospital or lab is a question for your tax advisor. Rules for healthcare are publicly contested, so this guide covers workflow only. The FBR Compliance Hub collects primary-text references to bring to that conversation.

Multi-counter billing, done properly

In a hospital, treat the outpatient desk, the pharmacy and the lab reception as separate counters, each with its own set-up, even though they belong to one facility. Two mistakes to avoid: routing everything through one "master" counter that does not reflect where the sale happened, and standing up counters informally without setting them up at all. Both create reconciliation headaches long before anyone outside asks a question.

Lab billing is not the same shape as ward billing

A lab bill is usually a bundle of individual tests, each with its own code and price, generated quickly and in volume, sometimes hundreds a day from one desk. A ward or outpatient bill is lower volume but higher value, with procedure codes, room charges and consumables in one bill.

If your lab test catalogue is not cleanly coded, or your ward billing cannot separate a procedure fee from a bed charge, you will see it as errors at the counter. Agree codes with your tax advisor, then keep them in one catalogue that every counter uses.

When the POS goes down

A hospital cannot stop billing because the internet drops or a terminal fails mid-shift. Patients keep arriving and tests keep running. Whoever owns billing at your facility should have a written procedure for an outage: who is told, how bills are recorded in the meantime, and how they are entered afterwards. Ask your tax advisor whether any reporting step applies.

Offline resilience helps here. A system that can queue receipts locally during an outage and sync them when connectivity returns makes recovery much easier than one that stops until the internet is back. See our load-shedding guide.

What to ask a vendor if you run more than one location

With more than one site, the questions shift from "does it work" to "does it work the same way everywhere, and can I see all of it from one place". Ask these:

• Can it set up and manage each branch without manual re-setup every time?
• Does it give one consolidated view across locations for records and reviews?
• How does it behave, concretely, during a connectivity outage at a single site?

These decide whether a rollout scales across a hospital network or turns into a separate project at every new site.

Where this leaves you

Get your counters set up consistently, keep your billing data clean, and write down your outage procedure. Then take the legal questions to your tax advisor. If you are weighing how to set up a multi-counter hospital or lab without disrupting patient care, contact us and we will walk through your counter layout and volume.

This article is informational and is not tax or legal advice. Confirm your specific obligations with FBR or your tax advisor.