Fintrix Consulting LLC

Outsourcing

Keeping your data secure with an outsourced team

November 19, 2026 · 10 min read

← All articles
Finger entering a passcode on a tablet lock screen
Photo via Pexels

Quick answer

Give the outside team named logins (never a shared password), turn on multi-factor authentication everywhere, and grant each person only the role their work needs. Keep the power to release payments with you, share files through a secure portal instead of email attachments, put confidentiality in the engagement letter, and remove access the day someone leaves. Done that way, an outsourced team can be safer than the setup most small businesses run today.

You've decided to hand the books to an outside team. Then the uncomfortable thought arrives: people you've never met will be able to see your bank balances, your payroll, every vendor and every customer. What stops that data from leaking, or someone from moving money?

Mostly, the same things that should already protect you from your own staff and outside fraudsters. The usual risk isn't the outside team. It's the shortcuts: a password emailed "just this once", one login shared by four people, a former bookkeeper still active.

Here's how to set up access properly, what to ask any provider, and a worked example of an access review.

What can actually go wrong?

Small business data problems tend to come from a short list of causes:

  • Shared logins. When three people use the same username, you can't tell who did what, and you can't remove one person without locking out the others.
  • Too much access. The bookkeeper is an administrator in the accounting file, the bank portal and payroll, when they only need to read and record.
  • Stale access. People leave, firms change, and their logins stay active for months.
  • Documents by email. Bank statements, W-2s and ID scans sitting in inboxes, where one compromised email account exposes all of it.
  • Payment fraud. A fake "change of bank details" email from a vendor (often called business email compromise) gets paid because nobody calls to check.

Why should every person have their own login?

Because a login is how you know who did something, and how you stop them doing it again.

Every serious accounting platform, including QuickBooks Online and Xero, lets you invite users by email with their own credentials and a defined role. Use that. Your outside bookkeeper gets an invitation to your file, under your subscription, as themselves. The audit trail then shows their name against every entry, and when the engagement ends you remove one user without changing anyone else's password.

The same goes for banks. Many business banking portals let you add users with view-only or limited rights. If your bank only allows one login, that's a reason to use a read-only bank feed into the accounting software rather than handing over the credentials.

A simple rule worth adopting: nobody outside the business should ever know your online banking password. If a provider asks for it, that tells you something about how they work.

Is multi-factor authentication really necessary?

Yes. Of everything on this list, it does the most for the least effort.

Multi-factor authentication (MFA) means a password plus something else: a code from an app, a hardware key, a fingerprint. A stolen password alone then isn't enough to get in. Turn it on for the accounting software, the bank, payroll, bill pay, email and the file sharing tool, for every user, including you.

If you want a sense of what regulators consider normal, two public documents are useful references. The FTC's Safeguards Rule, which covers tax preparation firms and other businesses the FTC treats as financial institutions, requires MFA for anyone accessing customer information, along with access controls and encryption. IRS Publication 4557, written for tax professionals, recommends the same. You may not be covered by either, but they're a fair picture of the standard a provider handling financial data should meet.

What does "least privilege" look like in practice?

Each person gets the narrowest role that still lets them do their job, and nobody gets to both create and release a payment.

That second part matters most. It's the money version of segregation of duties: the person who enters a bill or sets up a vendor isn't the person who approves the payment. With an outsourced team, the clean split is usually:

  • The outside team prepares: codes transactions, enters bills, drafts payroll, reconciles accounts.
  • You (or someone you name) approve and release: payments, payroll, new vendors, changes to bank details.
  • Banks see read-only connections wherever possible, so the people recording transactions can't send money from the account.

Our post on small business fraud controls covers the monthly owner review and bank tools like positive pay that sit on top of this.

A worked example: an access review

Say you run a 20-person HVAC contractor. You've just moved from a part-time in-house bookkeeper to an outsourced team, and before the switch you list every login to every finance system. Here's what you find, and what you change.

Before:

  • The former bookkeeper is still active in the accounting file, the bank portal and bill pay.
  • One shared "office" login is used in four systems (accounting, bank, payroll, bill pay) by whoever needs it.
  • Two people can both enter a bill and release the payment.
  • The shared drive has 11 users, including two former employees.

After:

PersonAccounting softwareBank portalPayrollBill payShared drive
OwnerAdminFull, approves paymentsApproves payrollApproves and releasesYes
Office managerStandard userView and enter, no releaseNoneEnters billsYes
Outsourced bookkeeperAccountant userRead-onlyPrepares payrollCodes bills, no releaseYes
Outsourced reviewerAccountant userNoneNoneNoneYes
Two project managersNoneNoneNoneNoneUpload receipts only

That's 4 accounting users, 3 bank users, 2 payroll users, 3 bill pay users and 6 shared drive users: 18 logins, down from 29. The shared login is gone from all four systems, and only the owner can release money.

Logins to finance systems, before and after the review

Hypothetical 20-person HVAC contractor

  • Before (29 total)
  • After (18 total)
051015Accounting · Before (29 total): 6Accounting · After (18 total): 4Bank portal · Before (29 total): 4Bank portal · After (18 total): 3Payroll · Before (29 total): 3Payroll · After (18 total): 2Bill pay · Before (29 total): 5Bill pay · After (18 total): 3Shared drive · Before (29 total): 11Shared drive · After (18 total): 6AccountingBank portalPayrollBill payShared drive

Hypothetical example. Removed: the former bookkeeper, one shared login, two former employees and unneeded rights.

Show the numbers
 Before (29 total)After (18 total)
