Direct answer: Owners should review ongoing accounting-system management through a short control report covering current users and administrators, approved setting changes, bank-feed and integration exceptions, reopened periods, audit-history findings, unresolved risks and the next review date. The review should explain exceptions, not just show that routine tasks were ticked.
This general guide is for Australian small-business owners, including Epping, Melbourne and Victoria. Confirm current rules and software settings for your circumstances.
Which access changes should owners see?
Review new, removed and privileged users, administrator ownership, multi-factor authentication where available and recovery access. The ATO recommends reviewing who can access business information and removing access that is no longer needed.
How should system changes be reported?
List material changes to bank rules, chart of accounts, tax settings, integrations, payroll connections and report layouts. Include the requester, approver, test evidence and effective date.
Which exceptions matter most?
Show failed bank feeds, duplicate imports, disconnected apps, backdated transactions, unreconciled balances and unusual manual journals. Give each exception an owner, due date and closure evidence.
How should lock dates and audit history be used?
Report any reviewed period that was reopened and why. Xero documents lock dates as a way to restrict edits to earlier transactions; history still needs review because authorised users may change or reopen settings.
What decision should the owner make?
The owner should accept the report, request remediation, change access or approve a planned system change. Record decisions and next dates so the review produces action rather than another dashboard.
What belongs in the practical checklist?
- Current users and administrators
- Recent access changes
- Approved configuration changes
- Feed and integration exceptions
- Reopened periods and reason
- Audit-history findings
- Risks, owners and due dates
- Owner decision and next review
What could this look like in practice?
Hypothetical example: A hypothetical Melbourne wholesaler reviews its monthly system report and finds a former contractor still has adviser access and one feed failed twice. Access is removed, the feed owner is assigned and the close is rechecked. This invented example is not a software guarantee.
What do business owners ask?
Does a clean dashboard prove the system is controlled?
No. Review access, history, exceptions and evidence behind the dashboard.
How often should owners review system management?
Use a rhythm based on risk and change volume, with faster review after material access or integration changes.
Should an owner approve every routine task?
Not necessarily. Define which changes are material and which exceptions require owner approval.
Where can you continue?
Read the live parent guide, review service information, use the related accounting-system rework controls guide, and explore the TNS Accounting homepage.
Which official sources were checked?
Published by TNS Accounting. Official sources checked 21 November 2026. Rules, guidance and software features can change; confirm the linked sources before acting.





