Client stories
Specific accounts of audits, reconciliation assessments, and analytics reviews.
Voices from recent engagements
“They caught a delayed wallet top-up path that our monthly pack never showed. The write-up was dense, and we needed a follow-up call to unpack one section, but the exception register alone paid for the engagement.”
— Operations lead, licensed e-wallet operator, Kuala Lumpur
“The analytics review forced our product team to admit three failure states were never emitted. Finance had been reconciling blind on those journeys for months.”
— Head of risk, digital lending firm, Petaling Jaya
“We expected a longer on-site presence. They finished sampling faster than planned, which was fine, though I would have liked one more joint session with our bank partner before the final memo.”
— Finance manager, remittance provider, Penang
Extended story: festive peak settlement breaks
A Klang Valley e-wallet team approached us after Chinese New Year volumes left suspense accounts elevated for three consecutive cycles. Our Settlement Reconciliation Assessment sat with the night shift through two cut-offs, traced partner file latency, and documented how manual journals cleared breaks without root-cause tags.
The findings memo grouped breaks by partner and by app journey, then recommended a modest change to the event payload so failed top-ups stopped looking like unsettled successes. Internal audit reused the matrix in their next quarterly pack. The client did not ask us to implement engineering changes; their own squad handled that after the walkthrough.
Extended story: pre-licence rail mapping
A payments start-up preparing an additional product line commissioned Regulatory Transaction Mapping before submitting expanded documentation. We built a matrix from each proposed transaction type to expected app events, settlement artefacts, and ledger postings. Two proposed journeys had no durable identifier shared across systems—the kind of gap that surfaces late in reviews.
They delayed the launch calendar by a few weeks to fix identifiers, then returned for a shorter App Analytics Review once the new events shipped. That sequence cost less than a rushed full audit would have after go-live.