The automation line
What should never happen automatically in outsourced finance?
Two categories. Anything consequential and external — money leaving the business, a filing being submitted, a message or commitment going out in the client’s name — and anything uncertain, whatever its size. Those need a person deciding, every time, and no volume of routine work earns an exemption from either.
Everything else is a different question, and the popular answer to it is wrong. Routine internal record-keeping does not need a human rubber stamp on every entry, and insisting on one buys the appearance of control rather than control itself. What makes routine recording safe is that the treatment is already established, the facts and evidence are complete, and independent checks agree — and that anything failing those conditions stops instead of completing.
“Does a person approve this?” is the wrong question.
The instinct is reasonable. If machinery is doing finance work, a person should sign off each thing it does. It sounds like control, and in a small enough business it briefly is one.
At any real volume it produces one of two outcomes, and neither is control. Either the approvals become a bottleneck nobody honours, so the books fall behind and the sign-off is abandoned quietly; or the approvals are given without being read, which is worse than no approval at all, because responsibility has been transferred without attention going with it. A signature applied to a hundred entries in four minutes is not a review. It is a record that somebody can be blamed.
Two better questions replace it, and between them they decide almost every case.
| Kind of act | Examples | What is appropriate |
|---|---|---|
| Routine, complete, internal | Recording a recognised supplier bill on an established treatment. Matching a receipt that agrees exactly to an issued invoice. Posting an already-approved payroll run to the ledger. A recurring charge treated the same way for a year. | Completes without a per-entry sign-off — where the treatment is established, the evidence is attached and independent checks agree. Recorded, evidenced and reviewable afterwards by anyone. |
| Anything uncertain | A payment that could settle either of two invoices. A document missing the fact its treatment depends on. An unfamiliar transaction type. An amount that does not agree to the statement. | Stops. Becomes a named open item with a reason, an owner and a date. Never completes on the most likely reading. |
| Consequential and external | Releasing a payment. Submitting a filing. Sending a message in the client’s name. Agreeing a term, conceding an amount, committing to a third party. | Never automatic, and never the provider’s to perform. Prepared in full, presented for decision, executed by the business. |
What routine completion actually requires.
Most finance work genuinely repeats. The same suppliers, the same treatments, the same shapes, month after month, at volumes no owner-led business wants to pay a person to re-decide. A provider that insists every one of those is individually reviewed is either not doing it, or charging for it and falling behind. Both are common, and neither is safer than the alternative.
What makes completion without a per-entry sign-off legitimate is not the absence of a control. It is the presence of four, all of which must hold at once.
- The treatment is established in advance. How this class of item is recorded was decided beforehand by somebody qualified to decide it, and has been applied consistently before. An item that is the first of its kind is not routine, by definition.
- The facts are complete. Everything the treatment depends on is present — counterparty, date, amount and currency, period, and the engagement or cost centre where that matters. Nothing has been inferred to fill a gap.
- The evidence is attached. The document supporting the entry is held against it at the moment of recording, not promised for later. A record whose support is outstanding is not a completed record.
- Independent checks agree. The work is checked separately from the pass that produced it, and a disagreement halts the record rather than being reconciled away. Agreement is a condition of completing, not a report produced afterwards.
Any one of those failing suspends completion. It does not lower the bar, and it does not trigger a faster review — the item simply becomes an exception and waits for a person. That is the entire safety property, and it is testable from outside: a provider can either tell you precisely what suspends automatic recording on your account, or it cannot.
Accountability here sits at the level of the treatment, not the individual entry. Somebody qualified decides how a class of item is handled and answers for that decision. A record produced under an established treatment is machine-finalised and evidenced — it should never be described as individually reviewed by a person, because it was not, and a provider that describes it that way is telling you something inaccurate about its own process.
Seven things that should never happen on their own.
These hold regardless of confidence, volume, track record or how well the previous eleven months went. Each has been automated somewhere by somebody, usually for good operational reasons, and each is a boundary worth writing into an engagement rather than assuming.
- Guessing where a fact is missing. If the treatment depends on something the business never supplied, the correct output is a question. The most likely answer, recorded, is indistinguishable from a known one the moment it lands in the ledger.
- Recording without support. An entry whose evidence is expected rather than held is a placeholder wearing the clothes of a record. Placeholders are fine while they are labelled. They stop being fine the second a period closes over them.
- Money leaving the business. A provider can prepare a payment run to the last detail — amounts, beneficiaries, dates, references, the lot. Releasing funds is an act of the business, and it should not be delegable by convenience, scheduled by default, or inherited from a previous approval of something similar.
- A filing being submitted. Identification, calculation, preparation, validation, packaging and deadline tracking can all be delegated and should be. Submission is a distinct legal act with the business’s name on it, and it should never be automatic or inferred from a general engagement.
- A message or commitment going out in the client’s name. Anything a counterparty will read as the business speaking — a chase, a revised term, a concession, an acknowledgement of liability — is the business speaking. Drafting is a service. Sending is authority.
- Silent correction of history. Errors are ordinary and correcting them is routine work. Doing it by typing over the original is not a correction, it is an erasure, and it should never be a system’s default behaviour.
- Ambiguity resolved in private. Where two treatments are both genuinely defensible, choosing between them is a decision, not a task. Decisions of that kind belong to the business, informed by whoever is qualified to frame them.
Silent correction and buried ambiguity: invisible by construction.
Five of the seven are obvious once stated, and most buyers will raise them unprompted. The last two are worth separating out, because they leave no trace in anything a client normally looks at. Neither appears in a monthly pack. Neither shows up in an accuracy figure or a service-level table. Both show up in a diligence room.
Silent correction makes the current books right and the past unknowable. An entry that was wrong is amended in place, and afterwards there is no way to establish what the accounts said when a decision was made against them, why a comparative figure moved, or whether a class of error has been recurring for a year. The alternative costs nothing at the time: record the correction as its own dated entry, with its reason, standing beside the original. At Par’s records are append-only for exactly this reason — the mechanics are set out under security and data protection.
Buried ambiguity is subtler and more common, because it usually involves nobody doing anything wrong. An item arrives that is genuinely arguable. Whoever picks it up forms a reasonable view and records it. No rule was broken, no policy ignored — a decision was simply taken several levels below where it belonged.
- Whether a cost is capital or an expense of the period.
- Which period a milestone or a stage of work actually belongs to.
- Whether a receipt is a deposit, a stage payment, or settlement in full.
- Whether a related-party charge reflects something real or is an allocation.
- Whether an item is material enough to disclose separately, or ordinary enough to absorb.
Each is defensible either way. Each changes the reported result. And the one thing that should never happen is that the choice gets made without the business knowing there was a choice.
A single question surfaces both: “What was decided about our books last month that we were not asked about?” A provider that treats it as a reasonable question is usually a provider with a short answer.
Where At Par fits — and the limits.
At Par draws the line exactly where this page draws it, and says so plainly rather than implying more oversight than exists. Routine internal records complete without a per-entry human sign-off — where the treatment has been established in advance, the facts and evidence are complete, and two independent checks agree. Anything failing those conditions is held as a named open item instead of being recorded. A qualified accountant (ACCA) is accountable for the treatments the desk applies, and records are append-only, so a correction stands beside the original rather than replacing it.
That model runs across bookkeeping and month-end close, payroll, receivables and invoice follow-up and management reporting, and it does not change with volume.
For how uncertainty is detected and surfaced in the first place, see what should happen when bookkeeping automation is unsure. For what the resulting records have to carry, see what evidence-backed bookkeeping means. For the wider control question — visibility, consent and getting your records back — see outsourcing without losing financial control.
Asked by owners writing the boundaries into an engagement.
What should never be automated in accounting? +
Two categories. Anything consequential and external — releasing money, submitting a filing, sending a message or making a commitment in the business’s name — because those acts have legal and commercial effect outside the company. And anything uncertain, of any size, because automating a decision means resolving it silently. Routine internal record-keeping sits outside both categories and can legitimately complete without a per-entry sign-off, provided the treatment is established, the evidence is complete and independent checks agree.
Does every accounting entry need to be approved by a human? +
No, and requiring it usually produces worse books rather than better ones. At any real volume, per-entry approval either becomes a bottleneck that is abandoned or a signature applied without reading, which transfers responsibility without transferring attention. What makes unsupervised completion safe is narrower and testable: the treatment was decided in advance by somebody qualified, the facts and evidence are complete, and separate checks agree. Anything failing those conditions should stop rather than complete.
Should a payment run ever be released automatically? +
No. Preparation can be complete to the last detail — beneficiaries, amounts, dates, references, supporting bills attached — and it should be, because that is where the work is. Release is a separate act. It should not run on a schedule, inherit authority from a previous approval of something similar, or be delegated for convenience during a busy period. At Par prepares payments and never moves, releases or executes client money; the client executes and settlement is recorded on evidence.
Can accounting software submit a tax return automatically? +
Some software can transmit to a tax authority once configured, which is a technical capability rather than a governance answer. Submission is a distinct legal act carrying the business’s name and its penalties, and it should be a deliberate decision each time rather than a setting switched on once. At Par identifies, calculates, prepares, validates, packages and tracks filings where they are in scope, and does not submit them on a client’s behalf.
Who should decide how an ambiguous transaction is treated? +
The business, informed by whoever is qualified to frame the options. Where two treatments are both genuinely defensible — capital or expense, this period or the next, deposit or settlement in full — the choice is a decision with a consequence for the reported result, not a task to be completed by whoever picked the item up. The failure here is rarely a wrong answer. It is a real answer chosen several levels below where the choice belonged.
What does it mean when a provider says a record was checked? +
Less than it sounds, until three follow-up questions are answered. Checked by what — a person, a rule, or a separate process. Checked against what — the source document, an outside statement, or simply the entry itself. And what happens on disagreement — does the item stop, or does somebody pick a version and move on. A provider that cannot answer those quickly is describing an intention rather than a control.
What should stop an automated bookkeeping process before it completes? +
Four conditions, any one of which should suspend it. No established treatment for this kind of item, because the first of its kind is not routine. A missing fact the treatment depends on. Supporting evidence not yet held against the entry. Or independent checks that do not agree. In each case the correct behaviour is the same: hold the item as a named exception with a reason and an owner, rather than recording the most likely version of it.
What is the real risk of automating too much in outsourced finance? +
Not that routine work gets done without supervision — that part is well understood and generally safe under the right conditions. The risk is that consequence and doubt get swept along with the routine, because they arrive through the same pipe and look similar at the moment of processing. An automated external act is discovered by a counterparty; an automated resolution of doubt is discovered at a year end. Both are found by somebody outside the business, later.
Tell us what should never happen without you. We’ll show you where the line already sits.
Bring your current arrangement — an engagement letter, a set of software permissions, or just how things happen today. We will map what completes on its own, what stops, and what only you can do.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Draw the line with usWe use your details only to prepare for and hold this call. No spam, ever.
Reviewed by an ACCA on the At Par team · Last updated 29 July 2026 · This page describes an appropriate boundary for any outsourced finance provider, not a description of one firm alone. See what we actually do.