MINSEONG.com
MINSEONG / GUIDES

UAE eInvoicing credit notes and price adjustments: worked scenarios for the four Decision 243/2025 Article 6(2) cases, timing and open questions

Published · Updated · Ministerial Decisions No. 243 of 2025 and No. 197 of 2026 read in the official English texts on 23 October 2026 · Other official sources last reviewed 22 October 2026 · 12 min read

Most eInvoicing projects start with the ordinary sales invoice. In day-to-day operations, though, finance teams also have to deal with what happens after an invoice has gone out: a deal is cancelled, a price is reduced, part of what was paid is given back, or a mistake is found. Under the UAE eInvoicing framework in Ministerial Decision No. 243 of 2025, these situations are addressed through the Electronic Credit Note, which Article 1 of the Decision describes, like the Electronic Invoice, as a document issued, transmitted and received in a structured electronic format that allows automatic and electronic processing (our paraphrase). A scanned or PDF credit memo sent by email is not what that definition describes.

This guide works through Article 6 of Decision 243/2025 with commercial scenarios for each of the four credit note cases, the timing rules in Article 6(4) and 6(5), and the internal controls a finance team may choose to set around them. Throughout, we separate three things: what the legal text says (paraphrased), what is our editorial reading or recommendation, and what we could not confirm. Where the text is silent, we say so rather than fill the gap.

How this guide differs from our general credit notes guide

Our Electronic Credit Notes guide is the reference piece: it sets out the Article 1 definitions, the four Article 6(2) cases, the timing rules, issuer and recipient flows, Article 9 self-billing and the interaction with excluded flows. This page is the scenario-led companion. It takes each Article 6(2) case, walks through a worked commercial example, and then focuses on the operational controls (approval, referencing, reconciliation and evidence) that a finance team may decide to put in place. If you need the rule set, start with the general guide; if you need to design or test a credit note workflow, use this one alongside it and our Article 6 Issuer and Recipient obligations guide.

1. What Article 6 says about credit notes

The provisions relevant to credit notes, as we read them in the official English text, are these (paraphrased, not quoted in full):

  • Article 6(1): the Issuer issues and transmits an Electronic Invoice for a Business Transaction, subject to Articles 8, 9 and 10.
  • Article 6(2)(a)–(d): the Issuer issues and transmits an Electronic Credit Note to the Recipient in four cases: (a) cancellation of the Business Transaction; (b) a reduction of the agreed consideration for any reason; (c) a full or partial return of the consideration; and (d) an administrative or numerical error.
  • Article 6(3): the Recipient processes Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System.
  • Article 6(4): an Issuer that is a Registrant follows the timeline set out in the VAT Law for issuing tax invoices and tax credit notes.
  • Article 6(5), as replaced by Ministerial Decision No. 197 of 2026: subject to Article 6(4), issuance and transmission takes place within fourteen (14) Business Days from the Date of Business Transaction. The original text said fourteen days; the Business Days wording comes from the replacement.
  • Article 6(7): the Issuer and the Recipient fulfil their Article 6 obligations through the appointment of an Accredited Service Provider (see our ASP accreditation guide).

Decision 197/2026 entered into force on 1 October 2026, and the Ministry of Finance announced it in a news release dated 19 October 2026. A full list of what that Decision changed is in our Decision 197/2026 changes guide. Article 6 does not, in the text we read, prescribe a data standard, a document format or a particular network architecture for credit notes; those topics belong to the technical specifications and are covered in our data mapping and system integration guide.

2. The four Article 6(2) cases, with worked scenarios

The case labels below follow the legal text. The scenarios, amounts and places are invented editorial illustrations, not official examples, and they do not settle how any specific transaction is treated for VAT purposes.

(a) Cancellation of the Business Transaction

Editorial scenario: a supplier issues an Electronic Invoice for equipment worth AED 750,000. Before delivery, both parties agree to cancel the order. Because Article 6(2)(a) names cancellation as a credit note case, the supplier would issue and transmit an Electronic Credit Note to the buyer rather than relying only on an internal journal reversal. Whether the credit note should cover the full amount and how it should point back to the original invoice are not spelled out in Article 6; see the unconfirmed items below.

