Client stories

These accounts describe real engagement shapes. Names of institutions are withheld where confidentiality agreements require it.

• They caught a reconciliation gap between our branch feed and the monthly capital report that our internal checklist never sampled. The write-up was blunt about what we still needed to fix before September.

  Compliance manager, regional bank — full application audit

• The readiness review was shorter than I expected, which was the point. It told us our override log was unusable for evidence and that a full audit would stall without cleaning it first. I wish we had booked that cleaning before inviting them in.

  Head of regulatory reporting, insurer — pre-audit readiness review

• After we remapped three product codes, remediation verification re-ran the exact tests from the original findings. Two closed cleanly; one remained open because the evidence folder still allowed silent deletes. That honesty kept us from declaring victory too early.

  Internal audit lead, securities firm — remediation verification

• Our new reporting owner sat through a control walkthrough that finally explained why maker-checker steps appeared twice in the application. Less inspiring theatre, more practical map — which is what we needed in the week before a filing.

  Finance controller, leasing company — reporting control walkthrough

Extended note: multi-entity capital pack

A Tokyo-based group asked Intel Studio to audit the application assembling its consolidated capital schedules. Fieldwork found that late adjustments from one overseas affiliate entered the pack through a spreadsheet bridge that bypassed the application’s approval trail. The memorandum recommended either bringing the bridge inside controlled intake or isolating that affiliate’s figures with a documented manual control. The client chose the second path for the imminent filing and scheduled a later rebuild. We returned for remediation verification on the manual control design before the following quarter.