- CLOUD/EDGE
- ASSESS
- A12 · EINVOICING READINESS SPRINT™
- 3 WEEKS
Wave 1 ready in three weeks.Master data first.ASP selection second, not first.
A UAE enterprise approaching the MoF eInvoicing Wave 1 deadline commissioned a three-week readiness sprint. The engagement inverted the assumed sequence: master data cleanup before ASP selection, not after. Two of the five vendor shortlist candidates were eliminated on scope-boundary and cost-envelope grounds before the competitive process ran. The retained shortlist selection ran on a scoped basis to a defensible ASP choice within eight weeks post-engagement.
N=1 ILLUSTRATIVE COMPOSITE — representative pattern for a UAE enterprise operating at scale. Details drawn from patterns across NexITC engagements and market data. Not a specific client narrative.
THE SITUATION
The situation
The client is a UAE enterprise operating across multiple UAE emirates with a business model requiring high-volume B2B invoicing across a substantial supplier and customer base. Annual invoice volume in the low-to-mid hundreds of thousands, with existing invoicing processes running across two ERP instances following historical acquisitions that had not been fully harmonised.
The MoF eInvoicing rollout had entered procurement conversations. Wave 1 deadline dates were public. Five ASP (Accredited Service Provider) candidates had presented to the CFO and CIO in the preceding quarter, each proposing implementation packages ranging from AED 1.8M to AED 4.5M with 6-10 month timelines.
Two problems surfaced during those presentations. First, the ASP proposals differed substantially in what they treated as "in scope" versus "client responsibility" — particularly around master data quality. Second, the enterprise's own master data condition — duplicate supplier records, inconsistent Tax Registration Number capture, missing HS codes in categories where required — had not been assessed independently.
THE SPECIFIC QUESTION
The specific question
The clinic conversation reframed the sequence. The CFO's operating assumption was: select the ASP, then let the ASP surface master data gaps as implementation risk. The Practice Lead's counter-position: assess master data condition first, then select the ASP against known scope, then implement against agreed responsibility boundaries. Inverting the sequence changed the ASP selection criteria and the implementation risk profile.
The Practice Lead's scoping response confirmed A12 as the right shape: three-week readiness sprint covering master data assessment, regulatory scope validation against Wave 1 requirements, and defensible ASP evaluation criteria — with the criteria published to the ASP shortlist as part of a competitive process rather than accepted from vendor proposals.
APPROACH AND TIMELINE
Approach and timeline
The engagement ran three weeks in parallel across three workstreams.
Week 1 assessed master data condition across both ERP instances: duplicate detection on the supplier and customer masters, Tax Registration Number completeness and format validation, HS code coverage in required categories, and reconciliation gaps between the two ERP instances. Sample-based initially, then extended to full population once sampling surfaced material issues.
Week 2 validated regulatory scope against Wave 1 requirements: Peppol PINT-AE compliance surface, 5-corner CTC model participation requirements, MoF/FTA notification thresholds, and the specific reporting the enterprise's transaction patterns would generate.
Week 3 synthesised evaluation criteria for ASP selection and walked the criteria with the CIO's team and the procurement function. Delivered artefacts: master data remediation backlog with prioritisation, regulatory scope memo, ASP evaluation scorecard weighted against the enterprise's specific operational and integration requirements, and defensible shortlist criteria.
Practice Lead attendance ran across all three weeks. CEO attendance was requested for the CIO-CFO briefing at end Week 3, given the vendor selection process implications.
WHAT WE RECOMMENDED AGAINST
What we recommended against
The recommendation the engagement was scoped to be willing to make.
Two of the five ASP candidates presented in the previous quarter were recommended for elimination from the shortlist during scoping. A third proposal element — a scope-inflation risk — was flagged for exclusion regardless of which ASP was selected.
The first eliminated candidate proposed an implementation package that made no explicit provision for master data condition — effectively treating master data quality as a post-implementation client problem. Recommendation: eliminate on scope-boundary grounds; the master data condition surfaced in Week 1 would have made this ASP's implementation timeline undeliverable within the proposed cost envelope. The scope-vs-cost mismatch was structural, not negotiable.
The second eliminated candidate proposed a proprietary reporting layer beyond the Peppol PINT-AE requirements, marketed as "compliance-plus". Recommendation: eliminate on scope-inflation grounds; the reporting-plus layer added cost without adding regulatory value, and could not be operated independently of the ASP's proprietary platform (vendor lock-in risk).
The third exclusion — a scope element rather than a candidate — was the "master data cleanup as ASP service" positioning that appeared in three of the five proposals. Recommendation: retain master data remediation with the client's internal data quality team, not the eventual ASP. Data quality remediation is a permanent operational capability the enterprise needed to build regardless; outsourcing it to the ASP would have created dependency on the ASP for a capability the client should own long-term.
The retained shortlist reduced from five candidates to three. The competitive process ran on the reduced shortlist over the following six weeks and concluded with a defensible ASP selection at a total implementation cost approximately 30% below the average of the original five proposals.
OUTCOMES
Outcomes
The A12 engagement produced the master data remediation backlog, the regulatory scope memo, and the ASP evaluation scorecard within the three-week timeline. The retained three-candidate ASP shortlist ran through a competitive process across the following six weeks, concluding with a defensible ASP selection at an implementation cost envelope substantially below the original five-vendor proposal average.
The master data remediation ran in parallel with ASP selection rather than after it — approximately 65% of the identified remediation items were resolved by the client's internal data quality team within twelve weeks of the A12 engagement close, before ASP implementation kickoff. The remaining items were structured into the ASP implementation scope with clear responsibility boundaries.
Wave 1 readiness was achieved on the client's own timeline, ahead of the MoF deadline, with a defensible audit trail for the ASP selection process itself — material both for internal governance and for regulator inquiry if it arose.
WHAT COMES NEXT
What comes next
The ASP implementation ran through the following two quarters with NexITC providing scoped advisory checkpoints at agreed acceptance-criteria gates rather than as ongoing engagement. The master data remediation surfaced adjacent data quality patterns the client subsequently addressed through an A6 Data Trust Sprint scoped separately.
Adjacent SKUs: A12 · B23 eInvoicing Integration & Data Cleanup Build™ · A6 Data Trust Sprint™
Facing the eInvoicing Wave 1 deadline with an ASP proposal on the table?
Book a clinic. Practice Lead attends. Master data first, defensible evaluation criteria, scope-boundary clarity — not vendor-provided scope accepted as-is.