Pakistan FBR Digital Invoicing for Business Central

Key Features

Real-time submission of posted sales invoices to the FBR digital invoicing system (IRIS/PRAL) via an AL HttpClient call to the FBR REST endpoint, with the FBR invoice number and QR payload written back to Business Central

Line-level computation of sales tax, further tax and extra tax mapped from your BC VAT/Tax posting setup into the FBR-required payload structure

Withholding-tax handling on sales documents, captured and reported in the submission so buyer/supplier obligations are reflected correctly

STRN and NTN validation on customers and on the invoice before submission, blocking non-compliant documents from posting silently

FBR invoice number assignment and QR code generation, rendered directly onto your posted sales invoice report layout (Word/RDLC) for compliant printing and PDF

Table extensions on Sales Invoice Header and Line plus a page extension that exposes FBR scenario, sale type, status and response fields on posted documents

Event subscriber on the posting routine (OnAfterPostSalesDoc) so submission happens automatically as part of your normal Post action — no separate manual step

Job Queue retry engine that re-submits invoices that failed or were posted while the FBR portal was unreachable, with exponential backoff and status tracking

FBR Submission Log page giving a complete audit trail of every request/response, with manual retry, resend and re-print actions for finance and audit teams

FBR API credentials and tokens stored securely in Isolated Storage (never in plain table fields), configurable per environment for sandbox vs production

Dedicated permission set so only authorised users can submit, retry or change FBR setup, aligned with your BC user groups

Sandbox/production environment toggle and a connection test page so you can validate against the FBR test environment before going live

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 Dynamics 365 Business Central.

Go live + support

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

About this Product

Pakistan's Federal Board of Revenue (FBR) now requires registered sales-tax persons to push every sales invoice to its digital invoicing system (the IRIS/PRAL platform) and print the FBR-assigned invoice number plus a QR code. Dynamics 365 Business Central has no native connector for this — so finance teams either run a fragile spreadsheet-and-portal workflow or risk non-compliant invoices.

This is a build-to-order AL extension that ECOSIRE designs, builds, installs and supports directly on your Business Central tenant. It is not an instant AppSource download. After purchase we scope your sales-tax configuration, build the extension against your environment, deploy it as a per-tenant extension, and stay on as your support partner.

What it does technically: a table extension on Sales Invoice Header/Line stores FBR fields (scenario, sale type, STRN, NTN, FBR invoice number, QR payload, response status). A page extension surfaces them on the posted invoice. On posting, an event subscriber (OnAfterPostSalesDoc) builds the FBR JSON payload — line-level sales tax, further tax, extra tax and withholding — and calls the FBR REST endpoint via an HttpClient with your bearer token stored in Isolated Storage. The FBR invoice number and QR code are written back and rendered on the invoice report layout. STRN/NTN values are validated before submission. A Job Queue entry retries any invoice that failed or was submitted while the portal was offline, and an FBR Submission Log page gives you a full audit trail with retry and re-print actions, all gated behind a dedicated permission set.

You own the source and the per-tenant deployment. ECOSIRE handles upgrades when FBR changes its schema and when Microsoft ships a new BC major release.

What you get

A per-tenant AL extension (.app) built for your specific Business Central version, deployed to your sandbox then production environment by ECOSIRE

Full AL source code (table/page extensions, codeunits, event subscribers, the FBR HttpClient integration and report layout changes) handed to you

FBR setup and configuration in your tenant: endpoints, sandbox/production toggle, token storage in Isolated Storage, tax-code-to-FBR mapping

Modified sales invoice report layout (Word or RDLC) showing the FBR invoice number and QR code for compliant printing

A dedicated FBR permission set wired to your existing Business Central user groups

End-to-end testing in the FBR sandbox plus go-live validation against the live FBR endpoint, with a sign-off checklist and a short admin/user guide

Who this is for

Finance Manager on Business Central

Owns sales-tax compliance and month-end close. Needs every posted invoice to reach FBR with the correct invoice number and QR code, without manual portal re-keying or audit gaps.

Tax & Compliance Lead

Responsible for STRN/NTN accuracy, withholding and further-tax treatment, and being audit-ready. Wants a full submission log and validation that blocks non-compliant invoices before they post.

IT / Business Central Administrator

Manages the BC environment, extensions and permissions. Prefers a clean per-tenant AL extension with source code, Isolated Storage for secrets, and a maintainable upgrade path over ad-hoc customizations.

How Pakistan FBR Digital Invoicing for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Real-time posted-invoice submission to the FBR IRIS/PRAL endpoint	Included	Partial support	Partial support
FBR invoice number + QR code rendered on the BC invoice layout	Included	Partial support	Partial support
STRN/NTN validation, further-tax and withholding-tax handling	Included	Partial support	Partial support
Job Queue retry + full FBR submission audit log	Included	Not included	Partial support
Tailored to your exact tax mapping and report layout	Included	Included	Not included
Full AL source code handed over to you	Included	Included	Not included
Installed and supported on your tenant by the provider	Included	Partial support	Partial support
Maintained across FBR schema changes and BC major releases	Included	Not included	Partial support

Frequently Asked Questions about Pakistan FBR Digital Invoicing for Business Central

How long until the extension is live in my Business Central environment?

This is build-to-order, not an instant AppSource install. Typical delivery is 3 to 5 weeks after we confirm your BC version, sales-tax configuration and FBR sandbox credentials. We build against your environment, deploy the per-tenant extension to your sandbox for FBR sandbox testing, then schedule go-live against the live FBR endpoint with you. Tight FBR deadlines can usually be accommodated — tell us your date during scoping.

What ongoing support and updates are included after go-live?

ECOSIRE supports the extension on your tenant. The one-time build price covers go-live plus a stabilisation period. After that we offer a support arrangement that covers FBR schema/endpoint changes (FBR revises its digital invoicing spec periodically) and compatibility with new Business Central major releases, plus issue triage on submissions and retries. You own the AL source either way, so you are never locked in.

Is this published on Microsoft AppSource?

No. It is delivered as a per-tenant extension installed directly on your Business Central environment, not a public AppSource listing. That lets us tailor the tax mapping, scenarios and report layout to your exact configuration and hand you the source code. We deploy and manage it for you.

Does it work with both Business Central online (SaaS) and on-premises?

Yes. The extension is standard AL using HttpClient, Isolated Storage and the Job Queue, so it runs on BC online (cloud) and on-premises. We confirm your exact version and licensing during scoping and build the .app to match, since per-tenant extension deployment differs slightly between the two.

How are FBR API tokens and credentials kept secure?

FBR bearer tokens and API credentials are stored in Business Central Isolated Storage, never in plain table fields or in the report layout. Access to submit, retry or change FBR setup is restricted by a dedicated permission set, and the sandbox and production environments use separate credentials so testing can never hit the live FBR endpoint by accident.