Client stories
Evidence from audits and readiness work — specific applications, constraints, and what changed after the findings landed.
Voices from recent work
“They caught a matching rule that had been silently forcing same-day clears into the exception queue for two closes. The write-up named the exact screen and the owner who could change it.”
Mika T., Controllership — Osaka manufacturing group · Full application audit
“I wished the schedule had been clearer in week one about interview load on my AP lead. Once we reset the calendar, the findings on access and segregation were practical, not theatrical.”
Kenji R., Finance operations — Tokyo retail chain · Full application audit
“Before year-end we needed to know whether our evidence packs would survive a new auditor’s questions. The readiness check gave us a punch-list of twelve items; nine were fixed before close week.”
Aya S., Assistant controller — Yokohama logistics · Period-close readiness
“The configuration review before our tolerance change stopped us from widening bands on intercompany matches that still needed dual approval. Dry, useful, and finished in under two weeks.”
Hiro N., Shared services lead — Kansai consumer goods · Configuration review
Extended story: intercompany clearing after a merger
A Tokyo-listed manufacturer absorbed a subsidiary whose reconciliation application used different auto-clear thresholds on intercompany receivables. Space Reason’s full application audit sampled three closes and found that forced clears by a legacy role still bypassed the dual-review step the parent had documented.
Constraint: Interviews had to avoid the subsidiary’s peak shipping week.
What we did: Mapped both rule sets, sat with break owners on aged items over ¥5 million, and traced overrides to the role that should have been retired at legal-entity cutover.
Outcome: Controllership retired the legacy role, aligned thresholds, and attached a short evidence note template to each forced clear. The following close’s aged intercompany queue shrank without adding headcount.
Extended story: bank module evidence under first-year audit
A Minato-ku professional services firm faced its first statutory audit after listing. Their bank reconciliation module stored attachments inconsistently; some months held statements, others only screenshots of balances.
The readiness check, run eighteen days before year-end, produced a dated punch-list: missing statement files for four accounts, two approvers on leave without deputies, and one matching rule that auto-cleared differences under ¥1,000 without a comment field.
They cleared the file gaps and deputy coverage before close. The auto-clear rule was left for January remediation with our configuration review — a choice we documented so the auditor saw intent rather than silence.