Direct answer: An accounting system management scope should define system ownership, user access, bank feeds, reconciliations, integrations, master data, close controls, backup or export responsibilities, issue handling and approval for changes. It should distinguish routine administration from bookkeeping and specialist implementation.
Who owns the accounting system and its decisions?
Name the business owner for subscriptions, organisation settings, data retention and final approval. Identify administrators, day-to-day users, external accountants or bookkeepers and read-only reviewers. Avoid a setup where only a departing employee or provider controls access.
Document who may invite users, change bank details, edit tax settings, post journals, connect apps or publish reports. Xero’s official user-role guidance shows that different roles have different capabilities; apply least access needed rather than giving everyone administrator rights.
Which recurring controls belong in scope?
- Bank-feed connection and exception monitoring
- Bank and control-account reconciliation dates
- User-access and dormant-account reviews
- Lock dates and review of changes to closed periods
- Chart-of-accounts and contact-master maintenance
- Integration failure and duplicate-transaction checks
- Month-end report review and issue register
Connect these tasks with the monthly accounting software controls parent guide. The scope should state frequency, evidence and escalation—not merely say the system will be “maintained.”
How should access and approvals be controlled?
Separate preparation and approval where practical. Require independent approval for new bank accounts, payment-detail changes, high-risk integrations, administrator access and material changes to reporting or tax settings. Use individual logins and multi-factor authentication; do not share a generic administrator password.
Schedule access reviews after staff or provider changes and at least at the frequency agreed in the scope. Remove access promptly, but preserve records and audit trails.
What belongs in integration and bank-feed management?
List each connected bank, payroll, point-of-sale, ecommerce, receipt and payment app, its owner, sync direction, expected timing and failure alert. State who investigates missing or duplicated data and how corrections are approved.
A connected feed is not the same as a completed reconciliation. Xero’s role guidance separates capabilities for bank transactions and reconciliation, so the business should confirm both access and review responsibility.
How should changes be requested and recorded?
Use a change log for new accounts, tracking categories, tax rates, templates, workflows, permissions and integrations. Record the request, reason, risk, tester, approval, implementation date and rollback plan. Test material changes before relying on them for a live reporting period.
Unplanned cleanup, migrations or app implementation should become a separate approved piece of work. See the Accounting System Management service page for the wider service context.
What evidence should the business receive?
Agree on a monthly control summary, reconciliation status, unresolved issue register, access-review record and list of significant changes. Confirm how data can be exported in a usable format and what the business retains if the provider changes.
The business should be able to understand what was done without depending on one person’s memory. Related guides are available from the TNS Accounting homepage.
Practical checklist
- Name the system owner and administrators
- List every user role and approval boundary
- List bank feeds and connected applications
- Set reconciliation and month-end deadlines
- Define change-request and testing steps
- Keep an issue and change register
- Review access after staff or provider changes
- Confirm export, retention and handover responsibilities
Hypothetical example
Hypothetical example only: A Melbourne trades business uses accounting software, a payroll app and a receipt app. Its monthly scope assigns bank-feed monitoring to the bookkeeper, reconciliation review to the owner, integration failures to the system manager and new app approval to a director. A new payment integration is excluded until a separate risk review and test plan are approved.
Frequently asked questions
Is system management the same as bookkeeping?
No. They overlap, but system management focuses on configuration, access, integrations and controls; bookkeeping records and reconciles transactions.
Should an external provider be the only administrator?
Usually the business should retain appropriate owner-level control and a documented recovery path, while limiting day-to-day administrator access.
How often should permissions be reviewed?
Review them after role or provider changes and on the recurring schedule set by risk, user count and the sensitivity of available functions.
Sources checked
- Xero Central – User roles and permissions
- Xero Central – Bank account and transaction access by role
- ATO – Overview of record-keeping rules for business
Published by TNS Accounting. Source check completed 20 November 2026. This general information does not replace advice for your circumstances.






One Response