Fintrix Consulting LLC

Bookkeeping

Writing finance SOPs your team can follow

November 19, 2026 · 10 min read

← All articles
Whiteboard grid drawn in blue marker with colored sticky notes, one yellow note reading How-To
Photo via Pexels

Quick answer

Start with the processes that move money or decide your numbers: the month-end close, accounts payable, payroll and accounts receivable. For each one, write a short SOP that names the owner and the backup, the trigger and deadline, the systems used, the numbered steps, who approves what, and how you know it's done. Keep each SOP to a page or two, store them in one shared place, and review them whenever a person, a system or a bank changes.

Your bookkeeper gives two weeks' notice. Or she's out for a month after surgery. Suddenly nobody knows which vendor gets paid by wire instead of ACH, why the payroll journal entry gets split across three accounts, or where the password for the state unemployment portal lives.

That knowledge was never written down because it never needed to be. Until it did.

Finance SOPs (standard operating procedures) fix this. Not a binder nobody opens, but short, practical instructions that let a capable person run a process they didn't build. Below: which processes to write first, a template that works, how to handle approvals and segregation of duties on a small team, a worked example, and how to stop SOPs going stale.

Why do finance SOPs matter so much in a small business?

In a small company, most finance processes live in one or two heads. That works fine day to day. The trouble shows up at the edges:

  • Turnover and time off. The close slips by a week because the one person who knows the accrual entries is on vacation.
  • Errors that repeat. If each month's close is done from memory, the same reconciling item gets missed every few months.
  • Fraud risk. When nobody else knows how a process should run, nobody notices when it runs differently. Our post on small business fraud controls covers this in more depth.
  • Growth. You can't hand work to a new hire, an outsourced team or a fractional controller if the process only exists in someone's habits.

There's a quieter benefit too. Writing a procedure down forces you to look at it, and that's often when you spot the step that makes no sense, like printing a report just to retype the numbers into a spreadsheet.

Which finance processes should you document first?

Don't try to document everything at once. Rank processes by two things: how much money or reporting risk they carry, and how painful it would be if the usual person disappeared tomorrow.

For most small businesses, that puts four processes at the top:

  1. Month-end close. It decides whether your financial statements are right. Your month-end close checklist is the backbone of this SOP.
  2. Accounts payable and bill pay. Money leaves the business here, so approvals and vendor changes need to be crystal clear.
  3. Payroll. Deadlines are fixed, mistakes hit people's paychecks, and tax deposits carry penalties if they're late.
  4. Accounts receivable and collections. Invoicing, applying payments and chasing overdue accounts. Slow AR is a cash problem, not just a bookkeeping one.

After those, add the smaller recurring jobs: expense reports and company cards, sales tax filings, fixed asset additions, year-end 1099s, and the annual handoff to your CPA.

A worked example: picking the first SOPs for an 18-person distributor

Say you run a hypothetical 18-person wholesale distributor with one full-time bookkeeper and an office manager who helps with invoicing. You list the recurring finance work and estimate the hours each takes per month:

ProcessHours per monthDone byRisk if the usual person is out
Month-end close22BookkeeperHigh: statements late or wrong
AP and bill pay16BookkeeperHigh: missed or duplicate payments
AR and collections12Office managerMedium: cash comes in slower
Payroll6BookkeeperHigh: fixed deadlines, tax deposits
Expense reports and cards4BookkeeperLow: can wait a week
Total60

Monthly hours by finance process

Hypothetical 18-person distributor, 60 hours a month in total

Month-end closeMonth-end close: 2222AP and bill payAP and bill pay: 1616AR and collectionsAR and collections: 1212PayrollPayroll: 66Expense reports and cardsExpense reports and cards: 44

Hypothetical example. Hours are estimates for planning which SOPs to write first.

Show the numbers
Month-end close22
AP and bill pay16
AR and collections12
Payroll6
Expense reports and cards4

Three things jump out. The bookkeeper does 48 of the 60 hours, so almost everything depends on one person. The close and AP together take 38 hours, the biggest share. And payroll is only 6 hours, but it's high risk because the deadlines don't move.

So the order here would be: close first, then AP, then payroll, then AR. Expense reports can wait. Notice that hours alone would have put payroll fourth; risk moves it up.

What should every finance SOP include?

A good SOP is boring in the best way. Same headings every time, so anyone can find what they need quickly.

Finance SOP template: the fields to fill in

The basics

  • Process name and a one-line purpose
  • Owner (one named person) and backup (another named person)
  • Trigger and deadline, such as "every Friday by noon" or "books closed by the 5th business day"
  • Systems and access needed: software, bank portals, shared folders (never the passwords themselves)

