Run it twice. Same fingerprint.
Anyone can say their AI is deterministic. This is what it looks like: one quarter, checked eight hours apart, landing on an identical fingerprint while the clock and the wording both moved. The rest of this page is what you can put in an auditor’s hands.
Two runs of one quarter, eight hours apart.
The engine is deterministic and the narration is not, on purpose. Timo writes two or three sentences on top of the report, out of the report, and cannot add a finding, remove one, or change how serious it is. The findings and the fingerprint come from rules alone.
First run
03.08.2026 09:14Two possible duplicates and six records dated outside the period. Worth a look before you file.
4d2989a03fcd9d1d
FI 2026-01 · v2
Second run
03.08.2026 17:42The quarter holds two duplicate suspicions, plus six entries whose dates fall outside it.
4d2989a03fcd9d1d
FI 2026-01 · v2
The stamp matters as much as the hash. Rules change, so a run from last year and a run from today can differ without a single entry moving, and the stamp says which of the two moved. An old run keeps reporting the engine version it actually ran on.
Four things, and none of them is a screenshot.
An auditor does not want a dashboard. They want the decision behind one number, the check you ran before filing, the statement for the period, and the evidence itself, in a form they can open without you sitting next to them.
The record behind one decision
Open any transaction and read its whole life: what was captured, what was extracted, the VAT decision on each line and what produced it, and every human change since. It downloads as a certificate PDF in the reader’s language.
The check before you file
A deterministic pass over the period: stuck records, undated ones, the VAT rules run at period scale, printed totals that disagree with the lines, duplicates within three days, one vendor billed at two rates. Suspicion rather than verdict, and every finding links to the row.
The profit and loss
Income minus expenses on a net basis, broken down by category, for a month, a quarter, a year or dates you pick. It prints as a PDF in your language. Transactions in another currency stay out of the total and are counted where you can see them.
The period as one archive
One ZIP: the profit and loss as a PDF, every transaction as machine-readable CSV, and the receipt files themselves in a folder. If a single receipt cannot be fetched, the archive still builds and the README names it.
The activity log, in the reader’s own language.
Every action on the books, with the person, the timestamp and what actually changed, rather than a bare event name and an empty panel beside it.
Money and dates in the log are written in the same canonical format as everywhere else, and an action’s label is translated for whoever is reading it rather than for whoever performed it.
How far back it stays readable
Six years is not a round number we liked the look of. The Bookkeeping Act keeps books for six years, and that is the promise Business Max makes.
Three things a fingerprint does not prove.
It does not prove your books are right. It proves the same rules ran over the same records and reached the same answer. A wrong entry, entered twice, hashes beautifully.
The check is suspicion, not judgement. Two invoices from one vendor for the same amount three days apart is worth a look, and is also completely ordinary in some businesses. Every finding is a question addressed to you.
We are not your auditor and we do not file for you. Baslic produces the record, the check and the archive. The opinion, and the signature, belong to a person.
Timo never sees the raw ledger when it writes that summary. It gets the finding codes, their severity, a count and a few labels, and only plain text is read back from it.
What an accountant asks first.
Can the same receipt classify differently later?
Not from the same rules. If the rule set changes, the stamp changes with it, so a rule change is distinguishable from a data change. That is exactly why both are printed next to the fingerprint.
Does the auditor need a login?
No. The certificate is a PDF and the period is a ZIP, and both open anywhere. If you would rather they had a live view, an accountant you connect gets a read-only one.
What happens to records dated outside the period?
They are found. A period scan filters by date and would never see them, so late arrivals are loaded separately and every record-level rule runs over them too. They carry a late badge and are counted on their own line.
Is the pre-filing check written by the AI?
No. The engine is ordinary code and produces the findings and the fingerprint. The AI writes the two or three sentences above them, out of the engine’s output, and cannot change what is in the list.
Does the log cover documents too?
It does, without their extracted text: a twenty-thousand-character contract in every diff would bury the log it belongs to. Creating a share link and revoking one are written as their own two events.
Be ready before the question.
The record, the check, the statement and the archive. All of it already there when somebody asks.