Client stories
Specific moments from engagements — not star ratings — showing how application findings changed day-to-day treasury practice.
“They found a dormant entitlement path in our cash-pooling module that still allowed a single user to amend beneficiary templates after hours. We closed it before year-end testing.”
Treasury manager · manufacturing group · Tokyo
“The report was denser than I expected in the first week — useful, but we had to free two operations people longer than planned for walkthroughs. Once that settled, the payment-release findings were concrete enough for our internal audit committee to act without another round of interpretation.”
Internal audit lead · trading company · Osaka liaison, fieldwork in Tokyo
“Ahead of our payment-hub cutover, Online Logic walked the pre-production approval ladder with us and flagged a cut-off calendar that still pointed at the old bank connectivity window. We delayed go-live by four days and avoided a messy first week.”
Programme sponsor · consumer goods · Kanagawa
Extended story — domestic payment hub remediation
A Tokyo-listed manufacturer asked us to examine its domestic payment hub after several reconciliation exceptions piled up at month-end. Fieldwork covered the hub itself and the bank connectivity module that carried approved batches.
We sampled release events across three weeks and compared them to the dual-authorization matrix. Two roles still held both template-maintenance and release rights — a combination that had survived an earlier HR system migration. Treasury operations closed both combinations within ten days; the following month-end exception queue shortened noticeably, according to the client’s own tracking.
The engagement did not rewrite their full control matrix. It gave them a prioritised list tied to named screens and user IDs, which their internal audit team then carried into the next scheduled testing cycle.