One idea at a time.
Practical reads on earning more and losing less with data and AI. One idea, one number, one thing to try.
Blog
Vendor master hygiene: the quiet control behind clean payments
Duplicate vendors, stale bank details and missing tax data cause duplicate payments, fraud and compliance problems. A clean vendor master prevents all three. A practical guide to cleaning it and keeping it clean.
Ten checks to run before you close the month
Most close problems are found after the books are closed, when fixing them is slow and visible. These ten data checks catch the common ones while there is still time to correct them.
Benford’s law in practice: a simple test that points to unusual numbers
In many real-world sets of numbers, the first digit is far more often 1 than 9. When a ledger breaks that pattern, it is worth a look. How the test works, where it helps and where it misleads.
Duplicate payments: how much is normal, and how to stop them
Every accounts payable team pays some invoices twice. The useful questions are how many, why, and whether your controls would notice. Here is how to find them and keep them from coming back.
Continuous controls monitoring: a buyer’s guide
Continuous controls monitoring promises to test every transaction, every day. Before you buy, know which controls to start with, what an alert should look like and who will act on it.
Know every vendor by what it does: TPRM beyond questionnaires
Third-party risk programmes run on questionnaires that vendors fill in once a year. The risk shows up somewhere else: in payments, bank changes, filings and the news. Here is how to watch it.
Paying MSMEs in 45 days: what Section 43B(h) means for your P&L
Under India’s Income-tax Act, late payments to micro and small suppliers can cost you the tax deduction for that year. Here is how the rule works in outline, and how to know which invoices are at risk before year end.
The end of sampling: testing 100% of transactions
Audit sampling was a sensible answer to paper records. With every transaction in a database, testing all of them is often faster than choosing which ones to test. Here is what changes when you do.
Private Gen AI for legal teams: ten questions to ask before you buy
Generative AI can read a contract in seconds. Before it reads yours, know where the data goes, how answers are checked and who stays accountable. Ten questions to put to any vendor.
See it in practice
Use cases from our own project work, anonymised, and scenarios that show the method: one problem, the checks we run, what they find.