Writing

An Accounting Agent That Cannot Book Until You Say So

5 min read

A quiet oak desk with a closed notebook, a cup and a stack of receipts in morning light
The receipt stays in the frame. The posting is a suggestion until someone owns it. Illustration.

Renbok is the accounting workspace we are building at Skjld Labs. It is in a free beta. The sentence I want associated with it is the same sentence I use for a clinical note: the model proposes, a person approves, and the original document is still attached when they do.

Bookkeeping is a good place to hold that line, because the failure mode is boring and expensive. A wrong account, a wrong VAT code, a supplier paid twice. None of that is fixed by a more fluent model. It is fixed by a workflow that refuses to post until someone who is allowed to post has looked at the source.

What the beta actually does

A company and its accountant work in the same set of books, with separate roles: owner, bookkeeper, accountant, read-only. Receipts and incoming invoices land in one inbox. If you allow it, the system reads the document and suggests an account and an amount. You see the suggestion next to the original and you correct it before anything is posted. Customers can be found through Brønnøysund. EHF files can be imported and validated. Bank files can be matched against vouchers, and you close a reconciliation only after you have looked at the mismatches. Reports link back to the entries that produced them.

There is also a path for preparing a VAT return and a small-company annual account. Preparing is not filing. Direct submission through ID-porten is not switched on. It waits on the client registration, the accesses and a tested run from login to receipt. The screen has to say whether a return is stored or actually sent. Those are different facts, and an accounting system that blurs them is not ready.

What is built and not live

I would rather list the gaps than have a beta customer discover them in a support thread.

  • Bank. The ZTL module is built: balances, transactions, reconciliation, and payment of supplier invoices. Direct connection and payment stay off until the agreement, the vendor access and an approved test are done. Bank files work in the beta now. Which live functions a bank will offer depends on the bank.
  • EHF over Peppol. Import and validation work. Sending and receiving do not. The access point, the certificates and a passed test come first. The company structure has to be finished before those agreements close.
  • Payroll and the tax return are not in this beta.
  • Mobile. The iPhone, iPad and Android apps are in progress. The iOS beta is in TestFlight. The browser is the product you can use today.
  • Security certification. The operating work uses ISO 27001 as the framework. The certification has not been done. I will not write “ISO 27001 certified” until it is.

Moving from Fiken, Tripletex or PowerOffice is a conversation, not a button. SAF-T and file import are the base. History, attachments and open items are agreed per system, and the old system stays available until the move has been reconciled.

The books are Norwegian first. UK reporting is supported, and one beta customer in the UK is already on it. That is a fact about the current beta, not a launch in a second market.

Why the agent gets a two-step write

Renbok exposes the same books to an agent. The MCP server is at https://renbok.no/mcp/accounting. The client has to speak Streamable HTTP and OAuth with PKCE S256, and it has to send the resource identifier. At full access the catalogue is 61 tools, four resources and three prompt templates. The REST API sits at https://renbok.no/api/integration/v1 for the same underlying operations.

The rule that matters is not the tool count. A write is previewed, then confirmed. The company chooses the legal entity and the scopes when the agent connects, and can revoke that connection. An agent that can draft an invoice is useful. An agent that can post it because the prompt said “go ahead” is how a book becomes unauditable.

This is the same shape as Svaragent, which drafts a customer email and waits, and the same shape as a SOAP note in MediVox, which a clinician signs. I do not want a special ethics policy per product. I want one mechanical fact: the side effect is a second call, made by a person, or by a system acting on a confirmation that person already gave.

Who it is for right now

A sole trader or a small company that wants the accountant in the same system, and is willing to be in a beta where the bank connection and the authority filing are visibly not done yet. An accounting firm that wants its own roles and a way to move between clients without a shared login. A developer who wants the books as tools, under OAuth, rather than a CSV export at midnight.

The beta is free. Prices after the beta are not set, and they will be said before anyone is asked to pay. The product is at renbok.no. The agent and API notes are at renbok.no/utviklere.

Portrait of Håkon Berntsen

Written by

Håkon Berntsen

CTO and co-founder of Skjld Labs AS. Builds production AI agents, Microsoft 365 systems and the courses around them, from Sandefjord.

About LinkedIn GitHub