MINSEONG / GUIDES

UAE eInvoicing for accounts payable: how a Recipient receives and processes Electronic Invoices and Credit Notes under Articles 6, 8 and 9

Published 23 October 2026 · Decisions 243/2025 and 197/2026 read in the official English text on 23 October 2026 · Other official sources last reviewed 22 October 2026 · 11 min read

Most writing about UAE eInvoicing looks at the seller: who issues the invoice, when and through which provider. Yet every in-scope sale also has a buyer, and the rules give that buyer obligations of its own. For accounts payable (AP) teams the questions are practical. What do we have to do with an incoming Electronic Invoice? Can we keep accepting PDFs by email? How do we know whether a supplier’s credit note is right, or whether it arrived on time? Who is allowed to raise an invoice on the supplier’s behalf?

This guide answers those questions from the Recipient’s side, using the text of Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System as amended by Ministerial Decision No. 197 of 2026, and the timetable in Ministerial Decision No. 244 of 2025. It separates what the text says from our own reading, and it lists what we have not been able to confirm. For the seller’s side of the same articles, read our Issuer and Recipient obligations guide first; this page builds on it for AP, procurement and finance operations teams. Our companion accounts receivable and Issuer guide covers the billing side.

For the operational steps to investigate a failed validation, supplier-data mismatch, disputed amount or unclear invoice status, see our invoice rejection and discrepancy workflow. It separates technical exchange status from commercial, tax, accounting and payment decisions.

After an invoice has entered the AP workflow, our three-way matching and duplicate payment controls guide explains how to compare purchase orders, goods receipts and supplier invoices, investigate price or quantity differences, separate payment approvals and retain audit evidence. These are recommended business controls, not additional statutory eInvoicing requirements.

Who counts as the Recipient

Article 1 of Decision 243/2025 defines a Recipient as any Person who receives Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System. The matching Issuer is the Person obligated to issue, transmit, share and exchange those documents. In an ordinary purchase, your supplier is the Issuer and your business is the Recipient. A business that both buys and sells will be a Recipient in its AP ledger and an Issuer in its accounts receivable ledger, so the two sides of a finance team should prepare together rather than separately.

What an Electronic Invoice is, from the buyer’s side

Both Electronic Invoices and Electronic Credit Notes are defined as documents issued, transmitted and received in a structured electronic format that enables automatic and electronic processing. A scanned or emailed PDF is not what the definition describes. For AP this is the most visible change: the document arrives as data meant to be processed by systems, not as an image to be keyed in. Article 7 says the data fields and particulars are those prescribed by the Ministry. We have not reviewed a field-by-field specification, so this guide does not list required fields or describe a file format. Our glossary of key terms explains the other definitions used below.

Article 6(3): the Recipient must process through the system

Article 6(3) requires the Recipient to process Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System. The obligation sits with the buyer, not only with the seller. An in-scope buyer cannot satisfy it by waiting for a PDF and booking it by hand; its AP process has to be able to receive structured documents through the system and handle them there.

Article 6(6), which Decision 197/2026 did not replace, adds that the Issuer and the Recipient report Electronic Invoices and Electronic Credit Notes to the Federal Tax Authority within the timeline prescribed by the Minister. We have not identified that ministerial timeline, so this guide gives no reporting deadline. The practical point for AP is that the Recipient is named in the reporting obligation as well as the Issuer. Our dedicated Article 6(6) reporting obligations guide explains how to confirm the official reporting timeline and design document-level controls without assuming an unverified deadline.

Our reading for AP processes

On our reading, “process” at least means that the receiving, matching and booking of in-scope supplier documents should run from the document received through the system. The text we read does not define the word further, does not say whether the Recipient must accept or reject a document, and does not set an approval or payment deadline. Do not build your process on an assumed acceptance or rejection step until your ASP and adviser confirm what the system provides.

Article 6(7): exchange through your own ASP

