For an accountant, least privilege means matching the scope to the stage of the job: read-only while you review, and no standing permission to alter a client's records. Let the assistant look and suggest; make the changes yourself or approve them one batch at a time. And disconnect when the review is done.
Why is this different for an accountant?
A personal user risks their own data. You carry the client's, along with a duty of confidentiality and the responsibility for any figures you hand back. A changed row you did not notice is not a small mistake when it goes into a ledger. Before connecting any assistant to client records, check your engagement terms and the client's consent, since those decide what you may share.
Which scope fits which stage of the work?
| Stage | What the assistant needs | Suggested scope |
|---|---|---|
| First look at a month of records | Read transactions | Read-only |
| Spotting odd or duplicate items | Read, compare | Read-only |
| Proposing categories for unplaced rows | Read; suggestions in chat | Read-only |
| Applying agreed category changes | Edit existing rows | Narrow edit, short-lived, if offered |
| Preparing export for the books | None | Do it in the app yourself |
Notice that only one row needs any write ability at all, and that one can be done by you in the app after reading the suggestions.
What does a review session look like?
Say a client's month has 480 rows and 35 are uncategorised. You connect read-only and ask the assistant to group the 35 by merchant and suggest a category for each, with its reasoning. You read the list, accept 28, change 4, and leave 3 for a call with the client. That is 28 + 4 + 3 = 35, every row accounted for.
Then you apply the changes in the app, in one sitting, where you can see each row. The assistant never had the power to change anything, so no suggestion could slip through unchecked.
What should I do before and after?
- Confirm client consent for using an assistant on their records.
- Connect with read-only and note the date and the purpose.
- Keep questions at the level of totals, merchants and patterns; avoid pulling more personal detail into the chat than the question needs.
- Apply any agreed changes in the app yourself.
- Disconnect at the end of the session and record that you did.
Where do the app's other features fit?
SpendixAI offers categories with GST rate, ITC-eligible and tax-deductible settings and an accounting code, and an Export centre with templates for Tally, Zoho Books and QuickBooks. Those are things you do with the data once you are satisfied with it, and they are done by you in the app, not by the connector. The report estimates are estimates; confirm them with invoices.
Pro covers one personal workspace, so it is not a multi-client practice tool. If you run several client books, check that the arrangement suits your obligations.
What should I tell the client?
Say plainly that you use an assistant for review, that it has read-only access for the length of the session, and that changes to their records are made by you. Clients are rarely troubled by the idea when it is put like that, and the conversation is easier before the work than after. Keep a short note of what was agreed, so that the permission you relied on is on file with the rest of your papers.
A closing checklist
- Client consent and engagement terms checked.
- Read-only scope chosen and noted with the date.
- Suggestions reviewed row by row.
- Changes made by hand in the app.
- Connector disconnected when the review ends.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
