Direct answer: The strongest controls are individual user access, documented change requests, owner approval for material settings, testing before release, lock dates for reviewed periods, monitored bank feeds and integrations, an exception register, and a history review showing who changed what. These controls reduce repeated fixes by preventing uncontrolled changes and making causes traceable.
This general guide is for Australian small-business owners, including Epping, Melbourne and Victoria. Confirm current rules and product settings for your circumstances.
How should access be controlled?
Give each person an individual account and the least access needed for their work. Review administrator and adviser roles regularly and remove access promptly when responsibilities change. The ATO recommends checking who can access business information and updating access when people leave.
Which changes need approval and testing?
Record the request, business reason, affected organisation, settings, approver and test result for bank rules, chart-of-accounts changes, integrations, payroll connections and reporting configurations. Separate the person requesting a material change from the person approving it where practical.
How do lock dates reduce repeated corrections?
Set a lock date after a reviewed reporting or tax period. Xero explains that lock dates restrict edits to earlier transactions, while administrators can remove them. Record why a period was reopened and recheck affected reports before restoring the lock.
How should feeds and integrations be monitored?
Use a recurring check for failed bank feeds, duplicate imports, disconnected applications, mapping changes and unusual backdated transactions. Give each alert an owner and closure evidence instead of repeatedly clearing symptoms.
Which audit evidence should owners review?
Review system history for settings, users and material transaction changes, then compare it with approved requests. An audit trail helps identify activity but does not prove the business reason or accounting treatment was correct.
What belongs in the practical checklist?
- Named users and appropriate roles
- Administrator ownership and recovery access
- Change request and approval record
- Test evidence before release
- Lock date and reopen procedure
- Feed and integration exception log
- Audit history reviewed
- Owner report and next control date
What could this look like in practice?
Hypothetical example: A hypothetical Melbourne retailer finds duplicate bank-feed entries after an integration change. The administrator disables the affected rule, records the cause, tests the corrected mapping and rechecks the month before restoring the lock date. This invented example is not a software guarantee.
What do business owners ask?
Can automation remove the need for review?
No. Automation reduces routine effort but settings, exceptions and outputs still need controlled review.
Should every user be an administrator?
No. Use role-based access and reserve administrator rights for people who genuinely need them.
Does a lock date prevent every historical change?
Permissions and product behaviour matter. Review history and control who may reopen a period.
Where can you continue?
Read the live parent guide, review service information, use the related accounting-system management quote guide, and explore the TNS Accounting homepage.
Which official sources were checked?
- ATO: review access to business information
- Xero: secure business data and review activity
- Xero: set or remove lock dates
Published by TNS Accounting. Official sources checked 21 November 2026. Rules, guidance and software features can change; confirm the linked sources before acting.





