E-invoicing for suppliers to UAE government entities: what changes for B2G

The national guidelines treat business-to-government (B2G), government-to-business and government-to-government transactions as in scope. Supplies of goods and services to government entities, including those made through UAE government procurement portals, are subject to e-invoicing.

Sovereign activities of government entities are excluded where the conditions in the guidelines are met. That exclusion concerns the government body’s own activities. It does not take a private supplier’s sales out of scope.

As a supplier, your obligation follows your revenue: businesses with AED 50 million or more go live on 1 January 2027, and those below on 1 July 2027. Government entities appoint a provider by 31 March 2027 and go live on 1 October 2027.

So a supplier with AED 70 million of revenue may be live in January 2027 while its biggest government buyer is not ready to receive until October. The guidelines note that a buyer not yet on the system may still need a regular tax invoice alongside the electronic one. Plan to run both for a while.

Government buyers match invoices tightly to purchase orders, contracts and goods receipt notes. A structured invoice that carries the wrong PO number is still a correct tax document but may sit unpaid for months. Store each buyer’s PO number, contract reference and cost centre on the invoice record, not in a free-text note.

• One customer record per paying entity, with its exact legal name and TRN.
• PO and contract references stored as fields you can search.
• Delivery or completion evidence attached to each invoice.
• Retention and milestone terms captured so partial billing is easy to follow.

A Dubai engineering consultancy has a AED 1.2 million net contract with a federal authority, billed in four milestones of AED 300,000 plus AED 15,000 VAT. Milestone two is approved on 20 February 2027. The consultancy, with AED 55 million of yearly revenue, is already live, so the invoice for AED 315,000 goes through its ASP as a structured document.

The authority is not live until October 2027, so the consultancy also uploads a regular tax invoice through the procurement portal, with the same number, date and amounts. In the ledger nothing is duplicated: one invoice, one receivable of AED 315,000, one output VAT entry of AED 15,000. Only the delivery channel differs.

Government payment cycles are already long for many suppliers. Any mismatch between the structured invoice, the portal upload and the purchase order adds another loop of queries before an approver signs off. For a supplier carrying AED 900,000 of government receivables, a 30-day slip in collection ties up that cash for an extra month, which can mean drawing on an overdraft or delaying supplier payments.

Suppliers that test early with their ASP, and agree with each government buyer how references will be quoted, tend to avoid that slip. Ask the buyer’s finance team which fields they match on and make sure your invoice record holds each one.

HelloBooks keeps PO numbers, contract references and attachments on each invoice, and the AI agent answers questions such as “which invoices to the municipality are unpaid past 60 days, and what PO were they on?”. Receivable ageing shows government balances separately if you group those customers, and payment reminders go by email or WhatsApp with the PO already quoted.

HelloBooks does not upload to procurement portals or transmit e-invoices; you or your ASP do that. If your contracts need a custom field or invoice layout, the team can add it; book a call at /book-a-demo.