Accounting64
Bank portal43
Payroll32
Bill pay53
Shared drive116

Fewer logins isn't the goal. The point is that every remaining login belongs to a named person who needs it.

29 → 18

Logins after removing stale, shared and unneeded access

0

Shared logins left (one was used in four systems)

1

Person who can release a payment: the owner

How should documents be shared?

Not as email attachments, if you can avoid it.

A statement or W-2 sent by email lives in at least two inboxes indefinitely, and anyone who gets into either account can search for it. A secure portal or a folder with named access keeps files in one place, shows who can open them, and lets you remove access.

A few habits help:

  • Ask the provider which tool they use for documents and who on their team can open your files.
  • Don't send passwords, Social Security numbers or full bank account numbers in the body of an email.
  • Use folder links restricted to named people, not "anyone with the link".

What should the contract say about confidentiality?

Your engagement letter or service agreement should cover confidentiality in plain terms. Look for:

  • A confidentiality clause covering your financial and personal data, and the provider's staff and any subcontractors
  • Where your data is stored, and whether any work is done by people outside the firm
  • What happens to your data and their access when the engagement ends
  • How they'll tell you if something goes wrong, like a lost laptop or a compromised account

If a provider won't put confidentiality in writing, that's your answer.

What should you ask a provider before giving access?

Questions to ask any outsourced accounting provider

Access

  • Will each person on your team use their own named login in our software?
  • Do you ever need our online banking password? (The right answer is no.)
  • Can you work with read-only bank access?
  • Who on your team will see our data, and who reviews their work?

Money

  • Who approves and releases payments and payroll?
  • How do you handle a vendor asking to change bank details?
  • Can anyone on your side add a vendor and pay it?

Data

  • How do we send you documents, if not by email?
  • Is MFA required for your staff on every system holding our data?
  • Is confidentiality written into the engagement letter?

Leaving

  • Does our accounting file stay in our name and subscription?
  • How is access removed when someone on your team leaves, or when we end the engagement?

How outsourced bookkeeping works walks through the setup weeks, which is when most of these access decisions get made.

How do you handle offboarding?

Two kinds of offboarding matter: someone on the provider's team leaving, and you ending the engagement.

For the first, ask how quickly a departing staff member's access to your systems is removed. Because the logins are named, you can see it happen in your user list.

For the second, it should be boring. The file is in your name, so you remove the provider's users from the accounting software, bank, payroll and file sharing, change any passwords that might ever have been shared, and ask for written confirmation that copies of your documents have been returned or deleted. Our guide to switching bookkeepers lists what to keep.

Two ways to give an outside team access

Common

Shortcut setup

  • One shared login, password sent by email
  • Bookkeeper is admin everywhere
  • Bank password handed over
  • Documents emailed back and forth
  • Access stays on after they leave

Recommended

Safer setup

  • Named login per person, MFA on
  • Role limited to the work
  • Read-only bank connection
  • Secure portal or restricted folders
  • Users removed the day work ends

Common mistakes

Letting the provider own the subscription. If the accounting file sits in the provider's account, leaving gets complicated. Keep the subscription and the admin role in your name.

Skipping MFA for the owner. Owners often have the most access and the weakest habits. MFA applies to you too.

Approving payments without looking. An approval step only works if someone checks the vendor and the amount. A quick glance at new vendors and changed bank details catches most fraud.

Never reviewing the user list. Set a quarterly reminder. It takes ten minutes.

Trusting an email to change bank details. Call the vendor on a number you already have, not the one in the email.

When to get help

With a small team, you can do everything above yourself in an afternoon: list the systems and users, remove what isn't needed, turn on MFA.

Get help when you're bringing in an outside team and want the roles and approvals set up properly from day one. At Fintrix Consulting, we work inside your own QuickBooks Online or Xero file, connect to banks with read-only access where your bank allows it, never ask for your online banking password, and you approve every payment. Our security page sets out exactly who can see and do what.

Frequently asked questions

Is it safe to give an outsourced bookkeeper access to my bank account?

It can be, if the access is read-only or limited to viewing and preparing, never the power to release payments. Many banks let you add users with view-only rights, and most accounting software connects to the bank through a read-only feed, so the bookkeeper never needs your banking password.

Should my bookkeeper use my login?

No. Each person should have their own named login with its own role. Shared logins hide who did what and make it impossible to remove one person without disrupting everyone else.

What is least privilege access?

Giving each person only the access their work requires. For an outsourced team that usually means recording and preparing, while the owner approves payments, payroll and new vendors.

Do I need an NDA with my bookkeeping firm?

You need confidentiality in writing, whether it's a separate NDA or a clause in the engagement letter. It should cover the firm's staff and any subcontractors and say what happens to your data when the engagement ends.

What should I do when I stop using a provider?

Remove their users from your accounting software, bank, payroll and file sharing, change any passwords that may have been shared, and ask for written confirmation that your documents were returned or deleted.

The bottom line

An outside team doesn't have to mean more risk. Named logins, MFA on everything, roles limited to the work, and payments released only by you take care of most of it. Share files through a portal instead of email, get confidentiality in writing, and review your user list every quarter. If a provider resists any of that, keep looking.

This article is general information, not advice for your situation. Rules change and details matter, so talk to us or your CPA before acting on it.

Have a question about this article?

Ask us. A real person will reply by email within one business day. Your question isn’t published.

Protected by reCAPTCHA. Google’s Privacy Policy and Terms apply.

Ready for books you can trust?

Book a free 30-minute consultation. We'll review where your finances stand today and show you exactly how we'd help.