If you run a sales-tax-registered business in Pakistan, your invoices now have to go to FBR as you issue them. This guide explains how that works in practice, why most existing invoicing software can’t do it, and what your options are. It is general information, not tax or legal advice, so check the current FBR notification for your own category of business.
The requirement in short
FBR’s Digital Invoicing system asks sales-tax-registered businesses to send each sales invoice to FBR electronically, in real time, through a connection called the Digital Invoicing API. The rule behind it is rule 150Q of the Sales Tax Rules, 2006, and FBR’s notifications let a business connect either through PRAL or through a licensed integrator. The deadlines were phased by category. S.R.O. 1852(I)/2025, issued on September 24, 2025, replaced the earlier August schedule and sorted registered persons into seven categories by company type and turnover. Public companies, importers and the larger companies had to be issuing electronic invoices from November 1, 2025, and the last category, all other registered persons, by December 31, 2025. By now, every sales-tax-registered business should be issuing them.
Notifications have been revised before and may be again, so check the latest one on the FBR website for your own category, or ask your tax advisor, before you rely on this summary.
What “submitting through PRAL” means
PRAL runs the technical side of the system and publishes the specification for it. Your invoicing software sends every invoice to FBR as a structured data message. The message carries the seller and buyer registration details, the date, the type of sale, and each line with its HS code, rate and amounts.
FBR checks the invoice and replies. If the invoice is valid, the reply includes an invoice number issued by FBR. FBR does not send back a QR code image. Your software has to generate the QR code from that number and print it on the invoice, together with the Digital Invoicing logo. According to PRAL’s technical documentation (version 1.12, the one we build against), the QR code must be version 2.0 (25×25) and print at 1.0 × 1.0 inch.
The same specification also describes a separate “validate” call. It checks an invoice against FBR’s rules without submitting it, which is useful for catching problems before the customer is standing at the counter.
Why most existing invoicing software can’t do it
Most invoicing and billing software in use before the requirement was built to produce an invoice and file it, not to call an external tax system and wait for a verdict. Three things are missing:
- A connection to FBR’s API, with the security token FBR issues to each business.
- A place to store the FBR invoice number that comes back and a way to print it with the QR code.
- Handling for the case where FBR says no, so the invoice can be corrected and sent again instead of being lost or duplicated.
The third one matters most day to day, because sooner or later FBR will reject an invoice.
What happens when FBR rejects an invoice
FBR’s reply says whether the invoice is valid (status code 00) or invalid (01), and for an invalid one it gives an error code and a message. The error can apply to the whole invoice or to a single line item. PRAL’s documentation lists the codes; a few that a business is likely to meet:
- 0001: the seller is not registered for sales tax. Check the registration number or NTN in your settings.
- 0002: the buyer’s registration number or NTN is in the wrong format. A registration number is 13 digits, and an NTN is 7 or 9 digits.
- 0005: the invoice date is not in the YYYY-MM-DD format.
- 0009: the buyer’s registration number is empty.
- 0019 and 0052: the HS code is missing or not valid.
- 0046: a line is missing its tax rate.
- 0101: steel-sector businesses must use the Toll Manufacturing sale type.
Most of these codes point to a data problem, such as a missing HS code or a mistyped NTN, and the fix belongs at the source: the customer record, the product record, or the invoice itself. Software that handles this well keeps the rejected invoice, shows the exact message, lets the user fix it, and re-submits it. A bad token or a server problem is different. The documentation lists those as HTTP 401 (unauthorized) and 500 (server error), and the fix is the token or a later retry, not an edit to the invoice.
Three ways to comply
- Use a ready product. Software built for this, such as eInvoicePro, creates the invoice, submits it, prints the FBR number and QR code, and handles rejections. This is the fastest route and suits businesses that don’t need to keep their current system. The trade-off is that you change how invoices are made.
- Connect your existing ERP or POS. If your system is flexible, it can send invoices to FBR through an integration or a licensed integrator. You keep your workflow, but the work depends on what your vendor supports, and every change in your system can affect the connection.
- Build it into custom software. If invoicing is part of a larger system you own, the connection can live inside it. That gives you the most control and the most to build and maintain. See our custom software development and business automation services.
A checklist before you go live
- Confirm your sales tax registration details and your category under the current FBR notification.
- Get your security token and test in the sandbox first. The specification lists a sandbox endpoint and requires a scenario ID on test submissions.
- Clean your data: customer registration numbers or NTNs, and an HS code and tax rate for every product.
- Check that your invoice numbering and sale types match how your business sells, including any sector-specific rules.
- Print the FBR invoice number, the QR code at the required size and the Digital Invoicing logo on every invoice.
- Decide who fixes rejected invoices, and how quickly.
- Keep the invoice data and FBR numbers safe so you can find any invoice later.
Where eInvoicePro fits
We built eInvoicePro because the invoicing systems our clients already had could not do this. It is used by almost 50 businesses and has processed more than 5,000 invoices. If you want to see how it works, read the eInvoicePro case study, or tell us what you’re using today and we’ll say honestly which of the three routes fits.