Correcting an FBR e-invoice: the 72-hour rule

Answer first. Since 30 March 2026 you can cancel, delete or edit a valid electronic sales tax invoice yourself, inside FBR’s system, within 72 hours of generating it, where the invoice was wrong because of a bona fide mistake. After 72 hours it needs the prior approval of the concerned Commissioner Inland Revenue, and FBR has published no form, screen or procedure for asking. Three things decide whether the window is any use to you: it closes at month end if month end arrives first; there is no cancel or edit method in the digital invoicing API, so a person has to do it in the portal; and editing a single line item permanently removes your ability to cancel that invoice. A commercial event after the sale — a return, a discount, a price revision — is a credit or debit note whether or not the 72 hours have run.

Where the rule comes from

Sales Tax General Order No. 01 of 2026 (C.No.1(190) ST-L&P/2026/33-166), dated 30 March 2026, is one page long. Its operative sentence on corrections reads:

an integrated person shall only be allowed to cancel, delete, or edit a valid electronic sales tax invoice generated due to bonafide mistake, through the Board’s computerized system within a period of seventy-two (72) hours from the time of its generation.

The proviso adds that any cancellation, deletion or editing after 72 hours is “subject to prior approval of the concerned Commissioner Inland Revenue, in such manner and subject to such conditions as may be specified by the Board.” The order also permits a registered person to engage one or more licensed integrators. It cites sub-sections (5) and (6) of section 23 of the Sales Tax Act 1990 and SRO 1413(I)/2025, and is signed by the Chief (Sales Tax-Operations) with the approval of Member (IR Operations).

Know what you are relying on. This is an administrative general order rather than a gazette notification or a statutory rule. FBR’s own Digital Invoicing “Legal Provisions” page does not list it, and FBR’s published digital invoicing FAQ still answers the question “How can an e-invoice be cancelled?” by quoting section 9 and the credit/debit note route alone, with no mention of a 72-hour facility. Three FBR-published surfaces disagree with each other. The STGO is the later and more specific one.

What counts as a genuine error

“Bona fide mistake” is defined nowhere. It does not appear as a defined term in the Sales Tax Act 1990 or the Sales Tax Rules 2006 in this sense, FBR has published no list of qualifying errors, and the cancel and edit functions carry no reason codes at all. (The enumerated reason field with an “Others” option that forces free-text remarks belongs to debit and credit notes, not to cancellation.)

The workable distinction is one of timing. Cancelling or editing addresses a data error that was already present when the invoice was generated: a mis-keyed quantity, the wrong rate, the wrong item, the same invoice transmitted twice. Anything that happens after a correctly issued invoice — the supply is cancelled, goods come back, the price is renegotiated, the nature of the supply changes — is a section 9 event and calls for a credit or debit note even if you are still inside the window. Cancelling a validly issued invoice because the customer later returned goods misstates the record.

Record why you did it regardless. The Rules require the electronic invoicing or POS system to record every adjustment, modification and cancellation, maintaining logs for each activity (rule 150Q(4), as substituted by SRO 69(I)/2025).

Inside 72 hours: what actually happens

The correction is made in FBR’s system, by a human, in the portal. DI API v1.12 — issued 7 April 2025, last changed 24 July 2025, and still the only technical specification FBR links as at August 2026 — exposes two POST methods, postinvoicedata and validateinvoicedata, plus twelve GET reference lookups. There is no cancel, delete, void or amend endpoint. Corrections cannot be automated, queued or batched from your ERP. They are made on the portal’s invoice screen, where invoices are retrieved by FBR invoice number or by date range and filtered by status.

The conditions the portal applies are set out in PRAL’s Digital Invoicing User Manual v1.6, whose cancellation section was added on 16 April 2026. These are documented behaviour rather than tested behaviour, and every one of them is worth re-checking against the current manual before you build a process on it:

• Only e-invoices received through DI integration are eligible for correction.
• The 72 hours run from the invoice insertion date.
• The invoice number is fixed and cannot be modified.
• Only individual item details can be edited. Header information remains fixed.
• The invoice date cannot be revised to a date earlier than three days before the current system date.
• Invoices linked with Annexure-C are not eligible for correction, and invoices already reported in submitted returns cannot be changed.
• Invoices move to the return 72 hours after posting time or at month end, whichever comes first, and cannot be cancelled afterwards.
• Cancellation is allowed only when the value does not exceed 10% of last month’s sales, and that 10% is the total limit for all invoice modification together, whether a single item or many.
• After modification, a revised invoice is generated retaining the original number and date.