Article 6(7) says the Issuer and the Recipient fulfil their Article 6 obligations through the appointment of an Accredited Service Provider. The buyer is therefore not a passive party that simply receives whatever its supplier’s provider sends: it needs its own appointed ASP to receive and process the documents. This is why the ASP appointment dates in Decision 244/2025 matter to AP teams and not only to billing teams.

The accreditation rules changed recently. Ministerial Decision 168/2026, in force from 1 October 2026, replaced the earlier service-provider rules (Decision 64/2025 and its amendments, including Decision 56/2026). It removed the former pre-approval stage and introduced direct accreditation, so an earlier pre-approval label is not the same as accreditation under the current framework. Reconfirm a provider's current accreditation status through official channels before you appoint it. The MoF described the change in its announcement on Decision 168/2026. Our guide to choosing and appointing an ASP covers the selection questions in more detail. For AP, add three questions to that selection: how incoming documents reach your ERP or AP tool, how credit notes are linked to the invoices they correct, and how exceptions are shown to the AP team. These are editorial suggestions, not official criteria, and we name no providers.

Supplier credit notes: the four Article 6(2) cases

Article 6(2) requires the Issuer to issue and transmit an Electronic Credit Note to the Recipient where:

the Business Transaction is cancelled;
the agreed consideration is reduced for any reason;
the consideration is returned in full or in part;
an administrative or numerical error has occurred in relation to the Business Transaction.

What this means for AP

From the buyer’s side these are familiar events: a cancelled order, an agreed discount or price reduction, a refund and an invoice with a wrong amount or detail. The rule places the duty to issue the credit note on the supplier. For AP, the useful consequence is a control: where one of these four events happens on an in-scope purchase, expect an Electronic Credit Note through the system, and track the case until it arrives. Informal fixes such as a supplier email promising a lower amount, or a manual deduction from the payment, do not replace the credit note the rule describes. Our Electronic Credit Notes guide sets out the four cases and the processing flow on both sides.

The text we read does not say how a credit note must reference the original invoice, how a price increase is handled, or how partial returns are calculated. We have not verified official guidance on these points. Agree the treatment with your adviser and your ASP, and test it before go-live with our go-live testing checklist.

Checking supplier timing under Articles 6(4) and 6(5)

The issuing deadline is the supplier’s obligation, but AP is often the first to notice when documents arrive late. Two paragraphs set the timing.

Registrant suppliers follow the VAT Law

Where the Issuer is a Registrant (registered for VAT with a Tax Registration Number), Article 6(4) requires it to issue and transmit the Electronic Invoice and Electronic Credit Note within the timeline prescribed by the VAT Law. Decision 243/2025 does not repeat that timeline and this guide does not state a number of days for it.

Fourteen Business Days, subject to Article 6(4)

Decision 197/2026, in force from 1 October 2026, replaced Article 6(5). The current text requires issue and transmission through the system within fourteen (14) Business Days from the Date of Business Transaction, subject to Article 6(4). The original wording said 14 days. The MoF explained the October amendments in its announcement of 19 October 2026, and our Decision 197/2026 guide covers the other changes.

How a buyer can use this

Our editorial reading is that a Registrant supplier follows the VAT Law timeline, and the fourteen Business Day period applies to suppliers outside Article 6(4). To check timing on your side you need three facts for each purchase: whether the supplier is a Registrant, the Date of Business Transaction (the earlier of the date the transaction occurred or the date payment was received, so advance payments start the clock early) and the count of Business Days (every day except weekends and official Federal Government holidays). The decision does not list those days, so use the current federal calendar. A late document is a matter to raise with the supplier. In Cabinet Decision 106/2025, the penalty for failing to issue and transmit an Electronic Invoice or Electronic Credit Note on time (AED 100 per document, up to AED 5,000 per calendar month) is written for the Issuer; see our Cabinet Decision 106/2025 penalties guide.