(b) Reduction of the agreed consideration for any reason

Editorial scenario: a wholesaler agrees to a retrospective 5% discount once a buyer reaches an agreed volume. The words “for any reason” in Article 6(2)(b) suggest, on our reading, that the commercial cause of the reduction (rebate, settlement, goodwill) does not change the fact that it is a credit note case. How a rebate spread across many earlier invoices should be allocated is not addressed in Article 6.

(c) Full or partial return of the consideration

Editorial scenario: after a dispute, a supplier refunds part of what the buyer paid, for example because some delivered items were rejected and sent back. The legal text speaks of a return of the consideration, not of goods; a return of goods is only one commercial situation that may lead to it. How a partial amount should be calculated (per line, per unit, including or excluding tax) is not set out in Article 6.

(d) Administrative or numerical error

Editorial scenario: a service provider bills AED 45,000 instead of the contracted AED 35,000 because of a keying mistake. Article 6(2)(d) covers administrative or numerical errors, so a credit note is the instrument the text names. Whether the correction should be a credit note for the AED 10,000 difference, or a full credit note followed by a new invoice, is an operational choice that Article 6 does not settle; your ASP and tax adviser are the right people to confirm the approach.

3. Timing: Article 6(4) and Article 6(5)

Two timing rules sit side by side. Article 6(4) says that an Issuer that is a Registrant follows the VAT Law timeline for issuing tax invoices and tax credit notes. Article 6(5), in the wording replaced by Decision 197/2026, sets fourteen (14) Business Days from the Date of Business Transaction, expressly subject to Article 6(4).

Our reading: because Article 6(5) is stated to be subject to Article 6(4), a Registrant Issuer looks first to the VAT Law timeline, and the fourteen Business Days rule is most relevant to Issuers outside Article 6(4). We have not confirmed the number of days in the VAT Law timeline for credit notes, and we have not confirmed which days count as non-business days for the Business Day calculation. We also did not find text explaining how the Date of Business Transaction should be read for a credit note, which is why the application of Article 6(5) to credit notes appears in our unconfirmed list.

Editorial recommendation: until those points are confirmed, record for every credit note the date the triggering event was agreed or identified, the approval date and the transmission date, so that any timing rule that is later confirmed can be checked against evidence you already hold.

4. Recipient side and VAT accounting

Article 6(3) requires the Recipient to process Electronic Credit Notes through the Electronic Invoicing System. Article 6 itself does not, in the text we read, say how either party must account for a credit note in its VAT return, which tax period the adjustment belongs to, or how input tax is to be adjusted by the buyer. Those questions are governed by the VAT legislation and FTA guidance, not by Article 6, and we have not verified them for this guide. Treat any statement about tax periods or input tax adjustments as something to confirm with a qualified UAE tax adviser.

Editorial recommendation for AP teams: route incoming credit notes into the same intake queue as invoices, match them to the related purchase records, and escalate any that cannot be matched. Our accounts payable guide covers the Recipient workflow in more detail, and our accounts receivable guide covers the Issuer side.

5. Linking a credit note to the original invoice: an editorial control

Article 6 lists when a credit note is issued, but the text we read does not specify how a credit note must identify the invoice it adjusts. Linking each credit note to its original invoice is therefore our editorial recommendation for audit traceability, not a requirement we can point to in Article 6. Article 7 says the data fields and particulars are those prescribed by the Ministry; we have not reviewed a field-by-field specification, so we cannot say whether a reference field is mandatory.

  • Reference the source invoice: store the identifier of the original Electronic Invoice on every credit note record in your billing system, whichever ERP you use.
  • Line-level mapping where practical: for partial reductions or returns, map credit lines to the original invoice lines so the adjustment can be explained line by line.
  • Reason codes: tag each credit note with the Article 6(2) case it relies on: (a), (b), (c) or (d).
  • Evidence: keep the approval, the commercial correspondence and the transmission confirmation with the credit note (see our record keeping guide).

6. What the text does not settle (unconfirmed)

