What is DI FBR Integration? A Plain-English Explainer for Pakistani Businesses

What Does "DI" Stand For?

DI is short for Digital Invoicing. When you see FBR documents talking about "DI integration", "DI submission", or the "DI gateway", they are talking about the same thing: Pakistan's Federal Board of Revenue Digital Invoicing System.

The system was rolled out in stages under SRO 69(I)/2025 and SRO 709(I)/2025. These two SROs set the rules for which businesses must submit invoices electronically, what data the invoice must contain, how the QR code must be printed, and how long records must be retained. As of 2026, DI compliance is mandatory for a steadily expanding set of business categories.

The shorthand "FBR integration" usually means the same thing as "DI integration". Some vendors also call it "FBR DIS integration" (Digital Invoicing System). All three phrases describe the same workflow.

How the Integration Actually Works

Think of DI integration as a conversation between three parties: your invoicing software, FBR's API gateway, and FBR's backend tax system.

Step 1: Your software builds the invoice payload

When you click "Create Invoice" in your billing system, the software gathers everything FBR needs: your NTN, the buyer's NTN or CNIC, the line items (with HS codes and UOM), the tax breakdown, the invoice reference number, and the date. This gets packaged into a JSON object that follows FBR's published specification (currently version V1.12).

Step 2: The payload is sent to the FBR gateway

The JSON is sent over HTTPS to gw.fbr.gov.pk/di_data/v1/di/postinvoicedata (production) or its sandbox equivalent. The request carries your business's Bearer token in the Authorization header so FBR knows who is submitting.

Step 3: FBR validates the invoice

FBR runs the payload through dozens of validation rules: is the NTN format correct, does the buyer exist in the taxpayer database, do the line items sum to the invoice total, is the sales tax rate appropriate for the HS code, are required fields filled. If anything fails, FBR returns an error code (the codes range from 0001 to several hundred) and your software must show the user a fix.

Step 4: FBR returns the invoice number and QR code

If validation passes, FBR sends back a 22-digit invoice number in the format XXXXXX-DDMMYYHHMMSS-0001 and a URL that the QR code will encode. Your software stores these against the invoice record and renders them on the printed PDF.

Step 5: The customer's PDF carries the QR code and verification info

When you hand the customer their copy of the invoice (printed or PDF), it must show the 22-digit FBR invoice number, the verification code, and a scannable QR code that points to FBR's verification page. The customer can scan it with the FBR Tax Asaan app to confirm the invoice is real.

Who Needs DI FBR Integration?

The list of businesses required to comply has expanded steadily since 2025. As of 2026, the practical answer is: if your business is registered for sales tax in Pakistan, you almost certainly need DI integration. The specific categories named in the SROs include:

• Retailers and wholesalers above the turnover threshold
• Manufacturers and processors
• Importers and exporters
• Service providers operating B2B
• Distributors of FMCG, pharma, fuel, and a growing list of regulated categories
• Restaurants and large retail chains

If you are unsure whether you are required to comply, check your sales tax registration status and the turnover threshold for your category in the latest SRO. When in doubt, it is safer to integrate early than to be caught short during an FBR audit.

Prerequisites Before You Integrate

Before any technical work starts, line up these basics:

• NTN (or CNIC for sole proprietors) issued by FBR
• STRN if you are sales tax registered
• An active IRIS portal account at iris.fbr.gov.pk
• A sandbox Bearer token from IRIS - our sandbox token guide walks through the exact request flow
• A static outbound IP if you are self-hosting, or use a platform like Tax It whose IP is already whitelisted

The Three-Stage Process: Mock, Sandbox, Production

Stage 1: Mock Mode

Mock mode does not contact FBR at all. Your software generates a fake but realistic-looking FBR invoice number and QR code locally. This is useful for demos, onboarding new staff, and proving the workflow before your real sandbox token arrives. Tax It's mock mode is the default for new companies so you can start invoicing within minutes of signing up.

Stage 2: Sandbox Mode

Sandbox mode submits invoices to the real FBR gateway at the sandbox URL. The response is real, the error codes are real, the validation is real, but the submission does not affect your tax record. Spend one to two weeks in sandbox running every type of invoice your business issues. Credit notes, debit notes, exports, exempt items, registered buyers, unregistered buyers, government buyers, all of them. By the end you should see zero rejections on a typical run.

Stage 3: Production Mode

Once sandbox is clean, request a production token from IRIS, paste it into your platform, switch the mode, and your next invoice is real. The 22-digit FBR invoice number on the customer's PDF is now binding.

What Happens If Your Business Is Not Integrated?

If your business is required to comply under SRO 69(I)/2025 and you are not integrated, two things happen:

• Your invoices are not legally valid for sales tax purposes. Your buyer cannot claim the input tax on a paper invoice that lacks an FBR number and QR code. This makes you very difficult to do business with for any registered B2B buyer.
• FBR can levy penalties. The penalty structure under the Sales Tax Act allows for fines per missed invoice plus suspension of registration in serious cases. Use our penalty calculator to estimate your specific exposure.

In practice, the larger commercial cost is usually losing B2B customers who cannot claim input tax on your paper invoices. That alone makes the case for integration.

Frequently Asked Questions