Likvid matches every movement on your bank account to the document behind it — invoice, tax record, receipt. When it can't, you get one question, once. Your answer holds for every similar item after it.
Bank, the tax authority's own invoice record, your invoicing tool. Nothing gets replaced and there is no implementation project. Sources →
Every movement is tied to the document behind it, and the chain is followed to the end — reversals, part-payments, card settlement. The unit →
Asked once, to a person who knows the business — and the answer is kept with its scope. How it learns →
Nothing is left to assemble, because nothing was left unexplained. Continuous close →
A bank feed is for sale and the model is the same one everyone has. What isn't for sale is how your company's money behaves — and that is what your corrections teach it. Behind every explained movement sits one of four kinds of knowledge, and the product always shows you which.
An invoice number in the memo, an amount that matches. Free — and free for everyone else too.
Someone who understands the business answered one question. Permanent. This is the asset.
A new item settles itself from an answer you gave weeks ago, to a different item. This is the compound interest.
Named on the item as the Likvid AI's candidate — separately from what's verified, with the evidence that would settle it. Worth exactly as much as the next human nod, and marked as such until it gets one.
The picture written overnight, one queue with one question each, and what's prepared and waiting for your nod.
A day in it →Your answer is kept with its scope and applied to the partner's next items — the queue gets shorter every month.
How it learns →Invoice, payment, fee, reversal and certificate hang off one happening — which is why what's missing can be counted.
The economic event →Trial balance, journal and ageing, each row pointing back at its document. Close the month, and it stays closed.
The books →Bank over PSD2, the tax authority's records — invoices, tax account, taxpayer register, VAT-return draft — your invoicing tool, card processors, your mailbox — with the limits named.
Sources →The explaining moves to the day the money moves, so there is nothing left to assemble three weeks later.
Continuous close →Nobody buys this because of their headcount. They buy it after the first full-time finance hire, after a second tax number appears, when an investor asks what's open — or when the spreadsheet quietly stops being reliable.
In a finance product this is the product. Every line below is enforced in code, not promised in a policy document.
Likvid is also a server your AI tools can sign into — Claude, Claude Code, Cursor. They read your live numbers with the source on every figure, and they can ask for a proposal: a project closure, an advance invoice, a proforma, a reversal. What they cannot do is approve it. A proposal lands in Likvid as a card and waits for a person, and no tool ever moves money.
Every Hungarian business invoice is reported to the tax authority as it is issued. We don't have to guess what was invoiced — we read it.
From then the return is prepared against the authority's own draft — so someone has to reconcile that draft with the company's books. Likvid already reads the authority's picture of the month and lists the differences against the books.
Romania's e-Factura, Poland's KSeF, then Slovakia — the region's invoice traffic becomes machine-readable on a published schedule. Hungary got there first.
We work with a small number of companies through the beta, hands-on. Connect your sources, and the first brief arrives the next morning.