Self Billing Invoice UAE: The Five FTA Conditions That Actually Matter

What is a self-billed (recipient-issued) tax invoice?

A self-billed tax invoice is a UAE tax invoice issued by the recipient of a supply on behalf of the supplier, not by the supplier itself. The document still has to satisfy every mandatory field listed in Article 59 of Cabinet Decision No. 52 of 2017 (the VAT Executive Regulations), together with the self-billing conditions set out in that same article that specifically govern recipient-issued invoices. When the workflow is set up correctly, the recipient can recover input VAT on the supply exactly as if the supplier had issued a normal tax invoice. When any condition fails, that input-VAT recovery collapses and the recipient (not the supplier) absorbs the cost.

Self-billing is not a workflow shortcut. It is a permitted exception for situations where the recipient is genuinely in a better position to calculate the consideration than the supplier. Think of a commodity buyer that grades scrap metal on arrival, a commission-based marketplace that calculates seller payouts from platform data, or a recruitment agency that calculates contractor commissions from timesheet output. In each case the supplier doesn’t know the final value until the recipient has done the measuring — so the FTA allows the recipient to draft and issue the document.

Self billing under UAE VAT — and the self billing arrangements common among Dubai commodity buyers and platforms — is one of the narrower corners of the tax-invoice rules, so it pays to get the mechanics right before e-invoicing hard-wires them. Need a full refresher on standard tax-invoice formatting first? Read our UAE tax invoice format guide — the field requirements there layer on top of everything below. For an overview of the wider 2026-27 rollout, see our UAE e-invoicing 2026 guide, and if you want the setup scoped for you, our e-invoicing setup support in the UAE covers self-billing document types and ASP onboarding.

Where the self-billing rule sits in the rulebook

The legal foundation for self-billing in the UAE is Article 59 of the Executive Regulations to the VAT Law — the same article that sets the mandatory tax-invoice fields. It allows the recipient of a taxable supply to issue the tax invoice instead of the supplier, provided a set of hard conditions is met (covered in detail below). Article 59 sits alongside Article 60 (Tax Credit Notes) as part of the tax-documentation framework. Nothing in the Decree-Law or the Executive Regulations exempts self-billed invoices from the standard field set; everything Article 59 requires of a normal invoice still applies, with the self-billing conditions layered on top.

A small but important point: there is no FTA pre-approval procedure for self-billing. The FTA does not run an application or licensing scheme. You meet the five conditions, you keep the evidence, and you produce that evidence if asked at audit. That makes the written self-billing agreement the central artefact in any FTA review — without it, you have no defensible position regardless of how clean the invoices themselves are.

When self-billing actually makes sense

Self-billing is a niche workflow. Most UAE SMEs will never use it. The scenarios where it adds real operational value are narrow, and each one shares the same DNA: the recipient knows the price; the supplier doesn’t.

There is an organisational point buried in that table that rarely gets raised early enough. A self-billed document is created inside accounts payable, not inside sales. The team that normally receives a purchase invoice and matches it against a purchase order is now the team writing the tax invoice the supplier will rely on for their own VAT return. That is a real transfer of responsibility, and it needs a second pair of hands attached to it: whoever raises the vendor invoice should not also be the person releasing payment against it. Build that segregation in before the first self-billed run rather than retrofitting it after an FTA query.

Outside those patterns, the usual supplier-issues-invoice flow is faster and safer, and it leaves the supplier in control of their own receivables ageing. If a procurement manager pushes for self-billing just “to speed things up”, that’s a tell — you have a process problem, not a documentation one. Fix PO matching and payment cycles first. Moving the invoicing job onto your finance team rarely solves the thing they were actually complaining about.

The five conditions the FTA expects on every self-billed invoice

Article 59 sets out the conditions for a valid self-billed invoice, and in practice they resolve into five hard checks. Each one is a binary pass/fail at audit; there is no “substantially complied” defence.

Before the five, it helps to see exactly what Clause 9 of Article 59 says, because that is the text an FTA officer will be reading. It carries four express limbs, and Clause 10 adds the consequence.

Read against that text, the five practical checks below map cleanly onto four statutory limbs plus one evidential step. Supplier acceptance is not a separate clause in Article 59; it is how you demonstrate, at audit, that the written agreement in 59(9)(b) was live and operating on the date of supply. Treat it as evidence rather than as a fifth rule and the file is easier to defend, not harder.

