Profiles and formats
Invoice, credit note and other supported document representations, syntax and semantic requirements.
Markets & compliance
One operating model. Market-specific control.
Invocor separates stable enterprise integration from changing e-Invoicing requirements. Each market is assessed across formats, validation, identifiers, exchange models, reporting and evidence—then enabled through a controlled country pack when the necessary capability, testing and authorisation are in place.
✓ Transparent market status✓ Version-controlled rules✓ One enterprise integration model
Stable enterprise coreSeparate integration from local change
Controlled country packsVersioned rules and effective dates
Explicit availabilityNo implied global or live coverage
Traceable changeTesting and release evidence
What a country pack controls
Peppol is a foundation—not a substitute for market compliance.
Interoperability is only one layer. Each jurisdiction may require its own data, identifiers, validation, routing, reporting, retention and approval model.
Validation logic
Structural, tax, business, recipient and market-specific checks with actionable results.
Identifiers and endpoints
Legal entities, tax identifiers, participant IDs, endpoint discovery and partner routing data.
Networks and authority models
Supported routes, acknowledgements, submission responses and configured lifecycle states.
Regulatory interactions
Market-specific reporting or clearance readiness where applicable, supported and authorised.
Retention and traceability
Configured retention policies, source records, responses, lifecycle history and evidence export.
Peppol-based markets
Interoperability architectureInvocor is designed around Peppol-based structured exchange patterns. Country enablement still depends on the relevant profile, national requirements, configured role, connection, testing and authorisation.
Understand Peppol →United Arab Emirates
PINT AE and five-corner architectureInvocor’s UAE implementation is in accreditation and pre-production. Production use remains subject to the applicable accreditation, testing and activation stages.
Explore UAE readiness →Oman
Regulatory watch and readiness planningInvocor tracks official programme developments and translates confirmed requirements into enterprise impact assessments. This page does not represent a live Invocor service or completed local authorisation.
Discuss Oman readiness →Additional markets
Controlled extension modelNew markets are assessed against the enterprise landscape and applicable regulatory model. They are not presented as available until the necessary product, operational and authorisation conditions are confirmed.
Transparent status model
Four labels. No ambiguity.
The market page distinguishes architectural capability, delivery preparation, approved availability and external regulatory information.
Architecture supports the model.
The platform contains relevant design patterns or common capabilities. This does not mean a country service is live.
Architecture statementEvidence and readiness are being developed.
Product configuration, testing, connection or accreditation work is underway. Production availability is not implied.
Readiness statementConfirmed for an approved scope.
Use only after the applicable technical, operational and authorisation conditions have been completed and documented.
Evidence-backed statementRegulatory developments are monitored.
External requirements are tracked for planning. This label is not an Invocor coverage or service-availability claim.
Regulatory referenceEnterprise readiness
Market readiness starts inside the enterprise.
Before selecting a route, establish which entities, systems, documents, partners and controls will be affected.
01
Entities and obligations
Identify legal entities, branches, registrations, document types and transaction flows.
02
Systems and data
Map ERP, billing, procurement, master data and the fields required by each flow.
03
Partners and identity
Validate recipient identifiers, endpoints, onboarding needs and routing ownership.
04
Operations and evidence
Assign exception ownership, status reconciliation, support and evidence requirements.
Regulatory-change governance
Turn rule changes into controlled releases.
Country content should change only through an evidence-led operating process—not through unreviewed marketing updates.
Monitor
Track authoritative regulator, tax authority and Peppol sources.
Assess
Classify impact across data, profiles, validation, routing and evidence.
Version
Prepare controlled rule, mapping and configuration updates.
Validate
Execute technical, business, partner and regression scenarios.
Release
Publish approved changes with effective dates and retained evidence.
Source policy: mandate dates, scope thresholds and technical requirements should be published only after review against authoritative regulator or recognised network documentation. Market facts must not be presented as proof of Invocor availability.
Build the shared understanding
Use the right guide for the decision in front of you.
Move from network fundamentals to market architecture, provider due diligence and enterprise readiness.
What is Peppol?
Understand participants, service providers, discovery and structured exchange.
Read the explainer →The five-corner model
See how document exchange and authority reporting roles fit together.
Explore the model →PINT AE
Understand the data and validation considerations behind the UAE profile.
Open the field guide →Enterprise readiness
Evaluate entities, systems, data, partners, governance and testing.
Download the checklist →Turn your market roadmap into a governed delivery plan.
Map entities, systems, document flows, target markets and approval dependencies in a structured architecture workshop.