The following points are unconfirmed. We did not find them answered in the text of Article 6 we read, and we have not verified them in other official sources. Do not rely on any reading of them without checking current Ministry of Finance and FTA material or taking professional advice.

  • Referencing method (unconfirmed): how, and with which data, a credit note must identify the original Electronic Invoice.
  • Price increases (unconfirmed): Article 6(2) lists reductions only; how an upward price adjustment after invoicing should be documented is not addressed there.
  • Partial-return calculation (unconfirmed): how the amount of a partial return of consideration should be computed and presented.
  • Article 7 fields (unconfirmed): Article 7 leaves the data fields to the Ministry; we have not reviewed a field-by-field specification for credit notes.
  • Article 6(5) and credit notes (unconfirmed): whether, and from which date, the fourteen Business Days rule applies to credit notes, given that it runs from the Date of Business Transaction.
  • Invoices issued before go-live (unconfirmed): how to adjust an invoice issued before a business became subject to eInvoicing, once the credit note is raised after that date.
  • VAT Law timeline (unconfirmed): the number of days the VAT Law allows a Registrant to issue a tax credit note under Article 6(4).

7. Practical checklist for finance and IT teams

These steps are editorial recommendations, not legal requirements.

  1. Map each trigger: list the business events in your company that fall under Article 6(2)(a)–(d) and who approves each one.
  2. Confirm the ASP flow: check with your Accredited Service Provider how credit notes are created, transmitted and received, since Article 6 obligations are fulfilled through the ASP (Article 6(7)).
  3. Capture the source invoice reference: configure your billing system so a credit note cannot be approved without an identified original invoice, as an internal control.
  4. Record timing evidence: keep event, approval and transmission dates so that Article 6(4) and 6(5) can be checked once the open timing points are confirmed.
  5. Agree the VAT treatment: have your tax team or adviser confirm tax period and input tax handling for each credit note type.
  6. Test before go-live: run at least one test credit note for each of the four cases with your ASP.
  7. Reconcile monthly: include credit notes in month-end matching (see our month-end reconciliation guide).

8. Operational workflow: from commercial event to closure

The following is a recommended internal workflow, not a Ministry-prescribed procedure. Adapt the controls to your ERP, delegated authority rules and Accredited Service Provider (ASP). The aim is to keep the commercial event, the decision to adjust consideration, the electronic document and the accounting outcome connected without treating an internal approval as a substitute for the required electronic document.

Step 1 — Open a case and capture the trigger

Open a case when a cancellation is agreed, a discount or rebate is approved, consideration is returned, or an administrative or numerical error is identified. Record the date the event became known, the source of the request, the requester, the business unit and the relevant contract, order or service reference. If the request is still a proposal, label it as pending; do not record a proposed reduction as though it has already been agreed.

Step 2 — Classify the reason and preserve evidence

Select the relevant Article 6(2) category and explain it in plain language. Keep evidence supporting the event: for example, a cancellation agreement, approved rebate terms, a return or refund record, or documentation of the numerical error. If the facts could fit more than one category, record the ambiguity and route it for tax review instead of selecting a label merely to make the system accept the record. The four legal categories come from Article 6(2); any additional internal reason codes are your own design.

Step 3 — Calculate the adjustment and check for duplicates

Prepare a calculation showing the original amount, the portion being adjusted, currency, calculation method and supporting source. For a partial adjustment, explain which goods, services, period or commercial component is affected. If several invoices relate to the same supplier or contract, identify which one or ones are intended to be adjusted and check whether a previous credit note already covers the same event. Article 6 does not itself settle every method for calculating a partial return or allocating a rebate; confirm the treatment with your tax adviser and ASP.

As a recommended duplicate-control, search using more than one signal where available: original invoice reference, supplier identifier, amount, currency, event reference and existing credit-note status. A matching amount alone is not proof of duplication. If a possible duplicate appears, compare the underlying event and existing records, and document why the new request is or is not separate. Do not delete a transmitted record just to clear a warning; preserve the audit trail and use the supported correction process.

Step 4 — Approve and review timing separately

