What is segregation of duties in bookkeeping?

Segregation of duties is the principle that no single person should control every step of a financial transaction — whoever creates a payment shouldn't be the one who approves it; whoever approves expenses shouldn't approve their own. It isn't an accusation of dishonesty. It's the recognition that errors and fraud both live in the same place: steps nobody else looks at.

The separations that matter most

In a finance function, four pairings do most of the protective work:

• Entering vs approving payments. The person who keys the supplier payment shouldn't release it.
• Creating vendors vs paying vendors. Someone who can add a vendor record and pay it can pay anyone, including a vendor that's their own bank account.
• Claiming vs approving expenses. Nobody approves their own claim — including, awkwardly, the most senior person in the room.
• Handling money vs reconciling it. Whoever banks the takings shouldn't be the one who reconciles the bank account that would reveal a shortfall.

The small-business problem

The textbook version assumes a finance department. Most Australian small businesses have one bookkeeper, and the full separation is arithmetically impossible. What's achievable is compensating control — someone else looking at the step you can't separate:

1. Split at the bank, not just the software. Dual authorisation on payments above a threshold costs nothing and puts a second set of eyes exactly where the money leaves.
2. Owner reviews the vendor list quarterly. New vendors, changed bank details, and dormant vendors that suddenly resumed — ten minutes, and it covers the create-and-pay gap.
3. Someone who isn't the bookkeeper opens the bank statement occasionally and scans it — the classic long-firm frauds survived on nobody but the fraudster ever seeing the actual statement.
4. Write down who approves what, even in a three-person business. An approval rule that lives in one person's head isn't a control; it's a habit.

Detecting breakdowns after the fact

Whatever the policy says, the ledger records what actually happened — and self-approval and its cousins are mechanically detectable. Finanomaly's journal and expense modules check for exactly these patterns: journal entries where the enterer and approver are the same person (its highest-severity journal rule), expense claims approved by the claimant, one approver concentrating a large share of all payment approvals, and payments to vendors whose details overlap with employee records.

The honest limit: detection sees the recorded fields. If approvals happen outside the system — a nod across the office, a shared login — the data shows a clean approver column and the control has already failed upstream. Detection complements the structural fixes above; it doesn't replace them.

FAQ

What is segregation of duties in simple terms? No one person should control a financial transaction from start to finish. Whoever enters a payment shouldn't approve it, nobody should approve their own expenses, and whoever handles money shouldn't be the one reconciling the account that would reveal a problem.

How do you implement segregation of duties in a small business with one bookkeeper? Full separation isn't possible, so use compensating controls: dual bank authorisation on payments above a threshold, a quarterly owner review of the vendor list and bank-detail changes, and someone other than the bookkeeper periodically reading the actual bank statement.

Finanomaly detects segregation-of-duties breakdowns — self-approvals, approver concentration, vendor-employee overlaps — in your finance data. Join the waitlist.