FBR POS Integration Requirements: Full Checklist

Who this checklist is actually for

FBR's POS integration requirements sit in the Income Tax Rules' real-time-monitoring chapter. SRO 428(I)/2024 is the final notification in force, with POS integration "on and after 1st July, 2024" for the categories in its schedule. SRO 288(I)/2026 is a draft published for comment, and FBR has not issued a final notification as of the last review. Whether and how these rules apply to your business is a question for your tax advisor. The technical baseline below describes what the POS rules ask of a counter system, whoever is in scope.

If you're trying to work out whether this applies to you at all — as opposed to, or alongside, Sales Tax Act digital invoicing under SRO 69(I)/2025 — start with our FBR Compliance Hub, which lays out how the two regimes relate.

The technical baseline, in plain terms

Strip away the legal language and FBR's POS integration requirements come down to a handful of practical asks:

• A supported operating environment. The rules specify baseline software requirements — a minimum supported Windows version and compatible web-server software chief among them — rather than mandating particular hardware. Confirm the current specified versions directly with your integrator or FBR's technical documentation before you buy or provision hardware, since these get updated.
• Real-time, encrypted data transmission. Every sale needs to reach FBR as it happens, over an encrypted connection — not batched up and sent later as a convenience.
• QR-coded invoice generation at the point of sale. Each transaction needs to produce an invoice carrying a QR code generated as part of the FBR-validated response, not a QR code your own system generates independently.
• Internet connectivity, with a plan for when it drops. The rules assume a live connection to FBR; what happens during an outage is a separate, important question we cover in our guide to offline POS during load-shedding.

Payment methods your POS needs to handle

Modern retail and service counters rarely take cash alone — card swipes, mobile wallets and bank transfers all need to route through the same compliant invoicing flow, tagged correctly by payment method. A POS that treats non-cash payments as an afterthought, reconciled separately from the FBR-submitted invoice, creates exactly the kind of mismatch that surfaces at audit time rather than at the counter where it's easy to fix.

Incident reporting: build the process, not just the IT fix

One of the more operationally important — and least discussed — requirements is what happens when your POS goes down: hacking, physical damage, tampering, or a simple disruption. The rules generally expect incidents like these to be reported to the concerned tax authority within a defined window. That window has shifted across different versions of the POS rules, so rather than state a specific number of hours here, the actionable takeaway is this: have a written process for who reports an outage, to whom, and by when — before you need it, not while a counter is actually down.

A pre-integration checklist before you call a vendor

Before you start evaluating POS software or integrators, it's worth confirming a few things internally:

1. Which of your points of sale are actually in scope — every active counter, generally, not just your busiest one.
2. Whether your current hardware and network setup meets the baseline software/OS requirements, or needs an upgrade first.
3. How reliable your internet connectivity actually is at each location, and what your fallback plan is for an outage.
4. Whether you're evaluating PRAL's free direct connection, a licensed integrator, or software that connects through either — our guide to PRAL vs. licensed integrator vs. software unpacks that choice.
5. Who internally owns incident reporting once you're live.

Walking into a vendor conversation with these answers ready helps a vendor quote accurately, compared with starting from "we need FBR POS integration" with no further detail.

Where Aboha fits

Tasdeeq by Aboha is counter software that takes payment and prints a receipt carrying its FBR invoice number and QR code. It can run beside an existing system or on its own, and comes with set-up, staff training and WhatsApp support. Ask us how it fits each point on the checklist above.

If you'd like a straight assessment of whether your current POS setup meets these requirements, or what it will take to get there, contact us and we'll walk through it with you.

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