Understanding FBR IRIS Integration: A Technical Overview

As Pakistan moves toward a fully digital tax environment, businesses are increasingly required to connect their invoicing workflow with the Federal Board of Revenue (FBR).

That means more than generating a digital invoice. Invoice information has to be transmitted electronically through FBR’s digital invoicing infrastructure so IRIS can record it.

This process is commonly referred to as FBR digital invoicing integration.

What is FBR IRIS integration?

IRIS is FBR’s online tax platform. The Digital Invoicing system provides the APIs that carry electronic invoices into that platform.

For a business, the basic concept looks like this:

Invoice data generated in your day-to-day tools is sent electronically instead of being summarised later on paper.

FBR’s technical documentation provides API-based specifications: integration steps, invoice data models, API responses, and POST request examples.

Why is FBR integration important?

Traditional invoicing leaves a lot of manual work. Invoices may need to be:

• Created by hand
• Recorded separately for tax
• Reconciled with the books
• Stored for later
• Reported to the authorities

Digital invoicing connects those steps. You create invoices as you already do, and the required fields are transmitted electronically.

That can improve:

• Tax compliance
• Invoice traceability
• Record keeping
• Data accuracy
• Transaction transparency
• Reporting efficiency

Who needs to integrate with FBR?

FBR’s FAQs state that electronic invoicing is mandatory for the relevant corporate and non-corporate registered persons under the applicable rules. Notified registered persons must connect their invoicing system to FBR’s digital invoicing infrastructure.

First confirm that you fall within those requirements. If you do, your invoicing workflow needs to be ready for digital submission.

What is a licensed integrator?

A licensed integrator is an entity authorised by FBR to provide electronic invoicing integration services - a technical bridge into FBR’s APIs.

FBR maintains an official list of licensed integrators, which currently includes organisations such as PRAL and other licensed technology providers. FBR states that PRAL can also provide integration services to registered persons on demand under the applicable rules.

FBR Digital Invoicing is the product layer you work in: upload or create invoices, validate them, and submit them through the official Digital Invoicing API so you are not wiring those calls yourself.

How does the integration process work?

The exact implementation varies, but the workflow usually has these stages.

1. Business registration

The business must be registered and have the details FBR needs for digital invoicing.

2. Integration partner

The business connects through FBR’s digital invoicing channel - including a licensed integrator where the rules require it.

3. Submit technical information

Technical details of the invoicing setup are provided so communication with FBR can be configured.

4. Sandbox integration

Before production, the integration is tested in a sandbox. FBR’s Digital Invoicing user manual covers sandbox API and token details, then production API and token details once you progress.

5. API testing

The software sends invoice information through the integration API. FBR/PRAL specifications include the invoice data model, POST endpoint, request examples, and response structure.

6. Production integration

After successful testing and approval, production credentials are configured. Live invoices can then be transmitted electronically.

What happens when an invoice is created?

A simplified technical flow:

Digital invoicing is not converting a paper invoice into a PDF. FBR defines an electronic invoice as a structured tax invoice created digitally in the specified format. Scanning or copying a paper invoice does not make it an electronic invoice.

What does the API integration involve?

The integration exchanges structured data between your software and FBR. Depending on the scenario, that includes:

• Seller information
• Buyer information
• Invoice details
• Product or service information
• Quantities
• Tax information
• Invoice values
• Payment-related information
• Invoice identification
• Other required fields

FBR’s technical documentation provides structured digital invoice models and API examples for transmitting this information.

Sandbox vs production environment

Sandbox

Used for testing. Developers can exercise API requests, authentication, invoice payloads, validation, responses, and error handling without treating the environment as live.

Production

The live environment for actual business transactions. Once integration is approved, the software uses production API credentials and endpoints.

FBR’s integration manual explicitly distinguishes sandbox and production API/token information.

What happens if an invoice has an error?

A proper integration must not assume every request succeeds.

Successful response - store the response and finalise the invoice.

Validation error - show the error, correct the data, retry where appropriate.

API or system error - record the failure, apply retry logic, and avoid inconsistent invoice records.

That matters most when you process invoices at volume.

Integration does not mean replacing how you invoice

A common misconception is that you must throw away your current tools. In many cases the goal is to connect what you already use - Excel, Word, PDFs, or accounting software - to FBR’s digital invoicing infrastructure.

FBR Digital Invoicing sits in that layer: you keep your existing process; the platform maps, validates, and submits.

How FBR Digital Invoicing helps businesses

Instead of:

Create → Print → Record by hand → Reconcile → Report

the workflow can become:

Create or upload → Validate → Transmit → Receive response → Store

That reduces repetitive work and keeps records consistent.

What should businesses prepare?

Before you start, review how you invoice today:

• Which tools you use to create invoices
• Where invoice data is stored
• How invoices are generated
• What tax information you already capture
• Whether your process can feed an API
• Who will own onboarding
• How errors and failed transmissions will be handled

FBR states that physical visits are not required for integration and publishes technical documentation and support material online.

The future of business invoicing is connected

FBR’s move toward digital invoicing is a shift from paper toward real-time, structured tax reporting.

The goal is not only to produce an electronic invoice. It is a workflow that can reliably talk to FBR while day-to-day sales stay simple.