Common FBR Digital Invoicing Errors and How to Fix Them

When you start reporting invoices through FBR Digital Invoicing, most problems fall into a handful of familiar categories. The good news is that almost all of them come down to data quality and setup — not deep technical faults — so once you know what to look for, they are quick to fix.

This guide walks through the errors businesses hit most often when reporting sales tax invoices to FBR, and the practical steps to resolve each one. If you are still setting up, our guide on how to integrate with FBR Digital Invoicing is a good companion read.

Why invoices get rejected

When FBR's platform receives an invoice, it validates the data before issuing an IRN. If something does not add up, the invoice is rejected and you get an error message instead of a reference number. A rejection is not a penalty — it is the system telling you to correct the data and try again. The trick is reading the message and knowing where to look.

1. Buyer detail mismatches

One of the most common problems is buyer information that does not match FBR's records — for example a registration number, name or status that is entered incorrectly.

How to fix it

• Double-check the buyer's registration number for typos or extra spaces;
• Confirm whether the buyer is registered or unregistered, since this affects how the invoice is treated;
• Keep a clean, verified customer master list so the same details are reused every time.

Getting the buyer's registration status right also matters for further tax on unregistered buyers, so it is worth being precise.

2. Wrong or missing tax rates

Applying the wrong rate — or leaving a rate off entirely — is another frequent cause of rejected or incorrect invoices. This often happens when a zero-rated export is left at the standard rate, or a standard-rated item is accidentally marked exempt.

How to fix it

• Set the correct rate on each item — standard rate, zero-rated or exempt as appropriate;
• Review export lines specifically to confirm they are set to 0%;
• Where further tax or federal excise duty applies, make sure those are captured too;
• Maintain tax rates against items in your software rather than typing them each time.

3. Calculation and totals not matching

FBR expects the maths on the invoice to be internally consistent — line values, tax amounts and totals all agreeing. Rounding done differently in a spreadsheet than on the platform can trigger a mismatch.

How to fix it

Let your accounting software calculate tax and totals rather than doing it by hand. Consistent, rule-based calculation removes almost all of these errors, which is one of the practical reasons to move from manual to e-invoicing.

4. Authentication and token problems

To report in the live (production) environment you need valid credentials or a token from FBR. If these are missing, expired or wrong, your invoices will not go through even when the invoice data itself is perfect.

How to fix it

• Confirm your production credentials are correctly entered in your software;
• Check whether a token has expired and needs to be refreshed or reissued;
• Make sure you are pointing at the production environment, not the sandbox, once you go live.

5. Duplicate invoice submissions

Submitting the same invoice twice — often after a timeout or a retry — can produce a duplicate error. The first submission may actually have succeeded even though you did not see the confirmation.

How to fix it

Before re-sending, check whether the invoice already received an IRN. Good software tracks the reporting status of each invoice so you can see at a glance what has already been accepted and avoid sending it again.

6. Connectivity and timeout issues

Because reporting happens over the internet, a dropped connection can leave an invoice in an uncertain state. This is a genuine technical error rather than a data one.

How to fix it

Retry once your connection is stable, and rely on your software's status tracking to confirm whether the invoice ultimately went through. A short delay is normal; a persistent failure is worth escalating.

A simple habit that prevents most errors

Nearly all of these problems trace back to inconsistent data entered by hand. Keeping clean master data — verified customers, correct tax rates against items, and accurate registration details — prevents the majority of rejections before they happen. Testing your setup in FBR's sandbox first, as covered in our sandbox vs production guide, catches the rest.

Frequently asked questions

Does a rejected invoice mean I have broken the law?

No. A rejection is a validation message asking you to correct and resubmit the data. It only becomes a compliance concern if you fail to report a required invoice at all.

How do I know if an invoice was actually reported?

A successfully reported invoice receives an IRN and QR code. If it has neither, it has not been accepted. Compliant software shows the reporting status of every invoice.

Who do I contact if the error is on FBR's side?

If the data is correct and the problem persists, it may be a platform or connectivity issue. Contact FBR support or your software provider — see our FAQs for more guidance.

Iris Accounts validates your invoice data before it reaches FBR and tracks the reporting status of every invoice, so most of these errors are caught and fixed before they ever become a problem.