An invoice went out in January for SAR 100,000 plus tax. In March the customer returned half the goods. The accountant opened the system, cancelled the original invoice, issued a fresh one at the corrected value, and closed the file.
That single action committed two violations and pushed SAR 7,500 of recoverable tax into a later period — or forfeited it entirely.
That is exactly what most locally-configured accounting systems allow: the button is there and the software raises no objection. The Regulation objects, in three separate places.
First: an issued electronic invoice cannot be deleted or edited
This is not good practice. It is a mandatory technical requirement. The Controls, Requirements, Technical Specifications and Procedural Rules issued by Governor's Resolution No. (62738) dated 23/11/1443H oblige the compliant technical solution to be "capable of protecting the issued electronic invoices and electronic notes against any modification or deletion."
The resolution goes further. In the list of prohibited functions that no compliant solution may contain, two entries appear verbatim:
Allowing the modification or deletion of issued electronic invoices or electronic notes. Allowing the modification or deletion of the records of electronic invoices or electronic notes.
Both sit under the heading "tampering with electronic invoices." The structural reason is that every invoice and note carries a hash that is embedded inside the hash of the next document in the chain — "to guarantee that they cannot be tampered with by deletion or substitution." Delete one document from the middle and every document after it breaks.
If you cannot delete the invoice and cannot edit it, the only remaining instrument for correcting its value is the note. That is what makes a credit note a statutory document rather than an internal bookkeeping courtesy.
When a note is required: the four cases in Article 40
Article 40 of the VAT Implementing Regulation lists the cases in which the value of a taxable supply is adjusted:
- a. The supply is cancelled or suspended after it occurred or was deemed to occur, wholly or partly.
- b. There is a fundamental change or amendment to the nature of the supply that changes the tax due.
- c. The value of the supply was agreed in advance and then modified for any reason — including an additional discount offered after the sale is complete.
- d. Goods or services, or any part of them, are returned to the supplier and the supplier accepts the return.
Point (c) is the one that catches companies out. A commercial discount granted after the invoice was issued — a year-end settlement, a volume rebate, waiving part of the value to close a dispute — all land here. It is not a credit line on the customer's statement. It is an event that requires a statutory note.
Credit or debit? The test is on the tax, not the amount
Article 54 settles it in two lines. Where the amount shown as tax on the invoice exceeds the tax due on the supply, the supplier must provide the customer with a credit note. Where it is less than the tax due, a debit note is required.
The distinction most Arabic explainers drop: the test in the text is the tax, not the supply value on its own. A correction that raises the value while lowering the tax — because the treatment of the supply changed, for instance — is read from the tax side first.
The 15-day deadline: the paragraph added in November 2024
This is the point that most of the pages currently ranking have not caught up with.
Article 54, paragraph 6 now reads:
The taxable person must issue the credit and/or debit notes required under the provisions of this Article no later than fifteen (15) days of the month following the date on which any of the cases requiring the issuance of the note occurred.
That paragraph did not exist in the Regulation. It was added by ZATCA Board Resolution by circulation No. (24-06-01) dated 17 Jumada al-Ula 1446H, corresponding to 19 November 2024 — the same resolution that raised the return-correction threshold from SAR 5,000 to SAR 15,000.
Note a precise difference in where the clock starts. The deadline for issuing an invoice under Article 53 runs from "the month in which the supply took place." The deadline for a note runs from "the date the case occurred" that requires it: the day the return was accepted, the day the discount was agreed, the day the supply was cancelled. The triggering event here is commercial, not logistical — which is precisely why it is missed so often, because it leaves no trace in the inventory system.
The rule that costs you cash: whichever is later
Here is the part that translates straight into liquidity, and it is deliberately asymmetric.
Where the adjustment increases output tax (a debit note), Article 40 paragraph 4 requires you to make it in the return for the period in which the event occurred. No grace, no choice.
Where the adjustment decreases output tax (a credit note), paragraph 5 places it in the return for the period in which the event occurred, or the period in which the credit note was issued to the customer — whichever occurred later.
The increase is owed from the moment of the event. The decrease you only get once you have actually issued the note.
Go back to the opening example. The event — acceptance of the return — happened in March, inside Q1. Had the credit note been issued in March, the reduction would have entered the Q1 return. The note slipped to May, "whichever is later" became May, and the reduction dropped into the Q2 return: SAR 7,500 of tax you finance for an extra three months, on a supply that is half undone.
Repeat that across a hundred returns a year and what looks like administrative slack is in fact an interest-free loan to the treasury. If correcting earlier returns is also on your plate, the four correction routes and when an error is fixed in the next return instead of amending a prior one are set out in the VAT return guide: deadline, penalties and corrections.
What the note must contain
Article 54 paragraph 4 leaves no room for interpretation: credit or debit notes must contain all the details required under Article 53 — every tax invoice field — according to the nature of the invoice they relate to, and must clearly refer to the previously issued tax invoice or invoices to which they relate.
That last phrase deserves a pause. The earlier wording of the Article required a reference to the serial number of the original invoice. It was amended by Resolution No. (21-2-7) dated 4 Rabi al-Akhir 1443H, corresponding to 9 October 2021, so that the reference is now made "as determined by the Authority" — meaning the binding form is the field defined in the technical specification, not a line of free text in the document.
In practice the note carries its own document type code in the XML — 381 for a credit note and 383 for a debit note, against 388 for an invoice — plus a structural reference to the original invoice. A note that mentions the invoice number only in the description field will satisfy your customer and fail clearance. Signing, chaining and type codes are walked through step by step in the ZATCA Phase 2 integration guide in TypeScript.
And if you first want to confirm that the original invoice itself carries the required fields and a valid QR, the compliant tax invoice generator gives you the reference model free.
The note goes through the same gate as the invoice
Many treat the note as an internal document to be emailed over. Resolution No. (62738) separates two paths:
Tax invoices and their associated notes. These are subject to Clearance: the Authority verifies compliance and "applies the cryptographic stamps only to the invoices and notes that meet the controls… and notifies the issuers of those invoices and notes before they are presented to customers." Your credit note is cleared before it reaches the customer, not after.
Simplified tax invoices and their associated notes. These are sent to the Authority by Reporting "within a period not exceeding 24 hours from the date of issuance."
If you are in retail, you are working against a clock measured in hours rather than days, on every return in every branch. When a simplified invoice applies and when it does not — a question that was materially changed — is covered in Article 53 and the simplified invoice.
What lateness costs
There is no penalty article named "late issuance of a credit note." But Article 45 of the VAT Law imposes a fine of up to SAR 50,000 on anyone who "violates any other provision of the Law or the Regulation" — and Article 54 paragraph 6 is a provision of the Regulation.
Two articles are read alongside it:
- Article 46: imposing the fine does not discharge the tax due. You pay both.
- Article 47: repeating the same violation within three years of the previous penalty decision becoming final permits the fine to be doubled.
If you are carrying fines from earlier periods, the penalty waiver initiative remains open until the end of December 2026 with a cut-off date that will not move — the detail is in the ZATCA fines waiver before 31 December 2026.
The other side has an obligation too, on its own clock
The credit note is not the supplier's duty alone. Article 40 paragraph 6 requires the taxable customer to correct its input tax "in the tax period in which the credit or debit note was issued."
A late note therefore creates a reconciliation gap between two registered parties: your reduced output tax lands in one period and your customer's corrected input tax in another — precisely the divergence automated matching is built to surface.
And here is a distinction that gets blurred constantly: an unpaid debt is not a credit note. If you never received the consideration, the route is entirely different. Article 40 paragraph 7 requires five conditions together before output tax can be reduced, among them that at least twelve months have passed since the taxable supply, that the customer is not a related party, and that you hold a certificate from a licensed accountant approved in the Kingdom evidencing the write-off of the debt from the commercial books. Where the unpaid amount exceeds SAR 100,000, you must also show that formal legal proceedings were commenced without result — a court judgment, a bankruptcy of the debtor, or a court order opening any other formal claim procedure.
Conversely, anyone who deducted input tax on a supply and has not paid for it in full twelve months after the month following the month of supply is required by paragraph 10 to adjust the deductible input tax. The equation runs in both directions.
Where this actually breaks: in the system, not the intent
In the invoicing reviews we run, the problem is almost never ignorance of the text. The systems invite the violation:
- The "cancel invoice" button is still visible to the user, while the resolution classifies offering it as a prohibited function.
- The note is created as a free-standing document with no structural link to the original invoice, so it is accepted internally and rejected at clearance.
- The note date is the system entry date, not the date the case occurred — so the 15-day window expires where nobody can see it.
- No alert connects acceptance of a return to issuance of a note. Stock moves; the tax document does not.
- The return report reads the event date only, so reductions are pulled into a period in which the note had not yet been issued — the reverse of what the whichever-is-later rule requires.
Every one of those five is fixable in the integration layer, without replacing your accounting system.
A practical starting point
Pull the list of returns, discounts and cancellations from your system for the last twelve months and put two columns beside each line: date the case occurred and date the note was issued. The gap between those columns is, literally, the number of days you financed the treasury out of your own liquidity — and your list of candidate violations under Article 45, at the same time.
If you want a second read on that list, request a free diagnostic of your notes workflow: we walk through five real cases from your own system and pinpoint where the path breaks — before the Authority pinpoints it for you.
Statutory sources: VAT Implementing Regulation (Articles 40, 53 and 54, and the amendments made by Resolutions No. 21-2-7 and No. 24-06-01) · VAT Law (Articles 41 to 47) · Controls, Requirements, Technical Specifications and Procedural Rules issued by Governor's Resolution No. (62738) dated 23/11/1443H.