Should the person who keeps the books also pay the bills
Where the line sits when there are only three of you.
Recording and releasing money should not be the same pair of hands. In a small company that sounds impossible and is not. The bookkeeper prepares the run, somebody without ledger access releases it, and one other person reads the bank statement once a month. Three habits, no extra headcount.
Work it out in a minute
Three numbers you already know and one answer. Shows what an old login could still reach today.
What we take on
Preparing and releasing are different jobs
Whoever codes the invoice can absolutely assemble the payment run. Somebody else clicks the button that sends the money. That single split does most of the work.
Read-only bank access is the quiet fix
A bookkeeper needs to see transactions to reconcile them. They do not need the ability to move money to do that, and most banks separate the two permissions in a couple of minutes.
Somebody reads the statement who touches nothing
Once a month, one person outside the process looks at the bank statement against the payment list. It takes ten minutes and it is the control that catches what the other two miss.
New payees deserve a second pair of eyes
Adding a supplier and changing bank details are the two moments worth a confirmation from somebody else, by a channel other than the email that asked for it.
Outsourcing tends to help here
When the recording sits outside the company and the release sits inside it, the separation is structural rather than something a small team has to arrange between friends.
Write down who does what
One page: who codes, who prepares, who releases, who reviews, and what happens when somebody is away. It is the difference between a control and an assumption.
How to get separation in a company of three
The textbook answer assumes a finance department. Most companies asking this question have one bookkeeper, an owner, and possibly an office manager, and the textbook answer is no help at all. The practical version needs no extra headcount.
Split preparing from releasing. The person who keeps the books assembles the payment run, with the invoices attached and the amounts visible. Somebody else, usually the owner, releases it. That one split removes the single largest risk.
Set bank access to read-only for whoever reconciles. They need to see what happened, not to be able to make it happen. Most banks and most accounting tools separate those permissions, and almost nobody uses the distinction.
Then add the review. Once a month somebody who is not in the process reads the bank statement against the payment list and asks about anything they do not recognize. It is ten minutes and it does more than the two controls above combined.
Treat new payees and changed bank details as their own moment. Both are worth a verbal confirmation to a number you already had, rather than a reply to the message that asked. This is where most of the real losses in small companies happen.
Write the whole thing on one page with names against each step and a line about cover when somebody is on holiday. Controls that live in people heads stop existing the week somebody is away, which is exactly the week they matter.
Questions we get
We are three people. Is separation realistic?
Yes, and it is smaller than it sounds. One person prepares, one releases, one reads the statement monthly. In a company of three those can be three different people without anybody taking on a second job.
Where it is genuinely two people, the monthly statement review becomes the control that carries the most weight.
Can our bookkeeper have bank access at all?
Read-only, yes, and it makes reconciliation far quicker. Payment initiation is the permission worth withholding, and it is a separate setting rather than an all or nothing choice.
Ask your bank for view access without payment rights. It is a standard request.
What about paying through accounting software?
The same split applies inside the tool. Most of them have an approval step, and it is usually switched off because it was faster that way on day one.
Switching it on takes a few minutes and it survives whoever is doing the work.
Is this only about fraud?
Mostly it is about mistakes. A duplicate payment, a wrong figure, an old invoice paid twice. A second pair of eyes catches those long before it catches anything deliberate.
The control pays for itself on ordinary errors.
Does an outside bookkeeper make this easier or harder?
Easier, usually. Recording sits with one party and releasing with another by default, which is the separation a small internal team has to construct deliberately.
The page on outsourcing or hiring covers where that work should sit more broadly.
What do you do here?
We keep the books current and prepare the run with the backup attached. Releasing payments stays inside your business, and bank access on our side is read-only.
The one page naming who does what is part of the setup rather than something you have to ask for.
The same question applies to filings. Delaware business filings shows what falls due whether or not anybody is watching.
More in the guides and every answer in one place.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built