The buyer and approver paths
Work with it — Procurement & Approvals.
The day-to-day.
Two of these articles describe journeys that start at your customer's company. The buyer submits a cart through your shop; the approver decides what it turned into. You read them so that you can recognise what somebody is describing on the phone, and so that you know what the Cockpit lets you do when a request needs a push: open it, see who it waits for, approve it over everyone's head or cancel it. Walk both paths once, with real contacts at a real customer, before that customer goes live.
The other two are yours. The budget ledger is what you read when a controller questions a number. Reporting is what you can hand a customer's Einkaufsleiter from the lists and the ledger, without building anything.
- The buyer's path: submit for approval — What happens when the shop submits a cart.
- The approver's path: approve or decline — Chains, decisions, and the two overrides.
- Reading the budget ledger — Every movement on a budget, and what caused it.
- Procurement reporting — What you can pull from the lists and the ledger.