Shared logins in a bookkeeping firm hide who did what. When three people use one sign-in, a changed entry or a downloaded statement cannot be traced to anyone, and nobody can be removed without resetting it for everyone. Named users fix both problems, and moving to them takes an afternoon per tool.
Why are shared logins in a bookkeeping firm a problem?
A shared login turns several people into one person as far as the software can tell. That breaks accountability, makes removing access painful, and usually weakens the password itself, because a password many people must remember tends to be short and rarely changed.
The shared password also travels. It gets written on a sticky note, pasted into a group chat or emailed to a new hire. Every copy is a way in. And multi-factor sign-in, which should protect the account, ends up tied to one person's phone, so colleagues relay codes to each other. That is the habit a phishing message counts on.
The data behind these logins is sensitive. A statement tool or a cloud folder holds full account details, names and addresses, the items listed in the guide to personal information on bank statements. One leaked shared password exposes all of it for every client at once.
The audit trail that shared logins erase
An audit trail is the software's record of who signed in and what they changed. With a shared login, every entry in that record carries the same name, so the trail exists but tells you nothing. When a client asks who reclassified a payment or deleted a transaction, the firm cannot answer.
The FTC's guide to the Safeguards Rule lists logging the activity of authorized users among the safeguards covered businesses must have. A log of a shared account cannot meet that aim in any meaningful way.
The trail matters most on a bad day. If ransomware or a stolen password hits the firm, the first job is working out which account was used and when. The guide to ransomware protection for bookkeepers explains why that question decides how much has to be rebuilt. With named users, you suspend one account and keep working. With a shared one, you lock everyone out.
Shared logins that stay with departed staff
A shared password stays in a departed employee's head, browser and phone until someone changes it. Firms often put that off, because changing it means telling everyone else the new one. So a person who left months ago can still sign in, and the log will never show it was them.
Contractors and seasonal help make this worse. A temporary bookkeeper hired for tax season learns the shared password in February and keeps it long after April. With a named user, ending access is one click on the day they finish, and nobody else notices.
Switching a bookkeeping firm from shared logins to named users
Moving a firm to named users means giving every person their own sign-in to every tool, with only the clients and rights they need, then retiring the shared account. Do it one tool at a time, starting with the tool that holds the most client data.
- List every shared account. Example line: "Cloud storage, one login, used by three staff, holds all client statements."
- Check each tool's user options. Note whether it offers separate users, roles or per-client permissions, and what extra seats cost.
- Create a named user for each person, using their own work email address.
- Turn on multi-factor sign-in for each user, on their own phone or authenticator app.
- Limit rights. Give each person only the clients and actions their role needs.
- Retire the shared account. Change its password, store it with the owner only, or delete it if the tool allows.
- Record the change in the firm's access list, with the date.
Statement tools deserve a place near the top of the list. The post on uploading client bank statements securely includes per-person access among its vendor questions. AutoBankConvert's Firm plan includes team seats and roles, so each bookkeeper can sign in under their own name.
When is a shared login hard to avoid for a bookkeeping firm?
Sometimes a tool or a client offers only one sign-in. A few older desktop programs have a single user, some small client portals allow one account, and many client bank logins belong to the owner alone. In those cases, limit who holds the password, keep it in a password manager, and record every use.
Nonprofit clients bring a version of this problem. A small charity may run its bank account and books under one login held by a volunteer treasurer, with the bookkeeper given the same password. The guide to nonprofit bookkeeping covers the board oversight such clients need. Here, ask the board to request a separate user from the bank, or switch to statements sent each month.
Where a single login truly cannot be avoided, treat it as an exception with an owner, a reason and a review date. An exception you wrote down is one you will remember to remove. To keep statement work off shared sign-ins entirely, see how AutoBankConvert handles client workspaces.