Client stories

Evidence from real engagements — specific constraints, interactions, and outcomes. Names appear with permission; some titles are generalised where requested.

Voices

“They reconstructed six months of journal overrides before our external auditors arrived. The timeline of who approved each override saved us two full days of fieldwork questions.”

— Mei Ling C., Group Financial Controller, Causeway Bay

“The weekly exception digest is denser than I expected at first, but once we tuned the materiality thresholds it became the only report our risk committee actually opens. I still wish the first month had been quieter.”

— Adrian K., Head of Compliance, Central

“We brought Datastreamcraft in after an ERP cutover left our change-log exports incomplete. Marcus walked IT through the exact extracts needed and produced a bridge pack our statutory auditors accepted without a second round of sampling.”

— Priya S., Finance Systems Lead, Kowloon Bay

“The pre-audit sprint was five intense days. Not everything looked flattering — three approval gaps were real — but going into fieldwork with those already documented was better than discovering them under pressure.”

— David L., Internal Audit Manager, Admiralty

Extended story: Quarterly close under dual listing pressure

A dual-listed group with entities in Hong Kong and Singapore asked us to monitor journal trails for two quarters ahead of a tightened board calendar. Kickoff mapped four ledgers and two approval workflows. The first fortnight surfaced a cluster of late-night postings from a shared-service login that had retained posting rights after a role change.

Working with the client’s IT access team, we confirmed the login trail, and the controller revoked the residual rights within the same week. Subsequent digests dropped that pattern. The monthly walkthroughs then focused on override volume around period-end rather than access anomalies. The engagement continued into a second year at a lower retainer once entity count stabilised.

Extended story: Reconstruction after a control incident

Following an unexplained back-dated journal in a single Hong Kong subsidiary, the group asked for a point-in-time reconstruction covering ninety days. We received extracts late — four days after the promised handoff — which pushed delivery by the same interval under the engagement letter. The chronology showed the back-date originated from a legitimate correcting entry with incomplete dual approval, not from an unauthorised user. The findings memo gave the audit committee a clear account and a recommendation on dual-approval enforcement, which the client implemented before the next close.

Request a trail review if a similar constraint is on your calendar.