OneSig Atlas · UAE e-invoicing readiness

The invoice will be perfect.
It still won't arrive.

One wrong digit in the buyer's TRN. 100 AED fine. Cash stuck.

Atlas finds the broken fields before go-live. Names the owner. Hands the ASP a clean spec.

01 What will break 02 Who owns the fix 03 What hands off to the ASP / SI

10 owner-assigned blockers in 48 hours, or you don't pay.

ATLAS
Live readiness cockpit
Live
Readiness score
72% +4
Last re-run, 12 minutes ago
AED 2.4M invoices at rejection risk
Master data 67%
Tax logic 71%
ASP layer 98%
Ship next Buyer TRN cleanup Reverse-charge mapping
The context

Italy ran clearance e-invoicing for six years. Rejections came from one place: master data. UAE goes live Jan 1, 2027.

Picking an ASP is the easy 10%. The other 90% decides whether you get paid.

Phase 1 deadline

Oct 30, 2026

Mandate go-live

Jan 1, 2027

Per-invoice fine

100 AED

Monthly non-compliance

5,000 AED

Why traditional readiness fails

Traditional readiness answers the wrong question.

Most assessments document today. Atlas tests tomorrow.

Traditional readiness
Atlas
Documents the current state
Identifies future-state risk
Captures answers
Challenges answers against evidence
Produces findings
Produces decisions
Creates presentations
Creates executable workplans
Ends with recommendations
Ends with fix owners and handoff requirements

Decisions, not documentation.

Worked example

The invoice was perfect. It still didn’t arrive.

Follow one field through one flow.

01 · ERP
Invoice leaves
✓ Amounts ✓ Tax ✓ PO ✓ Buyer TRN

15 digits, present, well-formed. One digit is wrong. Nobody knows.

02 · Schema & business rules
PASS
200 OK · format valid

The format is valid. Validation can’t know the digit is wrong.

03 · Network
No route. Cash stuck.
UAE Peppol address = 0235: + first 10 digits of TRN

Lookup finds no such participant — or a different company. The invoice never reaches your customer.

04 · Root cause
Typo in the customer master

Entered at onboarding three years ago. No system between then and now ever checked it against the FTA register.

Atlas output
One blocker. One owner. One rule. With evidence.
B-TRN-03 | TRN valid format, fails FTA-registry name match: registered “Al Noor Trading LLC” ≠ master “Al Nour General Trading” | owner: Master Data | verified: FTA registry + Peppol Directory, timestamped
And the easy cousin — caught in the first hour from your extract alone
B-TRN-01 | Buyer TRN blank — 30% of B2B customer records | owner: Master Data
How Atlas validates · three tiers
Tier 01 · your data
Rules on your extracts
Automated
Tier 02 · network
Peppol Directory check
Automated
Tier 03 · register
FTA-registry verification
Evidence-grade, timestamped

Now multiply by every field, every flow, every entity. That’s the scan.

How Atlas works

Use what your business already knows.

Atlas reads your workshops, docs, ERP, and samples. Surfaces what breaks.

Evidence in
Workshops Meeting transcripts Emails Existing documents ERP extracts Invoice samples Master data files Tax code lists
Atlas verification layer
01 Capture 02 Map 03 Validate 04 Challenge 05 Assign 06 Handoff
Readiness out
Decisions
Owners
Rules
Fixes
Requirements
Handoff package
01Capture
→ Evidence library
02Map
→ Source & field maps
03Validate
→ Failed fields, blockers
04Challenge
→ Contradiction report
05Assign
→ Fix backlog, owner matrix
06Handoff
→ Implementation-ready file
What you receive

Six deliverables. One handoff file.

01

Readiness score

Scored by area: master data, tax logic, flows, systems, ASP, exceptions, audit.

02

Contradiction report

Where teams disagree with their own evidence.

03

Rule library

Tribal knowledge converted into verifiable, owned controls.

04

Data validation results

Record-level failures with source system and owner.

05

Owner workplan

Who fixes what, in what order, with what evidence.

06

ASP / SI handoff package

The actual file your ASP, ERP partner, or SI needs to begin configuration. Detailed below ↓

Deliverable 06 · The handoff file
Implementation-ready, 10 artifacts
10 artifacts
  • 01Legal entity and VAT registration scope
  • 02Source system map
  • 03Customer, vendor, item, and tax-code master data gaps (caveats)
  • 04Field mapping requirements
  • 05UAT ownership matrix
  • 06Test invoice scenarios
  • 07Open action items and owners
  • 08Required ERP / CRM / POS changes
  • 09Required ASP integration and response-handling requirements
  • 10Version control of requirements — sign-offs by Tax, Finance, IT, AR, AP, and Master Data

Less an assessment output.

More an implementation accelerator.

The guarantee

Who gets paid when go-live fails?

Your ASP keeps its subscription. Your SI bills remediation. Your advisor bills the recovery. The FTA bills you 5,000 AED/month + 100 AED/rejected invoice.

Everyone gets paid on failure. Except you.

Atlas is priced the other way: 10 owner-assigned blockers, or you don't pay.

The offer

48 hours

Free teardown. Master data, sample invoices, ERP extracts.

The promise

10+

Record-level blockers. Owner. Source. Fix.

The terms

Or it's free

Under 10 blockers, no invoice. Bring receipts.

Other vendors' accountability
  • ASP: billed at signature. Reads logs.
  • SI: billed at milestones. Says the SoW called for clean data.
  • Readiness consultant: delivered the deck. Left.
  • Internal team: chases everyone, owns nothing.
Our accountability
  • Find 10+ blockers in 48 hours, or no invoice.
  • Every finding tied to a record, source, owner, and fix.
  • Re-run after fixes ship, evidence preserved.
  • If we miss something material, we own the rerun.

Most readiness providers walk away after the deck. We don't.

Mid-program

Mid-S/4HANA or ERP transformation?

Run Atlas before blueprint sign-off. The handoff feeds your SI's design — not their remediation backlog.

Readiness as design input. Not a project phase.

SAP S/4HANA Oracle Fusion NetSuite Dynamics 365 Workday Financials
Shaped by leaders

Our founders shipped tax and compliance platforms at Amazon. We've sat in the room a week before go-live, watching product, delivery, tax, and IT fight over who approved what and when.

Atlas is what we wished we'd had. Built so the team defending launch isn't the one reconstructing who signed off.

Connect with the founder on LinkedIn
For partners

Sell readiness as your offering.

You bring the client. We bring the engine.

Become a Readiness Partner → See what partners get
Get started

Readiness is not a deck.
It is a loop.

Scan → Fix → Validate → Prove

Run it before implementation starts.