What we do for a finance practice varies with the authorisations the firm holds. An AFSL-authorised adviser has ASIC's cyber-resilience expectations baked into their licensing obligations. A registered tax agent has Tax Practitioners Board record-keeping and client-data obligations. An accountant providing designated services (trust account, payroll, company formation) becomes an AUSTRAC reporting entity from 1 July 2026. Different obligations, overlapping technical controls. We map the overlap so a single well-designed stack covers the full obligation surface without ten separate implementations.
The practical work sits around client-data handling. Where client files live, who can access them, what happens when a staff member leaves, how the firm would prove to an auditor that an unauthorised access never happened. Most mid-size practices we onboard have good intentions on all of this and uneven evidence. We close the evidence gap with identity controls, logging, retention policy and document-management configuration, then keep the record current month by month.
Across the engagement, the cycle is continuous rather than event-driven. Gap analysis against the authorisations the firm holds, monitoring of the controls in operation, remediation when something drifts, evidence pipelines that produce on demand. The discipline that lets a finance practice walk into an ASIC review or a Big 4 vendor questionnaire confident rather than scrambling.
We do not provide financial-services advice or compliance sign-off. The CA ANZ, CPA Australia, FASEA, AFCA and similar interpretations remain the responsibility of the firm's principals and its compliance officer. We build the systems those interpretations rely on to be honest.