Questions to ask an e-invoicing ASP before signing
Turn a UAE e-invoicing provider proposal into written commitments on integration, acceptance, support, records, costs and exit responsibilities.
A provider proposal can describe invoice transmission clearly and still leave nobody responsible for the connection to your accounting system. Before signing, ask what happens when a document leaves the ledger, fails validation, reaches the buyer or remains stuck in reporting. Each answer needs an accountable party and evidence you can inspect.
Use the UAE e-invoicing readiness guide to organise the project. This article supplies a procurement worksheet, not a ranking of providers.
Rules checked on 30 September 2026. This is informational operational guidance, not legal advice. Your tax adviser owns scope and tax classification. Have qualified counsel review contractual liability, privacy and retention terms.
Establish the contracting identity
The MoF register separates accredited providers from pre-approved providers undergoing final accreditation assessment. Record the exact legal name, accreditation entry and date checked. Match that identity to the entity performing regulated exchange and reporting, even if you buy through a reseller.
Ask who contracts with you, who invoices you, and whose accreditation applies. A partner’s logo or global Peppol credentials does not establish the reseller’s UAE accreditation. The provider-accreditation explainer examines that distinction. Recheck status at signature and agree who tells you about a material change.
Keep appointment and implementation separate. For in-scope businesses with revenue equal to or exceeding AED 50 million, Decision 66 sets appointment by 30 October 2026 and implementation by 1 January 2027. Below AED 50 million, consolidated Decision 244, Article 5 sets 31 March 2027 and 1 July 2027. Your scope and deadline decision should precede a contractual launch promise.
Make compatibility a written boundary
Ask for the supported accounting product, edition, version and hosting arrangement. Include custom billing sources and every legal entity being onboarded. Request documentation for outbound invoices, credit notes, inbound supplier documents and status retrieval.
The MoF selection guide expressly raises integration, data management, support, security and pricing questions. Expand those into a responsibility schedule:
- Who extracts and cleans source data, and who approves mappings?
- Who builds the connector, owns its configuration and maintains it after upgrades?
- Which transaction types are excluded or need separate work?
- Where can finance see exchange and reporting outcomes?
- Who handles receiving, duplicate checks and purchase-document review?
If the answer is “your ERP partner”, ask that partner to accept the work in writing. Review whether you can keep the accounting system before agreeing to migration.
Use an evidence scorecard
Copy this table for each shortlisted proposal. Add the supplier’s written answer, attachment reference, internal owner and due date. Use demonstrated, documented only, pending or unacceptable as statuses. A documentation link is useful evidence, but it does not mean your installation passed a test.
| Contract question | Evidence to attach | Acceptance condition to negotiate |
|---|---|---|
| Which entity provides regulated services? | Dated registry check and agreement | Identity and responsibilities agree across documents |
| Does our installation fit? | Supported-version statement and scoped demo | Our required scenarios are included or explicitly excluded |
| What counts as completed transmission? | Status definitions and sample history | Submission, exchange and reporting are distinguishable |
| Who fixes a stuck document? | Escalation schedule and incident example | Named technical and finance owners can obtain evidence |
| What records can we retrieve? | Sample export with document and status linkage | Business can read and reconcile it without the portal |
| What changes cost extra? | Itemised quotation and change policy | Cleanup, upgrades and unsupported scenarios are visible |
| How do we leave? | Termination and migration procedure | Export, access window and transfer responsibilities are agreed |
Treat unresolved identity, missing required workflows or unusable record export as blockers. A low subscription fee should not offset them. Other gaps may be manageable if the contract names the remediation, owner and completion date.
Agree support in business terms
“Support included” needs a schedule. Define service hours, contact channels, response targets, escalation and who coordinates between the ASP and connector supplier. Distinguish acknowledging an incident from restoring service or resolving an individual invoice.
Ask how finance learns about failed reporting, what evidence support supplies, and what happens outside normal hours. Agree who assesses statutory notification duties with the adviser. This worksheet does not set notification deadlines or transfer the business’s obligations. Use the errors and ownership runbook to assign the practical handoff.
Request security and continuity evidence applicable to the actual service, including subcontractors, storage locations, access controls and recovery arrangements. Have the legal reviewer resolve deployment-specific privacy or residency questions rather than treating a certification logo as a complete answer.
Price acceptance and exit as part of the service
Ask how the quote counts successful documents, receiving, credit notes and failed attempts. Separate accounting licences from onboarding, integrations, archive access and ongoing support. Record minimum terms and renewal changes; request the cost of a realistic busy month using your own volumes.
Make an approved acceptance test plan part of delivery scope. Specify what evidence is due, how defects are handled and what happens if a required case fails. A sandbox demo should not be described as completed production readiness.
The MoF guidelines, Appendix 4 distinguish provider transmission logs from retained business documents and leave record responsibility with the business when storage is delegated. Negotiate export formats, related acknowledgements, retrieval charges and access after termination. Rehearse the records and provider-exit checklist before depending on the archive.
Bring the proposal, systems list and unanswered scorecard rows if you ask Nesaku for a systems review. Keep sensitive invoices and credentials out of the initial contact form; agree a suitable sharing channel separately.
Sources and review date
Checked on 30 September 2026: the live MoF provider register; Decisions 244 and 66 for the amended timetable; the MoF provider-selection guide, version 1.0, dated 23 February 2026; and the June 2026 guidelines, version 1.1, Appendix 4. Inline links identify the sources used. The selection-guide filename says 2024 although its cover says 2026. The guidelines’ older first-cohort appointment table is superseded by Decision 66.
The scorecard and acceptance conditions are proposed procurement controls. No provider contract, customer installation or Nesaku ASP accreditation is certified by this article.