Client stories
Evidence from real close cycles
Comments below reference specific engagement steps—sampling, credits, allocation keys—not generic praise.
“The sample design took longer than we expected, but the exception register finally gave AP something they could chase—credits we had left sitting in a shared inbox for months.”
“I wished we had narrowed to one vendor first. Midway through we added a second bill set and the timeline slipped a week. Still, the allocation correction list saved us from restating two cost centres.”
“Quarterly reviews keep our reserved-capacity credits from vanishing into ‘miscellaneous.’ The briefing call is short; the pack is what we attach to the close binder.”
“AP used the dispute schedule the same afternoon James walked us through unmatched data-transfer lines. We still negotiate with the vendor ourselves—that was never CloudScalr’s job.”
Engagement story: three months of compute invoices
A mid-size manufacturer asked CloudScalr to review three months of primary compute invoices before their external audit. Scope covered one vendor, materiality set at NT$50,000 per exception family.
Fieldwork found reserved instances billed after a cancellation request and a duplicated support add-on. The memorandum listed eight exceptions; five cleared with credit notes before close. Two remain open with the vendor; one was accepted as a known overage.
The controller’s note afterward: the working papers were dense, but the walkthrough made the exception register usable for AP without a second translation step.
Ask about a similar review