Key Takeaway
SRO 709(I)/2025 is the regulatory order that turns FBR digital invoicing from optional best practice into a legal obligation for most registered Pakistani businesses. It builds on SRO 69(I)/2025, sets a phased rollout by sector and turnover, and ties non compliance to Section 33 of the Sales Tax Act 1990 with penalties starting at PKR 10,000 per invoice. This guide explains the rule in plain English and tells you exactly what to do this month.
What Is an SRO, and Why Does This One Matter?
An SRO, or Statutory Regulatory Order, is the instrument Pakistan's federal government uses to issue binding rules without passing a full act of Parliament. The Federal Board of Revenue uses SROs to roll out tax procedures, amend rates, set thresholds, and put implementation timelines on the calendar. SROs carry the force of law: ignoring one is the same as ignoring a statute.
SRO 709(I)/2025 is one of two interlocking orders that together create Pakistan's current digital invoicing regime. The other, SRO 69(I)/2025, came earlier in the year and laid the conceptual foundation: defining the digital invoice, mandating QR codes and FBR verification codes on printed copies, and setting the six year retention period. SRO 709 then put hard implementation dates on the calendar, expanded the scope, and clarified penalties.
A Brief History: How We Got Here
Pakistan has been moving toward real time invoice reporting for almost a decade. The earlier point of sale system for tier one retailers proved the concept. SRO 69(I)/2025 generalised it to the B2B sales tax invoice, and SRO 709(I)/2025 expanded coverage and set the deadlines that businesses must meet now.
The current framework rests on three legal layers:
- The Sales Tax Act 1990: the parent statute that authorises FBR to require invoice reporting and impose penalties
- SRO 69(I)/2025: defines the digital invoice, QR code, FBR verification code, and 22 digit FBR invoice number format
- SRO 709(I)/2025: sets the phased rollout dates, the categories of businesses covered, and the procedure for sandbox and production token issuance
What Exactly Does SRO 709 Mandate?
Stripped of the legalese, SRO 709(I)/2025 says four practical things:
1. Every covered B2B sales tax invoice must be submitted electronically to FBR
You cannot just hand a paper invoice to a customer any more. The invoice must first be transmitted to FBR's Digital Invoice System through an authenticated API call, FBR must respond with a 22 digit invoice number and a verification code, and only then can the customer take their copy.
2. The printed invoice must show the FBR number, verification code, and QR code
The QR code must be at least 7 mm by 7 mm. The FBR logo must be visible. The QR code, when scanned, must take any reader to FBR's verification page where they can confirm the invoice is genuine. The FBR Tax Asaan mobile app is the reference scanner.
3. The seller must integrate through an authenticated channel
You cannot copy invoices into the FBR portal one at a time. You must either build your own integration against the FBR API, use a licensed integrator like PRAL, or use a cloud platform such as Tax It that handles the integration for you. Each integration path requires a sandbox and production Bearer token obtained through the IRIS portal.
4. Records must be retained for six years
Every digital invoice, every FBR response, every error log, and every retry attempt must be stored for six years. If FBR or PRAL knocks on your door for an audit in 2030 asking about an invoice from 2024, you have to produce the original payload and the FBR response.
Who Is Covered, and By When?
SRO 709 rolls out in phases. The exact dates published in the SRO have been refined through subsequent FBR notifications, but the broad pattern is:
- Phase 1: Large taxpayers (turnover above PKR 1 billion), tier one retailers already on the POS system, and selected manufacturers
- Phase 2: Medium turnover businesses (PKR 250 million to 1 billion), wholesale distributors, importers, exporters
- Phase 3: SMEs across services, retail, manufacturing, and trading down to the smallest sales tax registered business
- Final phase: All remaining registered sales tax payers
By the end of the rollout, effectively every business that holds an STRN and issues B2B invoices must be on the digital invoicing system. If you are reading this guide in 2026 and have not yet integrated, you are either already in scope or you will be within the next quarter.
How to check if you are in scope today:
- Log into IRIS and check your taxpayer category
- Read the latest FBR digital invoicing notification (issued under SRO 709)
- If you are unsure, consult your tax advisor or call the FBR helpline at 051 111 772 772
How SRO 709 Interacts with the Sales Tax Act 1990
SRO 709 does not create new penalties on its own. It hooks into the existing penalty framework under Section 33 of the Sales Tax Act 1990. That section is the legal basis for fines, default surcharges, and in serious cases criminal proceedings under Section 33A.
The practical penalties for failing to issue a digital invoice include:
- Per invoice fine: typically PKR 10,000 to PKR 25,000 per invoice, or 100 percent of the sales tax involved, whichever is higher
- Default surcharge: a monthly percentage on the unpaid tax until cleared
- Suspension of refunds: pending sales tax refund claims can be held up
- Loss of input tax credit: buyers may be denied credit on invoices that did not flow through the digital system, which means your customers will eventually stop buying from you
Why Buyers Care as Much as Sellers
This is the indirect enforcement mechanism that makes SRO 709 self policing. When a buyer claims input tax credit on their next sales tax return, FBR validates the invoice against its digital invoicing records. If the seller never submitted it, the buyer loses the credit. Sophisticated buyers (especially the federal ministries, large telecoms, and tier one manufacturers) have already updated their vendor onboarding to require an FBR submitted invoice. Refuse to comply and you stop winning work.
What to Do This Month
If your business is anywhere near the SRO 709 scope, run this checklist in the next 30 days:
- Confirm your IRIS profile is up to date with your current STRN, business address, and authorised contact
- Submit the digital invoicing integration request through IRIS and request your sandbox token (see the step by step sandbox guide)
- Pick an integration path: in house build, licensed integrator (PRAL is the free option), or a cloud platform like Tax It
- Run at least 30 test invoices through the sandbox covering all your scenarios (sales, credit notes, debit notes, registered buyers, unregistered buyers, government customers)
- Request your production token and switch over
- Update your printed invoice template to include the QR code, FBR invoice number, and verification code
- Brief your accounts team on the new flow
Warning: Do not assume that filing your monthly sales tax return as you always have is enough. SRO 709 makes the digital submission of each invoice an independent obligation. You can be fully tax paid and still face penalties simply for not submitting the invoices through the digital channel.
How Tax It Abstracts SRO 709 Away
The whole point of using a compliant cloud platform is that you do not have to read the SRO every time it is amended. Tax It tracks SRO updates, FBR technical specification changes (currently V1.12), and PRAL gateway behaviour. When FBR adds a new error code or shifts a field name, the platform's backend is updated and your invoices continue to flow without you doing anything. The features page covers the compliance side in detail and how it works walks through the day to day flow.
Frequently Asked Questions
Is SRO 709 the same as SRO 69(I)/2025?
No. SRO 69 defines what a digital invoice is and what it must contain. SRO 709 sets the implementation timeline and the categories of businesses required to integrate. They work together.
My turnover is under the threshold. Am I exempt forever?
No. The phased rollout is moving down the turnover ladder. Smaller SMEs are coming into scope. Plan for compliance even if your current phase has not been notified.
What if I only issue handful of invoices a month?
The Basic plan on Tax It handles 50 invoices a month at PKR 2,999. Even very small SMEs can integrate affordably rather than risk Section 33 penalties.
Are exports covered?
Export invoices typically follow the zero rate treatment and may have separate procedures. Tax It supports zero rated sale types. Confirm the specific export procedure with your tax advisor.
If I miss a single invoice can I just resubmit it later?
SRO 709 expects invoices to be submitted before or at the time of supply. Retroactive submission may be possible in limited cases through a credit / debit note adjustment but the safer path is to fix the integration so nothing falls through.
Who do I contact if FBR sends a notice?
Your case officer at the LTU or RTO administering your file. Have your STRN, the disputed invoice numbers, and the corresponding FBR responses ready. Tax It stores all of this in the audit log.
Get Compliant with SRO 709 in Days, Not Months
Tax It is built around SRO 69(I)/2025 and SRO 709(I)/2025 from the ground up. Mock mode for training, sandbox for testing, production for live submission, all on one platform from PKR 2,999 per month.