Automated accounting
Accounting that closes itself.
Bilantum takes bank statements, invoices and payroll straight from their sources, posts them in a PostgreSQL ledger by fixed rules, and renders the statements live. Nobody types a number twice.
BilantumNordwind Logistics GmbH · EUR
Overview — Q3 2026
Profit & loss
Revenue grew 6.2% on prior quarter, driven by two new contracts booked in August. Cash fell as the September VAT liability was settled early. One supplier invoice is duplicated across two entities and is held for review.
Principles
No data entry. One ledger. Every change logged.
Most accounting software is a form you fill in. Bilantum has no forms. Documents arrive from the systems that already hold them, rules decide where they are posted, and people are asked only about the exceptions.
Data arrives by API
Bank statements, sales and supplier invoices, payroll and FX rates are fetched from their source systems on a schedule. What the source says is what the ledger gets — character for character, with the fetch logged.
Posted by rules, in PostgreSQL
Depreciation, interest, FX revaluation, VAT and payroll are posted by database procedures, the same way every period. A posting checks for an existing booking first, and a locked period refuses everyone — users and programs alike.
Read live, never retyped
Balance sheet, P&L, cash flow and the VAT return are rendered from the ledger when you open them, on any device. There are no report files to version, email or reconcile against each other.
How it works
How a period closes
The close is a fixed sequence. Each step is a named procedure that can be run, undone and marked done — from a desk or from a phone.
Sync
Sources are fetched and compared with the ledger. New records are staged; nothing is posted yet.
Post
Recurring entries run in order: depreciation, interest, FX revaluation, payroll, VAT. Each one is skipped if it already exists.
Review
Open receivables, payables and unmatched items are listed with Claude's commentary. Questions are answered here, inside the close.
Approve
The approver signs off the review. Supplier invoices are released only by an explicit approval — there is one route and no side door.
Lock
The period is locked for every login. Statements and the VAT return are read live from the locked ledger from then on.
Architecture
Sources in. Statements out. One ledger between them.
Data sources
Posting procedures
Period lock
Change log
Outputs
Claude in the close
An analyst that has read every entry.
Claude reads the ledger, the bank statements and the invoices, writes the commentary for the period and flags what does not add up: a duplicated invoice, a receipt with no counterpart, a balance that moved for no booked reason.
It works under its own login. Everything it does is in the same change log as everything else, and a locked period is locked for it too.
Q3 closed with revenue of €1,284,300, up 6.2% on Q2. Two August contracts account for most of the increase. Operating expenses rose 1.8%, in line with the new headcount booked in July. Cash fell €21,600 because the September VAT liability was settled on the 28th rather than in October. Receivables over 60 days fell to €38,700 after the two oldest items were collected.
Control
Built the way an auditor would build it.
Change log on every entry
Who, from which application, and why — written by the database itself, not by the screen that asked for the change.
Period lock for everyone
A closed period cannot be changed by any user, any sync or any job. Reopening it is itself a logged, named action.
Read-only by default
Screens read with a login that can only read. Every change goes through a fixed list of named procedures. There is no free SQL and no form that writes to a table.
Your PostgreSQL
The ledger is a plain PostgreSQL database you control, backed up nightly. Groups run one database per entity set, in EUR, USD or any other currency.
Early access
Bilantum is in development.
It runs the books of a real group today and is being opened to finance teams in Cyprus and the EU in [QUARTER]. Leave an address and we will write once, when access opens.