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 “purchase orders”. 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 restaurant chain finds the stores, orders and recipes that do not add up
A quick-service restaurant chain wanted to know which stores needed attention and where food cost was slipping. Four checks on sales, purchase prices, orders and recipes point to them.
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.
Open orders and real customers, checked every month
An electronics maker could not easily see which purchase orders were still open, or whether every customer in its master was a real company. A monthly Python run on its SAP data now answers both.
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.