PINT-AE Readiness Advisory
Field-by-field, rule-by-rule preparation for PINT-AE BIS v1.0.2 compliance
PINT-AE is not a print format — it’s a UBL 2.1 XML specification with 51 mandatory fields and 114 schematron business rules, several governing UAE-specific BTAE extension fields that don’t exist in standard ERP invoice output. Getting this mapping wrong doesn’t fail quietly; it fails at ASP submission, after the transaction has already happened.
What's included
Scope of the engagement
- Full 51-field mapping against your ERP’s current invoice output
- BTAE extension field gap analysis and development planning
- Schematron rule-by-rule validation testing across all 114 mandatory business rules
- Code list conformance checks — UNCL1001 invoice type codes, UNCL4461 payment means, UNECE Rec 20 unit codes, ISO 3166 country codes, ISO 4217 currency codes
- Test invoice generation and ASP pre-submission validation
Why Contiqa
Practitioner-led, not vendor-led
Contiqa’s founder was directly involved in shaping the PINT-AE specification through the Ministry of Finance E-Invoicing Consultative Group — including the business rules that govern it. That’s a level of rule-level familiarity most implementation teams are reading about for the first time.
Background reading