UAE e-invoicing: the deadlines, and what changes for the invoices you send on WhatsApp

Today, 30 October 2026, is the date by which every UAE business with revenue of AED 50 million or more had to appoint an accredited e-invoicing provider. On 1 January 2027 those businesses start issuing invoices through the national e-invoicing system, and everyone else follows in 2027.

Finance teams have been preparing for months. Sales and customer teams often have not, and yet they are the ones who send “here is your invoice” on WhatsApp, chase late payments in the chat and answer “can you resend that?”. This post sets out the dates and rules that matter for those conversations, what stays the same and what changes, and how to keep reminders and payment links on WhatsApp once the invoice itself lives in the new system.

This is a summary to plan with, not tax advice. Your accredited provider and your tax adviser have the final word for your business.

The dates

The timeline is set by Ministerial Decision 244 of 2025, with the first deadline moved by Decision 66 of 2026:

Revenue means the gross income of the most recent accounting period, from the financial statements, or other documentation the Federal Tax Authority accepts.

The rules that change how you talk about invoices

A PDF is not an e-invoice. The Ministry of Finance is direct about it: “unstructured invoice formats such pdf, word document, images, scanned copies and emails are not eInvoices.” An e-invoice is structured data that moves from your accredited provider to your buyer’s provider, which also reports the tax data to the Federal Tax Authority. The Ministry calls it a decentralised continuous transaction control and exchange model.

Fourteen business days. Decision 197 of 2026, in force since 1 October 2026, says an electronic invoice or credit note must be issued and transmitted through the system within 14 business days from the date of the transaction.

Consumers are out, for now. Decision 244 says business-to-consumer transactions are not subject to the system, and a business that only sells to consumers is not subject to it, until the Minister decides otherwise.

Some transactions are excluded. Decision 197 lists them, among them certain airline tickets and services, VAT-exempt and zero-rated financial services, and, for 24 months from 1 January 2027, transactions between members of the same VAT tax group.

Choose your provider from the list. The Ministry’s list of accredited service providers held 80 names when we opened it, updated on 29 October 2026, among them Zoho, Tally, SAP, Avalara, ClearTax, Pagero, EDICOM, Comarch, Fonoa and Wafeq.

What this means for your WhatsApp conversations

For a B2B supplier, the invoice stops being a file you attach and becomes a record in your accounting system and the national network. The conversation around it stays exactly where it was. Customers still ask:

• “Did you send the invoice? Our finance team cannot find it.”
• “Can you resend it with our new PO number?”
• “When is it due, and how can we pay?”
• “We paid yesterday; can you confirm?”

Four habits to adjust:

1. Say where the invoice went. “Your e-invoice INV-2027-0142 was issued today through our e-invoicing provider to your company’s provider” helps a finance team more than a PDF does.
2. A copy is a courtesy. If you still send a PDF in the chat, call it a copy, and make sure it matches the e-invoice.
3. Corrections go through the system. A wrong amount is fixed with an electronic credit note, not with “ignore the previous file”.
4. Payment happens on a payment page. Send a link to your payment provider’s page and confirm once the provider reports the payment.

Where MonoChat fits, and where it does not

MonoChat is not an e-invoicing provider. It does not issue e-invoices, does not connect to the Peppol network and does not report anything to the Federal Tax Authority. Your accredited provider does that.

What MonoChat does is the conversation around the invoice: it receives a signal from your accounting system, writes to the customer on WhatsApp, waits for the answer, sends a payment link, and continues once the payment arrives. Your team sees every conversation in one inbox.

Build an invoice reminder flow, step by step

The example uses Zoho Books, which is on the Ministry’s list, but any accounting system that can call a web address works the same way.

1. Create the flow and its webhook. In Flows, create a flow and add a Webhook Received event node. Give it a name and select Create. The node shows its Webhook URL; turn on Require Secret so only your system can start the flow. Choose your WhatsApp Channel and set the Identity Path to where the customer’s phone number will be in the request, for example request.body.phone.

2. Keep the invoice details. Turn on Save Flow Variable in the same node and map the values you need, for example request.body.invoiceNumber, request.body.total and request.body.dueDate, so later nodes can use them.

3. Point your accounting system at it. In Zoho Books, go to Settings, then Workflow Actions under Automation, select Webhooks and click + New Webhook. Paste the MonoChat URL, keep the method on POST, and build the body with placeholders such as the contact’s mobile phone, the invoice number and the total. Then create a Workflow Rule on the invoice module, with the trigger your team wants (Zoho’s help shows “When an invoice is Created”), and choose this webhook under its actions. To see what Zoho really sends, add /test to the end of the MonoChat URL first: the request appears under Captured Request without starting the flow.

4. Open the conversation with a template. WhatsApp only lets a business start a conversation with an approved template. Add a Send Template Message node with a Utility template such as the one below.

5. Wait for the answer. A Question Answer node asks what the customer wants. Once they reply, the 24-hour window is open and the next messages are free-form.

6. Send the details and the link. A Send Payment Request node creates the payment order with your provider (N-Genius, Telr, PayTabs, Ziina, Mamo and others) for the amount in the flow variable and sends the link in the chat. Write its message text yourself: it can use the saved flow variables, for example {{flow.invoice.invoiceNumber}}, and {{paymentLink}} is replaced with the link.

7. Close the loop. Start a step from New Payment Received to thank the customer and tell your finance team, and hand the conversation to a person when the customer disputes the invoice.

Message examples

Utility template to open the conversation

Hello {{1}}, this is {{2}} accounts. A payment reminder is ready for your company. Reply “Details” to see the invoice number, amount and due date here. [Details] [Talk to accounts]

After the reply (free-form, inside the 24-hour window)

Invoice {{flow.invoice.invoiceNumber}} for AED {{flow.invoice.total}} is due on {{flow.invoice.dueDate}}. It was issued through our e-invoicing provider to your company’s provider. You can pay securely here: {{paymentLink}}

When a customer asks for a correction

Thank you for flagging this. We will issue an electronic credit note and a new invoice through the e-invoicing system; our accounts team will confirm here once it is done.

If you sell to businesses and to consumers

Many UAE companies do both: a furniture showroom sells to families and fits out offices, a clinic treats patients and bills insurers or corporate clients, a training centre takes individual sign-ups and company contracts. Only the business-to-business side is in the system for now, so your team needs to know which kind of customer it is talking to before it promises anything about an invoice.

Two simple ways to keep that clear in MonoChat:

• A profile field or a tag for business customers. Set it when a company first orders, and use it in a flow condition, so business customers get the e-invoicing wording and consumers get your usual receipt message.
• One question in the chat. A Question Answer node can ask “Is this purchase for you or for a company?” before your team prepares a quote, and store the answer for later steps.

When the Minister decides to bring consumer sales into the system, the same field tells you at once which conversations change.

A checklist for sales and customer teams

• Know your company’s phase and go-live date, and your provider’s name.
• Agree with finance what a PDF copy may say, and stop calling it “the invoice”.
• Write the correction process (credit notes) into your saved replies.
• Send payment links to your provider’s page, never card or bank details in chat.
• Build the reminder flow and test it with /test before you switch it on.
• Keep B2C conversations as they are; consumer sales are outside the system for now.

MonoChat’s Basic plan is free and Growth is AED 440.70 a month, taxes included. Meta charges the template messages at the AED rates on our pricing page, with no markup from MonoChat.