Every UAE finance team scoping eInvoicing readiness arrives at NexITC with a similar sequence in mind: pick the ASP, integrate it with the ERP, go live before the mandate deadline. What is rarely present when the CFO asks 'why is the ASP selection stuck?' is the specific answer — the specific master data fields failing CTC validation, the specific tax-code mappings unaligned with FTA schema, the specific buyer/supplier reference data missing Peppol IDs. ASP selection is stuck because ASP selection is the wrong first question. The right first question is whether master data can survive the CTC layer.
The instinct is to accelerate ASP selection to unblock the programme. The instinct produces a signed ASP contract and a delayed go-live because the first invoice submission cycles through rejection loops. What actually produces mandate-readiness is starting with master data — the specific fields that drive CTC-layer rejection, quality-assessed against Peppol PINT-AE schema requirements, remediated before ASP integration begins. A12 does that work on a fixed scope in 2 weeks. Master data first, because rejection at the CTC layer costs more than remediation at the master data layer — and ASP selection becomes tractable once the master data question is resolved rather than deferred.
Six streams,
ending in the board plan signed.
Obligation profile and master data sampling front-load week 1. ASP scoring, Peppol PINT-AE gap analysis, and board compliance plan close week 2. Two phases; six streams tightly sequenced against the mandate deadlines.
Obligation profile against entity structure
The specific MoF/FTA eInvoicing obligations applicable to your entity structure confirmed — VAT-registered entities in scope, invoice classes (B2B / B2G / B2C where CTC applies), phased timelines per entity, cross-border considerations. Scope ambiguity here extends every subsequent phase.
Master data sampling and validity check
Sample invoice data extracted from ERP for CTC-critical fields: TRN validity, tax code mapping to FTA schema, Peppol IDs on buyer/supplier records, reference data completeness. Sample size calibrated for statistical significance without extending the sprint duration.
Master data quality assessment
Every CTC-critical field scored on validity against Peppol PINT-AE schema requirements. Failure patterns named at the specific field and record class level — not aggregated to 'master data needs cleanup.' This is where most engagements do the load-bearing work, because master data failures at the CTC layer are the leading indicator of go-live delay.
Defensible ASP evaluation criteria
The ASP shortlist scored on your criteria — technical fit with your ERP, PINT-AE compliance maturity, geographic coverage, pricing model, service level commitments. The scorecard is criteria-based; where NexITC holds a commercial relationship with an ASP, the Practice Lead discloses it at scoping. Where three or fewer ASPs match your criteria, the shortlist may be short — we do not pad it to hit a headline number.
PINT-AE / 5-corner CTC gap analysis
Technical fit assessment against Peppol PINT-AE standard and 5-corner CTC model — where your ERP integration approach aligns, where custom middleware fills gaps, where the ASP handles transformation. Gaps documented at the specific integration-point level for downstream build scoping.
Costed remediation backlog & board plan
Master-data remediation backlog with cost estimates per work package and named owner. Board compliance plan against October 2026 ASP appointment and January 2027 go-live deadlines. Direct executive readout with CFO, Tax Director, and IT lead. Board sponsor briefing where the mandate is a board-level compliance concern.
Two weeks.
Two phases.
Duration is fixed at 2 weeks. Phase count is fixed at 2. Milestones are signed gates — not aspirations. Most organisations should start A12 with sufficient runway before the October 2026 ASP appointment deadline to allow B23 build time before January 2027 go-live.
The readiness,
run on master data first.
Every A12 engagement follows a fixed methodology tuned to your entity structure and ERP landscape in the first two days. Not an ASP procurement exercise; not an ERP replacement scoping. The sequence that produces mandate-readiness in 2 weeks against the specific master data quality gates that drive CTC-layer rejection.
From ASP selection stuck
to board plan signed.
A typical pre-engagement state has an ASP selection in progress, master data quality unassessed against CTC requirements, and a board compliance plan that reads as intent rather than execution. The engagement produces the evidence base under which the CFO can defend 'this is what we're doing, this is what it costs, this is how we make October and January.'
Reference pattern. Some engagements surface that master data quality is stronger than assumed and the leverage sits elsewhere (ERP integration complexity, cross-border invoice classes, entity-level obligation ambiguity). That's a legitimate finding, not a failure. The alternative is manufacturing master data findings to justify remediation work that isn't needed — which erodes the honest advisory posture the mandate compliance conversation requires.
A UAE manufacturer,
master data cleared before ASP signed.
Representative pattern for a UAE manufacturing group with multi-entity structure — VAT-registered subsidiaries in scope, ERP consolidation on SAP, ASP selection stuck at technical fit questions. Ranges reflect target outcomes NexITC underwrites in scope for this class of engagement. N=1 — illustrative composite, not a specific client.
Five artifacts,
each with signed acceptance.
Every deliverable has documented acceptance criteria signed at engagement kickoff. Nothing more, nothing less.
eInvoicing Obligation Profile
The specific MoF/FTA eInvoicing obligations applicable to your entity structure — VAT-registered entities in scope, invoice classes where CTC applies, phased timelines per entity, cross-border considerations. The document that answers 'what applies to us and when?' with specific evidence.
Defensible ASP Selection Criteria
The ASP shortlist scored on your criteria — technical fit with your ERP, PINT-AE compliance maturity, geographic coverage, pricing, SLAs. Criteria-based by design; where NexITC holds a commercial relationship with an ASP, the Practice Lead discloses it at scoping.
PINT-AE / 5-Corner CTC Gap Analysis
Technical fit assessment against Peppol PINT-AE and the 5-corner CTC model. Where your ERP integration aligns, where custom middleware fills gaps, where the ASP handles transformation — documented at integration-point level for downstream B23 scoping.
Master-Data Quality Report
Every CTC-critical field scored on validity — TRN validity, tax code mapping to FTA schema, Peppol IDs on buyer/supplier records, reference data completeness. Failure patterns named at specific field and record class level — not aggregated to 'master data needs cleanup.'
Costed Remediation Backlog & Board Compliance Plan
Master data remediation backlog with cost estimates per work package, named owner, and CTC-rejection-risk-weighted sequencing (the fields that would cause first-invoice rejection go first, not the fields easiest to clean). Paired with the board compliance plan against October 2026 ASP appointment and January 2027 go-live deadlines — the document the CFO and audit sponsor use to demonstrate mandate compliance progress at board level. Not intent; execution.
Six outcome metrics,
measured pre and post.
Success is not "the assessment happened." It is measured against six specific outcomes captured at engagement start, at handover, and at 30/60/90-day check-ins during downstream execution.
Honest scoping.
A12 is a fit when specific conditions are met. It is not a fit when other conditions are — and "master data quality is stronger than assumed and the leverage sits elsewhere" is a legitimate finding we surface early rather than manufacturing findings to justify remediation.
A12 has a quadruple buyer register — CFO for compliance narrative, Tax Director for FTA-schema alignment, Finance Controller for operational cadence, IT lead for ERP integration scoping. All must engage at readout for the board plan to convert to signed execution.
Read-only access to invoice-level data in your ERP (SAP, Oracle NetSuite, Microsoft Dynamics, or equivalent) for master data sampling. Sample sizes calibrated for statistical significance — access negotiation post-kickoff extends timeline; sort it up front.
Documented entity structure with VAT registration status per entity. Multi-entity organisations must confirm which subsidiaries are in scope for wave 1 vs later phases at kickoff — scope ambiguity carries into Phase 2 and corrupts obligation profiling.
Either an existing ASP shortlist under evaluation, OR willingness to build one from the criteria-based scorecard. A12 does not proceed without an ASP-shortlist scope agreed at kickoff.
Board-level acknowledgment that October 2026 ASP appointment and January 2027 go-live deadlines are procurement-real and remediation appetite is committed. Assessments run against non-committed timelines produce plans that lapse before execution begins.
That's B23 eInvoicing Integration & Data Cleanup Build™ — fixed-scope Cloud/Edge build engagement executing the ERP-to-ASP integration and master data cleanup A12 identifies. Sequence: A12 → B23 when the plan needs definition first; B23 directly when the plan is already signed and remediation scope is known.
That's A3 Compliance Fast-Track™ UAE — 2–4 week compliance readiness for PDPL, Dubai ISR, ADHICS v2 with eInvoicing evidence stream integrated (broader scope, less eInvoicing depth). Some organisations sequence A12 (deeper eInvoicing) and A3 (broader compliance) within the same annual cycle.
That's C6 ComplianceOps™ UAE — continuous compliance evidence refresh, quarterly audit-cycle preparation. A12 stands up eInvoicing readiness; C6 operates the ongoing compliance cadence including eInvoicing evidence stream.
NexITC is not an Accredited Service Provider, and where a commercial relationship with a specific ASP exists the Practice Lead discloses it at scoping. Where the request is 'tell us which ASP to pick,' the honest answer is 'we can score them against your criteria, but the selection is yours.' Organisations wanting a specific-ASP recommendation are better served by an ASP's own sales process — not by A12's criteria-based scoring.
Fixed fee.
Milestone-based. No surprises.
Every A-tier engagement is scoped and priced upfront against defined deliverables. Milestones tied to signed gates. Change orders negotiated through the Practice Lead, not surfaced as invoice surprises.
Five, most asked.
Q_01Why start with master data instead of ASP selection?
Because rejection at the CTC layer costs more than remediation at the master data layer. Every invoice that clears the ASP but fails at the government tax authority creates rework loops that consume finance and IT capacity for months post-go-live.
Starting with master data — the specific fields that drive CTC-layer rejection, quality-assessed against Peppol PINT-AE schema requirements — means ASP selection becomes tractable rather than stuck.
The ASP question is not 'which is best?' It is 'which one your master data can actually work with.' That question is answerable once master data quality is assessed; unanswerable when it isn't.
Q_02Are you an Accredited Service Provider (ASP)?
Q_03What is the 5-corner CTC model and why does it matter?
Q_04What if our master data is better than we assume?
Q_05What comes after A12?
One name.
Six accountabilities.
Specialist consulting means the person who scopes the work is the person who delivers it — with escalation to CEO on any material issue within 24 hours.
Practice Lead — Cloud/Edge
Present at every phase gate, every scope decision, every difficult conversation. Available for 30/60/90-day post-handover check-ins as part of the engagement.
Including scope amendments.
Signs off all 5 deliverables.
With executive sponsor.
Authorised to negotiate.
CEO within 24 hours.
30/60/90-day check-ins.
Peer. Next.
Compliance Fast-Track™ UAE
Peer Assess engagement for broader compliance evidence cadence (PDPL, Dubai ISR, ADHICS v2) with eInvoicing evidence stream integrated. A3 covers the compliance-evidence dimension of eInvoicing within a broader framework; A12 provides the deeper eInvoicing-specific mandate readiness. Sometimes sequenced together when both drivers apply.
eInvoicing Integration & Data Cleanup Build™
The natural build engagement after A12. Executes the ERP-to-ASP integration and master data cleanup A12 identifies — scope, KPIs, and named owners carry over from A12's remediation backlog as direct scope input. The primary post-A12 path per catalogue guidance.
ComplianceOps™ UAE
The natural run engagement for organisations wanting sustained compliance operations after A12 (and B23 where build is scoped). Continuous compliance evidence refresh with eInvoicing stream integrated alongside PDPL/ADHICS/ISR obligations.
30 minutes.
One mandate question.
Bring the specific mandate question blocking your board conversation — ASP selection stuck at technical fit, master data quality unassessed against CTC requirements, PINT-AE technical fit unknown, board compliance plan absent. A12 is scoped in the clinic — entity structure, ERP access, sponsor availability, prerequisites. If A12 is not the fit (broader compliance is the actual driver, or B23 build is directly scopable), the clinic surfaces the honest alternative.
- —Entity structure & VAT scope confirmation
- —ERP access agreement
- —CFO/Tax Director/IT lead joint availability
- —Fit assessment against A3, B23, C6