Route the request under your own delegated authority rules. A commercial owner may confirm the event, finance may check arithmetic and accounting references, and tax may resolve VAT questions. These are suggested control roles, not roles or thresholds prescribed by Article 6. Record who decided, when, the evidence considered and any conditions.

Separately record the event date, approval date, document creation date and transmission result. Article 6(4) refers a Registrant Issuer to the VAT Law timeline for tax invoices and tax credit notes; Article 6(5), as amended, contains a fourteen (14) Business Days rule subject to Article 6(4). This guide has not verified the detailed VAT Law credit-note timeline or how the amended date rule applies to every credit-note scenario. Do not present an internal service-level target as the statutory deadline. Confirm the rule for the actual transaction and retain the written conclusion.

Step 5 — Transmit and capture the actual system outcome

Create the electronic document through the configured billing and ASP workflow. Before transmission, compare it with the approved case: parties, amounts, currency, reason, source references and configured required fields. The Ministry's UAE Electronic Invoicing Guidelines, Version 2.0 and Electronic Invoice Mandatory Field Requirements are official starting points for checking current technical material. The field-requirements document is linked for reference only; we have not audited its complete field list here and do not infer a specific mandatory credit-note field from it.

Capture the ASP or system reference, transmission timestamp, result and any error or rejection message. Distinguish a document that is drafted, queued, transmitted, accepted by the relevant system, or failed; use the states actually exposed by your provider. Article 6(7) addresses fulfilment of Article 6 obligations through an ASP. When choosing or reviewing a provider, check the official accredited service-provider list and Ministerial Decision No. 168 of 2026, which governs the updated accreditation framework.

Step 6 — Reconcile, close or reopen the case

Match the credit note to the case, source invoice reference used by your organisation, accounting entry and any related refund, receivable or payable movement. Check that it has not been counted twice in a ledger import and that the related transaction remains traceable. This is a recommended accounting control; the exact ledger treatment and VAT reporting period must be confirmed under the applicable VAT rules. For unresolved mismatches, use the month-end reconciliation guide and record-keeping guide.

Close the case only when the outcome is recorded, such as completed, cancelled before transmission, awaiting evidence, under tax review, or failed and awaiting correction. If reopened, retain the earlier status and reason. A colleague who was not involved should be able to determine what happened commercially, why the credit note was raised, what was transmitted and how the accounting record was reconciled.

9. Exception playbook

  • Missing commercial evidence: keep the case pending and request the missing agreement, return record or error explanation. Do not invent a reason to progress the workflow.
  • Original invoice cannot be matched: compare supplier identity, references, dates and contract context, including whether the record predates go-live. Keep the match unresolved until supported by evidence, and seek ASP or tax advice where the correct treatment is unclear.
  • Amount differs from the approved request: if not transmitted, stop and correct the calculation before repeating configured checks. If already transmitted, preserve the result and use the documented correction path; do not silently overwrite it.
  • Transmission fails or times out: record the provider reference and establish whether the original submission reached the service before retrying. Follow the ASP's documented recovery procedure. This guide does not establish a universal retry method or statutory outage extension.
  • A duplicate is suspected: compare the underlying commercial event and existing credit notes. Do not assume identical amounts prove duplication, and do not erase an existing transmitted record to make the warning disappear.
  • VAT treatment or deadline is uncertain: separate the operational question from the tax conclusion, record the uncertainty and obtain a transaction-specific answer from a qualified UAE tax adviser.

10. Suggested case record and hand-off checklist

A controlled ERP workflow or case-management record can include: case ID; supplier and recipient identifiers; source invoice reference if available; Article 6(2) reason; commercial event and evidence location; requested and approved amounts; currency; relevant dates; tax-review status; internal decision-maker; ASP reference; transmission result; accounting reference; reconciliation status; current owner; next action; and closure date. These are suggested internal fields, not an official data schema. Apply normal access controls and retention policy rather than copying full invoice data into an uncontrolled tracker.

  • Commercial event and supporting evidence are recorded.
  • The Article 6(2) category is documented; ambiguity is escalated.
  • Amount and currency are checked, and possible duplicate adjustments are investigated.
  • The source invoice or related transaction is traceable where available; unmatched references are flagged.
  • Timing and VAT questions are identified without treating an internal target as law.
  • The electronic document's actual ASP or system outcome is recorded.
  • Accounting and reconciliation references are linked, with an owner and next action for unresolved items.
  • Evidence is stored under the organisation's approved access and retention controls.