First, you need a signed written agreement between supplier and recipient stating that the recipient will issue the tax invoice for the relevant supplies. An email exchange or verbal understanding does not qualify, and the agreement should cover scope, duration, renewal, termination, the supplier’s undertaking not to issue parallel invoices, and the recipient’s undertaking to share copies promptly.

Second, the supplier must not issue a tax invoice for the same supply. If a duplicate appears, even an automated one from the supplier’s ERP, Condition 2 fails for that transaction.

Third, the supplier has to accept the recipient-issued document as the valid tax invoice. This is the evidential limb rather than an express clause of Article 59, and acceptance is usually shown by a portal log, a counter-signed PDF, or an explicit “no objection” email after the document is shared. Build the acceptance step into your monthly close: it is what proves the written agreement was live on the date of supply.

Fourth, the document carries the phrase “Tax Invoice raised by buyer” prominently — the specific wording Article 59 requires on a recipient-issued invoice. Many self-billing implementations get this wrong by labelling the document just “Tax Invoice”, or worse “Self-Billing Statement” or “Payment Advice”, none of which is the wording the FTA looks for.

Fifth, both parties must be VAT-registered: Article 59 requires the recipient to be a Registrant, and the supplier must be registered on the date of supply, not the date of payment, so verify the TRN on the FTA portal. If either party has been deregistered, self-billing is invalid for that supply and input VAT cannot be claimed.

How self billing works under UAE VAT

Self billing under UAE VAT does not move the tax — it only moves the paperwork. The supplier still makes the taxable supply and still owes the output VAT on it; the recipient still recovers the input VAT where the normal recovery rules are satisfied. All that changes is who drafts the document. On the supplier’s VAT-201 the supply is reported as standard-rated output tax in Box 1, at the 5% rate, exactly as if the supplier had raised the invoice itself.

On the recipient’s VAT-201 the same amount appears as recoverable input tax in Box 9. Because both returns should carry the identical AED figure for the same supply, a self-billing relationship is easy to reconcile — and a mismatch between the two sides is a classic prompt for an FTA query. The tax point still governs which period the entry lands in: the date of supply under Articles 25 and 26 of the VAT Decree-Law, not the date you happen to raise the self-billed document.

And the recipient must hold a valid tax invoice to support the input claim. Here that invoice is the one the recipient issued to itself, which is precisely why the five Article 59 conditions carry so much weight.

What goes into a UAE VAT self-billing agreement

A written self-billing agreement is the first document an FTA officer asks for, so it earns its place at the front of the file. Under UAE VAT there is no prescribed template, but a defensible agreement covers the same ground every time. Name both parties and record both TRNs. Define the supplies the arrangement covers, and keep it to the supplies where the recipient genuinely calculates the price. State plainly that the recipient will issue the tax invoice for those supplies, and that the supplier will not raise its own invoice for the same transactions.

Set out how the supplier accepts each document — a portal log, a counter-signed copy or a no-objection email — and require the recipient to share copies promptly. Cover the term, renewal and termination, and add a clause requiring the supplier to tell the recipient at once if its VAT registration changes or is cancelled. Have both parties sign and date it, and review it whenever the commercial terms shift.

A tidy agreement like this is worth far more at audit than a folder of emails, and it pairs naturally with the field checklist in our UAE tax invoice format guide.

Self billing between VAT group members

One question comes up often: does self billing apply to supplies inside a UAE VAT group? Generally, no — and for a reason that removes the problem entirely. Supplies between members of the same VAT group are disregarded for VAT, because the group is treated as a single taxable person under the tax-group rules in the VAT Decree-Law. Where a supply is out of scope, there is no output tax, no input tax to recover and no tax invoice to raise, self-billed or otherwise.

So a self-billing agreement is only relevant for supplies that cross the group boundary, to or from a party that is not a member. If your commodity buyer and its grading subsidiary sit in the same VAT group, the internal movement needs no self-billed invoice at all; the arrangement only matters for the external supplier. It is worth mapping the group structure before you set self-billing up, so you are not building document flows for supplies the law already disregards.

If corporate structure and VAT registration are still being sorted, our VAT services page is a sensible starting point.

How PINT AE rewires the workflow

