Thred
All posts

How an agent learns your booking rules without you writing them

An accounting agent learns your booking rules from context, from your corrections and from memories it keeps per business. You correct it once, and it asks whether that should hold from now on.

Manoj Tutika5 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

An accounting agent learns your booking rules from three sources: the context it can read, such as your ledger history and the documents themselves, the corrections you make, and memories, which are short written rules it keeps for your business and applies to future work. You do not configure rules up front. You correct the agent once, and it asks whether that correction should hold from now on.

If you are the finance lead or controller of a growing company, this matters because your booking policies are the part of the job that never makes it into the software. They live in your head, in a spreadsheet of supplier rules and in the habits of whoever books the invoices. This post explains how an agent turns them into something it can apply, and how to check that it really learns.

Why aren't supplier rules enough?

A supplier rule maps one name to one account. That covers your landlord and your phone provider and not much else, because one supplier can sell you different things for different reasons, and nobody keeps a few hundred mappings current as the business changes.

Your real policies are not table rows anyway. They are sentences. "Parking and fuel for the delivery van go to vehicle costs, not travel." "Anything for the Utrecht shop goes on cost centre 20." "The freelance designer's hours are project costs for the client we rebill." An agent can work with sentences.

What can an agent learn from context alone?

Before you tell it anything, an agent can learn a lot from what is already in your books.

  • Your ledger history. How this supplier was booked the last dozen times, and whether any of those bookings were later corrected.
  • The document itself. The lines, the service period and what was actually bought.
  • The surrounding data. The bank line, the email the invoice came with, the contract or purchase order.
  • Your business. What you sell, your chart of accounts and your VAT position.

Most companies book consistently, so context covers a large part of the routine. History has to be read carefully, though. A booking that was later corrected is evidence against a pattern, not for it.

Why are corrections the strongest signal?

Every time you change a booking, you tell the system something true about your business. Most tools waste that. They save the new account and move on, and next month the same mistake comes back.

A learning agent does one extra thing. It asks whether your correction was a one-off or a rule, and if it is a rule, it writes it down in plain words for you to confirm.

A worked example

At the end of March, the agent books an invoice from Groothandel Van Dijk, a wholesaler you buy from regularly.

  • Net €300.00
  • BTW 21% €63.00
  • Total €363.00

It books the net amount to 4430 Cleaning supplies, because your previous three orders from this wholesaler went there. During your month-end review you change it to 7010 Packaging materials. This order was shipping boxes for your web shop, which is a cost of sales.

The agent asks a short question. Should orders from Groothandel Van Dijk go to Packaging materials from now on, or only this one?

You answer that it depends on what was ordered. Boxes and packaging are cost of sales, cleaning products are not. The agent saves a memory in exactly those words: "Groothandel Van Dijk. Shipping boxes and packaging go to 7010 Packaging materials. Cleaning products stay on 4430 Cleaning supplies."

In April an invoice arrives with both. The agent splits it.

  • Shipping boxes, net €240.00, BTW €50.40, to 7010 Packaging materials
  • Cleaning products, net €89.00, BTW €18.69, to 4430 Cleaning supplies
  • Invoice total €398.09, which is €329.00 net plus €69.09 BTW

The booking shows which memory it applied, so when you glance at it during the close you can see why it was split rather than wondering.

What makes a good memory?

A memory is the written result of what the agent has learned. It is a plain sentence, kept per business, that the agent applies as it works. Good memories share five properties.

  • Readable. A sentence you can read and edit, not a hidden setting or a statistical weight.
  • Scoped. It applies to one business and, where relevant, to one supplier, cost type, location or date range.
  • Sourced. It records where it came from, such as your correction on 31 March, an instruction in chat or a policy from your accountant.
  • Visible when used. Every booking that relies on a memory shows which one.
  • Revisable. You can change or remove it, and when two memories conflict, the agent tells you instead of picking one quietly.

A memory also never outranks the law. If you write "no VAT on anything from this supplier" and the invoice shows Dutch BTW, the agent should flag the conflict, not follow the memory. Where VAT treatment is in doubt, check with your accountant.

Where does the learning actually live?

This is the question to ask any vendor. In a good design the learning lives in your memories and your ledger history, as text you can open, not inside a model that nobody can inspect.

That has practical benefits for you. A new memory works on the very next document, with no retraining. You can see exactly what the agent believes about your business and delete what is wrong. And what it learns about your business stays with your business. At Thred, your data is used to do your work and never trains a model.

What should you expect in the first months?

In the first weeks you will get more questions than you would like. Answer them properly, because each answer becomes a memory. After the first close, the questions shift to things that are genuinely new, such as a first invoice from a supplier or a cost type you have not booked before.

From then on, review your memories the way you review your chart of accounts, a few times a year. Remove what no longer applies and tighten what is too broad. That review takes an hour, compared with the days a spreadsheet of supplier rules quietly costs you.

How can you tell whether a tool really learns?

Run a short test during your next close.

  1. Correct the same kind of booking twice. Does the tool ask you the second time, or does it already know?
  2. When you correct something, does it ask whether to make it a rule, and does it describe the rule in words you would use?
  3. Can you see the full list of what it has learned, and edit it?
  4. Does each booking show which memory it applied?
  5. If you remove a memory, does the next booking change accordingly?

If the answers are mostly no, the tool is storing your corrections, not learning from them.

On Thred, memories hold the rules and policies that are specific to your business or firm, and agents apply them as they work. Your rules, memories and history live with the ledger, so exceptions are explained and repeats are booked without asking. Thred Layer brings that to the accounting software you already use, and accounting firms can keep policies per client in the same way.

If your booking policies still live in your head and a spreadsheet of supplier rules, see how an agent learns them from your corrections.

Frequently asked questions

Why are supplier rules not enough for bookkeeping?

A supplier rule links one supplier name to one account. It works for suppliers that always sell the same thing, such as a landlord, but fails when one supplier sells several kinds of goods or the same purchase serves different purposes. Written policies applied per document handle those cases.

What is a memory for an accounting agent?

A memory is a plain-language rule stored for one business, such as how to split orders from a particular wholesaler. Good memories are scoped, record where they came from, show up on every booking that uses them and can be edited or removed.

Does the agent need retraining to learn a new rule?

Not when learning lives in written memories and ledger history. A new memory applies to the next document straight away, and you can see and change exactly what the agent has learned.

Can a booking memory override VAT rules?

It should not. If a memory conflicts with what an invoice shows, for example Dutch VAT charged where the memory says none, the agent should flag the conflict. Check doubtful VAT treatment with your accountant.

How do I test whether bookkeeping software learns from corrections?

Correct the same kind of booking twice and see whether it asks the second time, whether it offers to make the correction a rule, whether you can view and edit what it learned and whether bookings show which memory they applied.

Sources

  1. Keeping business records (Business.gov.nl)
  2. VAT rates and exemptions (Business.gov.nl)
  3. VAT invoicing rules (European Commission)

Read next

Where Thred comes in

Thred Layer

Finance agents running on top of your existing ledger. You set the rules, approve the work and handle the exceptions. No migration.

Keep reading

Finance, handled.

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

Book a demo