Article 8: when an agent sends the invoice

Article 6(1) is expressly subject to Articles 8, 9 and 10. Article 8 lets an agent acting on behalf of a principal issue and transmit the document for that principal. For AP this means an invoice may reach you from an agent rather than from the business you contracted with. Treat it as a matter for your supplier master data: record which suppliers use an agent, so that the AP team can link the document to the right supplier and purchase order. The decision text we read does not describe how the agent and principal must be shown on the document, so we do not describe it here.

Article 9: self-billing only when both parties are Registrants

Some buyers raise invoices themselves for their suppliers, for example on a buyer-generated statement. Article 9 allows the Recipient to issue an Electronic Invoice or Electronic Credit Note on behalf of the Issuer for a supply of goods or services only where both the Recipient and the Issuer are Registrants, and in accordance with the conditions in the VAT Executive Regulation or as otherwise determined by the Minister.

For an AP team running self-billing today, the first step is a supplier-by-supplier check of VAT registration on both sides. Where either party is not a Registrant, Article 9 does not allow self-billing, so the supplier would need to issue its own documents. Where both are Registrants, the VAT Executive Regulation conditions still apply. We have not reviewed those conditions and do not summarise them, so confirm them with your adviser before you carry any self-billing arrangement into the system. Our self-billing guide walks through Article 9 in detail.

Purchases inside a Tax Group

Ministerial Decision 197/2026, which amended Decision 243/2025 with effect from 1 October 2026, treats Business Transactions between members of the same VAT Tax Group as Excluded Transactions for 24 months starting 1 January 2027 (amended Article 4(1)(f)). Check the full list of exclusions in the official text. For AP this matters if your business is a member of a VAT Tax Group. Purchases from another member of the same Tax Group fall within that temporary exclusion. Purchases from suppliers outside the group are not covered by it, so the Recipient obligations above still apply to them unless another exclusion does. Record which supplier accounts are fellow group members so the AP process can treat intra-group invoices separately. We do not calculate the end date of the 24-month period; check the official text and any later decision before relying on it. Our Tax Group exclusion guide explains the rule in more detail.

Other exclusions in the replaced Article 4 also apply to transactions rather than to whole businesses, for example certain airline documents and certain VAT-exempt or zero-rated financial services. Our sector exclusions guide and transaction scope guide explain them. Article 4(3) also lets a Person take part voluntarily for otherwise excluded transactions, in which case the decisions apply to it mandatorily except those on violations and penalties.

B2C purchases and the Article 5(2) exclusion

Article 5(2) of Decision 244/2025 provides that B2C transactions, and persons engaged exclusively in them, are not subject to the system until a ministerial decision determines otherwise. For most AP teams this exclusion is about their customers rather than their own purchases: a business buying from another business is usually described as a B2B purchase. B2B and B2C are editorial labels here; the decisions we read do not define B2B, and we have not confirmed the legal definition of a B2C transaction. Our B2C exclusion guide explains the rule and the word “exclusively” in more detail.

Dates by category

The obligations above start to bite on the implementation dates in Article 5(1) of Decision 244/2025, with Article 5(1)(a) as replaced by Decision 66/2026. The dates apply to persons subject to the system, and Government Entities have their own timetable.

Annual revenue AED 50 million or more: ASP appointment by 30 October 2026; eInvoicing implementation by 1 January 2027. Including exactly AED 50,000,000. Decision 244/2025, Article 5(1)(a), as amended by Decision 66/2026.
Annual revenue below AED 50 million: ASP appointment by 31 March 2027; eInvoicing implementation by 1 July 2027. Decision 244/2025, Article 5(1)(b).
Government entities: ASP appointment by 31 March 2027; eInvoicing implementation by 1 October 2027. Decision 244/2025, Article 5(1)(c), which applies to Government Entities.

