Accounting is not an LLM problem anymore

Give the best model in the world your bank statement and a folder of invoices. It will understand every line.

It still can't close your books.

Accounting is not an LLM problem anymore. It's a harness and tooling problem. Today's models are already good enough. What's missing is the software around them: the harness the model works inside, and the tools it works with.

The model isn't the bottleneck

Ask a frontier model to explain accrual accounting, reconcile a tricky payment, or pick the right account for an odd invoice. It will do fine.

So why isn't accounting automated yet?

Because the hard part of accounting was never the reasoning. It's everything around it. Which invoice is this? Has it already been booked? Which customer paid, for which order, at which VAT rate? Is the bank feed from this morning or from last week? Did someone already fix that entry by hand?

A smarter model doesn't answer any of that. It just guesses more fluently.

Accounting punishes guessing

Most tasks tolerate a bit of creativity. Accounting doesn't.

The books have to balance. Every entry has to trace back to a document. The same input has to produce the same output, today and during the audit three years from now.

A probabilistic model writing directly into your ledger is the wrong shape for that job, however clever it gets. You don't want a ledger that is right 99% of the time. You want one that is right, and can prove it.

What accounting actually needs

What does it take to close your books without someone re-checking every line? Not a bigger model. It takes four things:

• A system of record. One place where invoices, payments, orders, customers and entries live, linked to each other. Not a pile of exports.
• Context. The entry doesn't stand alone. It belongs to a sale, a contract, a supplier. An employee's expense report is tied to a client, a trip, a project. The business around the number is what makes the number meaningful.
• Up-to-date data. Bank feeds, payments and documents flowing in continuously, so you decide on today's reality, not last month's spreadsheet.
• Deterministic flows. Matching, posting, VAT, closing: explicit rules that run the same way every time, can be tested, and can be audited.

Get those four right, and most of accounting stops being a judgment call. It becomes a pipeline.

The rules move too

Up-to-date data isn't only about your own transactions. The rules change as well.

January. A deduction cap changes. Your agent asks the web. It finds a 2023 blog post, a forum thread, and a page about Belgium. It picks one.

In Europe, this isn't an edge case. Twenty-seven member states share a common VAT framework, but each sets its own rates, its own deduction rules and its own reporting obligations, and updates them on its own calendar. E-invoicing mandates arrive country by country.

Web search is the wrong tool for this. Accounting needs a reliable, maintained source of rules: versioned, dated, and tied to the jurisdiction it applies to. When a rule changes, the source changes, and every flow that depends on it applies the new version from the right date.

Where the model fits

The model still does the work. It just doesn't work alone.

It reads every invoice and receipt, sorts expenses, answers the everyday questions and drafts the entries. It also helps build the tooling: writing a new matching rule, turning an accountant's practice into a flow, explaining why an account doesn't reconcile.

What changes is what it's allowed to decide alone. The harness makes sure of it: the model reads from the system of record, acts only through scoped tools, and nothing reaches the ledger until a rule or a person approves it.

Once a rule exists, it runs as code. Deterministic, versioned, reviewed. The model reads and reasons. The rules decide what gets booked.

That split is what makes automation trustworthy. When something goes wrong, you don't ask a model why it felt like booking that entry. You read the rule, see the input, and fix it.

Where the accountant fits

Every business needs an accounting tool. Not every question needs an accountant.

"Is this lunch deductible?" "Did the client pay?" "Which VAT rate applies here?" The rules and the system of record already hold those answers. They should be instant, and free.

The accountant's time goes where it counts: the big decisions, the risky ones, and the cases the rules don't cover yet. And review. Every correction becomes a rule, so the same question never needs a human twice. Less data entry. More judgment.

Where this goes

Today, a tax audit comes years after the fact. Someone samples your books and hopes to find what went wrong.

Now imagine the tax authority approves the harness itself: the rules, the flows, the system of record, and the limits on what the model can do. The check then happens the moment an invoice goes out or an expense hits the books. If the software says it's good, it's good. No surprises three years later.

This isn't science fiction. France already requires certified cash register software, and invoices now flow through state-approved platforms. Italy has routed every invoice through a central system since 2019. Spain sets requirements every invoicing software must meet. The next step is approving the whole chain.

For governments, it's a massive saving: every company checked, continuously, instead of a few sampled by hand. For businesses, the audit stops being a threat. It's already done.

The work ahead

None of this waits on the next model release. The ingredients are here. What's left is engineering: connecting the data, modeling the business, and turning accounting practice into flows that run on their own.

That's exactly what Enobase is built for. Each trade we model gets its own system of record and its own context: the business records that accounting entries refer back to. Accounting is the next layer on top of it.

The model is ready. The tooling isn't. That's the part we're building.

Want to see your accounting run on a real system of record? Book a call with us.