1 How to share financial documents securely with a bookkeeper: 4 rules
ricardodun9562 edited this page 2026-11-20 16:49:20 +00:00


Knowing how to share financial documents securely with a bookkeeper comes down to four habits. Keep every file in one controlled place, give each person a named login with only the access they need, never send bank passwords by email, and remove access when the work changes. The habits are simple to describe and easy to skip, so this guide explains each one and the trade-offs behind it.

Why are email attachments the weakest way to share financial records?


Let's be honest: benefits of a outsourced CFO in Miami most owners send documents by email because it is the tool they already open all day. A bank statement goes out as an attachment, then a payroll report, then a loan application with a photo of last year's return. Each message is a copy, and each copy can sit in someone's inbox for years.


The risk is not only a stranger reading a message. A copy in an old mailbox, a forwarded thread, or a phone lost on a trip is hard to trace. You cannot easily tell who opened the file, who saved it, or whether the version you sent last month is still the one in use.


Picture a hypothetical import business in South Florida. The owner emails the bookkeeper a PDF of the operating account statement, with the full account number visible. A few months later the bookkeeper leaves the firm, and the owner has no list of who received what. Nothing was hacked, yet the owner cannot answer a simple question about his own records.


Email is not useless. It works for a quick note or a one-time request. It fails as the main channel for ongoing financial records because it offers no access controls, no clear activity history, and no way to pull back a copy once the work ends. Every forward creates another copy you do not control.


Read the fine print of your own email setup too. Consumer and free accounts were built for personal messages, and business owners often forget that. Before you keep sending files this way, ask whether the arrangement would survive a lost password, a departed employee, and a lender asking for a specific statement from two years ago.

What does a bookkeeper actually need, and what should stay private?


Not every document needs to reach the bookkeeper in full. Start by sorting what they need to record transactions: bank and card activity, invoices you issue, bills you pay, payroll summaries, and sales tax filings if you collect tax in Florida. Those files drive the books, and they make up most of what the bookkeeper works with each month.


Some items rarely belong in the working files at all. Full Social Security numbers, complete online banking credentials, and private personal tax details are the usual examples. A bookkeeper seldom needs your personal password to post a deposit. If a request asks for that kind of material, question it before you send anything.


Redaction is a practical habit. Show only the last four digits of an account number when the full number is not needed for the work. Remove unrelated personal pages from a multi-page statement. The bookkeeper can still reconcile the account, and a lost or forwarded file reveals much less.


Consider a small construction company with seasonal swings. The owner handles crews, subcontractor agreements, and client contracts. The bookkeeper needs invoices, payment records, and any lien waivers filed with each job. Detailed contract pricing can stay in a separate folder that the bookkeeper requests only when a specific question comes up.


Write the list down. A one-page document that names each file type, who sees it, and where it lives stops the common drift where everything ends up in one shared folder. Review it every quarter, because the business usually changes faster than the list does, and new staff or new bank accounts quietly add files nobody planned for.

Rule 1: Where should your financial documents live?


The first rule is to keep documents in one controlled place that the business owns, not in whichever inbox someone happens to use. A single location gives you one list to check, one history to review, and one place to remove access when the engagement changes. Without that place, you are guessing about where your records are.


Two options fit most small businesses. The first is the accounting platform itself. QuickBooks Online, NetSuite, and Sage Intacct all let you attach files to transactions and assign user roles, though features vary by edition and plan. The second is a business cloud storage account with folder-level permissions and version history. Either works if it keeps access logs and lets you revoke a user quickly.


Ask who controls the account. If the bookkeeper's personal cloud drive holds your client records, the business does not really control its own history. The safest arrangement has the business as the account owner, with the bookkeeper invited as a user. If the bookkeeper leaves, the records stay with you.


Use one folder structure from the start. Organize by year and month, and name files consistently, such as "2026-10 operating account statement." Consistent names help the bookkeeper find things, and they help you spot gaps during month-end, when a missing statement is easier to see in a clean list than in a pile of attachments.


Let's be honest about the trade-off. A central system adds a step, because the owner must upload a file instead of forwarding it. That step feels slow at first. It is also the step that creates a record. Once the habit sticks, benefits of a outsourced CFO in Miami the extra effort is small compared with the time lost searching for an attachment nobody can locate.

Rule 2: How do you control who can see and change what?


The second rule is to give each person a named login and only the access the job requires. Shared logins make it impossible to know who changed a record. They also turn a simple access removal into a password change that affects everyone, which is why people avoid doing it at all.


Separate the roles. A bookkeeper usually needs to enter and reconcile transactions. They rarely need to change bank account settings, add other users, or approve outgoing payments. Many platforms offer roles such as read-only, bookkeeper, or administrator. Choose the narrowest role that still lets the work get done, and widen it only when a real task requires it.


Turn on multi-factor authentication for every account that holds financial data. A password alone is weak when people reuse it or keep it on a sticky note. A second step, such as a code from an authenticator app, adds friction, and that friction is worth it when the account holds payroll and bank information.


Keep administrator rights with the owner or with a senior person who stays with the company. If the only administrator is the outside bookkeeper, you have handed over the keys to the system. Read any outsourced agreement to see who holds administrator rights after the engagement ends, and make sure the answer is you.


A useful test is simple. Ask your bookkeeper to list every person who currently has access to your books. If the list takes long to produce, or if it includes a former employee or benefits of a outsourced CFO in Miami a contractor who finished a project months ago, the controls are not working, whatever the software promises on its marketing page.

Rule 3: How do you connect bank data without sharing passwords?


