Thred
All posts

When finance people build their own tools, a new role appears in small finance teams

A finance engineer is a finance person who builds: checks, rules, small tools and agent setups. Here is what the role looks like in a small team, and how to start safely.

Mark Holleman6 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

A finance engineer is a finance professional who builds the tools, checks and automations their team runs on, instead of waiting for software vendors or IT to build them. In a small company this is rarely a new hire. It is usually the controller, the finance lead or the founder who starts writing rules and small programs around the books.

That shift matters most in companies of 10 to 200 people. You do not have an internal developer for finance, your accountant works in their own tools, and your ledger does roughly what it did five years ago. Meanwhile the work keeps growing. The finance engineer is the person who stops absorbing that growth by hand.

What does a finance engineer actually do?

The role sits between bookkeeping and software. A finance engineer understands why a journal is booked a certain way and can also turn that understanding into something a machine repeats.

In practice the work falls into four groups.

  • Checks. Small routines that look at the books and flag what is wrong. A bank line older than five days without a match. A supplier invoice booked twice. A VAT code that does not fit the supplier's country.
  • Rules. Written-down booking and approval logic. "Software subscriptions under €500 go to account 4510 with 21% BTW and need no approval." The rule exists so that people, scripts and agents all apply it the same way.
  • Glue. Small pieces that move data between systems that do not talk to each other, such as payment platform reports into the ledger, or hours from a planning tool into a project margin view.
  • Reports. Views the standard reporting does not give you, built on live data instead of a monthly export.

None of this is new. Finance teams have always had someone who was good with macros. What is new is how far that person can now get without being a developer.

Why is the role appearing now?

Three things changed at roughly the same time.

First, assistants that write and explain code are good enough for the kind of small, well-defined program finance needs. A controller can describe a check in plain language, get working code, and ask what each line does.

Second, the systems around the books opened up. Most ledgers used by Dutch and UK SMEs, such as Exact Online, Xero and Moneybird, have documented APIs. Banks offer feeds, and payment providers like Stripe, Mollie and Adyen publish detailed payout reports. Open standards such as the Model Context Protocol let an assistant call those systems as tools.

Third, agents arrived. Instead of writing a program for every step, you can now configure software that does a whole task, such as matching bank lines or chasing an overdue invoice, within rules you set. The finance engineer's job then becomes less about code and more about writing good rules, choosing the limits and reviewing what the agent did.

What should a finance engineer build, and what should they buy?

This is the most important judgement in the role, and the place where enthusiastic builders most often go wrong.

A useful way to decide is to think in three layers.

  1. The core. The ledger, bank feeds, posting, VAT records, the audit trail. This must be correct, complete and kept for seven years in the Netherlands (six in the UK for companies). Do not build it. Buy it, and choose software that keeps it current.
  2. The rules. Your chart of accounts, your booking logic, approval limits, payment terms, the way you treat a holding's management fee. This is specific to you, so you configure it, ideally in a place where both people and software can read it.
  3. The edges. Checks, one-off analyses, a custom report for the board, a bridge to an unusual industry system. This is where building pays off, because nobody else will build it for you.

The mistake is building in the core. A home-made script that posts journals straight into the ledger feels efficient until the person who wrote it leaves, or until a supplier changes the layout of its invoices and the script quietly books the wrong amounts for two months.

What does this look like on a normal Monday?

Take a controller at a 40-person wholesale business on Exact Online.

Every month she spends about three hours checking that each supplier invoice above €1,000 has an approved purchase order. She writes the rule down once, then has a small check run every night that compares invoices to orders and lists the exceptions. Her monthly work drops from three hours to about 20 minutes of reviewing the exception list.

That is 2 hours and 40 minutes saved a month, or 32 hours a year, from one check. The real gain is larger, because the check runs daily instead of at month-end, so problems surface while the supplier still remembers the order.

Her next step is not a bigger script. It is handing the routine part to an agent that follows the same rule, asks her about the exceptions and leaves a record of every decision. Her role moves from doing the check to owning it.

What are the risks of home-made finance tools?