Our deadlines guide and the key dates summary explain the categories. One question matters especially to buyers: whether a Recipient in a later category must receive through the system from an earlier-category supplier before its own implementation date. The texts we read do not answer it directly, so we list it as unconfirmed below. Plan your AP readiness for your own category’s dates and confirm the position with your adviser.

AP exception handling: from mismatch to resolution

The legislation establishes document-processing and reporting obligations, but the official material reviewed for this guide does not define every operational status, rejection code, service-level target or recovery procedure. The workflow below is a recommended internal control, not a claim that the Electronic Invoicing System mandates these exact steps. Adapt it to the capabilities confirmed by your ASP, your ERP controls and advice from your UAE tax adviser.

A practical exception workflow

Capture the case. Keep the system document identifier or available reference, supplier, purchase order, invoice or credit note number, document date, receipt timestamp, amount and currency, and a short description of the issue. Record the system status exactly as shown; do not invent an “accepted” or “rejected” status if the interface does not provide one.
Separate technical from commercial questions. A missing transmission, unreadable payload or integration failure belongs first with the AP systems owner and ASP. A price, quantity, tax treatment, delivery or contractual mismatch belongs with procurement and the relevant finance or tax owner. A case may need both tracks.
Prevent duplicate posting. Before entering a manual or replacement document, search the system inbox and purchase ledger using supplier identity, supplier document number, date and amount. If the same document may already have been received or booked, place the posting in an internal review queue while the team checks; do not create a second payable simply to clear an alert.
Preserve the original evidence. Keep the document as received, relevant system messages, purchase order or goods-receipt evidence, correspondence and the case decision in accordance with your retention policy. A staff note or supplier email can explain a discrepancy, but it does not itself become an Electronic Invoice or Electronic Credit Note.
Assign an owner and next action. Record who must respond, what evidence is missing, the next follow-up date under your internal policy and the reason the case can be closed. Escalate unresolved tax interpretation or reporting questions to the designated tax owner or adviser rather than having AP infer a legal treatment.
Close with a traceable outcome. Link the final resolution to the original case: corrected or replacement document received, credit note received, duplicate confirmed, commercial dispute resolved, or technical incident recovered. Reconcile the result to the purchase ledger and retain the audit trail.

Common scenarios and recommended controls

Supplier sends only a PDF by email. For a transaction subject to the system, Article 6(3) requires the Recipient to process Electronic Invoices and Electronic Credit Notes through the system. Ask the supplier to investigate transmission with its ASP and contact your own ASP about receipt. Keep the PDF and correspondence as supporting evidence, but do not assume that the email attachment substitutes for the required system processing. If a business-continuity procedure is needed, document it separately and confirm the compliant treatment with your adviser.
Nothing appears in the AP inbox. Check the supplier and transaction details, the ASP portal or status information available to you, integration queues and incident notices. Ask the supplier to confirm its transmission reference and involve both ASP support teams where appropriate. Record the period affected and the documents potentially missing; do not conclude that no invoice exists solely because the ERP interface is empty.
Invoice total, quantity or purchase order does not match. Compare the structured document with the purchase order, goods-receipt record, approved contract or change order, and the supplier account. Route commercial discrepancies to procurement and tax-sensitive discrepancies to the tax owner. Keep the document and the dispute linked. Do not silently edit the supplier’s source document or assume that a payment adjustment corrects the invoice.
The same invoice may have arrived twice. Compare the supplier’s document reference and the available system identifier, then inspect both the ASP inbox and ERP posting history. Preserve both receipt records if they are distinct transmission events, mark the suspected duplicate for investigation and ensure that only the properly supported liability is posted. Ask the ASP how retransmissions and duplicate indicators are represented; the reviewed decisions do not prescribe a duplicate-detection algorithm.
A credit note is expected but missing. Identify the underlying event—cancellation, reduction in consideration, return of consideration, or an administrative or numerical error—and link it to the original purchase and any related correspondence. Article 6(2) places the issuance and transmission obligation on the Issuer for the listed cases. Follow up with the supplier and track the unresolved balance; do not treat a promise by email or a manual deduction as the Electronic Credit Note itself.
A credit note arrives but the original invoice is unclear. Match the supplier, amounts, dates, purchase order and the event that caused the adjustment. Ask the supplier and ASP how the document should be associated in their systems. The official text reviewed here does not establish a universal original-invoice reference format, so do not invent a mandatory field or reject rule. Escalate unresolved tax or accounting treatment before final posting.
Agent-issued document or self-billing arrangement. Check the supplier-master record and contract to establish who the principal is and whether an agent arrangement is expected. For self-billing under Article 9, verify that both parties are Registrants and confirm the applicable VAT Executive Regulation conditions with an adviser. If the arrangement cannot be substantiated, route it to the tax owner instead of treating an existing commercial practice as automatically compliant.
ASP, network or ERP integration outage. Open an incident with a timestamp, affected systems, supplier or document references, error messages and business impact. Follow the organisation’s approved continuity and security procedures, protect records against loss and duplicate entry, and keep any temporary manual register clearly separate from completed system processing. After recovery, reconcile the affected population against the ASP and ERP records and investigate gaps. The reviewed decisions do not specify an outage grace period or authorise a particular substitute channel, so confirm regulatory handling with the ASP and adviser.
Supplier and Recipient have different implementation dates. Record both parties’ categories and the transaction date, then ask your ASP and tax adviser how the exchange should be handled during the transition. The materials reviewed for this guide do not directly resolve every earlier-supplier/later-Recipient combination. Do not infer that the other party’s date automatically changes your own obligations.

