Two SRO numbers come up constantly in conversations about FBR Digital Invoicing: SRO 350(I)/2024 and SRO 709(I)/2025. If you've seen both referenced and aren't sure how they relate to each other, here's a plain-language comparison.
What an SRO is, briefly
An SRO (Statutory Regulatory Order) is how FBR formally introduces or amends rules under Pakistan's tax law without needing a full act of parliament for every operational detail. Digital Invoicing's technical and procedural requirements have been introduced and refined through a series of these notifications – which is why you'll see specific SRO numbers cited whenever the topic comes up.
How the two relate
| SRO 350(I)/2024 | SRO 709(I)/2025 | |
|---|---|---|
| Role | Establishes the core Digital Invoicing framework and requirements | Builds on and refines the framework with updates and clarifications |
| What it covers | Foundational requirements – real-time invoice reporting, IRN issuance, QR code requirements | Adjustments to scope, procedure, or technical detail as the rollout matured |
| Why it matters to you | If you're compliant with the original requirements, this is your baseline | Check this for anything that's changed since your original compliance setup |
Why these notifications get updated
Large-scale rollouts like Digital Invoicing rarely stay static in their first iterations. As FBR onboards more categories of businesses and gathers feedback from the system in production, amendments and follow-up notifications are a normal part of the process – clarifying edge cases, adjusting timelines for specific sectors, or refining technical requirements based on real submission data. SRO 709(I)/2025 sits in that lineage relative to SRO 350(I)/2024.
How to stay current without tracking every notification yourself
Realistically, most business owners don't have the time to monitor FBR's notification pipeline directly. A few practical approaches:
- Rely on software that fetches rules dynamically. If your invoicing system pulls tax rates and validation rules live from FBR's API rather than hardcoding them, many downstream changes are handled automatically without you needing to track the underlying SRO.
- Keep a relationship with a tax advisor who flags changes relevant to your specific sector – SROs often have sector-specific implications that a general summary (including this one) won't capture.
- Check FBR's official notifications page periodically, particularly around your return filing schedule, rather than relying solely on secondhand summaries.
The bottom line
Think of SRO 350(I)/2024 as the foundation and SRO 709(I)/2025 as part of how that foundation has been refined in response to real-world rollout. Neither replaces the other outright – together they form the current shape of Pakistan's Digital Invoicing requirements. If your invoicing software already handles FBR/PRAL DI API integration and pulls validation rules dynamically, most of what changes between notifications is handled for you; the main thing worth double-checking after any new SRO is whether your specific business category or invoice type is affected.