Skip to content
Homeβ€Ί Worked examplesβ€Ί Invoice approval
Worked example Β· Finance

Invoice approval, in full.

A supplier invoice arrives by email and has to reach a payment run. Three roles touch it, one decision point sends a share of them back, and the loop that follows had never been drawn. This is what Modilo produced from one paragraph of description.

6 tasks3 roles1 decision point1 loop-backValid BPMN 2.0

The process as it runs today

Nothing is annotated on the canvas beyond the step names β€” the detail travels in the BPMN documentation, so the file stays clean when your client opens it in their own tool. The amber markers key to the findings below.

Invoice approval Accounts Payable Cost centre owner Finance No corrected Yes Invoice arrives Capture invoice Match to purchase order Match? Resolve query Approve invoice Post to SAP Release payment Paid

On a narrow screen the diagram scales to fit; the full step names and the per-step detail are in the downloadable file.

Modilo found four things

Where this process actually loses time.

Each finding points at the step it came from. None of it is written on the diagram β€” a BPMN file a client opens should be notation, not commentary.

1

Invoices are re-typed from PDFs

Every invoice arrives as an email attachment and is read and keyed into SAP by a person. There is no capture queue, so there is also no record of how many arrive or how long they wait.

Manual re-key
2

The query loop has no owner

When an invoice does not match the purchase order it goes back by email and re-enters wherever it left off. Nothing measures that loop, so nobody can say what share of invoices take it.

Untracked rework
3

Approval sits in one inbox

The cost-centre owner approves by replying to an email. There is no queue, no delegation and no escalation β€” when they are away, the invoice waits for them.

Single point of failure
4

Posting repeats work already done

The header and line data were already read at the matching step. Posting types the same values into a second screen, which is where most correction bookings originate.

Duplicate entry
Findings 1 and 4 are the same underlying gap seen twice β€” the invoice data is never captured once and reused. They are treated together below.
Solution Engine

Three ways to close findings 1 and 4.

In order of what it costs you to try. Modilo names tools it does not sell, and says so when the answer is something you have already paid for β€” which, in SAP shops, it very often is.

Modilo recommends
1 Β· Configure what you own

SAP Invoice Management (OpenText VIM)

If you run S/4HANA, the capture queue, purchase-order matching and an approval workflow with delegation are very likely already licensed and switched off. Check this before you buy anything: it closes findings 1, 3 and 4 without a new contract.

Already licensed?Lowest risk
Ask us how to check your licence β†’
2 Β· Buy it

Dedicated invoice capture

Cloud capture reads the PDF, matches it against the purchase order and hands SAP a posting-ready document. Worth it when VIM is not licensed, or the invoice mix is too varied for standard templates.

Commonly shortlisted: Rossum, xSuite, Klippa, Medius
Pricing: check current rates
How the Solution Engine picks β†’
3 Β· Have it built

A capture-and-match service

Only worth doing where the two options above genuinely do not fit β€” an unusual purchase-order structure, a second ERP, or a matching rule no standard product expresses. Modilo builds these.

Modilo can build thisScoped from this diagram
Request a quote β†’
Findings 2 and 3 are process decisions, not purchases β€” who owns a query, and who may approve when the cost-centre owner is away. Neither needs a tool.

Looking for the shorter version? The invoice approval teardown covers the same process in about a minute.

Run this on your own process.

Describe it in a paragraph β€” English, German or Italian. You get the same three things: the BPMN file, the findings, and the options. Three processes free, no card.

Map a process free See the other examples