Abzer DMCC
UAE-headquartered enterprise software company responsible for product ownership, architecture, governance and the applicable contracted operating model.
About Invocor & Abzer
Built from operating experience. Governed for what comes next.
Invocor is developed and owned by Abzer DMCC, a UAE enterprise software company with operating roots in the UAE since 2015. It brings together Abzer’s experience in statutory e-Invoicing, enterprise integration, finance workflows and regulated digital platforms into one global Peppol-based product.
✓ Clear product ownership✓ Evidence-qualified status✓ Enterprise operating experience
Ownership & product architecture
One owner. Two distinct statutory platforms.
Abzer DMCC owns the proprietary software and intellectual property behind Invocor and the shared Abzer e-Invoicing foundation. The platform architecture reflects lessons from both exchange-based and clearance-based operating models without treating their regulatory permissions as interchangeable.
Invocor
Compliance and exchange infrastructure for multi-entity organisations, including a connectivity-layer mode and a managed invoice workspace mode.
UAE pre-productionFatooraOnline
Abzer’s dedicated statutory e-Invoicing deployment for Saudi Arabia, providing the live regulatory-operating experience that informs the wider engineering foundation.
Separate product and market scopeEngineering lineage
Consolidated—not assembled overnight.
Invocor is the current expression of capabilities developed across Abzer’s e-Invoicing, billing, ERP and enterprise-integration work. The lineage explains the engineering depth; it does not merge the products or their regulatory status.
SmartInvoice
Early UAE invoicing, payment and enterprise-workflow experience established a practical foundation for invoice operations.
FatooraOnline
Saudi statutory e-Invoicing added production experience in regulated validation, reporting, identifiers, exceptions and change.
BillXPro & ERP
Billing, subscription, accounts-receivable and ERP integration work contributed workflow, data and enterprise-connectivity patterns.
Invocor
The consolidated global platform separates a reusable regulatory core from market rules, customer configuration and activation permissions.
Relevant operating experience
Experience measured by the work behind the exchange.
We do not use customer logos or inflated transaction counts as substitutes for evidence. The relevant proof is the operating discipline required to connect systems, govern data and sustain regulated document lifecycles.
From rules to controlled software
Translate specifications into versioned validation, transformation, reporting and exception behaviour with testable acceptance criteria.
Connect without replacing the source of record
Work across ERP, billing, procurement, middleware, files and APIs while the customer’s authoritative system remains explicit.
Operate the full document lifecycle
Correlate source records, structured documents, responses, exceptions and evidence across technical and business ownership.
Govern reuse and local variation
Separate common architecture from entity, workflow, market and integration differences so programmes can scale with control.
How we work
Trust is an operating discipline.
Invocor’s positioning follows the same rule as its architecture: make boundaries visible, make evidence traceable and keep regulatory permission distinct from product capability.
Name the entity and stage
Membership, certification, accreditation, testing, production and market availability are separate facts and should be described separately.
Trace the complete lifecycle
Identifiers, validation, transport, responses, reporting and customer delivery need one correlated evidence chain.
Define the operating boundary
Provider, customer, partner and authority responsibilities belong in the architecture, service description and contract.
Version what can affect compliance
Rule, mapping, interface and operating changes require impact assessment, testing, release evidence and accountable approval.
Assurance & footprint
Corporate controls around the product.
Invocor is developed within Abzer’s management and delivery environment. Assurance evidence must be checked for the relevant legal entity, scope and validity; it is not a substitute for product, Peppol or country-specific authorisation.
Dubai, UAE
Corporate ownership, commercial leadership and regional product governance.
Abzer group teams
Product engineering, integration, delivery and operational capabilities supporting the Abzer platform portfolio.
Current governance and supporting evidence should be confirmed for the contracted entity and service scope.
Continuity design, recovery objectives and current exercise evidence should be reviewed during due diligence.
Delivery governance, controlled change and quality evidence should be reviewed for the proposed service.
Abzer DMCC appears in the OpenPeppol full members list. Membership must not be represented as certified-service-provider status or UAE accreditation.
Current UAE boundary: Invocor is in accreditation and pre-production preparation. It is not live as an accredited UAE e-Invoicing Service Provider. Production activation remains subject to accreditation, production onboarding, certificates, authority access, customer acceptance and controlled cut-over.
Evaluate the company behind the platform.
Review ownership, architecture, evidence, responsibilities and current status in one structured discussion.