When an engagement ends or a review is finished, an accountant should disconnect any AI assistant from the client's finance app, confirm that access is gone, and note the date in the working papers. It takes minutes, and it protects you if anyone later asks who could see the client's records and until when.
When should you disconnect?
- At the end of a review or a quarterly close
- When a staff member who set up the connection leaves your firm
- When the client withdraws consent
- Before you share a laptop or hand over a file to another reviewer
- Whenever you changed the scope for a one-off task
The procedure
- Open the client's workspace using your own access
- Open the list of connected assistants; in SpendixAI, MCP connections are listed with a disconnect option
- Record the assistant name and connection date before removing
- Disconnect, then ask the assistant a test question and confirm it cannot answer
- Remove the connector from the assistant's side as well
- Note the date, the time and the reason in your file
What goes in the file note?
| Item | Example entry |
|---|---|
| Client and period | Client A, quarter ended 30 September |
| Assistant and scope | Claude, read-only |
| Connected on | Date noted from the connection list |
| Disconnected on | Date and time of revocation |
| Verification | Test question returned no data |
| Reviewer | Initials of the person who did it |
A worked tie-out after disconnecting
Say you used the assistant read-only to find that October had 212 transactions totalling ₹4,86,300 and you noted both figures. After disconnecting, open the transactions list yourself and confirm the same count and total. If they match, your review stayed read-only. If the count is 215, three entries were created during the session, so find them and ask the client whether they are intended. A difference of ₹3,600 across three rows would be easy to spot against a statement.
What about the client's data inside the assistant?
Anything the assistant displayed during your session may remain in the conversation history held by that assistant. Delete the conversation if it contains client records, and avoid pasting figures into chats you cannot remove. Client consent should cover the purpose, so keep the use narrow.
What if the client asks what the assistant saw?
Answer from your note. You should be able to say which assistant, which scope, which period and which questions. If the answer is that you used it read-only to scan for duplicates and large round amounts across one quarter, that is a clear, limited description. A vague answer invites worry, even where nothing went wrong.
Does disconnecting affect the client's reports?
No. The client's imports, categories, rules and reports are unaffected, because the connection only granted permission to read or add records. What can change is the entries created during your session, so they are worth checking. Share the list of anything you added, and explain that the client may delete it if it should not be there. In SpendixAI deleted items stay in a recycle bin for 30 days.
One practical tip: do the disconnect while the client is still on the call or has just approved the review. Then the sequence of consent, work, revocation and confirmation sits in one tidy stretch of your file, and nobody has to reconstruct it from memory a quarter later.
Closing the engagement
- Tell the client in writing that access has been removed
- Export what your engagement needs; the app offers templates for Tally, Zoho Books and QuickBooks
- Do not keep client credentials; a connection never needs the client's bank login
- Remember that a connection does not change the client's own records; correct entries by hand if needed
Useful ideas start with a clearer picture of your own spending.
Explore your reports

