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) and the additional conditions in Article 60 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.

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.

Where Article 60 sits in the rulebook

The legal foundation for self-billing in the UAE is Article 60 of the Executive Regulations to the VAT Law. The article allows the recipient of a taxable supply to issue the tax invoice instead of the supplier — provided five hard conditions are met (covered in detail below). Article 60 sits alongside Article 59 (mandatory tax invoice fields) and Article 62 (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 added Article 60 wrapper.

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.

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 60 sets out five conditions. Each one is a binary pass/fail at audit; there is no “substantially complied” defence.

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. Acceptance is usually evidenced 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.

Fourth, the document carries the phrase “Tax Invoice” prominently, exactly as a supplier-issued invoice would. Many self-billing implementations get this wrong by labelling the document “Self-Billing Statement” or “Payment Advice”, which the FTA will not treat as a valid tax invoice.

Fifth, the supplier must be VAT-registered on the date of supply, not the date of payment, so verify the TRN on the FTA portal. If the supplier has been deregistered, self-billing is invalid for that supply and input VAT cannot be claimed.

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). ASPs (Accredited Service Providers) must be appointed by 30 October 2026, with the intra-group VAT-group transition extending until 1 January 2029. Self-billed invoices fall into the same waves as standard tax invoices — there is no separate carve-out.

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 major ASPs in the UAE market — Avalara, Comarch, Basware, Pagero, Edicom, Sovos — each support self-billing as a document type in their PINT AE roadmaps. 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 satisfies Condition 3 of Article 60 automatically — the ASP log is the audit-grade acceptance record.
7. The recipient’s ASP archives the full transmission package — XML, validation result, FTA receipt, Peppol delivery report — for the 5-year retention period.

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 assets (where the Capital Assets Scheme applies under Article 57 ER) the retention period extends to 15 years.

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 we see SMEs slip up

From self-billing setups we have unwound for clients:

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.