11. Additional frequently asked questions

Should a credit note be transmitted again if the ASP response is delayed?

Not automatically. First establish whether the original submission reached the service and whether a document reference or status exists. Follow the provider's documented recovery process and preserve response evidence. This guide does not prescribe a universal retry rule; an unverified retry can create duplicate-processing risk.

Can an internal credit memo replace an Electronic Credit Note?

An internal memo can document an approval or accounting action, but should not be assumed to replace the Electronic Credit Note described in the UAE eInvoicing framework. Article 6(2) identifies cases for issuing and transmitting an Electronic Credit Note. Confirm the required treatment for the transaction with your ASP and a qualified UAE tax adviser.

What evidence should be kept for a partial adjustment?

As an internal-control recommendation, retain the commercial agreement or return/refund evidence, the calculation, relevant source references, approval record and transmission outcome. The exact legally required fields and evidence depend on applicable legislation and technical requirements; this list is not represented as a statutory minimum.

Can finance use a spreadsheet to track credit notes?

A controlled tracker may help manage ownership and exceptions, but should not become an uncontrolled substitute for the source electronic document or accounting system. Restrict access, avoid unnecessary invoice data, identify the authoritative record and reconcile the tracker to system outcomes.

What if the original invoice predates eInvoicing go-live?

The treatment of a pre-go-live invoice adjusted after a business becomes subject to the system remains unconfirmed in this guide. Preserve the original evidence and transaction dates, then confirm the applicable route with current official guidance, your ASP and a qualified UAE tax adviser. Do not assume a particular electronic correction is always required.

12. Frequently asked questions

When does Article 6 call for an Electronic Credit Note?

In four cases listed in Article 6(2): cancellation of the Business Transaction, a reduction of the agreed consideration for any reason, a full or partial return of the consideration, and an administrative or numerical error.

Does Article 6 require the credit note to reference the original invoice?

We did not find such a requirement stated in Article 6. Referencing the original invoice is our editorial recommendation for traceability; the exact referencing method is unconfirmed and may be set in the technical specifications.

How quickly must a credit note be issued?

A Registrant Issuer follows the VAT Law timeline (Article 6(4)). Article 6(5), as replaced by Decision 197/2026, sets fourteen (14) Business Days from the Date of Business Transaction, subject to Article 6(4). The number of days in the VAT Law timeline and the way Article 6(5) applies to credit notes are unconfirmed.

Is a return of goods the same as case (c)?

Not exactly. The legal text refers to a full or partial return of the consideration. Goods being sent back may lead to such a return, but the case is framed around the consideration.

What about a price increase after the invoice was issued?

Article 6(2) covers reductions only. How an increase should be handled is unconfirmed; check with your ASP and tax adviser.

Can the buyer issue the credit note instead of the supplier?

Article 9 allows the Recipient to issue an Electronic Invoice or Electronic Credit Note on behalf of the Issuer only where both parties are Registrants, under the VAT Executive Regulation conditions or as otherwise determined by the Minister. See our Article 9 self-billing guide.

Does Article 6 tell me which VAT period a credit note belongs to?

No. That is a VAT question outside Article 6, and we have not verified it for this guide. Confirm it with a qualified UAE tax adviser.

13. Related guides and official sources

This guide is general information prepared by MINSEONG.COM, an independent website. It is not legal or tax advice, it is not an official government publication, and it does not determine whether any transaction is subject to specific tax treatments. Statements marked as our reading or recommendation are editorial, scenarios are invented illustrations, and unconfirmed items have not been verified. Decisions 243/2025 and 197/2026 were read on 23 October 2026 and other official sources on 22 October 2026. Always check current Ministry of Finance and Federal Tax Authority publications and consult a qualified UAE tax adviser. Browse all our guides or try the readiness check.