Get the Data Ready Before the ASP

Readiness work starts before provider selection

The Ministry of Finance June 2026 UAE Electronic Invoicing Guidelines describe a system in which an ASP supports exchange and reporting, while the Person subject to the system remains responsible for its obligations. A readiness consultant sits before that technical role. It can organise the evidence, map the source data and prepare questions. It cannot turn itself into the accredited provider.

We recommend starting with the invoices your business actually issues and receives, because they show which source records the provider must test. List the legal entities, invoice series, accounting systems, sales channels and purchase flows. Then collect the customer, supplier, item, tax and entity records feeding those documents. The aim is a pack another provider can read without a meeting devoted to discovering where the data came from.

The deliverable is not a polished spreadsheet with blank columns hidden. It is a decision file. Each gap should say what is missing, which document could prove it, who owns the answer and whether the issue is a source-data fix, a tax decision or an ASP implementation question.

Count the work by entity and exception

A single-entity business with one accounting system and clean masters needs a different review from a group that invoices from an ERP, a point-of-sale system and a sales platform. The source objects drive the work. Count the legal entities, invoice streams, customer records, supplier records, item classes and tax treatments that will enter testing.

Do not estimate the assignment from the number of pages in the Ministry's guide. The PINT AE Mandatory Fields document lists 51 fields, but a field can be easy or difficult depending on the source. An invoice date may be in one table. A buyer electronic address may require reconciliation across a CRM, a customer master and a provider identifier.

Ask for the evidence before fixing a fee or timetable. A prior invoice sample, a source export, the chart of legal entities and the list of known exceptions tell you more than a general description of the business. This is the point where a client can see what is included and what remains with the ASP or tax adviser.

Leave the provider with decisions it can test

A usable pack contains the scope map, source-system map, customer and supplier extracts, item and tax mappings, entity data, invoice samples and an open-item register. Include the owner beside each unresolved row. If the answer depends on a contract, attach an anonymised contract extract or state exactly which document must be checked.

The pack should distinguish data from judgement. A supplier legal name is a source value. Whether a line is standard rated or exempt is a tax decision. Whether the ASP can accept a particular endpoint format is a technical question. Mixing those layers creates a long list that no one owns. Keep the supporting object beside the conclusion.

The Ministry field list gives the required PINT AE data groups. Your pack adds the business context the list cannot know: which entity sells, which system stores the value, which documents support it and which exceptions occur in ordinary operations. That extra layer is what makes the handover usable.

Move from source export to comparable test

First, freeze a dated copy of the source exports and record which system produced each file. Second, remove duplicates and reconcile party identifiers without deleting the original row. Third, map the source columns to the PINT AE fields and mark transformations. Fourth, prepare anonymised invoices and exceptions. Fifth, send the same test pack to the shortlisted ASPs and retain their responses.

That order matters. If provider questions arrive before the source is frozen, the team can change a record to satisfy a demo and lose the evidence of what was wrong. Keep a change note for every merge, tax-code change and entity correction. The record should show the old value, the approved new value and the document or owner supporting it.

If your appointment date is near, begin with the invoice stream that combines the most systems and the most exceptions. A simple invoice may prove the connection. A credit note, advance payment or free-zone transaction shows whether the process can preserve the references and party details that make the record defensible.

• Freeze dated source exports
• Reconcile without deleting original rows
• Map fields and document transformations
• Compare providers using one test pack

Price follows the data problem, not the label

The work expands when there are more legal entities, more invoice sources, more duplicate records, more tax treatments and more exceptions to test. A business with one clean source table can prepare a smaller pack than a group joining several systems. Count those objects before asking for a fee. The useful quote describes the review scope, the output and the client evidence required.

The official guide does not specify a fixed private advisory fee or promise how long an ERP vendor will take to complete its integration. That is the boundary of the evidence. Getting the scope wrong creates two workstreams: cleanup that was not planned and provider integration that cannot be compared fairly. A consultant should state what it will review and hand over, while the chosen ASP confirms its own onboarding, transmission and error-handling work.

The Ministry's Appendix 5 gives a good test for a readiness file. A contract is AED 10,000 plus VAT at 5%. The advance is AED 1,000 plus AED 50 VAT, or AED 1,050. The final invoice covers AED 9,000 plus AED 450 VAT, or AED 9,450. A test pack should preserve the advance invoice reference and show why the final invoice is not for the full contract amount.