FBR System Is Down — Can You Still Make a Sale?

Q: My invoice was rejected, not delayed. Is that the same thing?

No. A rejection means the system responded and your data failed validation. Common causes are buyer NTN or CNIC format issues, incorrect HS codes, wrong unit of measure, or a tax amount that does not reconcile. Fix the source record, then re-validate and re-post.

Last updated: August 2026

Short answer: Yes. If your internet, power or the FBR system goes down, you may continue issuing invoices in offline mode. However, those invoices must be uploaded to the FBR system within 24 hours of connectivity being restored. Failing to upload within that window can attract penalty action. Your invoicing software must be capable of storing invoices locally during the outage and transmitting them automatically once the connection returns.

It is 6pm on a Friday. The shop is busy. A customer is at the counter with a full trolley. You scan the last item, the system reaches out to FBR — and nothing happens. The connection has dropped.

Behind the counter, one question: do I sell, or do I stop?

This is one of the most common real-world questions about FBR digital invoicing, and one of the least clearly answered. Most guides explain registration and integration. Very few explain what to do when the system simply is not there.

Yes, you can keep selling

The rules anticipate this situation. Businesses may issue invoices in offline mode during internet or power outages, provided those invoices are uploaded to the FBR system within 24 hours of restoration.

FBR’s own published FAQs acknowledge the scenario directly, listing the case where an invoice is issued and goods dispatched, but the internet at the registered person’s end — or at the licensed integrator’s end — remains down for a day or more.

So the answer is not “stop trading.” The answer is: keep trading, but keep a complete record, and upload as soon as you can.

What “offline mode” does not mean. It is not permission to sell without documentation. Every offline sale must still produce a complete invoice with all mandatory fields, and it must reach FBR within the permitted window. Offline mode is a delay in transmission — not an exemption from it.

The 24-hour rule, explained

The clock does not start when the outage begins. It starts when connectivity is restored.

Time	What happens	Your obligation
Outage begins	System cannot reach FBR	Continue issuing invoices offline, stored locally
During outage	Invoices queue in your system	Keep selling; do not delete or re-number anything
Connectivity restored	The 24-hour clock starts	Upload all queued invoices
Within 24 hours	All queued invoices transmitted and numbered	Verify each one posted successfully
After 24 hours	Queued invoices still not uploaded	Exposure to penalty action

Failure to comply may attract penalties under Section 182, in addition to other legal action. That is the part most businesses do not plan for — not the outage itself, but the hours after it, when everything is busy again and nobody remembers to check whether the queue actually cleared.

Three different failures — and they are not the same

“The system is down” covers at least three separate situations, and the correct response differs for each. Diagnosing it correctly saves hours.

1. Your internet or power is down

The most common case. Your POS or ERP is running, but it cannot reach the outside world.

What to do: Continue selling. Your system should queue invoices locally. Once the connection returns, verify the queue has transmitted. If you have a backup connection — a mobile hotspot, a second SIM — this is the moment to use it.

2. FBR’s or your integrator’s system is down

Your internet works, other sites load, but invoice submissions time out or return server errors. This is the situation FBR’s own FAQ describes: the system at the registered person’s end or the licensed integrator’s end is down.

What to do: Continue selling offline. Take a screenshot of the error message with the timestamp visible. Note the start time. Contact your integrator to confirm the outage — this creates evidence that the delay was not on your side.

3. Your invoices are being rejected

This one is often mistaken for an outage — but it is not. If the system responds with a validation error, the system is working. Your data is the problem: a buyer NTN mismatch, a wrong HS code, a tax calculation that does not reconcile.

What to do: Do not queue these and hope. Fix the underlying record — customer, product or tax line — then re-validate and re-post. Repeatedly retrying an invalid invoice will not make it valid.

What to do during an outage — step by step

Confirm what has actually failed. Try loading any website. If nothing loads, it is your connection. If everything loads but FBR submission fails, it is upstream.
Note the exact start time. Write it down or screenshot it. If a question is ever raised about a delay, this is the first thing you will want.
Keep issuing invoices normally. Do not switch to handwritten receipts and do not skip numbers. Your invoice sequence must stay unbroken.
Confirm your system is queuing, not discarding. Most compliant systems show a pending or unsynced count. If yours shows nothing, stop and check — invoices that were never stored cannot be recovered.
Do not restart or reinstall anything. A well-meaning restart during an outage is one of the most common ways queued invoices get lost.
Tell your staff. Cashiers need to know that the receipt handed to the customer may not yet carry an FBR number, and that this is expected.

What to do the moment it comes back

This is where most of the real risk sits. The outage is over, the shop is busy, and everyone moves on. The queue is quietly forgotten.

Trigger the upload. Good systems do this automatically. Confirm it has started rather than assuming.
Watch the pending count fall to zero. If it stalls, some invoices are being rejected — that is a data problem, not a connectivity one.
Check every invoice received an FBR number. An invoice without a unique FBR invoice number has not been accepted, regardless of what your local record says.
Reprint or reissue where required. If a customer received a receipt before the FBR number was assigned, your process should cover how they get a compliant copy.
Record the outage. Start time, end time, number of invoices affected, and confirmation that all cleared. Keep this with your monthly records.

Do this once, today. Ask your software provider a single question: “If my internet drops mid-sale, what exactly happens to that invoice — and how do I confirm it reached FBR afterwards?” If the answer is vague, that is your real risk, not the outage.