The third rule is to never give anyone your bank password, your card password, or the security answers for your online banking. Bookkeepers do not need them. A password shared once tends to stay shared, even after the engagement ends and the person who received it has forgotten it exists.


Most banks offer ways to link transaction data without a shared password. A read-only feed through the accounting platform, or a user permission set up by the bank for a business account, lets the bookkeeper see activity without the ability to move money. Ask your bank which options exist for your account type, because names and features differ from one institution to another.


Be careful with phone calls and screen-sharing sessions where someone asks you to read out a one-time code. A legitimate bookkeeper does not need your code. If a message or a caller asks for one, stop, and call the bookkeeper's office on a number you already trust, not the one in the message.


Keep the bank feed as the main source of transactions where you can. Imported lines reduce the chance of someone typing a figure wrong. Bank statements still matter for reconciliation, so download them through your own login and upload them to the controlled location described in Rule 1. The statement itself should never travel by a channel the business does not control.


Think about a hypothetical retail shop with two bank accounts and one business card. The owner shares the card login so the bookkeeper can download transactions. Now the shop has handed over control of a payment method, and it cannot easily tell who used it. A read-only feed would have solved the same problem with far less exposure, and it would have left the owner in charge of the money.

Rule 4: When should access end, and how do you prove it did?


The fourth rule is to remove access on purpose. Many security problems in small businesses come from accounts that stayed open long after the work ended, not from dramatic breaches. Every login should have a start, a purpose, and an end date, even if nobody writes the end date down.


Build a short offboarding checklist. When a bookkeeper leaves the engagement, a staff member changes role, or a contractor finishes a project, the owner removes that person from the accounting platform, the cloud folders, the bank feeds, and any shared mailbox. Check each system separately, because one of them is almost always forgotten.


Review access on a fixed schedule. Quarterly works for many owners, and more often when staff turns over. Export the user list, compare it with the people who should still be working on the books, and mark each name as keep or remove. Save a dated copy of that review, so you can show later that the check happened.


Ask for activity logs. Many platforms record who logged in, who edited a transaction, and who exported a report. You do not need to read every line. You do need to know the log exists and where to find it when a question comes up during an audit, a lender review, or preparation for an investor's due diligence.


Keep your records under a clear retention plan. How long to keep each document type depends on the document and on your tax adviser's guidance, so confirm the periods with that person instead of guessing. Also remember that deleting a shared folder does not delete the copies a bookkeeper downloaded to a personal laptop. Ask for written confirmation that those copies are removed when the work ends.

How do the usual sharing methods compare side by side?


The table below compares four common ways to share financial records. The ratings describe typical behavior, not a promise about any product. Features vary by platform, plan, and contract, so verify each point against the tool you actually plan to use before you rely on it.

MethodAccess controlActivity historyRemoving access

Email attachmentNone once the file is sentLimited to the mailboxHard, because copies remain Shared cloud folderFolder-level permissionsOften available, depending on planStraightforward if the owner is administrator Accounting platform with user rolesRole-based, by userOften available, depending on planDone per user from one place Provider's client portalSet by the providerAsk the provider to show itDepends on the agreement


Email is the clear weak point. Once a file leaves your hands, you have no reliable way to control it. Even if you delete your own copy, the recipient's copy and every forward remain. Use email for short messages and never as the main archive for records that an audit, a lender, or a buyer may ask for later.


A shared cloud folder is a reasonable step up for storage. It gives you permissions and version history, which covers much of what a bookkeeper needs to find files. Its weakness is that folders hold documents, not the working transactions. Someone still has to reconcile the books somewhere else, so check how the two systems connect.


An accounting platform with user roles is usually the strongest option for ongoing work, because the files attach to the transactions they support. The roles limit what each person can change, and removing one user takes a few clicks from one screen. The benefit depends on using those roles properly. A platform with a single shared administrator login gains very little from its features.


A provider's client portal can be a good choice when a firm manages your books. Ask the provider to show you how access is granted, how it is removed, and what activity records exist. Read the fine print on where the data is stored, how long it is kept, and what happens to the files when the relationship ends. If the answers are vague, the portal is only a more polished inbox.

What should you verify this month before you trust the setup?


Verification is the step most owners skip. A setup that looked right in the first week can drift quietly as people join, leave, and change roles. Treat this check as part benefits of a Outsourced CFO in Miami the routine, and run it at the start of each quarter, before you add new documents or sign a new engagement.


Work through this short list with your bookkeeper or your internal finance lead. If you cannot answer one of the items, fix that item before you move anything else into the system:

Who is the administrator of the accounting platform and the cloud folders, and does that person still work with you? Does every user have a named login, with multi-factor authentication turned on? Can you export a list of everyone with access, and does it match the people you expect? Are bank connections read-only or feed-based, with no shared banking passwords anywhere? Can you find the activity log and a dated record of your last access review?


Do not try to solve everything in one afternoon. Pick the item that fails first, fix it, and move to the next. A partial fix that is documented is more useful than a full plan that exists only in someone's head. Keep the checklist and its dated results together, so the record shows the process, not just the intention.


Apply the same test to any outside accounting or CFO-level provider before you share a single file. Ask them to walk you through their document intake, their access roles, and their offboarding steps. A firm that handles financial data well can explain the process clearly and without drama. Vague answers, or a plan to send everything by email for convenience, are a warning sign worth taking seriously.


Finally, pick one method and move the active files into it this month. Start with the current-year bank statements, open invoices, and the payroll summaries that the bookkeeper uses every week. Then bring older records in over time. Stop using email as the storage habit for financial records, and keep short notes on each step, so when a lender, an investor, or an auditor asks how you handle your documents, you can show them the process you actually follow.