Credit Notes, Debit Notes and Self-Billing Under PINT AE: The Document Types Nobody Prepared For
Most businesses will not struggle with their first UAE e-invoicing transaction. They will struggle with the second one.
The invoice has been created, transmitted, and accepted. Then a customer returns goods, a contract value changes, or an adjustment is required after the original document has already entered the system. That is where many implementations face questions they were not designed to answer.
Under PINT AE, businesses need to map more than invoices. The framework defines separate document types for billing, credit notes, and self-billing.
Understanding how these documents work and which document to use in each situation is the difference between a smooth go-live and an unexpected correction issue later.
The six document types PINT AE actually recognises
PINT AE uses specific document codes for invoices, credit notes, and self-billing transactions. Correctly mapping these documents is a key ERP readiness step before connecting with an Accredited Service Provider (ASP).
The official PINT AE Billing specification and Self-Billing specification define the document structures and requirements.
| Code | Document type | Used for |
| 380 | Tax Invoice | Standard supplier invoice |
| 480 | Invoice out of scope of tax | Transactions outside tax scope |
| 381 | Tax Credit Note | Reduction or correction of taxable invoice |
| 81 | Credit Note | Adjustment for relevant non-tax transactions |
| 389 | Self-Billed Invoice | Buyer-issued invoice under self-billing arrangement |
| 261 | Self-Billed Credit Note | Buyer-issued credit note under self-billing arrangement |
The important point is what is not included. PINT AE does not contain a debit-note document type. This affects how businesses design ERP workflows when an issued invoice requires adjustment.
Why is there no debit note in the UAE VAT?
A debit note and a credit note may work as opposite accounting documents, but UAE VAT follows a different adjustment mechanism. When Output Tax increases after an invoice is issued, the supplier must issue a new Tax Invoice.
A Tax Credit Note is used where the VAT amount charged was higher than the amount that should have been charged.
Under Article 62(1) of the Federal Decree-Law No. 8 of 2017 on Value Added Tax, an increase in Output Tax requires the supplier to issue a new Tax Invoice for the additional amount. Where excess VAT has been charged, the adjustment is made through a Tax Credit Note.
The confusion around debit note and credit note arises because debit notes are used in some other VAT jurisdictions and commercial practices. However, under UAE VAT, a debit note is not the mechanism for increasing Output Tax after a supply.
A commercial debit note may still exist in internal accounting processes, but it is not the UAE e-invoicing document for increasing VAT.
Similarly, a negative invoice cannot be used to reverse an issued electronic invoice under the PINT AE rules. The correction must follow the appropriate adjustment process.
The correct document depends on the nature of the correction and the VAT treatment.
The VAT provisions that govern this, and what each one does
A tax credit note under UAE VAT law is governed by specific provisions that determine when it is issued, how the adjustment is calculated, and how it affects VAT reporting.
| Provision | Purpose |
| Article 61 | Identifies events requiring Output Tax adjustment |
| Article 62 | Determines whether to issue a new Tax Invoice or Tax Credit Note |
| Article 63 | Covers VAT treatment after issuing or receiving a Tax Credit Note |
| Article 64 | Covers separate bad debt adjustment rules |
| Article 70 | Sets Tax Credit Note issuance obligations, including Electronic Credit Note requirements under eInvoicing |
| Article 60 of Executive Regulation | Covers Tax Credit Note particulars, buyer-created credit notes and related conditions |
These provisions are available through the official UAE VAT legislation portal.
The practical distinction is:
- Increase in VAT after invoicing → issue a new Tax Invoice.
- Excess VAT charged → issue a Tax Credit Note.
For businesses within the Electronic Invoicing System, Article 70 is particularly relevant because the Tax Credit Note must follow the electronic issuance and transmission requirements where applicable.
Understanding these rules is essential before configuring PINT AE adjustment workflows.
The mandatory fields an adjustment document carries
A credit note format UAE businesses use under traditional VAT rules is not identical to an Electronic Credit Note under PINT AE. Businesses need to distinguish between VAT-law requirements that determine the validity of the adjustment and the additional electronic fields required for validation and transmission.
Article 60 of the UAE VAT Executive Regulation sets the Tax Credit Note requirements. However, Article 60(8) provides specific treatment where the Tax Credit Note is issued as an Electronic Credit Note.
Therefore, businesses should not simply transfer the traditional Tax Credit Note checklist into their e-invoicing system without considering the applicable electronic requirements.
Key information includes:
- Document details — document type, unique identification number and issue date.
- Original transaction reference — reference to the invoice or transaction being adjusted.
- Supplier and customer information — relevant identification and party details.
- Reason for adjustment — explanation of the correction or reduction.
- Amounts and VAT details — taxable amounts and VAT values presented in AED, with applicable currency conversion rules where required.
The PINT AE specifications define the electronic structure, semantic requirements, and validation rules for Electronic Credit Notes.
A common implementation issue is confusing the Tax Identification Number (TIN) used for e-invoicing with the VAT Tax Registration Number (TRN). Under UAE e-invoicing, scheme 0235 identifies the electronic address using the relevant TIN.
Businesses should confirm the correct identifier before ASP onboarding because the e-invoicing participant identifier is not automatically interchangeable with VAT registration details.
The 14-day clock, and what does not start it
A tax credit note under UAE VAT law is not issued based on the original invoice date alone. The 14-day period under Article 62(2) starts from the date the relevant adjustment event occurs under Article 61(1). This means businesses need to monitor the event that changes the VAT position, not simply the date of the original invoice.
The relevant events include:
- cancellation of the supply;
- changes in the consideration agreed between the parties;
- return of goods or services;
- a change in the VAT treatment of the supply; or
- an error in the VAT amount originally charged.
The rule is set out in Federal Decree-Law No. 8 of 2017 on Value Added Tax.
A common mistake is starting the 14-day calculation from the invoice date. For example, if an invoice was issued in January but the agreed price reduction occurs in March, the relevant date is the March adjustment event, not the January invoice.
Not every reduction in an accounting balance creates a credit-note requirement.
For example:
- Bad debts follow the separate bad-debt relief rules under Article 64. A business does not issue a credit note simply because a customer has not paid.
- Foreign exchange movements do not create a credit note where the agreed consideration remains unchanged. The impact is generally dealt with through accounting treatment rather than a VAT adjustment.
- Internal write-offs or provisions do not reduce VAT payable because they do not change the underlying supply.
The treatment of discounts also requires care. A genuine reduction in the agreed consideration may require a credit note, while an unrelated commercial concession may need a different analysis.
Understanding this distinction matters because an incorrectly issued credit note can reduce Output Tax when no VAT adjustment has actually occurred.
Self-billing: codes 389 and 261
Self-billing is an arrangement where the buyer creates the invoice on behalf of the supplier. Under UAE VAT rules, this requires a valid agreement between the parties and compliance with the applicable invoicing requirements. The conditions for buyer-created documents are set out in the UAE VAT legislation.
Under PINT AE, self-billing uses separate document types:
| Code | Document | Created by |
| 389 | Self-billed Invoice | Buyer on behalf of supplier |
| 261 | Self-billed Credit Note | Buyer on behalf of supplier |
The supplier and buyer roles do not change. The buyer only prepares the document under the agreed self-billing arrangement.
A common example is construction, where a main contractor may prepare invoices for subcontractors based on approved work completion records. The same process applies when an adjustment is required through a self-billed credit note, which must maintain the relevant transaction traceability.
The self-billed credit note should also retain a clear link to the underlying transaction and supporting records to allow proper verification of the adjustment.
Before ERP configuration, businesses should document the self-billing agreement, approval process, and document ownership to avoid workflow errors.
The eight-flag transaction type string
PINT AE identifies not only the document type but also certain transaction characteristics through an eight-position transaction-type classification. These flags help apply the correct validation rules for special transaction scenarios.
The eight transaction types are:
- Free Trade Zone transactions;
- Deemed Supply;
- Profit Margin Scheme;
- Summary Invoice;
- Continuous Supply;
- Disclosed Agent Billing;
- Supply through e-commerce; and
- Exports.
The classification is included through the ProfileExecutionID field using the UAE BTAE-02 transaction-type string.
When an adjustment document is issued, the credit note must contain its own valid transaction classification and reflect the nature of the transaction being adjusted. Businesses should not assume that every attribute from the original invoice is automatically copied; the adjustment document must meet the applicable PINT AE validation requirements.
This is why ERP mapping must test not only document creation, but also how transaction characteristics flow into correction and adjustment documents.
How an adjustment travels through the five corners
An Electronic Credit Note does not move directly between two businesses.
Under the UAE Peppol UAE model, the document flows through five points: the supplier, the supplier’s Accredited Service Provider (ASP), the recipient’s ASP, the buyer, and the Federal Tax Authority (FTA) reporting layer.
The process works as follows:
| Stage | What happens |
| Creation | Supplier prepares the Electronic Credit Note in the required format |
| Validation | Supplier’s ASP checks technical requirements before transmission |
| Exchange | Document is routed through the Peppol network to the recipient’s ASP |
| Reporting | Tax Data Document (TDD) information is shared with the FTA |
The official Ministry of Finance eInvoicing framework explains the UAE five-corner model and the role of ASPs.
Where a recipient is not registered on the network or is outside the Electronic Invoicing System scope, the applicable endpoint treatment under the UAE framework should be followed.
The Electronic Invoicing System does not replace VAT return obligations. Businesses remain responsible for ensuring their VAT reporting is accurate and complete.
Once transmitted, an electronic document cannot simply be edited or deleted to achieve a VAT adjustment. Any correction must follow the applicable process, such as issuing a Tax Credit Note where required.
Businesses also remain responsible for record retention. Appointing an ASP or using its storage facilities does not transfer the taxpayer’s legal obligation to maintain supporting documents and records.
For implementation support, ADEPTS assists businesses with UAE e-invoicing readiness, document mapping and workflow design
What Cabinet Decision No. 100 of 2025 changes for e-invoicing
Cabinet Decision No. 100 of 2025 changes how certain VAT invoice and credit-note provisions apply when businesses issue Electronic Invoices. It does not abolish simplified tax invoices across UAE VAT; instead, specific provisions no longer apply within the Electronic Invoicing System environment.
The changes affect Articles 59 and 60 of the VAT Executive Regulation. Under Article 59(16), certain existing Tax Invoice provisions, including simplified Tax Invoice rules and related exceptions, do not apply where a Registrant issues Electronic Invoices under the eInvoicing system.
For businesses, this means reviewing existing invoice processes, including:
- ERP invoice configurations;
- required electronic fields; and
- credit-note workflows under Electronic Credit Note requirements.
Article 60(8) is also relevant because it provides specific treatment for Tax Credit Notes issued electronically.
The full legislative changes are available through the UAE Ministry of Finance tax legislation resources
What it costs to get this wrong
Incorrect e-invoicing setup can create issues under both VAT rules and the Electronic Invoicing System requirements. The applicable penalty depends on the nature of the failure.
| Issue | Applicable framework |
| Electronic Invoicing System violations | Cabinet Decision No. 106 of 2025 |
| VAT invoice and tax-document failures | Cabinet Decision No. 40 of 2017 and subsequent amendments |
Cabinet Decision No. 106 of 2025 introduced specific penalties for failures such as not implementing the system, not appointing an ASP, or not issuing required electronic documents.
These penalties do not automatically apply together for every error. The relevant framework depends on the specific compliance failure.
Businesses implementing eInvoicing voluntarily before their mandatory date are not subject to eInvoicing-specific penalties during that voluntary period. However, existing VAT obligations continue to apply.
A proper readiness review should therefore test more than invoice creation. Credit notes, self-billing and correction workflows also need to be tested before go-live.
The mapping gaps that break at go-live
Most e-invoicing failures do not happen when a business creates its first invoice. They appear when the system has to handle an exception. A credit note against multiple lines, a self-billed reversal, or a correction after transmission can expose gaps that were not identified during initial testing.
Common mapping gaps include:
| Scenario | What needs to be checked |
| Partial credit | The ERP must allow adjustments against only the affected items, not the entire invoice |
| Multi-line invoice credit | The system should correctly link the credit note to the relevant invoice lines |
| Credit across VAT periods | The VAT treatment and reporting period should follow the applicable adjustment rules |
| Self-billed reversal | The workflow must maintain the correct buyer-created document process |
| Special transaction types | The adjustment document must carry the correct transaction classification |
| TIN or administrative correction | The correction approach should follow Ministerial Decision No. 243 of 2025 and applicable PINT AE requirements rather than editing a transmitted document |
A successful implementation is not only about sending invoices. Your ERP, VAT process, and e-invoicing workflow must also handle the documents created after the original transaction.
How ADEPTS handles this for you
Preparing for UAE e-invoicing is not only a system implementation exercise. The key challenge is aligning VAT requirements, document types, and existing business processes before transactions move through the electronic invoicing system.
ADEPTS supports businesses with:
- e-invoicing readiness assessments;
- mapping invoice, credit note and self-billing documents under PINT AE;
- Accredited Service Provider (ASP) evaluation and selection support; and
- ERP adjustment workflow design.
The focus is on identifying document, process, and system gaps before they affect live transactions, particularly where credit notes, self-billing, and special transaction types require different treatment.
Closing
A successful e-invoicing implementation is not measured by whether your first invoice is transmitted successfully. It is measured by whether your systems can handle the transactions that come after it.
Before your mandatory implementation date, review your document mapping, adjustment workflows, and ERP readiness. The gaps found before go-live are easier to fix than errors discovered after electronic documents start flowing.
If your business is preparing for UAE e-invoicing, now is the time to test the documents your system has not yet produced.
FAQs:
No. UAE e-invoicing does not use a debit note to increase Output Tax after an invoice is issued. The supplier must issue a new Tax Invoice for the additional VAT amount as required under Article 62(1) of the UAE VAT law.
A credit note reduces the value or VAT of a previous transaction. A debit note is commonly used in accounting to increase amounts payable, but UAE VAT uses a new Tax Invoice instead when Output Tax needs to increase.
You cannot edit a transmitted electronic invoice to increase its value. Where additional VAT becomes payable, the supplier should issue a new Tax Invoice reflecting the increased amount.
No. A transmitted Electronic Invoice should not be edited or deleted. Any correction must follow the applicable adjustment process, such as issuing a Tax Credit Note where required.
A Tax Credit Note must generally be issued within 14 days from the relevant adjustment event, not from the original invoice date. The trigger depends on the circumstances listed under Article 61 of the UAE VAT law.
No. Bad debt adjustments are handled separately under Article 64 of the UAE VAT law. A business cannot issue a credit note only because a customer has failed to pay an outstanding amount.
The issuer sends the Electronic Credit Note through its appointed ASP. The recipient must also be able to receive electronic documents through the applicable e-invoicing process.
The buyer creates the self-billed credit note on behalf of the supplier under an approved self-billing arrangement. The commercial roles remain unchanged; only the document creation responsibility shifts.
No. The e-invoicing TIN used with scheme 0235 is an electronic identifier and should not automatically be treated as the VAT Tax Registration Number (TRN). Businesses should confirm the correct identifier before onboarding.
E-invoicing-specific penalties apply from the date a business becomes mandatorily required to implement the system. Voluntary users are not subject to those penalties, but normal VAT obligations still apply.
References
- Cabinet Decision No. 100 of 2025 – Issued 12 Aug 2025 (Effective from 29 Sep 2025).
https://tax.gov.ae/Datafolder/Files/Legislation/Executive-Regulation-of-Federal-Decree-Law-No-08-of-2017-Publish-18-09-2025.pdf. - Cabinet Resolution No. (106) of 2025. https://uaelegislation.gov.ae/en/legislations/3714/download.
- ‘eInvoicing’. Ministry of Finance – United Arab Emirates, https://mof.gov.ae/en/about-us/initiatives/einvoicing/.
- Federal Decree-Law No. (8) of 2017 on Value-Added Tax (VAT.
https://uaelegislation.gov.ae/en/legislations/1227/download.
- PINT AE Billing Version 1.0.4 | United Arab Emirates Electronic Document Specifications.
https://docs.peppol.eu/poac/ae/upcoming/pint-ae/. - PINT AE Self-Billing | United Arab Emirates Electronic Document Specifications — Version 1.0.1.
https://docs.peppol.eu/poac/ae/v1.0.1/pint-ae-sb/
Related Articles
