Client stories

What finance teams noticed after the fieldwork

Comments reference specific cycles, constraints, and follow-up—not star ratings. Names appear with permission; company names stay general where requested.

“They spent two full days on our purchase cycle in Tainan before writing a single finding. The draft called out a duplicate-payment risk we had waved away for years because 'everyone knows the vendors.' We still disagree on how urgent the IT access comment was, but the cash findings were exact.”

Mei-Ling Chen · Finance Director, regional distributor · Internal Controls Review

“Our external auditors arrive every March. Last year CloudConnect ran a readiness check in January—binder gaps, missing cut-off tags, and a payroll approval trail that only lived in chat messages. Fieldwork was quieter than the year before.”

Wei-Ting Hsu · Controller, manufacturing group · Pre-Audit Readiness Assessment

“I expected a thick report. What we got was a short severity table and a working session where process owners left with names next to each fix. Some wording felt stern for a first review, yet the follow-up retest three months later showed which fixes held.”

Andrea Vogel · Operations lead, import partnership · Findings Remediation Support

“The walkthrough of revenue recognition for our wholesale contracts surfaced handoffs nobody had drawn on paper. Not glamorous work—sticky notes on a whiteboard—but it stopped us from testing controls that did not exist.”

Jun Park · Internal audit liaison · Financial Process Walkthroughs

Extended note

Purchase cycle review for a regional distributor

A Tainan distributor asked us to look only at purchases and cash disbursements after two near-duplicate payments slipped through during peak season. Over nine fieldwork days we walked vendor master changes, three-way match exceptions, and payment release passwords.

Findings focused on a shared approval login and a vendor-create right sitting with accounts payable clerks. Management accepted both. They declined a broader inventory add-on that quarter—capacity was thin—and scheduled remediation retesting for the following quarter instead.

Three months later, sample testing showed dual release operating on high-value runs. Vendor-create rights were still being tightened; we noted that honestly in the retest memo.

Extended note

January readiness before a March external audit

A manufacturing controller wanted fewer open items when the audit team arrived. Our readiness pass checked inventory count instructions, cut-off tags from the prior year, and payroll approval trails that had migrated into chat threads.

We rebuilt a simple approval evidence folder and flagged missing voided-tag logs. Fieldwork in March still raised questions—as audits do—but the inventory and payroll sections closed earlier than the prior year according to the controller’s own timeline notes.

Talk through your situation