FBR Licensed Integrator List 2026: Complete Directory for Pakistani Businesses

What is an FBR Licensed Integrator?

An FBR licensed integrator is a company that has been formally approved by the Federal Board of Revenue to build and operate software that connects a Pakistani business's billing system to FBR's Digital Invoice System (DIS). The license confirms that the integrator's software meets FBR's technical specifications, follows the security requirements of SRO 69(I)/2025 and SRO 709(I)/2025, and can reliably submit invoices to the FBR gateway with the correct payload format.

The licensed status matters because FBR holds the integrator accountable for the technical quality of submissions. If a licensed integrator's software produces malformed payloads or fails to handle FBR error responses correctly, FBR can revoke the license. That accountability gives businesses a level of confidence they would not get from an unlicensed vendor.

The public directory of licensed integrators is maintained at fbr.gov.pk/list-of-license-interprator/. FBR updates the list as new licenses are issued and old ones expire, so always check the most recent version before signing a contract.

Where PRAL Fits In

Pakistan Revenue Automation Limited (PRAL) is the technical arm of FBR. PRAL operates the IRIS portal, runs the API gateway at gw.fbr.gov.pk, and acts as the default licensed integrator for any business that does not want to go through a third party. PRAL is free of charge for the integration itself.

That makes PRAL attractive on paper. In practice, PRAL gives you the raw API access and very little else. You still need to:

• Build the software that constructs the JSON payload for every invoice
• Handle the dozens of FBR error codes returned by the gateway
• Generate the QR code and 22-digit FBR invoice number on the printed PDF
• Maintain the 6-year audit trail required by FBR
• Manage Bearer token rotation, IP whitelisting requests, and PRAL support tickets

For a business with an in-house engineering team and budget for a 3-to-6 month build, going through PRAL directly is realistic. For most Pakistani SMEs, freelancers, and traders, it is not.

What Licensed Integrators Actually Do for You

A licensed integrator's job is to translate your business's invoicing data into the exact JSON shape that FBR's gateway expects, send it over HTTPS with a Bearer token, parse the response, handle errors gracefully, and store everything for audit. That sounds simple. It is not.

Payload Construction

Every invoice payload has seller details, buyer details, line items with HS codes from FBR's catalogue, tax breakdowns split across sales tax, further tax, FED, and withholding, plus province codes, UOM codes, sale type codes, and SRO references. A small error in any of these triggers a rejection. Licensed integrators have already worked through every FBR error scenario and know what each error code means.

Bearer Token and IP Management

Your business has a 5-year Bearer token issued by IRIS. The integrator manages where this token is stored, how it is rotated, and which IP addresses are whitelisted with PRAL. If you change hosting providers, the integrator handles re-whitelisting. Our sandbox token guide walks through what is involved on a single token; multiply that by ongoing operations and you see why outsourcing this is attractive.

QR Code and PDF Generation

FBR requires every printed invoice to carry a QR code that points to a verification URL on the FBR servers. The minimum print size is 7mm by 7mm. The integrator handles QR generation and embeds it in the PDF layout. The integrator also makes sure the FBR invoice number and verification code are clearly printed.

Audit Trail and Retention

FBR can demand a copy of any submitted invoice for up to 6 years. The integrator stores the original payload, the FBR response, and the timestamp of submission in a way that survives audits. Building this storage layer yourself means thinking about backup, encryption, and access control.

In-House Build vs Licensed Integrator vs Cloud Platform

Option A: Build In-House Through PRAL

Best for: large enterprises with an existing engineering team, custom workflows, or strict data residency requirements. Expect to spend PKR 1.5 million to PKR 5 million in engineering time over 3 to 6 months, plus ongoing maintenance of around 1 engineer's time per year. You own the code, but you also own every bug, every FBR specification change, and every error code that gets added in a future SRO.

Option B: Third-Party Licensed Integrator

Best for: medium-sized businesses with an existing ERP or POS system that needs to be wired to FBR. The integrator handles the FBR side, but you still pay for and maintain your own invoicing front end. Integration fees usually start around PKR 200,000 with annual maintenance of PKR 100,000 to PKR 500,000 depending on transaction volume. You get FBR compliance without the engineering investment, but you also get vendor lock-in.

Option C: Cloud Platform like Tax It

Best for: small and medium businesses, freelancers, traders, and anyone who wants to log in and start invoicing today. The cloud platform bundles the FBR integration, the invoicing UI, customer and product management, reports, and bulk import into a single monthly subscription. Tax It plans start at PKR 2,999 per month. There is no integration fee, no engineering project, and updates to FBR specifications are pushed by the platform automatically.

A Decision Framework for Pakistani SMEs

Use this quick framework to narrow your choice:

• Do you have an in-house engineering team and a budget over PKR 1.5 million? Consider integrating directly through PRAL. Otherwise skip this option.
• Do you have an existing ERP or POS that you cannot replace? Pick a third-party licensed integrator that supports your platform.
• Are you a small business, freelancer, manufacturer, distributor, or trader who just needs FBR-compliant invoices fast? Pick a cloud platform like Tax It.
• Is your monthly invoice volume under 50? A cloud platform on the Basic tier is almost always the best value.
• Do you have multiple branches? Cloud platforms handle branch-level invoice numbering, user permissions, and reporting out of the box. Building this in-house adds months to the project.

Questions to Ask Any Licensed Integrator Before Signing

Whether you go with a third-party integrator or a cloud platform, ask these before you commit:

• Are you on the FBR public licensed integrator list? Show me your listing.
• What FBR API version do you currently support? (The current version as of 2026 is V1.12.)
• How do you handle sandbox testing? Can I run test invoices before going live?
• How quickly do you push updates when FBR releases a new SRO or changes the spec?
• What happens if FBR's gateway returns an error? Do I see the raw error or just a generic failure?
• How do you store my invoice data, and how long do you retain it?
• What is your monthly uptime guarantee, and what is the support response time?
• Can I export all my invoice data if I want to switch providers?

Frequently Asked Questions