UAE e-invoicing under the PEPPOL PINT-AE specification goes live on 1 January 2027 for VAT-registered businesses with annual revenue at or above AED 50 million (Phase 1), and on 1 July 2027 for all remaining VAT-registered businesses (Phase 2). Accredited Service Providers must be appointed by 30 October 2026 where revenue is AED 50 million or more, under Article 5(1)(a) of Ministerial Decision No. 244 of 2025 as amended by Ministerial Decision No. 66 of 2026, and by 31 March 2027 below that threshold under Article 5(1)(b). Self-billed invoices fall into the same waves as standard tax invoices — there is no separate carve-out.

Intra-group supplies are worth stating precisely, because they are widely misdescribed as excluded. They are not. Article 4 of Ministerial Decision No. 243 of 2025 lists the excluded transactions — sovereign government activity, certain airline services, and VAT-exempt or zero-rated financial services — and nothing in it exempts a transaction merely for being intra-group. What exists instead is a temporary grace period set out in the UAE Electronic Invoicing Guidelines v1.1 (1 June 2026), running 24 months from 1 January 2027 for business transactions between members of the same VAT group.

The Guidelines say plainly that the grace period affects the timing of compliance only, does not remove intra-group transactions from scope, and expires into full application. A grace period published in guidance is a weaker instrument than an exclusion written into a Ministerial Decision, and it should be planned for accordingly.

The architectural change is the 5-corner DCTCE (Decentralised Continuous Transaction Controls and Exchange) model. In the standard supplier-issued flow:

• Corner 1 is the supplier
• Corner 2 is the supplier’s ASP
• Corner 3 is the recipient’s ASP
• Corner 4 is the recipient
• Corner 5 is the FTA exchange

For self-billing under PINT AE, the document still originates with the recipient but the 5-corner positions remain — the recipient (Corner 4) submits the structured XML invoice to its own ASP, which validates, posts a copy to the FTA exchange (Corner 5) and routes the original via Peppol to the supplier’s ASP (Corner 2) for delivery to the supplier (Corner 1). The PINT AE schema includes a document-type indicator that flags the invoice as self-billed, so both parties’ systems and the FTA see consistent metadata.

What that means operationally: under e-invoicing the recipient is not just the issuer on paper, the recipient is also the transmission party. Your ASP contract, your validation rulebook, and your Peppol routing all sit with you, not the supplier. Read our deeper note on the e-invoicing setup advisory for how to scope the ASP appointment and PINT AE readiness work.

“

“Under PINT AE the recipient does not just issue the invoice — the recipient becomes the transmission party. Your ASP, your Peppol routing, your validation logs.”

ASP workflow for self-billing under e-invoicing

The Ministry of Finance publishes and maintains the list of Accredited Service Providers, and Article 5(2) of Ministerial Decision No. 243 of 2025 makes that published list the only authority on who is accredited. Check it directly before you appoint anyone, ask specifically whether the provider supports self-billing document types on its PINT AE roadmap, and check the list again at renewal — accreditation is a status that can change. The workflow at month-end looks broadly like this:

1. The recipient’s ERP (SAP, Oracle, NetSuite, Tally, Zoho, QuickBooks, Odoo, Wafeq) generates the self-billed invoice from goods-received notes, weighbridge tickets or platform commission data.
2. The ERP posts the structured PINT AE XML to the recipient’s ASP via the accredited connector.
3. The ASP runs schema validation against the FTA-published PINT AE rulebook — TRN format, AED rounding, mandatory fields, document-type indicator set to self-billing.
4. On pass, the ASP posts a copy of the validated invoice to the FTA exchange (Corner 5) for tax reporting.
5. The ASP routes the original via Peppol to the supplier’s ASP using the supplier’s Peppol Participant ID (mapped from TRN).
6. The supplier’s ASP delivers to the supplier’s ERP. The supplier’s acknowledgement produces the acceptance evidence automatically — the ASP log becomes the audit-grade record that the written agreement under Article 59(9)(b) was operating.
7. The recipient’s ASP archives the full transmission package — XML, validation result, FTA receipt, Peppol delivery report — for the 5-year retention period.

