Friday, end of the month. Your inbox has a dozen cost invoices waiting, there’s a receipt from the garage in your wallet, and the business account statement still needs a look. A sole proprietor puts it off, because bookkeeping can wait until it has to be done. In Qkwit, that moment looks different: documents go into the system, AI reads them, and how much tax and social security you owe gets calculated by code — not a language model.
What a bookkeeping month looks like today, without AI
For most sole proprietors, the monthly cycle looks fairly similar: gathering cost and sales invoices scattered across email, a banking app, and paper receipts, manually entering them into a spreadsheet or accounting software, sending everything to an accountant, waiting for the income tax advance and social security contributions to be calculated, and finally making corrections if something was misclassified or forgotten.
None of this work is complicated on its own. It’s just spread out over time and requires keeping track of a lot of small things at once — easy to forget exactly when something more pressing than sorting receipts comes up, which only means more corrections at the end of the month.
What changes with AI: who reads, and who calculates
In Qkwit, we split two roles that get tangled together in the traditional process. The first role is reading and understanding documents — that’s what AI does: recognizing whether something is a cost invoice, a sales invoice, or a receipt, and extracting amounts, dates, tax rates, and expense categories. The second role is calculating what’s owed — the income tax advance, social security contributions, VAT due. That’s handled by a separate, deterministic engine built on explicit tax rules, not a language model.
AI never “guesses” a tax amount — it supplies input data, and the engine calculates it using the same rules a person would apply with a calculator and the regulations in front of them. For the same inputs, the engine always returns the same result, while a model asked the same question twice can phrase its answer slightly differently. We go into more detail on the extraction and validation mechanism behind document reading in Qkwit in document workflow automation with AI.
We want to be precise here, because it’s easy to over-read this claim: “a bookkeeping month in one day” is a design goal we build Qkwit around, not a measured, averaged result across every user. The actual time it takes depends on how many documents need processing in a given month and how unusual they are.
What documents AI actually reads in Qkwit
In practice, this means the documents you’d have to deal with every month regardless: cost invoices from suppliers, sales invoices issued to clients, fiscal receipts, payment confirmations, and in some cases correction notes to previously issued documents. AI recognizes the document type, extracts the data needed for bookkeeping, and assigns it to the right expense or revenue category.
The more standard a document — a typical VAT invoice in a typical format — the lower the chance it needs manual review instead of being processed automatically. Unusual documents, handwritten notes, or poor-quality scans increase the odds of escalation to a person. In practice, the more consistently you keep your paperwork through the month, the fewer documents need a manual look at the end of it.
Qkwit today: sole proprietors are one of four areas
This article describes the mechanism specifically for sole proprietors, because that’s where Qkwit started. Today the product covers four areas: sole proprietors, limited-liability companies, payroll and HR, and accounting firms running several client companies from one panel. Each area has its own specifics — a company files CIT and JPK rather than a flat-rate or scale tax, and an accounting firm manages several businesses at once from a single place.
The split of roles is the same across all four areas: AI reads and classifies documents, and a deterministic engine handles the numbers. If you run a company or an accounting firm, the mechanism in this article applies to you in an equivalent form, adapted to your type of business — the split between reading and calculating stays the same, only the documents and regulations in play change.
Why AI shouldn’t calculate your taxes on its own
This question comes up often in conversations with clients interested in automating bookkeeping, so it’s worth naming directly: language models, even the best ones available today, aren’t a tool for calculating tax liabilities. They’re very good at reading, classifying, and recognizing patterns in documents — exactly what they do in Qkwit. The actual calculation is left to code that implements explicit, verifiable tax rules. That’s the same principle we apply across every one of our products where AI runs in daily use, not just in bookkeeping.
A deterministic engine has another advantage that matters if you’re ever audited: for the same inputs, it always reproduces exactly the same result, and you can trace which rules produced it. A language model, however good, doesn’t give you that guarantee of repeatability — and in bookkeeping, being able to reproduce and explain a result matters just as much as the number itself being correct.
That’s also why a sole proprietor doesn’t need to understand exactly how their tax is calculated to trust the result — it just needs to be checkable and explainable at any moment.
In short
Compressing the bookkeeping month in Qkwit comes down to a split of roles: AI reads documents, and calculating tax and social security stays with deterministic code. We apply the same principle whether you run a sole proprietorship, a company, or an accounting firm. If you want to see what that looks like for your type of business, visit the Qkwit page.
Frequently asked questions
Does Qkwit really compress the bookkeeping month to one day?
That’s a design goal we’re building toward in the product’s architecture, not a measured, guaranteed result for every user. The actual time depends on how many documents there are in a given month and what kind they are.
Does AI in Qkwit decide on its own how much tax is owed?
No. AI reads and classifies documents, but the actual tax and social security liability is calculated by a separate, deterministic engine built on explicit rules — not the language model.
Does Qkwit support companies or accounting firms?
Yes. Qkwit covers four areas today: sole proprietors, companies, payroll and HR, and accounting firms. This article focuses on the mechanism for sole proprietors, but the “AI reads, code calculates” principle works the same way in the other areas.
What happens if AI misclassifies a document?
Documents that can’t be classified unambiguously, or that raise a question, go to manual review instead of being posted automatically — the same pattern as any other implementation where AI reads documents, not just sole-proprietor bookkeeping.
Is the financial data AI processes kept secure?
The layer that reads documents and the layer that calculates liabilities are kept separate, and access to data is limited to what a given task actually requires. That’s the same standard we apply across every one of our products where AI runs in daily use.