Because the header is fixed, a wrong buyer registration number, a wrong buyer name, a wrong province or a wrong invoice date is not an editing problem. It is a cancel-and-reissue, and only if the next two constraints allow it.

Editing a line forfeits cancelling the invoice

From the same manual: “Once an item on an invoice has been edited, it can no longer be cancelled. As a result, the entire invoice containing that item is also ineligible for cancellation. Each item only be edited once.” And: “The ‘Cancel All’ option is enabled only if none of the items in the invoice have been edited.”

The sequencing rule follows. If there is any chance the whole document is wrong, cancel it first — you cannot edit and then change your mind. The portal’s status filter carries Valid, Edited, Cancelled, Partially Edited, Partially Cancelled, and Partially Edited and Cancelled; the exported PDF marks cancelled and edited items with C and E. Pre-edit details remain viewable against the FBR invoice number.

Month end cuts the window short

An invoice posted at 16:00 on 31 August has roughly eight hours of correctability, not three days. The reason is that the correction window and the return are the same clock: Annexure-C of the sales tax return is auto-filled from the electronic invoices issued by the integrated person (Chapter XIV of the Sales Tax Rules 2006, as substituted by SRO 69(I)/2025), Annexure-C and Annexure-I data are due by the 10th day of the month following the tax period, and an invoice linked to Annexure-C is locked. The window is shortest exactly when invoice volume and error rates are highest.

The 10% cap, and the three things nobody has published

The cap is stated in a single sentence and defines none of its own terms. The manual does not say whether 10% is measured on taxable value or gross value, whether “last month’s sales” means the last filed return, the system’s own recorded DI total or the preceding calendar month, or when the allowance resets. FBR has published nothing on any of the three.

What you can act on is the part that is stated: it is one shared monthly allowance covering every edit and every cancellation. Spending it on small fixes early in the month can leave nothing available for a large erroneous invoice later in the same month.

The clock, and who watches it

The order measures the window from “the time of its generation”. The manual measures it from the insertion date and says invoices move to the return 72 hours after posting time. For an integration that transmits each invoice in real time as it is generated, which is what the system requires, those are the same moment — the acceptance timestamp carried inside the FBR invoice number.

Portal-only access plus a hard clock is a staffing question, not just a technical one. Name the person who holds portal access, make sure the cover extends across month end and public holidays, and make sure whoever spots a bad invoice knows who to tell within hours rather than days.

After 72 hours

The STGO leaves the post-window route to be specified by the Board, and as at 13 August 2026 the Board has specified nothing: no form, no IRIS screen, no API method, no documentation checklist, no stated turnaround, no published conditions. FBR has built this kind of workflow before — the Commissioner’s approval required for a credit note to an unregistered buyer runs through IRIS — which makes the absence here conspicuous.

Two routes do work after the window closes.

A credit or debit note under section 9, subject to the 180-day limit below. This is the normal answer.

A revised return. Under section 26(3) a revised return requires the Commissioner’s approval and must be filed within 120 days of filing the original. Section 26(3A), inserted by the Finance Act 2025, removes the approval requirement where the revised return is filed within 60 days and the tax payable is more, or the refund claimed is less, than in the return being revised — unless the Board’s compliance risk management system restricts it. A correction that increases tax is therefore materially easier than one that reduces it.

How credit and debit notes relate to all this

Section 9 of the Sales Tax Act 1990 covers cancellation of supply, return of goods, a change in the nature of the supply or a change in its value: where the amount shown in the tax invoice or the return needs to be modified, the registered person may issue a debit or credit note and make the corresponding adjustment against output tax in the return.

Who issues which document is routinely reversed in practice:

• Supply cancelled or goods returned, buyer registered. The buyer issues the debit note, in duplicate, carrying the number and date of the original invoice and the reason for issuance (rule 20(1)).
• Same event, buyer unregistered. The supplier issues the credit note — and since the proviso added by SRO 350(I)/2024 dated 7 March 2024, that credit note may only be issued with the prior approval of the Commissioner (rule 20(3)).
• Value or tax increases later. The supplier issues a debit note (rule 21(1)).
• Value or tax decreases later. The supplier issues a credit note (rule 21(2)), and the recipient issues a debit note acknowledging it (rule 21(3)).

