Frequently asked questions

Electronic invoicing was phased in across late 2025 under SRO 1852(I)/2025. The final category, "registered persons other than listed above", had to be issuing electronic invoices from 31 December 2025, so every date in that timetable has passed. Exact scope still depends on your own registration — confirm it with your tax advisor.

See the full timetable →

SRO 709(I)/2025 is the FBR notification, issued on 22 April 2025, that set the first timetable requiring sales tax registered businesses in Pakistan to issue their sales tax invoices electronically to FBR. It has since been superseded — the operative timetable is now SRO 1852(I)/2025.

Read the SRO 709 guide →

We have not found any notification setting a 2026 deadline. The phase-in dates were set by SRO 1852(I)/2025 and all fell between October and December 2025. Claims of a mid-2026 deadline appear on several vendor sites but we could not trace any of them to a notification.

See which notification set which date →

Penalties sit in section 33 of the Sales Tax Act 1990, and more than one entry in that section can be relevant. Amounts run into millions of rupees and the provisions allow for business premises to be sealed. FBR has not published a clarification saying which entry applies to a given default, so confirm your own exposure with a qualified tax adviser.

What the law says →

Licensed integrators are FBR-approved gateway providers responsible for the authorized connection to FBR. Invoicing software is the workspace where staff build invoices, run buyer checks, and manage volume. Read our integrator vs software guide for the full comparison.

Integrator vs software →

IRIS is FBR’s online portal ecosystem. Most businesses need proper IRIS access before digital invoicing go-live. See our IRIS registration guide for practical steps.

IRIS registration guide →

Yes. Testing happens in a sandbox environment, where representative invoices are submitted without affecting live tax records — including invoices that should fail, so your team sees what a rejection looks like before it matters.

Sandbox to go-live →

Invoice data is transmitted over encrypted connections, and FBR credentials are stored encrypted and never returned by the API once saved. Access is per account, and submissions are logged so you can show what was sent and what FBR returned.

It helps ERP, POS, and custom billing systems send invoices to FBR. Your software calls eInvoicePro; we handle the hard FBR integration work, checks, and responses so your team does not rebuild that part.

A direct government link often means long setup, special testing, and ongoing maintenance when rules change. eInvoicePro is built for real business systems so your team ships faster and with fewer surprises.

Yes. High-volume businesses and software teams can submit many invoices through the API — not only one-by-one in the screen.

Enterprises with ERP or custom billing, software houses building for Pakistani clients, and teams that need reliable FBR submission without rebuilding the hard part themselves.

With a single API key created in the developer portal, sent as either an Authorization: Bearer header or an X-API-Key header — whichever your HTTP client makes easier. Either one alone is enough; you never send both. Every endpoint requires it, including the reference lookups.

Yes, and it uses the same base URL and the same API key as production — you switch by setting isSandbox on the request. Sandbox jobs do not consume quota, and every sandbox invoice carries its FBR scenario ID (SN001 to SN028). You can also validate a single invoice against FBR without submitting it at all.

The rest of the batch keeps going — one bad invoice does not sink the job. The failed row records why it failed, and you can fetch the exact payload that was sent along with FBR’s raw response for that row. Once the job has finished you retry just that invoice, rather than resubmitting everything.

A single job takes between 1 and 1,000 invoices, and the same endpoint handles one invoice or a thousand. One batch can mix invoices belonging to different sellers, because each invoice carries its own seller NTN or CNIC and the platform picks the right FBR credential per row.

Seller FBR tokens are write-only and encrypted at rest: you can save or rotate them, but the API never returns them — only whether a sandbox and production token exist. Webhook deliveries are signed, and the signing secret is shown once when you register the endpoint.

Open the eInvoicePro API docs for endpoints, schemas and setup. Business teams can book a demo if they want a guided walkthrough first.