About Datafusiontools
A Mong Kok practice built around financial auditing that ends in usable policy exception registers — not shelfware findings lists.
Why we exist
Hong Kong finance teams already know when a waiver stamp appeared after a payment went out. What they lack, more often, is a register that survives the audit committee’s second round of questions. Datafusiontools was formed to do that narrower job well: policy exception reporting grounded in the manuals you actually use.
Origin
The practice grew out of repeated interim assignments where exception lists arrived as spreadsheet dumps — different severity labels each quarter, missing policy clause references, and no owner for aged items. We standardised a register format that finance secretaries in Kowloon and on the Island could drop into packs without a late rewrite.
How we work with clients
We treat your policy set as the contract. If practice diverges from the manual, we record it as an exception or a documented waiver — we do not quietly “interpret away” breaches to keep the list short. Fieldwork stays proportionate: enough testing to support the register, not a full statutory audit in disguise.
People
Engagements are led by practitioners who have prepared exception schedules for trading companies, professional firms, and group subsidiaries with multi-entity ledgers. Support staff handle extract hygiene and pack formatting so fieldwork days stay on process owners and evidence.
Values we hold to
- Clause-level honesty — every exception cites the policy text it fails.
- Committee readability — severity and status language stays consistent across periods.
- Local presence — Pioneer Centre, 750 Nathan Road, Mong Kok, Kowloon keeps us reachable for wet-file reviews.
- Clear edges — we say when a matter needs counsel or a statutory auditor, not our register.
Hong Kong context
Many of our clients close in HKD with group reporting in another currency, dual-language manuals, and approval chains that mix email and wet signature. Our exception work respects those realities instead of assuming a single ERP workflow.