Kvitta

I built a small team of agents with distinct roles, set to question each other until they surfaced buildable businesses with a clear path to market. An accounting assistant for Fortnox and Visma came back. Those are the two platforms Swedish bookkeeping runs on. Then I looked at where a bureau’s hours go. Much of a consultant’s day is coding supplier invoices. Most of that is machine work. So I built it.

The first version connected to Fortnox or Visma. One button handed new invoices to an agent trained on the 2026 BAS rules. A person reviewed before anything went back. I built it model-swappable and EU-data-residency-first. Accounting consultants tested it and the response was positive. I pitched it to Fortnox. A follow-up meeting came next, then clearance to sell it in their marketplace.

The testers needed more than coding. Invoices arrive in every format. The consultant wants the last word. Every client books in its own way. So I rebuilt Kvitta on Orca, my own system for building products. Orca gave it the frame, the design system and the charts. Kvitta became five modules on top: Inflöde, Översikt, Granska, Förtroende and Stängning. Invoices arrive on their own from Fortnox, Visma, e-invoices and the bureau’s inbox. Kvitta reads each client’s history first and follows the same pattern.

I read the rules first: the BAS chart and the VAT rules. They became the basis for the model and the answer key to measure against. Then I built the bureau. It has 40 clients and a year of invoices, with errors and duplicates planted on purpose. I pulled more invoices from Fortnox’s test environment. Then I ran the model, measured and fixed, until it read the patterns well enough. It booked courses as licence fees, for one. The right account is training. That got fixed.

Företagsuniversitetet sells courses. All 26 of its invoices landed on licence fees and the model was sure every time. So Kvitta approved them and no person saw them. A queue of unsure invoices never finds that error. Now every error that surfaces is grouped by supplier, whether a consultant corrected it or the monthly spot check found it. 26 errors become one row. Gör till regel shows what a rule would change before it is saved. The rule then goes before the model. All 26 land right.

The threshold is how sure the model must be before Kvitta approves on its own. The bureau sets it. Almost every invoice gets one of two scores, 0.95 or 0.98. Raise the threshold from 0.95 to 0.96 and half the invoices fall back to a person. So before the bureau changes it, Kvitta shows the cost: 1,126 more invoices to review, for 59 fewer errors. The bureau chooses with the numbers in front of it.

A flag is a warning on an invoice, like check the VAT or possible duplicate. The flags stopped 240 invoices the model was sure of, so a person checked them. Only 2 of the 240 were wrong. So I split the flags into three kinds in three colours: the model is unsure, a check stopped the invoice, or information only. Only the ones that matter stop an invoice. The consultant’s time goes where a person is needed.

The bureau head needs one answer in a few seconds: can I trust the model? Round 0 was a scatter of every invoice. Everything was there except the answer. Round 3 gave each confidence level its own row, with the share in a separate column. The eye had to jump to read one row. The chosen version puts a bar and a tick on the same row. The bar is how often the model was right. The tick is how sure it was. If the bar reaches the tick, the model can be trusted.

A pie of the model’s confidence is nearly whole. The few unsure invoices, where the errors live, become a sliver no one sees. Red on everything that deviates stops being seen. A bureau head with a few minutes needs six numbers, not fifty. An off-the-shelf chart library couldn’t be shaped all the way. So the charts are my own, built into Orca. Every one can show as a list.

What I build for one product goes into Orca, so the next one can use it. Kvitta added 17 chart components, modules for supplier invoices, connections to Fortnox and Visma, a colour palette for data and rules in the design system. The next product that needs a chart or an invoice doesn’t start from zero.

Creator, solo and end to end: the research that found the idea, both versions, the test bureau and its answer key, the measures and the design. Built on Orca, my own system for building products.