180 days. An adjustment that reduces output tax or increases input tax can only be made if the note is issued within 180 days of the relevant supply; the Collector may, on a written request giving reasons in a specific case, extend that by a further 180 days (rule 22(4)). Perishable food destroyed under rule 23 has its own 15-day rule. FBR’s API enforces the limit directly and rejects a late note with “Debit/Credit note can only be added within 180 days of original invoice date.” The adjustment goes into the return for the period in which the note was issued, not the period of the original supply.

Notes must be electronic. The debit note and credit note must also be issued electronically through the integrated system and retained for six years (rule 150S(2)). A paper credit note against a digital invoice does not close the loop.

Sending a debit note is the same payload as a sale invoice with two changes: invoiceType becomes “Debit Note”, and invoiceRefNo carries the FBR invoice number of the original invoice — 22 characters where the seller is registered on an NTN, 28 on a CNIC. That is the reason to persist the FBR invoice number at the moment of submission; without it the original cannot be referenced. Validations to expect, in FBR’s wording: “Invoice Reference No. is mandatory requirement for debit/credit note”; “Reference invoice for debit/credit note does not exists”; “Debit/Credit note date should be equal or greater from original invoice date”; “Credit note is already added to a invoice”, so one credit note per invoice; a credit note’s value of sale and value of sales tax withheld must be less than or equal to the original; a debit note’s sales tax may not exceed the original invoice’s.

The error catalogue also demands a Reason, and Reason Remarks where the reason is “Others”. Neither has a documented field name in any published payload, so there is nothing to look up if you hit it. On document types, v1.12 lists “Sale Invoice” and “Debit Note” for invoiceType and the doctypecode reference sample returns those two — but that response is labelled a sample. Call /pdi/v1/doctypecode with your own production token and treat what comes back as the list for your registration.

A credit note is not self-executing either. Notes go into Annexure-I and become visible to the buyer in his Debit or Credit Note Data. Where a reduction in output tax is not accepted, it is adjusted or recovered through column 7(a) of your next return, and disallowed reductions appear in column 7(c).

What is published, and what is only in a manual

This distinction decides how much weight a limit can carry in your process design.

There is a further wrinkle in FBR’s own documentation. The manual version FBR’s Digital Invoicing technical assistance page links is v1.5, and it contains no cancellation content at all — no mention of cancelling, editing or the 72 hours. Teams building a correction workflow from FBR’s linked documentation will not learn that the function exists. Date every figure you rely on, attribute it to the manual version you read, and re-check before you turn it into a policy.

One live rewrite risk: the Finance Act 2026 added a proviso to section 9, effective 1 July 2026, making the issuance of debit and credit notes subject to a mechanism “including electronic adjustments, as may be prescribed by the Board”. No such mechanism had been prescribed as at 13 August 2026, so rules 20 to 22 still govern — but this is the part of the correction route most likely to change next.

FAQs

Can I cancel an invoice from my ERP through the API? No. DI API v1.12 has postinvoicedata, validateinvoicedata and twelve GET reference lookups. There is no cancel, delete, void or amend method. Every correction is a manual action in FBR’s portal, inside the window, by someone with access. The API’s validateinvoicedata method takes the identical payload and runs the same validation without issuing an invoice number, which is the only pre-flight check available to you.

I posted a wrong invoice at 4pm on the 31st. How long do I have? Until the invoice moves to the return, which is 72 hours after posting or month end, whichever comes first. In that example, hours. Treat the last days of any month as a period where corrections have to happen the same day.

My customer returned goods three weeks after the invoice. Do I cancel it? No. A return is a section 9 event and calls for a note, not a cancellation — and if the buyer is registered, the buyer issues the debit note. Where the buyer is unregistered, you issue the credit note, and that requires the Commissioner’s prior approval under rule 20(3). Either way the note must be issued within 180 days of the supply.

Can I fix a wrong buyer NTN by editing the invoice? No. Header information is fixed, including the buyer details and the invoice number. That is a cancel-and-reissue — possible only if no line item on the invoice has been edited and you still have room under the 10% monthly allowance. If either of those has gone, the invoice stands and you correct through a note or a revised return.

Am I past the window? Can I still ask the Commissioner? The STGO says yes in principle, and specifies nothing about how. There is no published form, IRIS screen, documentation list or turnaround. In practice, plan on a credit or debit note within 180 days, or a revised return under section 26, and treat a post-72-hour cancellation as an exception you negotiate rather than a process you can rely on.

Related reading: what a rejection actually means and how digital invoicing works end to end.