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
One rule for every money trail in an anti-money-laundering review
Twenty-three customer cases had been prepared in different ways, so the same check gave different answers. One layout and one tracing rule, first in, first out, now give one answer that anyone can check.
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 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 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 cement maker cuts the cost of every tonne delivered
Freight is one of the largest costs in cement. Planning which plant serves which customer, by which route and vehicle, from data instead of habit lowered the cost per tonne without slowing deliveries.
Segregation of duties where one application feeds SAP
A distributor system and a cloud procurement platform both feed SAP, and neither had a segregation-of-duties rule set. We defined 293 functions, found 41 conflicts and rated each by whether one person alone could cause a loss.
A logistics business audits every freight invoice before it pays
Thousands of carrier invoices a month were checked by hand, a few at a time. Checking every one against rates, routes and proof of delivery found overcharges that had been paid for years.
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.
A bank reviews who can do what across 15 applications
A bank needed a role and access review across 15 core applications. Ten checks on users, roles and job titles found segregation-of-duties conflicts, dormant access and roles that were near copies of each other.
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.
An engineering manufacturer's SAP audit, built from raw tables
An engineering manufacturer wanted its SAP configuration, access and transactions audited together. Rule-based analytics on raw table extracts found over-privileged accounts and segregation-of-duties conflicts.
Internal audits moved from spreadsheets and email to one platform
Internal audits ran on spreadsheets, emails and shared folders, so evidence was hard to find and follow-up depended on memory. AuditVault Pro puts the whole audit in one place, from plan to report.
Expense claim reviews with 95% less manual processing
Employee reimbursements were prepared and checked in spreadsheets, by hand. A Python script and a dashboard replaced the manual steps and cut the processing effort by 95%.
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.
Before a core banking go-live, 40 job roles mapped to 611 screens
A bank moving to a new core banking system had job titles matched to access in the old system, but none in the new one. Reusing the old mapping, we built one matrix of 2,368 rows in under three weeks.
Checking every rent agreement against what was actually paid
An infrastructure group rents offices, homes and guest houses for its staff. Reading every agreement, recalculating each rent and checking the documents themselves showed where the payments and the paperwork drifted apart.
No use cases match every filter.
Read the thinking behind it
Short articles on revenue leakage, fraud, controls, forecasting and private AI.