FBR digital invoicing is the requirement for registered persons in Pakistan to issue every sales-tax invoice electronically in a structured format and transmit it to the Federal Board of Revenue (FBR) in real time through a licensed integrator, so that each invoice carries an FBR-issued invoice number (IRN) and a verifiable QR code. Formalised through SRO 69(I)/2025, it extends what used to be a Tier-1-retail-only obligation to the much wider population of registered businesses, including B2B and wholesale.
This is the step-by-step companion to our POS software for Pakistan & FBR compliance hub. The hub explains the whole compliance landscape; this guide drills into one part of it — getting digital invoicing implemented end to end, and getting the federal and provincial tax right on every electronic invoice you send.
> Scope note: SRO numbers, phase deadlines, and rates below reflect the position as of early 2026 and are explained at a conceptual level. Roll-out dates change by category and by notification — always confirm the current deadline for your registration type with FBR (fbr.gov.pk), your licensed integrator, or a qualified tax advisor before acting.
What is FBR digital invoicing?
FBR digital invoicing (also called electronic invoicing or e-invoicing) is a system in which a registered person’s invoicing software generates each invoice in FBR’s prescribed structured data format and pushes it to FBR’s central system at the moment of issue, rather than printing a paper invoice and reporting it later in a monthly return. In return, FBR validates the invoice and assigns it a unique invoice number; the seller prints that number plus a QR code on the customer’s copy. A buyer — or an FBR officer — can scan the QR code to confirm the invoice is genuine and was reported.
The shift matters because it changes invoicing from a self-declared, after-the-fact process into a validated, real-time one. There is no longer a gap in which an unreported sale can hide.
What SRO 69(I)/2025 actually changed
For years, real-time reporting to FBR was effectively a story about large retailers: Tier-1 stores in malls and chains had to integrate their point-of-sale terminals, and everyone else carried on issuing ordinary invoices. SRO 69(I)/2025 (and the notifications around it) moved the goalposts in three ways:
- It widened who is in scope. The obligation now reaches registered persons generally — corporate first, then non-corporate in phases — not just shopping-mall retail. Wholesalers and B2B suppliers who never touched a POS terminal are now being brought into electronic invoicing.
- It standardised the format. Invoices must follow FBR’s structured digital schema (a defined set of fields and codes), so that machines on both ends can read them. A scanned PDF or a paper receipt is not a digital invoice.
- It mandated the channel. Transmission happens through an FBR-licensed integrator — an approved intermediary that connects your software to FBR’s system — rather than each business building its own private link.
The practical upshot: if you are a registered person, “we’ll just keep printing invoices” is no longer a compliant position, and a foreign invoicing tool that has never heard of an SRO will not get you there.
Who must comply, and by when
The regime is being rolled out in phases by taxpayer category rather than switched on for everyone at once. As a general shape:
- Corporate registered persons are brought in first.
- Non-corporate registered persons follow in later phases.
- Within those bands, FBR has issued category-specific deadlines and, in some cases, extensions.
Because the exact dates shift with each notification, the safe move is to treat the category as the lookup key: identify whether you are corporate or non-corporate and what sector you fall in, then confirm your current go-live date directly with FBR or your integrator. Do not rely on a date you read in a blog — including this one.
If you are not yet in an active phase, you are not exempt; you are next. Selecting invoicing software that already supports the schema now means the eventual deadline becomes a configuration step, not a software-replacement project.
Digital invoicing vs FBR POS integration — are they the same thing?
This is the most common point of confusion. They overlap but are not identical:
| FBR POS integration | FBR digital invoicing (SRO 69(I)/2025) | |
|---|---|---|
| Primary audience | Tier-1 retailers (B2C) | Registered persons broadly (incl. B2B, wholesale) |
| Trigger | Tier-1 status under the Sales Tax Act, 1990 | Registration + your rollout phase |
| What is sent | Retail sale data, in real time | A structured electronic invoice, in real time |
| Result on the receipt | FBR invoice number + QR code | FBR invoice number (IRN) + QR code |
| Channel | Integration with FBR / via PRAL or an integrator | Through a licensed integrator |
In short: POS integration is the retail-checkout slice of the wider digital-invoicing picture. If you are a Tier-1 retailer you have likely already met the POS-integration rule; digital invoicing extends similar real-time discipline to your other invoices and to businesses that were never Tier-1 at all. Our hub’s section on FBR POS integration covers the retail side in detail.
How to get FBR digital invoicing working — step by step
Here is the end-to-end path most registered businesses follow. Treat it as a checklist; the order rarely changes even if the labels do.
- Confirm your obligation and date. Establish whether you are a registered person in an active or upcoming phase, and the exact go-live deadline for your category. This determines your timeline for everything below.
- Choose compliant invoicing software. Your POS or ERP must be able to emit FBR’s structured invoice schema and talk to a licensed integrator. Ask the vendor to name the current SRO and their integrator — a vague answer is disqualifying.
- Select a licensed integrator. Transmission to FBR runs through an FBR-approved integrator (or PRAL where applicable). Your software vendor will often have a preferred, pre-tested integration.
- Register and obtain credentials. Complete the FBR onboarding for digital invoicing and receive the API credentials/tokens that authorise your software to push invoices on your behalf.
- Map your data to the FBR schema. Align your product catalogue, tax codes, buyer fields and HS/PCT codes to the fields FBR expects. This is where most implementation effort lives — clean tax mapping now prevents rejected invoices later.
- Test in the sandbox. Push sample invoices through the test environment, confirm FBR returns a valid invoice number, and check the QR code resolves. Validate edge cases: exempt lines, zero-rated goods, services taxed by a province, credit notes.
- Go live and reconcile. Switch to production, start issuing real digital invoices, and reconcile what your system reports against FBR’s records and your monthly sales-tax return. Build an offline-and-retry path so a dropped connection queues invoices instead of stopping sales.
The business that sails through is the one whose software already speaks the schema — for them, steps 5–7 are configuration. The business that struggles is the one trying to bolt compliance onto a tool that was never built for this market.
What a compliant digital invoice has to contain
FBR’s structured schema expects, at minimum, the data that makes an invoice machine-verifiable and tax-correct:
- Seller’s and buyer’s identifying details (including registration numbers where the buyer is registered).
- Line-level item description with the correct tax classification — HS/PCT code where required.
- The correct tax per line: 18% federal sales tax on standard-rated goods, reduced/zero/exempt where it applies, and the appropriate provincial rate on services (more on that next).
- Invoice totals, tax totals, and any further tax or withholding.
- The FBR-issued invoice number (IRN) and a QR code on the printed/issued copy.
A tool that can only print a 18%-on-everything receipt cannot produce this. The schema forces correct tax logic, which is exactly why locale-aware software matters.
Provincial sales tax on a digital invoice — PRA, SRB, KPRA, BRA
Here is the trap that catches even businesses that get the FBR side right: services are not taxed by FBR. They are taxed by the provinces, each with its own authority, rate card and (increasingly) its own electronic-invoicing expectations. A digital invoice for a service has to carry the provincial tax, reported to the provincial authority — not the 18% federal goods rate.
| Province / territory | Authority | What it taxes |
|---|---|---|
| Punjab | PRA (Punjab Revenue Authority) | Services; reduced restaurant rate for card/digital-paid bills vs cash |
| Sindh | SRB (Sindh Revenue Board) | Services — restaurants, salons, franchises, and more, on its own schedule |
| Khyber Pakhtunkhwa | KPRA (KP Revenue Authority) | Services on its own rate schedule |
| Balochistan | BRA (Balochistan Revenue Authority) | Services on its own rate schedule |
| Islamabad (ICT) | FBR | Services in the capital territory fall under FBR |
Three consequences for anyone implementing digital invoicing:
- Your tax engine must be province-aware. The same software screen has to apply Punjab’s PRA rate for a Lahore service and Sindh’s SRB rate for a Karachi one — automatically, based on where the supply is taxed.
- Payment method can change the rate. Several provinces — Punjab’s PRA is the well-known example — apply a lower restaurant sales-tax rate to bills paid by card or digital wallet than to cash bills, to encourage documentation. Your POS has to detect the payment method and pick the matching rate at the moment of sale.
- Reporting goes to the right authority. The services component is reported to the relevant provincial authority (PRA/SRB/KPRA/BRA), while goods go to FBR. A system that lumps everything under FBR will misreport.
If your business sells both goods and services — say, a restaurant that also retails packaged products, or a workshop that bills parts and labour — you need software that splits each invoice correctly across the federal and provincial regimes. That province-by-province, payment-aware logic is precisely the locale depth that global invoicing tools omit.
Common mistakes and what non-compliance costs
- Treating digital invoicing as “just a printer setting.” It is a data-and-process change: schema mapping, integrator onboarding, reconciliation.
- Applying 18% to services. Services are provincial; over- or under-charging both create exposure.
- No offline fallback. If a dropped connection halts your checkout, you have a business-continuity problem; the system must queue and reconcile.
- Ignoring the phase you are in. Missing your category’s go-live date can mean penalties, rejected input-tax adjustment for your buyers, and reputational risk.
Penalties under the sales-tax framework for failing to issue compliant invoices, or for not integrating when required, are real and are tied to the relevant provisions of the Sales Tax Act and the governing SROs — another reason to confirm your obligations early rather than after a notice arrives.
How EloERP Suite supports FBR digital invoicing
EloERP Suite is built in and for the Pakistani market. It is designed to issue invoices with the mandated FBR fields and QR code, to work with licensed-integrator connectivity for real-time transmission, and to run a tax engine that distinguishes federal goods tax from province-specific services tax — including payment-method-aware restaurant rates for provinces that offer them. Add batch-and-expiry tracking for pharmacy and perishable stock, multi-branch consolidation for chains, and PKR/Urdu-aware documents, and you have the local depth a registered person here actually needs.
If you are scoping a digital-invoicing project, start from the buyer checklist on our compliance hub and ask every vendor the SRO question: which current notification do you support, and through which licensed integrator? The answer tells you whether they operate in this market or merely sell into it.
Frequently asked questions
What is FBR digital invoicing under SRO 69(I)/2025? It is the requirement for registered persons to issue invoices electronically in FBR’s structured format and transmit them to FBR in real time through a licensed integrator. SRO 69(I)/2025 extended electronic invoicing beyond Tier-1 retailers to registered persons more broadly, in phases. Each invoice receives an FBR invoice number and a verifiable QR code.
Is FBR digital invoicing the same as FBR POS integration? No, though they overlap. POS integration is the real-time reporting rule for Tier-1 retailers at the checkout. Digital invoicing applies similar real-time, structured-invoice discipline to registered persons more broadly, including B2B and wholesale businesses that were never Tier-1 retailers.
Who has to comply with FBR digital invoicing and when? The rollout is phased by taxpayer category — corporate registered persons first, non-corporate following — with category-specific deadlines that FBR updates by notification. Identify your registration type and sector, then confirm your current go-live date with FBR or your licensed integrator.
Do I need a licensed integrator for FBR digital invoicing? Yes. Under the regime, invoices are transmitted to FBR through an FBR-licensed integrator rather than a private link each business builds itself. Most compliant software vendors have a pre-tested integrator they connect through.
How does provincial sales tax work on a digital invoice? Services are taxed by the provinces (PRA in Punjab, SRB in Sindh, KPRA in KP, BRA in Balochistan), not by FBR, while goods carry the 18% federal rate. Your software must apply the correct provincial services rate — and some provinces charge a lower restaurant rate for card or digital payments than for cash — and report each component to the right authority.
Can foreign invoicing software handle FBR digital invoicing? Generally no. Global tools are not built for FBR’s structured schema, licensed-integrator transmission, phased SRO deadlines, or province-specific services tax. A Pakistan-built system such as EloERP Suite is designed for these requirements.
Compliance rules, thresholds, SRO numbers, phase deadlines, and tax rates change with each finance act and notification. This guide is for general information as of 2026 — confirm the current position with FBR (fbr.gov.pk), your provincial revenue authority, your licensed integrator, or a qualified tax advisor before acting.