To split duties in a small finance team, write down which steps in a process should not sit with the same person, assign them to different people where the team is large enough, and where it is not, record a compensating review by someone outside the process. The written version is the part that lasts. Which steps a given organization treats as incompatible, and how often any review happens, is for the organization to decide with its qualified advisors and record in its own documents.
This article is general information about process and recordkeeping. It is not accounting, tax, legal or investment advice. How any transaction is recorded, classified or reported is a judgment for a qualified accountant who knows the business. Any limit, threshold or cadence mentioned here is for the organization to set with its qualified advisors and write into its own documents.
What it means to split duties in a small finance team
Separating duties means that no single person carries a process from request to record without another pair of eyes somewhere in the chain. It is sometimes called separation of duties, and in small organizations it is more often a documentation exercise than a staffing one.
The unit of analysis is the step, not the job title. A person can hold a wide job and still have a clean split, as long as the specific steps that should not combine are held apart. Writing the process out as steps is what makes that visible, and most teams find the exercise useful on its own, because it is often the first time the whole sequence has existed in one place.
What this buys you is a record and a clear line of responsibility. When someone asks later how a particular commitment came to be entered, the written split plus the review record answers it. That is the benefit being claimed here, and it is the only one worth claiming.
How to split duties in a small finance team step by step
- Write the process out as steps. Take one process at a time and list each step in order, from the request through to the point the record is final. Use the words the team actually uses.
- Mark who performs each step today. Initials against each step is enough. Do this from observation, not from job descriptions, because the two usually differ.
- Mark the steps that should not combine. Typically these are the step that initiates a commitment, the step that approves it, the step that releases payment, the step that enters it into the records, and the step that reconciles the result. Which combinations the organization treats as incompatible is its own decision, taken with its qualified advisors.
- Reassign what you can. Look for the cheapest moves first. Often a single step can shift to a colleague outside finance with no training burden, and that one move resolves most of the overlap.
- Name the compensating review where you cannot reassign. State who performs it, what they look at, and what they do when something looks wrong.
- Write the result down as a one-page table. Steps down the side, who holds each one, and where a compensating review sits.
- Date it, name an owner, and keep the superseded versions. The history is what shows the arrangement is maintained rather than invented once.
Doing this without restructuring the team
Resist the instinct to redraw jobs. Almost every workable split in a small organization comes from moving a step or so, not from creating new roles.
A handful of moves are usually available. A step can go to someone outside the finance function who already has the information. A step can be split so one person prepares and another releases. Or a step can stay where it is and be covered by a review that is recorded. Any of them is legitimate as long as the written version says which one you chose.
Anything that touches employment terms, job descriptions as contractual documents, discipline or the monitoring of individual staff belongs with an employment attorney and the organization's HR advisors, not with a process document.
When the team is too small to split anything
Plenty of organizations have one person doing the whole finance function. The answer is not to pretend otherwise.
In that situation the split moves upward and outward. Someone who does not perform the work reviews a defined slice of it: the person who runs the organization, a director, an office manager, or an outside accountant engaged for the purpose. The reviewer does not need finance skills to be useful. They need a written list of what to look at and a place to record that they looked.
Write down explicitly that the duties cannot be separated at current size, what review stands in its place, and who performs it. A document that says this plainly is far stronger than one that claims a split the organization does not have. Claiming a separation that is not real means the document has recorded a gap rather than a practice.
Also write down what changes when the team grows. One line is enough: when another person joins the function, these steps move to them. That line saves the whole exercise being redone later.
How a compensating review gets recorded
A compensating review that is not recorded has not happened, as far as anyone reading the file is concerned. Recording it well takes four elements.
| What a complete review record shows | What leaves a gap | |
|---|---|---|
| Who | The named person who performed the review | "Reviewed by finance" |
| What | The defined slice they looked at | "Checked the records" |
| When | A date | No date at all |
| Outcome | What they found and what happened next | A checkmark with nothing beside it |
Keep the record where the process lives rather than in a personal folder. A review note in someone's inbox is not part of the organization's record, and it leaves with them.
The outcome line matters more than it looks. A review that always records "nothing found" starts to look like a formality. A review that occasionally records a question, and what was done about it, reads as real, because that is how reviews actually go.
Choosing what the reviewer looks at
Give the reviewer a short, fixed list rather than an open instruction to review everything. Open instructions produce either nothing or an exhausting first attempt followed by nothing.
A workable list names the items to pull, says how they are selected, and says what the reviewer compares them against. Keep the selection method written down, because a reviewer who chooses items by feel cannot explain the basis later and neither can anyone else.
Keeping the written split honest
Review the document on a cadence the organization sets and records in its own documents, and log each review even when nothing changes.
Four events should trigger a look regardless of cadence. Someone joins or leaves the finance function. A step moves to a different person informally and nobody updates the page. The organization adds a process the page does not cover. Or a review record goes missing for a stretch, which usually means the review stopped and nobody noticed.
Keep the document short. A one-page table a new joiner can read in a sitting is worth more than a detailed manual that only the person who wrote it has ever opened. If the page has grown past scanning length, split it by process rather than letting it become a document people route around.
Separating duties in a small team is mostly an act of writing things down clearly enough that someone else could pick up the process. That clarity is the whole return, and it compounds every time the team changes. If you want a structure to start from, the Free Resources page on this site is where to look.