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
4 results for “business controls”. 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 consumer-goods company puts six applications under one control framework
Six business applications around SAP were each governed on their own. One matrix of 91 controls and 103 segregation-of-duties rules, tested against real user data, showed what to fix first.
A lender moves its payment controls from quarterly to daily
An internal audit team tested vendor payments and disbursements once a quarter, on a sample. Moving the same controls onto every transaction, every day, found issues while they could still be stopped.
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.