Client Stories
Evidence from receivables application audits — specific constraints, interactions, and outcomes.
“They traced a dispute queue that aged invoices correctly on screen but never updated the export our collectors used. The write-up named the exact field mapping — not a generic control list.”
Soo-jin Park, Credit Controller · mid-market manufacturer, Gyeonggi“The readiness check before our AR module cutover caught a credit-hold rule that would have released blocked customers overnight. We delayed go-live by five days and fixed it. The schedule slipped, and I am still glad we waited.”
Daniel Orth, Finance Project Sponsor · logistics group, Incheon“Follow-up testing closed six of eight prior findings cleanly. Two stayed open because our IT queue had not finished role splits — the note said so without soft language, which helped me escalate.”
Yuna Kim, Internal Control Lead · retail wholesale, Seoul“The aging review was shorter than I expected and sharper than our last general IT assessment. One mild reservation: scheduling around month-end took more back-and-forth than I hoped, though they refused to rush sample work during closing week.”
Marcus Ellery, Group Controller · industrial parts distributorExtended story: dispute statuses that never aged
A Seongnam-based components supplier asked for a focused aging and dispute review after collectors complained that “stuck” invoices disappeared from their daily list while still sitting open in the ledger. The receivables tracking application showed dispute statuses correctly inside the workstation view, yet the nightly export that fed the dialer filtered on an older status field retired two upgrades earlier.
Fieldwork lasted six business days. We sampled forty dispute items, compared export definitions to on-screen filters, and sat with two collectors during a morning list run. The findings memo recommended restoring the export to the live status field and archiving the retired codes. Within three weeks of remediation, the credit manager reported that dispute items older than fourteen days were visible again on the dialer list — matching the ledger aging for the first time that quarter.
The engagement did not rewrite collection scripts or renegotiate customer terms. It restored alignment between the application’s live data and the list collectors trusted.
Extended story: write-off rights after a shared-service move
After moving receivables processing into a shared-service center, a client’s write-off approval matrix still allowed plant clerks to clear balances up to a limit meant for the center supervisor. The flagship application audit mapped roles across two entities, traced twelve write-offs, and showed that four had been posted by users whose plant roles should have been read-only after the move.
Remediation split roles and added a dual-approval threshold. Our follow-up review three months later confirmed the new path on a fresh sample. The controller’s comment in the closing call: the audit felt slow in week one while access was arranged — and precise once evidence arrived.