FBR Digital Invoicing (Pakistan)

Key Features

Generates and submits FBR digital sales-tax invoices to the IRIS API in real time as Magento invoices are created

Maps Magento line items to FBR sales-tax categories using a dedicated product attribute, kept separate from ordinary VAT/tax classes

Registers and stores the FBR invoice number (IRN) and QR code returned by IRIS back onto the Magento order and PDF invoice

Authenticated REST client to the FBR/IRIS endpoints built on Magento's HTTP ClientInterface with configurable sandbox and production base URLs

Observer on sales_order_invoice_save_after triggers submission without overriding core sales classes (upgrade-safe)

Service contract FbrInvoiceSubmitterInterface wired via di.xml so the transport and payload builder are independently testable and swappable

Submission status tracking (pending / submitted / failed) on a custom entity with full request and response logging for audit

Cron-based retry queue with exponential backoff for transient FBR API failures and timeouts, plus manual resubmit

Admin grid under an ACL resource (Ecosire_FbrEInvoicing::manage) to inspect payloads, FBR responses, QR codes and resubmit invoices

Supports FBR sandbox testing and seller STRN / NTN configuration per store view via system.xml store config

Handles debit and credit note (refund / credit memo) reporting scenarios as agreed during scoping

Optional REST/GraphQL endpoint to expose FBR invoice status to your POS, ERP or downstream reconciliation tooling

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

FBR Digital Invoicing (Pakistan) connects your Magento 2 Open Source or Adobe Commerce store directly to the Federal Board of Revenue's IRIS digital invoicing system, so every taxable sale is reported in real time instead of being reconciled by hand at month end.

This is not an instant Adobe Commerce Marketplace download. It is a build-to-order extension: ECOSIRE builds it as a proper module under app/code/Ecosire/FbrEInvoicing, then installs, configures and supports it on your Magento install. We tailor the field mapping, scenario IDs and tax rules to how your catalog and Pakistan sales-tax classes are actually set up.

Technically, the module hooks Magento's invoice lifecycle with an observer on sales_order_invoice_save_after, transforms the invoice into the FBR payload via a service contract (FbrInvoiceSubmitterInterface), and posts it to the FBR/IRIS REST API over an authenticated client built with Magento's Guzzle-based HTTP\ClientInterface. On success it persists the FBR invoice number, IRN and QR code back onto the order, ready to render on the PDF invoice and order grid.

Sales-tax item mapping is kept separate from generic VAT, using a dedicated attribute and di.xml virtual types so a single catalog can carry both FBR sales-tax categories and ordinary tax classes. A cron job sweeps any invoices left in pending/failed and retries them with backoff, and an admin ACL-gated grid lets your finance team inspect payloads, FBR responses and resubmit on demand.

Because it is custom-built, scope and edge cases (POS-04 scenarios, debit/credit notes, multi-store sales-tax registration numbers) are agreed up front and covered by ongoing support. You get a maintainable, upgrade-safe module — not a brittle core hack.

What you get

A namespaced Magento 2 module (Ecosire_FbrEInvoicing) delivered under app/code, Composer-installable and compatible with Magento Open Source and Adobe Commerce

Installation, configuration and smoke-testing on your Magento environment against the FBR IRIS sandbox, then production cutover

Mapping of your catalog and Pakistan sales-tax classes to the correct FBR sales-tax categories and scenario IDs

Admin configuration of seller STRN/NTN, IRIS credentials and base URLs per store view, with credentials stored in encrypted config

Technical handover document covering the di.xml wiring, observers, cron schedule, ACL and retry behaviour

Post-deployment support window for FBR API changes, bug fixes and field-mapping adjustments per the agreed support terms

Who this is for

Pakistani Magento merchant under FBR mandate

An online retailer registered for sales tax whose Magento 2 store now falls under FBR's digital invoicing requirement and needs IRIS submission to happen automatically at the point of invoice, not as a manual month-end task.

Finance / tax compliance manager

Owns sales-tax filing and audit readiness. Needs every Magento invoice to carry a valid FBR invoice number and QR code, with a clear audit trail of what was sent to IRIS and a way to resubmit anything that failed.

Magento solution partner / in-house developer

Maintains the store and wants FBR integration delivered as a clean, upgrade-safe module using observers, service contracts and di.xml, rather than a core override they will have to untangle at the next Magento upgrade.

How FBR Digital Invoicing (Pakistan) Compares

Criterion	ECOSIRE	Custom Build	Competitor
Real-time submission to FBR IRIS API on invoice creation	Included	Partial support	Partial support
Pakistan sales-tax mapping kept separate from generic VAT/tax classes	Included	Partial support	Not included
FBR invoice number (IRN) and QR code stored and printed on PDF invoice	Included	Partial support	Partial support
Cron retry queue with backoff and manual resubmit for failed submissions	Included	Not included	Partial support
Built, installed and supported on your store by the vendor	Included	Partial support	Not included
Tailored to your exact catalog, scenarios and registration setup	Included	Included	Not included
Instant self-service download from Adobe Commerce Marketplace	Not included	Not included	Included
Upgrade-safe module (observers/service contracts, no core overrides)	Included	Partial support	Partial support

Frequently Asked Questions about FBR Digital Invoicing (Pakistan)

How long does delivery take, since this is build-to-order?

Typical delivery is around 2 to 4 weeks from kickoff, depending on scope (number of FBR scenarios, credit/debit notes, multi-store registration). After a short scoping call we confirm the timeline, build the module, validate it against the FBR IRIS sandbox, then install and cut over to production on your store. This is a custom build installed by ECOSIRE, not an instant Adobe Commerce Marketplace download.

Do you provide ongoing support and updates when FBR changes its API?

Yes. Every build includes a post-deployment support window for bug fixes and field-mapping adjustments. FBR periodically revises IRIS payload formats, scenario IDs and validation rules; we offer ongoing maintenance so the module is kept compliant. Because it is a clean module using observers and service contracts rather than core overrides, updates are applied without destabilising your Magento upgrades.

Does this work on Magento Open Source as well as Adobe Commerce?

Yes. The module is built against standard Magento 2 APIs (service contracts, di.xml, observers, cron, admin ACL) so it runs on both Magento Open Source and Adobe Commerce. Adobe Commerce specifics such as additional store-view scoping or B2B flows are handled during scoping if they apply to your setup.

How are sales-tax invoices actually submitted to FBR?

When a Magento invoice is created, an observer on sales_order_invoice_save_after builds the FBR payload through a service contract and posts it to the IRIS REST API over an authenticated HTTP client. On success the FBR invoice number and QR code are written back to the order and rendered on the PDF invoice. Failures are logged and retried by a cron-driven queue, with manual resubmit available from an ACL-gated admin grid.

What do you need from us to build and deploy it?

We need your FBR IRIS sandbox and production credentials (or help obtaining them), your seller STRN/NTN, SSH or deployment access to a staging environment, and a short session to confirm how your catalog and Pakistan sales-tax classes map to FBR sales-tax categories. We build and test against sandbox first, then schedule the production cutover with you.