One consequence of that architecture deserves to be stated bluntly, because it moves money. In a self-billing arrangement the buyer is the Issuer, and Cabinet Decision No. 106 of 2025 attaches the e-invoicing penalties to the Issuer. Failure to issue and transmit an electronic invoice within the prescribed timeline costs AED 100 per invoice, capped at AED 5,000 per calendar month; failure to implement the system or appoint an accredited provider on time costs AED 5,000 for each month or part month; and failure to notify the FTA of a system failure costs AED 1,000 for every day of delay. A UAE buyer running self-billing across several hundred supplier lines is therefore carrying its suppliers’ transmission exposure as well as its own.

The acceptance log is the operational win compared with pre-e-invoicing self-billing. Today you collect a manual email or counter-signed PDF; under PINT AE the ASP provides a cryptographically signed delivery report that is harder to dispute and easier to retrieve at audit. The trade-off: you cannot informally “fix” a self-billed invoice after transmission. Corrections must flow through a structured credit note, not a quiet re-issue.

What to keep on file for five years

Under Federal Decree-Law No. 28 of 2022 on Tax Procedures, the full audit trail must be retained for 5 years from the end of the tax period to which the records relate. For capital-asset records the retention period extends to 10 years under Article 60(2) of Federal Decree-Law 8 of 2017 — a retention rule, not to be confused with the Capital Assets Scheme adjustment period in Article 58 of the VAT Executive Regulation, which runs 10 years for a building and 5 for other capital assets.

Records relating to real estate must be kept for 7 years from the end of the calendar year in which the document was created (Cabinet Decision 74 of 2023), and for 15 years after the end of the tax period where VAT applies, under Article 71(2) of the VAT Executive Regulation.

For a self-billing setup, the audit trail the FTA expects includes:

• The signed self-billing agreement with the supplier, including renewals and termination notices
• Every self-billed tax invoice issued, in the document format actually transmitted (PDF today, PINT AE XML from your mandatory date)
• Supplier TRN validity evidence at the date of each supply (a dated screenshot or API log from the FTA portal)
• Supplier acceptance evidence — email, portal log or, post-PINT AE, the ASP delivery report
• Source measurement records that justify the consideration calculated by the recipient — weighbridge tickets, grading reports, platform commission calculations, contractor timesheets
• Payment records matching each invoice
• Any self-billed credit notes issued, with reference to the original invoice number
• For PINT AE periods, the ASP validation log, FTA receipt and Peppol delivery report for each invoice

Store the agreement and the supporting source records in a location your auditor can find without a treasure hunt. The FTA does not have a “you tried” defence — missing documentation is the same as no documentation.

Where SMEs slip up

The failure patterns in self-billing setups are consistent, and each one traces back to a specific limb of Article 59 of the UAE VAT Executive Regulation. The FTA tests these in the same order, so a self-billing file that survives the first two checks usually survives the rest:

Each of these is fixable in advance and expensive to discover at audit. If you are setting up self-billing for the first time, treat the conditions as a checklist signed off by your tax adviser before the first invoice is issued, not as a clean-up exercise after the first FTA query.

For broader support on getting your VAT and corporate-tax house in order before e-invoicing goes live, see our VAT services and corporate tax services pages. If you need help adapting a current self-billing arrangement to PINT AE, the e-invoicing setup advisory is the right starting point.

If you’re filing this quarter, do this

If you already self-bill, the next three months are about hardening the paperwork before e-invoicing pressure arrives. Pull every active self-billing agreement; check it is signed, in date and covers the right supplies. Run a TRN validity sweep against the FTA portal for every supplier. Reconcile the recipient-issued invoice register against any supplier-issued documents for the last four VAT quarters — a clean reconciliation is your first defence at audit. Build a self-billing document-type indicator into your ERP now so the PINT AE migration is a configuration change, not a re-implementation.

If you are considering self-billing for the first time, weigh the operational benefit honestly. Outside the narrow scenarios where the recipient genuinely controls the price calculation, the supplier-issues route stays simpler and cheaper. Self-billing is a privilege the recipient earns through paperwork — it is not a workflow shortcut the supplier offers.

For the wider e-invoicing context — including the PINT AE specification, ASP selection criteria and the 2026-27 rollout timeline — see our UAE e-invoicing 2026 guide and the tax invoice format guide for the field set every self-billed invoice still has to carry. The detail on quotes versus tax invoices is covered separately in our proforma invoice UAE guide.