Incoming Invoice Workflow

Incoming invoices are read, allocated, approved and posted to Logo

Incoming e-invoices are fetched as UBL-TR, due dates and amounts are read, and costs are split to service cards and cost centres with allocation keys. Invoices that pass multi-level approval are posted to Logo; on rejection, e-mails go to the supplier and stakeholders.

Request a quote All solutions

What it offers

Modules and capabilities

Invoice reading

e-Invoice retrieval, UBL-TR parsing, due-date reading; special rules for utility supplier invoices.

Cost allocation

Splitting to service cards and cost centres with allocation keys; accounting preview and template learning.

Multi-level approval

Per-user approval rights by invoice type and level; invoice rendering via XSLT.

Notifications

Rejection and reminder e-mails, supplier mail rules.

Posting to Logo

Account and stock matching, synchronisation to Logo; e-delivery-note and order import.

Traceability

Every step is logged to database and file; licensing and update infrastructure.

How we work

We carry the project end to end

Discovery and analysis

We map your processes, Logo set-up and goals together.

Pilot

We validate with a limited-scope pilot, then scale up.

Go-live

Data migration, training and cut-over, by our own engineers.

Support and growth

Remote and on-site support; co-development for new needs.

FAQ

Frequently asked questions

Which e-invoice providers are supported?

The current implementation uses eLogo. Thanks to an adapter design, other providers can be added within a project.

Can invoices from other systems be imported?

Yes. A separate tool pulls invoices from a document-management system's web services and posts them to Logo through a staging database.

Ecosystem

Let's set this up in your business together

In a short call our engineers listen to your need and outline the right scope and pilot plan.

Request a quote Message on WhatsApp