PP23Case file
Invoice & payment · open to read
Invoice and payment status requests tie up helpdesk and business units
Users and suppliers ask for the status of requisition, PO and invoice by email or ticket.
Seen: 7 findings in 3 environments, 2017 to 2025.
The path with advisory
KULIC AdvisoryAdvisory and workshopSee the advisory ladder →02The case file
- From practice
- Business case: around 57,000 P2P FAQ requests per year at 30 minutes each, around 5,600 person-days per year of non-value-adding P2P work; in the use case list of one bot vendor, 40 of around 70 cases are status or list queries.
- Cause and lever
- Integration/system. Lever: automate.
- What a machine can do
- Of the 7 findings, a machine could solve 5 on its own and help with 2; it would be of no use for none.
- The first question on Monday
- How many times a day does someone ask where their invoice is?
03Rule and scene
Rule B-07For every order it is clear whom the supplier can ask. Dario's standard: a name.Read in the rule book →
The scene in the book (German edition)Chapter 6 · Wo ist meine Rechnung?Comic: Die Warteschleife · The Procurement Practice Bible
04Terms from the glossary
- Business caseA business case sets the costs of a project against its benefits.
- SupplierA supplier is any company you buy goods or services from.
- Use caseA use case describes exactly one task where a tool is meant to help, with its benefit and risk.
- InvoiceAn invoice is the supplier's request for payment.
Companies stay unnamed, figures are rounded, the patterns are real. No legal or tax advice.