Thred
All posts

Automated accounting controls for small companies, and which ones matter

A small finance team cannot separate every duty, but it can still have strong controls. Eight that matter, and how agents run them on every transaction.

David van Duijn6 min read

Working on this yourself? Talk to Mark, our co-founder. We’re here to solve it with you.

Book a demo
On this page

Accounting controls are the safeguards that stop errors and fraud from reaching your books or your bank account, such as a second approval on payments or a daily bank reconciliation. In a small company the controls that matter most are few, and software can now run most of them on every transaction instead of on a sample at month-end.

If you are the finance lead in a company of 20 to 150 people, you have probably heard that good controls need segregation of duties. Then you look at your team of two and wonder how that is supposed to work. This post is about controls that fit that reality.

What counts as an accounting control?

A control is any step that makes a wrong outcome less likely or catches it quickly. There are two kinds.

  • Preventive controls make the wrong outcome impossible, or at least harder. A payment cannot leave the bank without a second approver, and nobody can post to a closed period.
  • Detective controls let you notice quickly when something slipped through anyway. A bank reconciliation with a line nobody can explain, or a second look at unusual journal entries.

Small companies usually rely on detective controls done by hand, late and on a sample. Somebody reviews the supplier list once a year, or checks the bank at month-end. The gap between when something goes wrong and when someone notices is where the damage happens.

Why do controls matter in a small company?

Three reasons, in order of how often they bite:

  1. Payment fraud. Fake invoices and requests to change a supplier's bank account are common across Europe. The Dutch Fraudehelpdesk and UK Action Fraud both warn businesses about them regularly. One unchecked change of IBAN can cost more than a year of bookkeeping.
  2. Plain errors. A supplier invoice paid twice, a VAT code wrong for a quarter, a customer payment matched to the wrong invoice. None of it is fraud, all of it costs time and money to unwind.
  3. Growth. Investors, banks and, once you cross the size thresholds, your statutory auditor will want to see how you control your numbers. Controls you can show are worth more than controls you describe.

Which accounting controls matter most?

You do not need dozens. These eight cover most of the risk in a small company.

1. Two people on every payment

One person prepares a payment run, another approves and releases it in the bank. This is the four-eyes principle, and it is the single most valuable control you can have. Even with a team of two, it is possible.

2. Verification of supplier bank account changes

Any new or changed IBAN on a supplier is checked through a channel you already trust, such as a phone number from an earlier contract, before money goes to it. Payments to a changed account are held until someone confirms.

3. Duplicate invoice checks

Every incoming invoice is compared with earlier ones on supplier, invoice number, amount and date. Duplicates are the most common way companies overpay.

4. Approval limits by budget owner

Invoices are approved by the person responsible for the budget, with limits by amount. Above the limit, a second approver or the founder signs off.

5. Daily bank reconciliation

Every bank line is matched to an invoice, a payment or a booking, and anything unmatched is investigated within days. This is your best detective control, because nothing can leave the bank without showing up.

6. VAT code check on every entry

Each booking is checked against the expected VAT treatment for that supplier or customer, domestic rates, reverse charge or exempt. Errors are cheaper to fix in the week they happen than in the quarter you file.

7. Review of manual journal entries

Entries made by hand, outside the normal flow of invoices and bank lines, are reviewed by a second person. Manual entries are where both errors and deliberate misstatements tend to sit.

8. Period lock after close

Once a month is closed, nobody can post to it without reopening it, and every reopen is logged with a reason. Your reported numbers stay the numbers.

How do you handle segregation of duties with a small team?

Full segregation means the person who records a transaction is not the person who approves it, and neither is the person who handles the cash. With two people that is not fully possible. The answer is compensating controls:

  • Make sure payment release in the bank always requires a second person, even if that is the founder.
  • Give each person the minimum access they need in the accounting software and the bank, nothing more.
  • Log every change to master data such as supplier bank details, and have someone else review that log.
  • Have an outside party, often your accountant, review manual entries and the change log each quarter.

This is also where software changes the picture. When agents prepare the work and people approve it, you get a natural separation. The agent records and proposes, a person decides, and the log shows both.

How can software run accounting controls?

Most of the eight controls follow clear rules, which means software can run them on every transaction as it happens. That changes two things. Coverage goes from a sample to everything, and detection goes from months to minutes.

