Pricing & engagement

Price the operating model. Not only the document.

A dependable e-Invoicing proposal reflects the entities, flows, integrations, controls and service responsibilities behind every exchange. Invocor scopes those inputs first, then presents the commercial model in lines procurement and finance can test.

Plan your rollout ↗See pricing inputs ↓

Pricing principles

Clarity before commitment.

Invocor does not publish a universal rate because the same invoice count can represent very different implementation and operating obligations. A credible proposal makes the scope, assumptions and change mechanics visible.

One commercial schedule

Implementation, recurring service, usage, options and third-party items should be cross-referenced from one authoritative schedule.

Scope before price

Entities, document flows, systems, environments, responsibilities and markets are confirmed before the proposal is treated as final.

Core versus change

The regulatory and exchange baseline is separated from customer-specific integration, transformation, reporting and operating work.

Assumptions in view

Dependencies, allowances, exclusions, customer duties and change triggers are recorded beside the relevant commercial line.

Engagement paths

Start where your decision is today.

These are scoping paths—not pre-packaged tiers. The selected path establishes the work required to reach an evidence-based proposal and, where applicable, an implementation plan.

Path 01 · Decide

Readiness & architecture

For organisations that need to establish mandate exposure, target architecture, process ownership and a prioritised roadmap before selecting delivery scope.

Focus: Entities, flows, systems, gaps, decisions and delivery risks.
Basis: Defined advisory work package and agreed outputs.

Path 02 · Connect

Compliance connectivity

For teams retaining existing invoice workflows while adding validation, transformation, provider exchange, reporting and lifecycle evidence.

Focus: Interfaces, mappings, message lifecycle, exceptions and reconciliation.
Basis: Implementation scope plus agreed recurring service and any applicable usage component.

Path 03 · Operate

Managed invoice workspace

For organisations that also need user workflows, controlled exception handling, accounts, reporting and administration around the same regulatory core.

Focus: Roles, workflow, source channels, approvals, operations and delivery.
Basis: Configured workspace scope, implementation, recurring service and agreed options.

Path 04 · Scale

Multi-entity or multi-market programme

For groups that need common governance with phased entities, systems or market activations under a coordinated architecture.

Focus: Reusable patterns, local variation, sequencing, controls and programme governance.
Basis: Phased work packages and market-specific scope, subject to availability and regulatory permission.

Price drivers

What changes the proposal.

Provide representative volumes and real integration scenarios—not only annual totals. Complexity is often driven by variation, ownership and exception handling rather than document count alone.

InputWhat to defineWhy it matters

Entities & registrationsLegal entities, tax registrations, business units and phased activation sequence.Sets onboarding, configuration, testing and governance scope.

Flows & document typesOutbound AR, inbound AP, Invoice, Credit Note, Self-Billing and purchase scenarios in scope.Determines rules, mappings, workflow and test coverage.

Volumes & peaksExpected inbound and outbound volumes, seasonality, bursts and growth assumptions.Informs capacity, operating design and any usage construct.

Systems & interfacesERP, billing, procurement, middleware, file and API patterns by flow.Shapes integration, orchestration and support boundaries.

Data & mappingSource completeness, master data, transformations, enrichment and ownership of correction.Influences discovery, mapping, remediation and exception effort.

Environments & deliverySandboxes, test cycles, negative tests, migration, cut-over and acceptance evidence.Sets delivery stages, dependencies and acceptance criteria.

Operations & supportService hours, severities, escalation, reporting, reconciliation and evidence access.Defines ongoing responsibilities and contracted service scope.

Markets & retentionJurisdictions, country profiles, availability status, data location and retention needs.Separates reusable core capability from market-specific and data obligations.

Proposal anatomy

Make every charge traceable to scope.

A procurement-ready proposal should let reviewers test the baseline, compare scenarios and see what happens when an entity, market, volume or integration changes.

Implementation work packages

Discovery, design, configuration, mapping, integration, testing, training, cut-over and acceptance outputs.

Recurring platform & service

Named entities, flows, environments, platform functions and operating responsibilities included in the baseline.

Usage mechanics

Measurement unit, allowance if used, reconciliation cadence, overage treatment and worked volume scenarios.

Support & service levels

Included hours, channels, severity definitions, escalation, reporting, dependencies and optional coverage.

External & optional costs

Third-party or pass-through items, additional environments, market activation, specialist services and approved change.

Commercial controls

Currency, taxes, invoicing terms, indexation or price-change rules, assumptions, validity, renewal and termination.

Exit & transition

Data and evidence export, transition assistance, retention, deletion, timing, formats and any applicable charges.

Responsibility model

Included, owned, or separately scoped.

The final contract and statement of work control. This framework shows the questions each proposal should resolve; it is not a promise that every item is included in every engagement.

Invocor baseline · as contracted

Provider scope

Agreed platform functions and configured document flows
Defined integration endpoints and message lifecycle evidence
Specified environments, operating procedures and support
Regulatory baseline maintenance within the contracted scope

Customer-led

Customer responsibilities

Authoritative source data and master-data quality
ERP ownership, internal controls and authorised users
Business decisions, test participation and acceptance
Tax, legal, security and operational approvals

Requires confirmation

Separately scoped

Custom integrations, remediation and transformation
Additional markets, entities, environments or workflows
Extended support, specialist reporting or programme services
Third-party services and external execution dependencies

Can be scoped now

Readiness, architecture and pre-production delivery

Discovery, solution design, integration preparation, mapping, controlled testing and rollout planning can proceed against agreed scope.

Production boundary

UAE activation remains gated

Accreditation, production onboarding, certificates, authority access, customer acceptance and cut-over approval must be complete before accredited UAE production service. Product capability is not regulatory permission.

Commercial questions

Pricing FAQ

Why does Invocor not publish a universal price?

Because entity count, flow coverage, data quality, integrations, environments, operating responsibilities, support and markets materially change the work and service. Publishing one number would conceal assumptions that procurement needs to see.

Is pricing based only on invoice volume?

No. Volume may be one input or commercial component, but implementation and recurring scope also depend on the operating model. The proposal should state whether and how usage is measured.

Do inbound documents count?

Inbound AP and outbound AR are scoped explicitly. Any allowance, usage definition or measurement treatment must state which directions, document types, retries, duplicates and test traffic are included or excluded.

What usually changes price the most?

Additional systems and mapping variation, incomplete source data, new entities or markets, broader workflow, more environments, extended support and customer-specific reporting can materially change effort or operating scope.

Are new country activations automatically included?

No assumption should be made. Each market has its own availability status, rules, accreditation or partner dependencies, testing and operating scope. The proposal should show what is available, planned, partner-enabled or separately scoped.

Can commercial terms be fixed after discovery?

Confirmed scope can support fixed work packages or recurring lines where appropriate. Variable usage, third-party charges, regulatory change, unconfirmed integrations and customer-requested changes should retain clearly defined adjustment mechanics.

Build a proposal your teams can test.

Bring your entities, flows, systems and rollout priorities to a structured scoping discussion.

Plan your rollout ↗