Building makes finance faster, but it also creates new ways to be wrong. Watch for these.

  • Key-person risk. If only one person understands how the cash view is put together, you have replaced a spreadsheet nobody understands with a script nobody understands.
  • Silent failure. A check that stops running looks exactly like a check that found nothing. Every routine needs a visible "ran at, found X" result.
  • Write access. Anything that changes the ledger needs limits, review and an audit trail. Reading the books is low risk. Changing them is not.
  • Data protection. Customer and payroll data fall under the GDPR. Know where your scripts and assistants send data, and use business plans with a data processing agreement.
  • Audit and retention. Your accountant and, later, the Belastingdienst or HMRC need to follow how a number was produced. If a tool booked it, the tool's logic and inputs must be traceable.

None of these is a reason not to build. They are reasons to build the edges, keep the core in proper software and write things down.

How do you become a finance engineer?

You do not need a computer science degree. You need curiosity, a clear sense of how your books should look, and a habit of writing things down.

A practical path for a controller or finance lead:

  1. Pick one recurring annoyance. Something you do every week or month that follows clear logic. Unmatched bank lines, missing receipts, a recurring intercompany charge.
  2. Write the rule in plain language first. If you cannot explain it in five sentences, it is not ready to automate.
  3. Start read-only. Build checks that report, not tools that book. Let them run for a month and compare their output with what you would have done.
  4. Keep it somewhere shared. Rules in a document or system the team can read, code in a repository with history, not on one laptop.
  5. Add write steps last, with limits. When something should change the books, give it an amount limit and a review step, and log what it did.
  6. Review monthly. Which checks fired, which were noise, which rules need changing.

Founders can use the same path. The difference is that a founder should spend less time on the edges and more on making sure the core is in good hands, because that is where the risk sits.

Where does Thred fit?

We built Thred for exactly this shift. The recurring work runs as agents that you configure, the rules live in Memories that both your team and the agents read, and every entry is traceable back to its source document. Agents read by default and only write within the limits you approve. You can read more about how that works for growing companies on our businesses page.

For finance engineers who want to build at the edges, Thred also exposes an API and an MCP server, so a check or report you build in Claude or your own tools works on the same live books. If you want to keep your current ledger, Thred Layer runs on top of it. If you want books that are updated as transactions happen, there is Thred Ledger. And because agents work inside your financial data, our security page explains where that data lives and who can change what.

The finance engineer is not a trend for large companies only. In a small team, it is often the difference between hiring a second bookkeeper and not needing one.

If you want to see what that looks like on your own books, book a demo.

Frequently asked questions

Do you need to know how to code to be a finance engineer?

Not much. Assistants can write and explain small programs from a plain-language description. What matters more is a precise understanding of how the books should look and the discipline to write rules down and review what runs.

What is the difference between a finance engineer and a financial systems analyst?

A systems analyst usually configures and maintains the large finance applications in a bigger company. A finance engineer in a small team builds around those systems, writing checks, rules and small tools close to the daily work.

What should a small finance team automate first?

Start with a recurring task that follows clear logic and only needs reading the books, such as unmatched bank lines, missing receipts or invoices without an approved order. Read-only checks carry little risk and show quickly whether the logic is right.

Is it safe to let scripts write into the ledger?

Only with limits. Anything that changes the books needs an amount limit, a review step and a log of what it did, so your accountant and the tax authorities can trace each entry. Keep posting logic in proper finance software rather than home-made scripts where you can.

How long do Dutch and UK companies have to keep their records?

Dutch businesses generally keep records for at least seven years, and UK limited companies for at least six years from the end of the financial year. Automated tools must keep their outputs traceable for that period too. Check the details for your situation with your accountant.

Sources

  1. Keeping business records (business.gov.nl)
  2. Running a limited company: company and accounting records (GOV.UK)
  3. Introducing the Model Context Protocol (Anthropic)
  4. Data protection in the EU (European Commission)

Read next

Where Thred comes in

Finance Leaders

For finance leaders who want more capacity without more headcount.

Keep reading

Finance, handled.

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

Book a demo