Suggested ownership and escalation

Use a responsibility matrix so exceptions do not remain in a shared inbox without an accountable owner. The following is an internal operating suggestion; it does not assign legal responsibility on behalf of the Ministry or FTA.

AP operations: monitor incoming documents, capture the case, match purchase and receipt evidence, prevent duplicate booking and follow up with suppliers.
Procurement or the business owner: resolve purchase-order, quantity, delivery, contract and commercial price disputes.
Tax or finance policy owner: decide when VAT treatment, Registrant status, exclusions, credit-note accounting or reporting interpretation needs specialist review.
IT and the ASP: investigate transmission, structured-data, access, interface, queue and recovery issues; provide available technical evidence and explain system statuses.
Finance controller: review material unresolved balances, period-end cut-off, aged exceptions and closure evidence under internal policy.

For each open case, keep a status, owner, next action, last update and evidence link. Set response targets internally based on risk and volume; do not present those targets as statutory deadlines. Escalate any issue that could affect a reporting obligation before the relevant official timeline, once that timeline has been verified.

Month-end control: reconcile the whole population

Export or otherwise obtain the period’s available inbound-document listing from the ASP and the corresponding AP or purchase-ledger listing from the ERP.
Compare document counts and totals, then match individual records using the available supplier identity, document reference, date, currency and amount. Use stable system identifiers where available rather than relying only on supplier-entered text.
Investigate documents present in the ASP listing but absent from the ledger, ledger postings with no matching system record, suspected duplicates, unresolved credit notes, failed integrations and documents parked in an exception queue.
Check cut-off around period end and separately identify advance payments, returns, cancellations and documents received after the accounting period. Do not assume the accounting period determines the statutory Date of Business Transaction.
Assign each difference an owner and disposition, retain the reconciliation and supporting evidence, and carry unresolved items into the next period with a clear status. Have the finance controller review material or ageing items under the organisation’s own policy.

This reconciliation is a recommended completeness and accuracy control, not a substitute for the reporting obligation in Article 6(6). The ministerial reporting timeline has not been verified in the sources reviewed for this guide. See our Article 6(6) reporting obligations guide and month-end reconciliation guide for related controls.

What we have not been able to confirm

