FBR Digital Invoicing for Businesses with Multiple Branches or Outlets (2026)
One NTN, many shops. How FBR digital invoicing works across branches: one token, branch invoice prefixes, the right province, and offline-branch fixes.
Does every branch need its own FBR registration?
Short answer: no. FBR digital invoicing (the real-time billing system, meaning FBR checks and saves each bill the moment you make it) sits on your business, not on your shop door. One sales tax registration — one NTN (National Tax Number, the number FBR gives your business) — covers every branch you run, whether that is three shops or thirty.
The rules come from SRO 1852(I)/2025, the notification FBR issued on 24 September 2025 that says who must join and by when. Under it the last group of registered businesses had to be in by 31 December 2025. Miss your date and the penalty starts at Rs 1 million. Every bill you post, from any branch, comes back with an IRN (Invoice Reference Number — the unique number FBR gives each invoice) and a QR code (the square barcode a buyer can scan to check the bill is real).
So having many branches does not change the law. It changes the plumbing. Four things need a decision: who holds the token, how invoice numbers stay unique across shops, which province goes on each bill, and what a counter does when its internet drops. This guide covers all four in plain words.
One token for the whole business — and where to keep it
Your FBR token (the long secret key that lets your software talk to FBR on behalf of one business) belongs to the registration, not to a branch. You do not get one token per shop. The same key is used whether the sale happened in Lahore or Karachi, because FBR is identifying the business, not the counter.
That leads to one safety rule: do not copy your live token onto every branch computer. Keep it in one place — your server or your software provider's system — and let branches send their sales through it. A token sitting on ten counter PCs is ten chances for it to leak. Tokens run for five years, so treat them like a bank password. Our guide 'How to Get Your FBR Sandbox and Production Token' shows how to issue and store them.
If different branches use different billing software — say the showroom runs an ERP and the small outlets run a simple POS — that is allowed. Under STGO 01 of 2026 FBR lets one registered person work with more than one licensed integrator at the same time. Our guide 'Using More Than One Licensed Integrator' explains how the two connections sit side by side without clashing.
Invoice numbers: give every branch its own prefix
Keep two numbers apart in your head. Your own invoice number is the one you create in your books. The IRN is the number FBR sends back after the bill is accepted. You control the first one; FBR controls the second.
FBR checks the shape of your own number. It must be letters and digits, and if you use a hyphen it must sit between parts of the number, never at the start or the end. A number like LHR-0001 is fine. A number like -0001 or 0001- is rejected (FBR error 0088).
The practical answer for a chain is a branch prefix. Lahore bills LHR-0001, Karachi bills KHI-0001, Multan bills MUL-0001. Every branch counts on its own, so no two shops can land on the same number. Without a prefix, two counters both reach "0007" in the same week and your records stop matching FBR's. Set the prefix once per branch in your software.
Branches in different provinces
Every invoice carries a seller province. That province is where the supply starts from — the branch that actually made the sale, not your head office. A Karachi branch bills with Sindh, a Lahore branch bills with Punjab, even when the company's registered office is somewhere else.
This matters for more than the address line. FBR looks up the correct tax rate for a sale using the province the supply comes from, so the wrong province can bring back the wrong rate, or a rejection. Leaving the seller province empty or using a name FBR does not recognise gives error 0073; the same problem on the buyer's side gives error 0074. Use the exact province names FBR lists, and set each branch up once with its own province and its own address.
The buyer's province is separate — that is where the goods or services are going. On one bill you can easily have a Punjab seller and a Sindh buyer, and that is normal. If your branches also sell services, remember that services are usually taxed by the provinces themselves, not by FBR. Our guide 'FBR vs Provincial E-Invoicing (SRB, PRA, KPRA)' shows which authority gets which bill.
When one branch loses its internet
This is the question every multi-branch owner asks. FBR does not retry for you. If the connection drops while a bill is being sent, that bill is simply not with FBR — no IRN, no QR code, nothing saved on their side.
The right move is to save the bill and send the same bill again when the line comes back. Do not create a fresh bill with a new number for the same sale — that leaves two records for one sale. Our guide 'FBR Invoice Failed to Post — What to Do' walks through the checks, and 'FBR Digital Invoicing Bulk Upload' shows how to push a batch of held-back bills once a branch is back online.
If a bill did go through and it was wrong, you do not delete it. FBR keeps every posted invoice. A genuine mistake can be corrected inside FBR's 72-hour window; after that you need the Commissioner's approval. In day-to-day trade the normal fix is a credit note to reduce a bill or a debit note to add to it — see 'Debit Notes and Credit Notes in FBR Digital Invoicing'.
Outlets, POS and the SRO 288 draft
Digital invoicing is not the same thing as FBR's POS system for large retailers. A chain can end up inside both: POS integration for its retail counters and digital invoicing for its sales tax invoices. Our guide 'FBR POS Integration vs Digital Invoicing' explains the difference so you do not pay twice for the same job.
There is also a rule still on the way. SRO 288(I)/2026 was published on 18 February 2026 as a draft replacement for Chapter VIIA of the Income Tax Rules 2002. It would require many named businesses to declare each of their outlets and connect the billing system at every one of them. Because it is a draft, it becomes binding only after FBR issues the final notification and then an Income Tax General Order with dates. Our guide 'SRO 288(I)/2026 Explained' keeps track of its status.
Chains feel this most: footwear shops in three cities, furniture showrooms, opticians, pharmacies, general stores. Our sector guides — 'FBR Digital Invoicing for Footwear & Shoe Shops', 'Furniture & Home Furnishing Shops', 'Opticians & Optical Shops' — cover the product rules; this page covers the branch side.
Running many branches on Digi Invoice
Give each branch its own number prefix, its own province and its own address, keep one token safely on the server, and let staff at the counter just pick items and print. The IRN and QR code come back in seconds, and every bill from every shop lands in one place you can search. FBR expects records to be kept for six years — our guide 'Record Keeping for Six Years' explains what to hold on to.
Ready to start? Create a free account, add your branches, and post a test invoice in the sandbox (FBR's free practice system where test invoices do not count as real) before you switch your shops over.
Difficult words in this guide
NTN (National Tax Number) — the number FBR gives your business. One NTN covers all your branches.
Token — the long secret key that lets your software talk to FBR for one business. One token, one registration, not one per shop.
IRN (Invoice Reference Number) — the unique number FBR sends back after your bill is accepted. No IRN means the bill is not valid for FBR.
Licensed integrator — a company FBR has approved to carry invoices from your software to FBR. PRAL is one of them.
Seller province — the province the sale starts from, meaning the branch that made the sale, not your head office.
Sandbox — FBR's free practice system where test invoices do not count as real sales.