FBR POS integration guide for Pakistan tier-1 retailers
Last reviewed 2026-05-27 · by the RetailPOS team
Pakistan's Federal Board of Revenue (FBR) requires tier-1 retailers — retail businesses with annual revenue above PKR 1 crore (10 million) or operating from a leased property of more than 1,000 sq ft — to integrate their POS with FBR's e-invoicing system. Each invoice gets a verifiable QR code; transaction data flows in near-real-time to FBR via the Single Sales Tax Return (SSTR) portal. The mandate rolled out progressively from 2019 onwards; the enforcement teeth have sharpened since 2023.
For a tier-1 retailer running RetailPOS (or any compliant POS), the integration is live before the first sale rings — no manual upload, no end-of-day batch, no spreadsheet workaround. This guide covers what FBR e-invoicing actually requires, which retailers qualify as tier-1, what the POS integration architecture looks like under the hood, the penalty schedule, the integration partner landscape (since FBR works through licensed integrators), and how RetailPOS' FBR connector ships.
Tier-1 retailer — the threshold definition that catches many shop owners off guard
FBR defines a tier-1 retailer as a retail business meeting any one of:
- Annual revenue above PKR 1 crore (10 million)
- Operating from a leased property of more than 1,000 sq ft
- Operating from an air-conditioned shopping mall, plaza, or centre
- Listed as a wholesaler-cum-retailer in the FBR's active taxpayer list
- Located in specified cities + categories per FBR's notification updates
The mall/plaza clause catches many shop owners who don't realise it applies. If your shop is in Centaurus, Safa Gold Mall, Hadi Plaza Faisalabad, or any other air-conditioned plaza — you're tier-1 regardless of revenue. The 1,000 sqft threshold catches mid-size standalone retailers; a single ground+mezzanine shop in F-7 Markaz Islamabad easily exceeds 1,000 sqft.
The PKR 1 crore revenue threshold catches active mid-market kiryana, mobile shops, garment retailers — particularly during festive seasons when Eid + back- to-school + wedding-season concentrated revenue lifts annual totals quickly. Track your trailing-12-month revenue continuously; the POS' reporting tools should make this visible on a single dashboard view.
What FBR e-invoicing actually requires
Every sale invoice generated by your POS must:
- Carry a unique FBR-assigned Invoice Number (separate from your internal sequence)
- Carry a QR code that decodes to invoice details verifiable on FBR's public verification portal
- Include the buyer's NTN (National Tax Number) if the buyer requests a tax-invoice for input-tax claim
- Include line-item detail with HS code (or appropriate category code) + GST rate + GST amount per line
- Be transmitted to FBR's SSTR endpoint within the allowed time window (real-time for most categories)
- Be retained electronically for the audit-retention period
The buyer-side experience changes too: customers scanning the QR see the invoice on FBR's portal, confirming the sale was reported to FBR. This is part of FBR's consumer-side compliance push (the “Tax Asaan” app + verification portal); it cuts down on unreported-sale leakage.
POS integration architecture — what happens under the hood
When a tier-1 retailer rings a sale on RetailPOS:
- Cashier scans items + selects tender; standard checkout flow.
- On payment confirmation, the POS commits the sale locally + emits an outbox event for downstream consumers (per the standard architecture).
- The FBR connector picks up the event; formats the invoice payload per FBR's schema (XML or JSON depending on the FBR endpoint version); signs it with the registered device certificate.
- Connector posts to FBR's SSTR endpoint; FBR responds with the official Invoice Number + QR-encoded payload.
- Connector writes the FBR response back to the sale record; the receipt printer prints the customer copy with the FBR Invoice Number + QR code.
Total elapsed time from payment confirmation to printed receipt: typically 1-3 seconds with healthy connectivity. The POS doesn't block on FBR response — if FBR is slow or briefly unreachable, the local sale completes on time and the connector retries in the background, then prints the QR code on the digital receipt or via a customer-pickup reprint flow.
For sustained FBR outages (rare; FBR's SSTR has been reliable since 2023 upgrades), the connector queues invoices locally and submits in order when connectivity returns. FBR's policy permits a defined queuing window without penalty; the connector enforces that policy.
Device registration + certificate provisioning
FBR requires each POS device (each till) to be individually registered. The registration flow:
- Apply for FBR POS Integration registration via the FBR IRIS portal (online).
- Submit your tier-1 retailer status documentation + the POS vendor identity.
- FBR issues a device-specific certificate + registration ID.
- Vendor (or the integration partner) configures the certificate into the till; the till is then enrolled in the FBR SSTR system.
For multi-till operations, each till registers individually. Adding a till later requires re-running the registration for the new device. RetailPOS' onboarding handles the device-registration step as part of go-live; subsequent new tills can be self-served via the back-office config screen.
Branch-level registration is also required if you operate from multiple premises — each branch has its own FBR registration tied to its address.
Penalty schedule — why this matters
FBR's penalty schedule for non-compliance has sharpened since 2023:
- Operating as a tier-1 retailer without FBR POS integration: significant per-day penalty + shop-sealing action available to FBR officers in escalated cases.
- Generating an invoice outside the integrated system (manual or non-compliant POS): penalty per invoice + adjusted assessment for inferred under-reporting.
- Failing to issue an FBR-numbered invoice when required: customer-side complaint via the Tax Asaan app triggers an investigation.
- Refusing to accept a buyer's NTN for tax-invoice issuance: escalation to FBR + risk of denied input-tax credit by the buyer (your buyer becomes upset; reputational risk).
Penalty amounts update via FBR notifications; consult the current schedule via your tax advisor or the FBR portal. The general direction since 2023 is tightening enforcement, not loosening.
FBR also runs spot-check operations during festive seasons (Eid, wedding season) — officers visit shops, scan customer invoices, verify they appear in FBR's system. Non-compliance discovered during a spot-check escalates faster than routine audit.
Integration partner landscape — FBR works through licensed integrators
FBR licenses POS Service Integrators (PSIs) — independent companies authorised to act as the technical bridge between a retailer's POS and FBR's SSTR endpoint. There are roughly 30+ licensed PSIs as of 2026; quality and ongoing service levels vary materially.
For a retailer running an international POS (Square, Toast, etc.) that doesn't natively integrate with FBR, the path is via a PSI — they sit between your POS and FBR, accept your sales data via their connector, format and submit to FBR. This adds latency, a service fee per invoice, and a second integration point of failure.
For a retailer running RetailPOS, the FBR connector ships as part of the product; no separate PSI relationship needed for standard categories. RetailPOS holds (or partners with a holding entity for) the licensed-PSI status required for direct submission. The connector is part of the standard sign-up flow for tier-1 retailers; no extra contract, no per-invoice fee beyond the platform subscription.
For specialised retail categories (jewellery, pharmaceuticals, certain regulated goods) FBR may require additional category-specific integrators; confirm at sign-up that your category is in scope for RetailPOS' direct integration vs requires a partner relationship.
Reporting + reconciliation — your side of the audit trail
The POS retains your side of every transaction submitted to FBR, indexed by FBR Invoice Number and by your internal sale ID. Reconciliation at month-end: export the period's sales from RetailPOS, reconcile against FBR's SSTR portal report (your tax advisor or in-house accountant runs this), file the monthly sales tax return.
Discrepancies are rare with real-time integration (the data went via FBR's endpoint in the first place; mismatch would only arise from a connector retry duplicating an invoice or a manual override on either side). When they do arise, the audit-trail UI in RetailPOS shows the full per-invoice FBR interaction including request payload, response, retry history; this gives you what you need to resolve the discrepancy quickly.
FBR audit visits occasionally request a 6-month or 12-month transaction export; the data-export endpoint produces a clean CSV + per-invoice PDF on demand. Audit-defensibility is the entire point of the integration.
Frequently asked
- I'm under PKR 1 crore revenue but my shop is in Centaurus — am I tier-1?
- Yes. The air-conditioned shopping mall clause makes any shop located in a mall like Centaurus a tier-1 retailer regardless of revenue. The 1,000-sqft threshold is also independent — a single shop exceeding that floorplate qualifies as tier-1.
- Does RetailPOS' FBR integration cost extra?
- For standard retail categories, the FBR connector ships as part of the platform — no separate per-invoice fee, no PSI integration fee. Specialised categories (jewellery, pharma, regulated goods) may have category-specific partner arrangements; confirm at sign-up.
- How long does device registration with FBR take?
- Typically 3-10 business days from FBR IRIS application submission to certificate issuance. RetailPOS' onboarding handles the technical steps; you provide the documentation. New tills added later self-serve via back-office.
- What happens if FBR's SSTR portal is down during a sale?
- The local sale completes on time; the connector queues the FBR submission and retries when the endpoint recovers. FBR's policy permits a defined queueing window without penalty. Sustained outages (rare since 2023) are surfaced via the manager dashboard.
- Can I issue a tax-invoice with the buyer's NTN?
- Yes — the till has a one-tap toggle to capture buyer NTN + business name during checkout. The FBR invoice flows with the buyer's tax-credit eligibility intact. Corporate buyers (embassies, government, multinationals) typically request this.
- Do I need a separate PSI relationship?
- For standard retail categories on RetailPOS — no. The FBR connector ships natively; the platform holds (or partners with the holding entity for) the licensed-PSI status. For specialised categories, confirm at sign-up.
Open your shop in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.