In practice it looks like this:

  • When a supplier invoice arrives, an agent checks it for duplicates, compares the VAT code with earlier invoices from that supplier and routes it to the right budget owner based on the approval limits you set.
  • When a supplier's bank details change, any payment to the new IBAN is held and flagged until a person confirms the change.
  • When a payment run is prepared, the agent checks every line against approved invoices and the supplier's verified bank account, and a person releases the run.
  • When bank lines arrive, they are matched and booked, and anything unmatched goes to an exception queue with a named owner.
  • When someone posts a manual entry, it is flagged for review by a second person.

At Thred, the agents work this way. They read by default, write only with your permission and ask above the limits you set. The Payer prepares payment runs and pays bills on time, never twice. The Bookkeeper keeps the record current on each bank sync. Every step is logged and traceable to the source document and the person who approved it.

A worked example of a payment run

Here is an illustrative payment run for a 35-person company on a Friday:

  • 14 supplier invoices are due, totalling €38,420.50
  • 13 of them go to suppliers with verified bank accounts and approved invoices, totalling €36,210.50
  • 1 invoice of €2,210.00 goes to a supplier whose IBAN was changed four days earlier, after an email asking for the change

The agent prepares a run of 13 payments for €36,210.50 and holds the 14th with a note explaining why. The finance lead calls the supplier on the number from the original contract. The supplier never asked for a change. The fake invoice is rejected, the bank details are reset, and the 13 legitimate payments are released by the founder as second approver.

Where should you start automating?

Begin with the controls that would have stopped the fake invoice in the example above, then work outwards:

  1. Supplier bank account changes and payment holds
  2. Duplicate invoice checks
  3. Daily bank reconciliation
  4. Approval routing by budget owner

Then add the VAT code checks, the manual entry review and the period lock. Some reviews cannot be reduced to a rule, such as whether an accrual estimate is reasonable. Software can gather the numbers for those, and a person signs them off.

What should your accountant or auditor see?

A control only counts if you can show it ran. For each control, you want a record of what was checked, when, by whom or by which agent, and what happened to exceptions. If your auditor or your accountant asks how you prevent duplicate payments, the answer should be a log, not a description. This is also why it pays to check how any finance software handles access, logging and data location, which we describe for Thred on our security page.

Where does Thred fit?

Thred runs these controls as part of the daily work, on top of your current accounting software through Thred Layer or in Thred's own ledger. You set the rules and limits, agents apply them on every transaction, and people approve what matters. If you lead finance in a growing company and want controls you can prove without adding headcount, start with Thred for businesses.

Book a demo to see a payment run with the checks switched on.

Frequently asked questions

What is the four-eyes principle in finance?

It means two people are involved in every important transaction, typically one who prepares a payment and another who approves and releases it. It prevents both errors and fraud by a single person.

How can a small company have segregation of duties?

Use compensating controls. Require a second approver for payment release, limit system access, log changes to supplier bank details and have someone else, often the external accountant, review manual entries and the change log.

How do you prevent invoice fraud with changed bank details?

Hold any payment to a new or changed supplier bank account until the change is confirmed through a channel you already trust, such as a phone number from an earlier contract. Never confirm through details in the email asking for the change.

What is the difference between preventive and detective controls?

Preventive controls make a wrong outcome impossible or harder, such as a required second approval before a payment leaves the bank. Detective controls help you notice quickly when something slipped through, such as a bank reconciliation that surfaces an unexplained payment.

Which accounting controls can be automated?

Rule-based controls such as duplicate checks, approval routing, payment holds on changed bank details, bank matching and VAT code checks. Reviews that cannot be reduced to a rule, like whether an estimate is reasonable, are signed off by a person.

Sources

  1. Fraudehelpdesk (Dutch fraud helpdesk)
  2. Small business guide (UK National Cyber Security Centre)
  3. Keeping business records (business.gov.nl)
  4. VAT for businesses (Belastingdienst)

Read next

Where Thred comes in

Security

Hosted in the EU, GDPR compliant, encrypted at rest and in transit. Thred reads by default and writes only with your permission.

Keep reading

Finance, handled.

Book a demo, or request a callback and we will call you.

Book a demo