For groups and multiple administrations

Multi-entity invoice processing for Exact Online administrations

Growing trading and manufacturing companies often work with multiple administrations, locations, or entities. Glimps helps centralize invoice processing without losing local context.

AP cockpit
Live overview
Multi-entity invoice processing
Structure
Central inbox

Invoices arrive centrally and are then assigned to the right administration.

Control
Per entity

Rules, approvers, and dimensions can differ by administration.

Reporting
Group-wide visibility

Finance sees status, aging, and bottlenecks across entities.

Benchmark: Ardent Partners (2024) reported $9.40 average cost per invoice, 9.15 days processing time, 32.6% straight-through processing. Source

Does this match your situation?

Where this solution fits — and where it doesn't

Good fit
  • You have multiple Exact Online administrations or entities.
  • Finance wants central control while approvals remain local or by budget owner.
  • You want consistent processes, ledgers, audit trails, and reporting.
Less relevant
  • You only have one administration and no need for entity routing.
  • Every entity intentionally uses completely different processes.

Process design

From intake to controlled posting

Glimps handles the routine so finance can focus on the exceptions — not the data entry.

01

1. Determine entity

Glimps uses supplier, VAT number, email address, administration context, or invoice data to determine the right entity.

02

2. Apply local coding logic

GL, VAT, dimensions, and workflows are applied based on the selected administration.

03

3. Route approval

Invoices go to the right budget owner, location, or operations manager.

04

4. Post per administration

The final posting is processed in the correct Exact Online administration.

Where things get stuck

The real value is in the exceptions

High-volume AP automation only pays off when it is clear what can flow through safely — and what must be reviewed by a human.

Focused on exceptions, not data entry

Wrong administration

With shared suppliers, invoices can easily be posted to the wrong administration.

Different ledgers

Not every entity uses the same accounts, VAT codes, or dimensions.

Central status is missing

Without group-wide visibility, finance sees too late which entity or approver is behind.

Concrete exceptions

How Glimps handles the cases that would otherwise stall

Scenario 1

Supplier works for multiple entities

What Glimps checks

VAT number, address, order reference, and historic postings.

Action

Suggest entity or route to review.

Scenario 2

Approver belongs to another location

What Glimps checks

Dimension, cost center, location, and approval matrix.

Action

Route to the correct local owner.

Scenario 3

GL account does not exist in administration

What Glimps checks

Chart of accounts per Exact Online administration.

Action

Ask finance to confirm mapping.

Exact Online setup checklist

The prerequisites to get this solution into production.

  • Administrations and entities are clearly named.
  • Suppliers, VAT codes, and accounts are synced per entity.
  • Approval matrix is documented per entity, location, or cost center.
  • There is a central owner for process standards.

What Glimps automates for you

The concrete parts of the process Glimps takes off your hands.

  • Entity recognition and administration routing.
  • Per-entity coding proposals.
  • Central status across all invoices.
  • Audit trail for local and central controls.

FAQ

Frequently asked questions

Specific questions about this solution for multi-entity invoice processing.

Want to see it yourself?Open the demo

Yes. The multi-entity flow is for organizations that want to process invoices centrally and post per administration.

Yes. Approval rules can differ by administration, cost center, amount, or budget owner.

By combining entity signals: supplier, VAT number, email route, references, and historic postings.