Use cases.
One problem, the checks we ran and what they found. Most come from our own project work with the client names removed; the rest are illustrative scenarios, and each one is marked.
Use cases
5 results for “procure to pay”. Show everything
A building-materials maker runs 64 exception checks on its full SAP data
Reviewing purchases, payments, assets and sales by sample left gaps. We moved the company's SAP data into one database and built a library of 64 checks that run on every record.
A fraud investigation that followed the people, the vendors and the money
Allegations of fraud at an interior fit-out company could not be settled by looking at accounting entries alone. Six workstreams, across 10+ people and 1,000+ vendors, were brought together into one picture.
A pharma company watches its suppliers by what they do
Thousands of suppliers were assessed once, at onboarding, by questionnaire. Adding payment data, public records and news turned a yearly exercise into a risk view that updates itself.
Process mining on SAP tables, with no system integration
Internal audit could not see how purchase-to-pay and order-to-cash transactions really moved through SAP. We built the event log straight from SAP tables, so every case is traced from order to payment.
An electronics maker checks every serial number its partners report
An electronics maker relied on its channel partners to report what they sold. Thirteen checks on serial numbers, returns, customers and vendors showed where the reports and the records disagreed.
No use cases match every filter.
Read the thinking behind it
Short articles on revenue leakage, fraud, controls, forecasting and private AI.