Client stories
What the exception memo changed
Controllers and finance managers describe specific findings, constraints, and the mild frustrations that still came with the work.
“The pre-audit anomaly review ranked three intercompany clearings we had marked as ‘timing.’ Two really were timing. One was a duplicated recharge that would have sat in the sample. We fixed it in two days.”
“Closing pack readiness felt slower than I hoped because our binder naming was inconsistent. Once they mapped items to the PBC list, the second half moved quickly. I would clean the folder structure before hiring them again.”
“Interim sampling support caught a cluster of manual expense journals posted after the freeze with blank narrations. Not dramatic amounts, but exactly the kind of thing our auditors love to expand. We added reason codes the same week.”
“They refused to inflate the memo with trivia below our performance materiality. That restraint mattered more than the fancy detection language. Our partner meeting stayed focused.”
Extended story: year-end cut-off at a Kaohsiung trader
A multi-entity trading group approached us six weeks before year-end fieldwork. Revenue recognition was clean on paper; shipping evidence lived in three warehouse systems. Our anomaly pass highlighted credit notes clustered in the final twelve days — ordinary individually, irregular as a pattern against the prior three years.
The controller’s team traced half to genuine returns. The other half lacked matching outbound documents. They prepared a cut-off schedule before auditors selected samples. Fieldwork still asked for vouchers, but the conversation started from a documented explanation instead of a scramble.
Constraint we could not remove: one overseas warehouse would not grant extract access in time. Those shipments stayed out of the AI-assisted scan and were reviewed manually. The client accepted that gap in writing — a useful reminder that anomaly detection only covers what you can extract.