CD 106 Article 2: Why Voluntary E-Invoicing Adoption Carries No Penalty Exposure

The Carve-Out That Rewards Moving Early

Article 2(2) of Cabinet Decision No. 106 of 2025 states plainly that the provisions of the decision do not apply to any Person who issues, transmits, shares, exchanges, or reports Electronic Invoices and Electronic Credit Notes on a voluntary basis, in accordance with the decisions issued pursuant to Federal Decree-Law No. 28 of 2022. Read against Article 2(1), which applies the penalty framework to violations of the legislation regulating the Electronic Invoicing System, the effect is a clean line: the AED-denominated penalties in the annexed table attach only from a business's mandatory implementation date.

What This Means in Practice

A business that begins issuing Electronic Invoices ahead of its mandatory phase date is operating in a window where CD 106's penalty structure simply does not reach it. Mistakes made during that voluntary period — a late transmission, a data mismatch, an unreported system disruption — carry none of the AED 100-per-document, AED 1,000-per-day, or AED 5,000-per-month exposure that the same mistakes would carry after the mandatory date arrives. The scope limitation in Article 2(2) is a structural boundary on where the penalty framework applies at all.

Why the Definitions in Article 1 Matter for This Boundary

Article 1 defines Issuer as any Person obligated to issue, transmit, share and exchange Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System, and Recipient as any Person who shall receive them through that system. Both definitions are framed around obligation. A business operating voluntarily has not yet crossed into that obligated status under the mandatory regime, even though it is functionally issuing and receiving the same documents through the same system. The voluntary exclusion in Article 2(2) is consistent with this framing: the penalty regime is built to apply to obligated Persons, and a business acting voluntarily, ahead of its own mandatory date, has not yet become one.

The Strategic Case for Early Adoption

This creates a genuine incentive to move early. A Phase 1 business that begins live electronic invoicing before its mandatory go-live date can use that period to surface integration defects, train staff on the ASP relationship, and correct process gaps around issuance timing and system-failure notification — all without the AED exposure those same gaps would generate once the mandatory date passes. The learning happens in an environment where errors are operationally costly but not financially penalised under CD 106. Businesses that wait until the mandatory date to go live for the first time are, by definition, doing their first-run debugging inside the penalty framework rather than outside it.

Where the Boundary Ends

The protection in Article 2(2) is scoped precisely to the decisions issued pursuant to Federal Decree-Law No. 28 of 2022 — it exempts voluntary activity from CD 106's administrative penalties only, leaving intact any other legal consequences that might attach to a business's conduct under separate tax or commercial law. It also ends automatically and without any transitional buffer at the mandatory date: a business voluntarily compliant on 31 December 2026 and mandatorily obligated from 1 January 2027 moves from full protection to full exposure overnight, with no phased tightening in between. Programme timelines that plan for a "soft launch" straddling the mandatory date should build around that hard edge rather than assume it will be forgiving.