The number of days in the VAT Law timeline referred to in Article 6(4).
The ministerial reporting timeline under Article 6(6).
Whether the system includes a Recipient acceptance or rejection step, and any time limit for processing.
How a Recipient in a later category should handle documents from a supplier that goes live earlier.
The Article 7 technical specifications and data fields, including how agents, principals and original invoice references appear.
How the penalties are applied in practice. The violations and amounts are set in Cabinet Decision 106/2025, which does not apply to voluntary participants. We have not confirmed its exact entry-into-force date (the Official Gazette publication date) or how the FTA applies it; see our penalties guide.
The self-billing conditions in the VAT Executive Regulation, and which days are federal holidays for Business Day counting.

We state these gaps rather than filling them with estimates. Check the official texts on the MoF eInvoicing programme page and ask a qualified adviser. We also do not name, compare or price any providers or AP software.

An accounts payable checklist

This is an editorial planning list, not an official checklist or a legal test.

Confirm scope and category. Check whether your business and its purchases are in scope with the scope guide, and note your ASP appointment and implementation dates.
Appoint an accredited ASP that covers receiving. Confirm current accreditation under Decision 168/2026 and how incoming documents reach your AP system.
Clean supplier master data. Record each supplier’s VAT registration status, whether it uses an agent under Article 8 and whether it is a fellow Tax Group member.
Review self-billing. List every buyer-issued arrangement and check that both parties are Registrants under Article 9.
Map credit note cases. Link cancellations, price reductions, refunds and error corrections to an expected supplier Electronic Credit Note.
Capture timing data. Record the Date of Business Transaction, including advance payments, and decide how Business Days are counted.
Phase out manual intake. Plan how in-scope supplier PDFs and emailed invoices are replaced by processing through the system under Article 6(3).
Test and assign owners. Run receiving and credit note scenarios using the go-live testing checklist, fit the work into the readiness project plan and score your preparation with the free readiness check.
Reconcile every month. Compare supplier documents delivered through your ASP with the purchase ledger at period end, as described in our month-end reconciliation guide.

Frequently asked questions

Can we keep accepting PDF invoices from in-scope suppliers?

Article 6(3) requires the Recipient to process Electronic Invoices and Electronic Credit Notes through the system, and those documents are defined as structured electronic documents. On our reading, an in-scope purchase should therefore be processed from the document received through the system rather than from a PDF.

Do we need our own ASP if our supplier already has one?

Article 6(7) says both the Issuer and the Recipient meet their Article 6 obligations through the appointment of an Accredited Service Provider. Your supplier’s appointment does not replace yours.

Who must issue a credit note when we return goods?

The supplier, as Issuer, under Article 6(2)(c) where consideration is returned in full or in part. Your AP team should expect the Electronic Credit Note and follow up if it does not arrive.

Can we issue invoices for our suppliers?

Only under Article 9, where both you and the supplier are Registrants and the VAT Executive Regulation conditions, or conditions set by the Minister, are met.

Are invoices from other members of our Tax Group covered?

Business Transactions between members of the same VAT Tax Group are Excluded Transactions for 24 months starting 1 January 2027. Purchases from outside the group are not covered by that exclusion.

Official sources used in this guide

Before go-live, confirm with each supplier its Registrant status, VAT Tax Group membership, ASP appointment, category dates and any self-billing or agent arrangement using the trading partner onboarding guide. To agree which of AP, Tax, IT and your ASP owns each exception and handoff, use our functional responsibility matrix.

Important notice

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 business or transaction is subject to the UAE eInvoicing system or what deadline applies to it. Statements marked as our reading are editorial interpretations, and the items listed as unconfirmed have not been verified. Decisions 243/2025 and 197/2026 were read on 23 October 2026 and the other official sources on 22 October 2026; later decisions may change these rules. Always check the current Ministry of Finance and Federal Tax Authority publications and consult a qualified UAE tax adviser. See all our guides.