FBR digital invoicing explained in plain language

If your business is registered for sales tax in Pakistan, the way you issue invoices has legally changed. This is what the rules actually require, without the circular references.

What changed

Previously an invoice was a document you produced and FBR saw later, if at all, through your return. Now the invoice data must be transmitted to FBR's system at the moment the invoice is issued. FBR validates it and returns an invoice reference number and a QR code, and both must appear on the invoice you hand your customer.

An invoice without that number and QR code is not a valid sales tax invoice.

Who it applies to

Sales tax registered persons. The rollout was phased by taxpayer category, with the phases progressively pulling in the rest of the register. If you are registered, assume it applies to you and confirm the specific date for your category with your tax consultant.

The penalties

Non compliance penalties run into the millions of rupees. The exact figures and the schedule for your category are set out in FBR's notifications, and this is the one detail worth confirming directly rather than taking from any article, including this one.

The part that surprises people

FBR provides the system to connect to. FBR does not provide the software that connects you to it.

There is an API. Your billing system has to be built or modified to speak to it, or you need software that already does. That part is every business's own responsibility, and it is why the phrase "FBR integration" exists as a service at all.

The government installed the socket. Running the wire from your counter to that socket is still your job.

What compliance actually looks like day to day

• Your billing clerk creates an invoice the same way as before.
• The system sends the data to FBR and receives back a reference number and QR code, usually in a second or two.
• The invoice prints with both on it.
• If FBR rejects it, someone has to find out why and fix it before that sale can be invoiced properly.

That last point is the one nobody plans for and it is where most of the ongoing work lives.

Why invoices get rejected

Almost never because the connection is broken. Nearly always because of data:

• The buyer's registration number is wrong by a digit or missing entirely
• The HS code does not match the item
• The tax rate applied does not match the schedule for that product
• FBR's server timed out during a peak period

Which means an FBR project is mostly a data project. The item master and the buyer records have to be right before any of it works reliably.

The upside nobody advertises

Once every sale is recorded digitally as it happens, your sales tax return data is assembled continuously instead of reconstructed at month end. Businesses that used to lose three days a month to that get the three days back.

You also end up with verifiable sales history, which is exactly the thing banks have always said Pakistani SMEs cannot produce when they apply for financing.

What to do now

Ask your tax consultant to confirm your category and date. Then ask whoever maintains your billing system whether it can talk to FBR's API. If the answer is no, or nobody maintains it, that is the project.

We build these integrations, and we have a working demo of what a compliant system looks like. Ask and we will show you.