What the Owner Must Own and What the Bookkeeper Owns
Why this matters
Most owners draw the line in the wrong place. They hand off everything that looks like accounting and keep everything that looks like running the shop, which sounds sensible and quietly gives away the two or three judgment calls that decide whether the numbers mean anything. The bookkeeper then makes those calls by default, in the only way an outsider can: by picking the safest-looking option and being consistent about it. Nothing is stolen, nothing is late, every account reconciles, and the gross margin you price against is wrong by several points for a year.
The line that works is not about skill. A good bookkeeper is better at recording than you will ever be. It is about who has to answer for the number afterward.
The wrong boundary and the right one
The wrong boundary is difficulty. It puts everything technical on their side and everything obvious on yours, which is exactly backwards, because the technical work has a right answer somewhere and the obvious work does not.
The right boundary is one question: if this were wrong, would it change a decision I make in the next 30 days? If yes, you own the call. Someone else can do the keystrokes, prepare the schedule, and chase the paperwork, but you make the call and you sign it. If no, and the task has a defined right answer that a competent person can reach without knowing your shop, it belongs to the bookkeeper outright.
Two secondary tests catch the edge cases. Is there a rule that decides it? A task governed by a written rule is delegable even when it is important, because the judgment was already made when you wrote the rule. Would a stranger reach the same answer? If two competent bookkeepers would code the same receipt differently, that is not a recording task, that is a policy question wearing a receipt.
The split
| Area | Owner owns | Bookkeeper owns |
|---|---|---|
| Chart of accounts | The shape: what counts as job cost, how many revenue lines, what gets tracked separately | Keeping entries inside the shape, flagging anything that does not fit |
| Transaction coding | The rule and the exceptions list | Applying the rule to every transaction |
| Revenue recognition | What "done" means for your work | Booking revenue on that definition, consistently |
| Receivables | Who gets credit, who goes to collections, who gets written off | The aging report, the reminder cadence, the record of contact |
| Payables | Which bills get paid when cash is tight | Entering bills, scheduling, matching to purchase records |
| Payroll | Classification, pay rates, overtime policy | Running it, filing it, reconciling it |
| Owner pay | Draw versus wage, and how much | Recording it correctly to the right account |
| Bank access | Signing authority and who can move money | View and entry access, reconciliation |
| Statements | Reading them and asking the questions | Producing them on schedule, on a consistent basis |
| Tax positions | Nothing. Route to your accountant | Nothing. Route to your accountant |
That last row is not a joke. A bookkeeper records, an accountant advises, and the two are different jobs even when the same person does both. Anything genuinely tax-determinative goes to the person who signs the return, and this card is not tax advice.
What you deliberately do not hand over, and why
This is the part that gets given away quietly, so it is worth naming item by item.
Signing authority. Someone else can prepare payments, queue them, and hand you the list. You release them. This is the single control that survives every other control failing, and it costs you a few minutes a week.
Sole possession of a login. Every account, bank, card, payroll, and accounting file must have an owner login that does not depend on anyone else's cooperation. Not because you expect a problem, but because a bookkeeper can get sick, get hired away, or get into a dispute with you, and none of those should be able to lock you out of your own history.
The meaning of a variance. A bookkeeper can tell you that job cost ran 6 percentage points above the trailing quarter. Only you know whether that was the two large installs, the new tech's learning curve, or a coding change. Handing over the interpretation is how a real problem gets explained away in a sentence and then repeats for three quarters.
Customer credit decisions. Extending terms, holding work on a past-due account, and writing off a balance are commercial decisions with relationship consequences. The aging report is theirs. Deciding who gets cut off is yours.
The definition of a completed job. If revenue books at scheduling, at completion, or at collection, your revenue line moves by weeks and your margin by more than that. Decide it once, write it down, and never let it drift because a particular month looked thin.
Two cases people get wrong
Job costing. Owners hand this off because it lives in the accounting file. But job costing is the act of deciding which costs belong to which job, and that is your pricing model expressed as bookkeeping. Write the rule, adjudicate the exceptions, and let the bookkeeper execute. If you cannot state your rule in one sentence, you do not have one, and every ambiguous receipt for the last year has been resolved by someone guessing.
Owner draws. These get miscoded more than any other transaction in a small shop, usually into an expense account, which makes the business look less profitable than it is and quietly overstates operating cost. The bookkeeper cannot fix this because they cannot tell your grocery run from a shop supply run without being told. You tell them, once, with a rule about which card gets used for what.
Worked example: the boundary that was one sentence short
A four-technician shop hands the books to an outside bookkeeper. Everything runs clean for three quarters: reconciled on time, statements out by the fifth working day, no missing receipts.
In the fourth quarter the owner walks the coding for the first time. The quarter carries 612 coded transactions. Of those, 47 are genuinely ambiguous between direct job cost and overhead: shop consumables, a tool that lived on one truck for two months, fuel on days that mixed service calls with a supply run. With no rule to apply, the bookkeeper had sent 41 of the 47 to overhead, which is the conservative-looking default, and the remaining 6 to job cost where a job number happened to be written on the slip.
Reworking those 41 into job cost moves 6 percentage points of revenue from overhead into direct cost. As booked, direct job cost ran 52% of revenue and gross margin 48%. Corrected, direct job cost is 58% and gross margin is 42%.
That 6-point swing is the whole story. The owner's target gross margin was 45%. On the booked numbers he was 3 points above target and spent the year holding prices to stay competitive. On the corrected numbers he was 3 points below target, and every price held was held against a margin he did not have. Nothing was stolen and nothing was misreported in a way an audit would flag. A recording task was left to be decided 47 times by someone with no basis for deciding it.
The fix was one sentence: anything consumed on a specific job codes to job cost, anything that stays at the shop or serves every job codes to overhead, and anything the bookkeeper cannot place goes on an exceptions list for the owner. In the following quarter the exceptions list ran 9 items. At roughly 2 minutes each that is about 18 minutes of owner time for the quarter, against a 6-point error in the number he prices from.
What would move an item across the line
Two conditions genuinely shift the boundary, and neither is "the bookkeeper is very good."
A written rule moves a call from your side to theirs. Once you have decided what counts as job cost, the coding is execution. That is the mechanism for shrinking your own load: not delegating harder, but deciding once in writing so the same decision does not need you again.
Scale moves review from item to sample. Below a few hundred transactions a month you can eyeball the coding. Above that, you stop reviewing items and start reviewing the exceptions list plus a sample: pull 10 transactions at random and check them against the rule. If more than 1 of 10 is coded against your own rule, the rule is unclear rather than the bookkeeper careless, and rewriting it beats correcting entries.
How to check the boundary is real
Four checks, none of which takes long, and each of which fails loudly when the line has drifted.
- Log in yourself, from your own device, to every financial account, without asking anyone. Do this quarterly. If you cannot, the boundary has already failed regardless of how the statements look.
- Read your own coding rule out loud and pull five recent ambiguous transactions. If you cannot predict how each was coded, the rule is not doing the work you think it is.
- Ask for last month's exceptions list. If there is no list, either your rule covers everything, which is unlikely, or the ambiguity is being resolved silently, which is the failure this card is about.
- Ask one question about a variance and see who answers it. If the bookkeeper explains what a movement in job cost means for your business rather than what changed in the accounts, you have outsourced interpretation, and the person interpreting has never been on one of your jobs.
The bookkeeper who pushes back on the exceptions list, insists you sign payments, and refuses to interpret a variance is the one to keep. That is not friction, that is someone protecting the line you should have drawn yourself.
References
- U.S. Small Business Administration (SBA), guidance on separation of financial duties in small businesses
- Generally Accepted Accounting Principles (GAAP), consistency and revenue recognition concepts
- See related: The First Office Hire: CSR vs Dispatcher vs Bookkeeper Decision Matrix; Chart of Accounts Design for a Service Business; Reading Your Profit and Loss Statement