The work

  • Numbered steps, one action each, in the order you actually do them
  • Screenshots or report names where a step is easy to get wrong
  • Inputs (what you need before you start) and outputs (what exists when you're done)
  • Known exceptions: the vendor paid by wire, the customer who always short-pays

Controls

  • Who approves what, and the dollar limits
  • Who reviews the finished work, and what they check
  • Where the evidence is saved: approvals, reconciliations, sign-offs

Upkeep

  • Last reviewed date and by whom
  • A short change log
  • Who to ask when something doesn't fit the steps

A few practical points on writing the steps:

Write for a smart stranger. Picture a competent accountant who's never seen your business. "Reconcile the bank" isn't enough. "Reconcile the operating account (ending 4421) in QuickBooks Online to the bank statement; any item older than 60 days goes on the open items list" is.

One action per step. If a step has "and" in it twice, split it.

Name reports exactly. "Run the A/P Aging Summary as of the last day of the month" beats "check payables."

Keep passwords out. The SOP says where access is managed (a password manager, the owner) and who grants it. Never paste credentials into a document.

How do you handle approvals and segregation of duties on a small team?

Segregation of duties means no single person controls every step of a transaction. As BDO puts it, the goal is to keep one individual from controlling multiple critical functions: getting at the money or systems, authorizing transactions, and recording or reconciling them.

On a team of two or three, perfect separation isn't possible, and that's fine. BDO's advice for lean teams is to separate the highest-risk duties first and add compensating controls, like management review, for the rest. A University of Florida internal control guide makes the same point from the other side: compensating controls are mostly extra reviews, they usually happen after the fact, and they're a fallback, not a replacement for separation when you have the people.

Your SOPs are where those decisions get written down. For example:

Who does what in the AP process

Prepares

Bookkeeper

  • Enters bills and codes them
  • Sets up new vendors after a verified W-9
  • Schedules payments in the bill pay system
  • Reconciles the bank account monthly

Approves and reviews

Owner

  • Approves every payment batch before it's released
  • Approves any vendor bank detail change after a call-back to a known number
  • Reviews the bank reconciliation and the vendor list each month
  • Holds admin rights in the bank and the accounting software

The bookkeeper can't both add a vendor and release a payment to it without the owner seeing it. The owner doesn't need to do any bookkeeping, just look at the right things on a schedule. That's a compensating control written into a procedure.

Put dollar limits in the SOP too. "Payments over $5,000 need the owner's approval in the bill pay system" is clear. "Large payments need approval" will be read differently by everyone.

Where should you keep finance SOPs?

One place, everyone on the finance team can find it, and with version history. A shared folder in your cloud drive or a wiki page per process both work. What doesn't work: SOPs scattered across email attachments, one person's desktop, and a printed copy from three years ago.

Link each SOP to the things it uses: the close checklist, the chart of accounts, the vendor setup form, the reconciliation template. If your close uses a calendar, our month-end close calendar can be the schedule your close SOP points to.

How do you keep SOPs from going stale?

SOPs rot quietly. The bank changes its portal, you switch payroll providers, a new approval limit gets agreed in a meeting, and the document still describes last year.

When to review a finance SOP
  1. Every time it's used by the backup

    Test run

    Have the backup run the process from the SOP once a quarter. Every question they ask is a gap to fix.

  2. Any change

    Trigger review

    New software, new bank, new person, new approval limit or a new vendor payment method: update the SOP the same week.

  3. Once a year

    Full review

    The owner of each SOP reads it end to end, updates the last reviewed date, and confirms the approvals still match reality.

The backup test run is the one that actually works. Reading an SOP, everything seems obvious. Doing the process from it, the missing steps show up in minutes.

Common mistakes

Writing a novel. A 20-page procedure won't get read or updated. If an SOP runs past two or three pages, it's probably two processes.

Documenting the ideal, not the real. Write how the process works today, then improve it. An SOP describing a process nobody follows is worse than none, because it gives false comfort.

No named owner. "Finance team" isn't an owner. One person is responsible for keeping each SOP current.

Backups who've never done it. Naming a backup is meaningless until that person has run the process at least once with the SOP in hand.

Leaving out the exceptions. The odd vendor, the customer on special terms, the account that always needs a manual entry. These are exactly what a stand-in will get wrong.

Burying controls. Approvals and reviews belong in the steps, not in a separate policy nobody connects to the work.

When to get help

If you have a stable bookkeeper and simple processes, you can write good SOPs yourself in a few afternoons. Start with the close, use the template above, and have someone else test it.

Get help when the person who knows the process is already leaving, when the books are behind and you'd be documenting a process that doesn't really work, or when you're about to hand work to someone outside the business. Written procedures for the work we take on are part of how a finance team extension works at Fintrix Consulting, so the process stays with your business, not with the people doing it.

Frequently asked questions

How long should a finance SOP be?

Usually one to three pages. Long enough to list every step and exception, short enough that people actually use and update it. If it's longer, split it into separate processes.

Who should write the SOP?

The person who does the work today should draft it, because they know the real steps. Someone else (often the owner or the backup) should then test it by running the process from the document.

Do we need SOPs if we outsource our bookkeeping?

Yes, though they look different. Your provider should document the work they do, and you still need SOPs for what stays in-house, like approving payments, sending invoices and handing over documents.

How often should SOPs be updated?

Whenever something changes (software, bank, people, approval limits) and at least once a year. A quarterly test run by the backup catches most gaps.

Can a two-person team really separate duties?

Partly. Separate the riskiest steps, like adding vendors and releasing payments, and cover the rest with reviews: the owner looks at bank reconciliations, vendor changes and payment batches on a fixed schedule.

The bottom line

Finance SOPs are insurance against the day the usual person isn't there. Start with the close, AP, payroll and AR. Give each one an owner, a backup, numbered steps, clear approval limits and a place to save the evidence. Then have the backup run it from the document, because that's the only real test that it works.

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.