What your software is actually required to do

This is not an optional feature. Under the framework governing electronic invoicing, the software itself is expected to maintain continuous functioning — and in the event of an internet or system failure, to store the invoice data and upload it to FBR’s system within 24 hours of connectivity being restored.

In practice, that means your POS or ERP should:

Store offline invoices locally and durably — not in temporary memory that a restart clears
Preserve the invoice sequence so no numbers are skipped or duplicated
Retry automatically once the connection returns, without someone needing to remember
Show a visible pending count so the queue cannot be silently forgotten
Log the response against each invoice, so you can prove what was sent and when
Separate connectivity failures from validation failures — because the fix for each is completely different

If your current setup does not do these things, an outage is not an inconvenience. It is an unrecorded liability sitting on your counter. Our FBR-integrated POS software handles offline queuing and automatic retry as part of the core system.

Related rule: you now have only 72 hours to correct an invoice

There is a second time limit that interacts with outages, and it catches people out.

Under Sales Tax General Order No. 01 of 2026, cancellations, amendments and deletions are permitted only within 72 hours through the FBR system. Beyond that window, any change requires approval from the Commissioner Inland Revenue — effectively closing the door on retroactive adjustments.

Why this matters after an outage: if invoices sat in a queue for a day and one of them was wrong, you have already spent part of your correction window. The longer the queue sits, the less room you have to fix anything inside it.

This is another reason to clear the queue promptly rather than at the end of the week.

Common mistakes businesses make during outages

Mistake	Why it causes problems
Switching to handwritten receipts	Breaks the invoice sequence and creates records that never enter the system
Skipping invoice numbers “to fix later”	Gaps in sequence are exactly what reconciliation and audit look for
Restarting the system to “reset” it	Can discard queued invoices that were never written to storage
Assuming the queue cleared	Nobody checks, and the failure is discovered weeks later at return filing
Treating rejections as an outage	Retrying an invalid invoice forever; the data was the problem all along
Not recording outage times	No evidence that the delay was caused by a system failure rather than negligence

Reducing the chance of an outage in the first place

Keep a backup connection. A mobile hotspot on a different network costs very little and removes the most common cause entirely.
Put your POS on a UPS. Power cuts are not a reason to lose invoices.
Test your offline mode deliberately. Once a quarter, disconnect the internet, issue a test invoice, reconnect, and confirm it uploads. Do not discover this process during a real outage.
Know who to call. Your integrator’s support number should be written somewhere the cashier can see it, not buried in an email.
Reconcile monthly. Compare invoices issued against invoices accepted by FBR before filing your return, not after.

Frequently asked questions

Can I keep selling if the FBR system is down?

Yes. Businesses may issue invoices in offline mode during internet or power outages. Those invoices must be uploaded to the FBR system within 24 hours of connectivity being restored. Offline mode delays transmission — it does not remove the requirement to transmit.

How long do I have to upload offline invoices?

Within 24 hours of the connection being restored. The clock starts at restoration, not at the start of the outage. Failure to upload within that window may attract penalty action under Section 182, in addition to other legal consequences.

What if the outage is at FBR’s end, not mine?

The same 24-hour rule applies from the point transmission becomes possible again. FBR’s published FAQs acknowledge that the system at the registered person’s end or the licensed integrator’s end may be down for a day or more. Record the error messages and timestamps, and confirm the outage with your integrator so the cause of the delay is documented.

Can I issue a handwritten invoice during an outage?

This is not the intended route. The framework anticipates offline invoicing through your integrated system, which stores the invoice and transmits it later. Handwritten receipts break your invoice sequence and create records that may never enter the system. Keep issuing through your software in offline mode instead.

How do I know whether my invoices actually reached FBR?

Every accepted invoice receives a unique FBR invoice number and carries a verifiable QR code. If an invoice has no FBR number, it has not been accepted — regardless of what your local record shows. Check the pending or unsynced count in your system after every outage and confirm it reaches zero. See our guide on FBR invoice QR code verification.

My invoice was rejected, not delayed. Is that the same thing?

No, and treating it as the same wastes time. A rejection means the system responded — your data failed validation. Common causes are buyer NTN or CNIC format issues, incorrect HS codes, wrong unit of measure, or a tax amount that does not reconcile. Fix the source record, then re-validate and re-post.

What happens if I miss the 24-hour window?

You are exposed to penalty action under Section 182, alongside other legal consequences. The practical advice is to clear the queue as soon as connectivity returns and to keep a written record of the outage — start time, end time, invoices affected, and confirmation that all cleared.

Does an outage affect my sales tax return?

It can. Invoice data transmitted to FBR feeds the relevant annexures of your monthly sales tax return. If invoices are stuck in a queue at month end, your return and FBR’s records will not agree. Reconcile invoices issued against invoices accepted before filing. See our guide on FBR tax return filing.

See how offline mode actually works

Book a free demo and we will disconnect the internet live, issue an invoice, reconnect, and show you exactly how it reaches FBR — so you know before it happens for real.

WhatsApp 0324-2419744

Related guides

This article is for general information only and is not legal or tax advice. FBR rules, timelines and penalty provisions are subject to change through SROs, general orders and other notifications. Always confirm the current requirements applicable to your business on the official FBR website or with a qualified tax advisor before acting. Switcher Techno is not a PRAL or FBR licensed integrator — integration is carried out through a licensed integrator or PRAL.