Client stories

Evidence from banks and payment providers that commissioned financial audit work on their mobile banking applications.

Client stories

Voices from recent engagements

“They caught a mismatch between the in-app FX fee banner and the nostro posting for same-day remittances. The correction landed before our next supervisory visit. Turnaround took longer than we hoped once sample volumes grew, yet the working papers were orderly.”

— Head of Retail Channels, mid-size Thai commercial bank

“Our settlement team already knew about late declines on bill pay. The value was tying those breaks to the exact confirmation wording customers saw in the Android build. That gave compliance a concrete change request instead of another vague ticket.”

— Payments Operations Lead, Bangkok-based payment company

“The release readiness review blocked a fee schedule that still referenced an old SMS alert charge. I would have preferred denser daily stand-ups during the freeze week, but the go/no-go memo was unambiguous.”

— Digital Product Owner, regional bank subsidiary

Extended story: dual-skin retail app

A commercial bank operated two visual skins of the same mobile banking application — one for mass retail, one for affluent customers — with shared posting logic but separate fee banners. Our financial audit sampled three months of transfers and FX. We found that the affluent skin displayed a waived transfer fee while the core still posted a charge for amounts under a threshold inherited from a retired campaign.

Finance reversed affected fees within a fortnight. Channel owners unified the banner source so both skins read from one approved schedule. The bank reused our sample frame in the following quarter’s internal audit plan.

Extended story: PromptPay confirmation lag

A payment provider’s merchant app confirmed QR acceptance before the switch finalised. Customers rarely noticed, yet finance carried overnight suspense. The settlement reconciliation audit aged breaks by merchant category and showed that a single biller class drove most mismatches. Operations moved that class to a delayed confirmation pattern and cut open items sharply within six weeks.