The accountant's guide to Vantnod
How a bookkeeper or accounting firm works with a client who runs Vantnod. The Ledger Room gives the accountant a scoped view: requests, missing receipts, and batch entries without the client's whole workspace.
When a client runs Vantnod, the accountant works in the Ledger Room: document requests land in the client's work queue, gaps are visible as they appear, and repetitive postings go in as batches. VAT drafts are built from real entries, and everything exports as CSV and SIE4.
What changes when a client runs Vantnod
A typical month at an accounting firm starts with collection: receipts chased by email, statements waited on, entries posted in one pile at the end of the period. A client on Vantnod does the daily work in the product, so the material accumulates through the month.
Invoicing runs end to end: quote to invoice, numbering, Maventa e-invoices, payment links, reference numbers, and credit notes. Receipts are scanned with Noa, which reads the amount, the VAT, and the vendor. A person confirms every entry; the AI never posts alone.
The accountant pays nothing. The client subscribes, and tiers start at zero. The tier that matters for firm collaboration is Perusta at €119 per month, with team roles and a shared cockpit.
Inside the Ledger Room: requests, missing receipts, batch entries
The Ledger Room is the accountant's own portal into Vantnod. The view is scoped on purpose: you see what the work requires, not the client's whole workspace. The client opens access from their own account.
Three things carry the daily work:
- 01Document requests: when a receipt or an explanation is missing, you request it straight from the Ledger Room. The request lands in the client's work queue, not in an email thread.
- 02Missing receipts: gaps appear in their own queue as they arise, not at the end of the month.
- 03Batch journal entries: repetitive postings go in as one batch instead of one at a time.
The VAT rhythm and what is deliberately not automated yet
Vantnod knows how often the company files VAT and shows the current period and its deadline plainly. The VAT draft is built from real entries, so you can see where every figure comes from.
One thing said out loud: Vantnod does not yet file the return to the Finnish Tax Administration. The integration is built and tested, but filing opens later, and behind human approval when it does. We do not call a feature ready before it is.
The same line applies to bank connections: they are coming through a PSD2-licensed aggregator, Enable Banking, and until the connection is real we do not show a connected bank.
An audit trail that does not change after the fact
Every decision is stamped on the server side: who did what, and when. History cannot be written from a browser, so it cannot be tidied up afterwards either.
A sent invoice is an immutable version. Corrections go through credit notes, and the original stays as it was.
For a firm this is a practical matter. When you review entries or trace an old transaction, the trail is complete and identical for every party. A disagreement never comes down to memory.
How to start with a client
Nobody is locked into Vantnod. Everything exports as standard CSV and SIE4, formats any Finnish accounting firm or software can read. You can try the collaboration with one client without committing to anything.
The start is light. Ask the client for four things:
- 01Open accountant access to the Ledger Room.
- 02Turn on receipt scanning so the missing-receipts queue stays short.
- 03Keep invoicing in Vantnod so sales invoices, numbering, and reference numbers are created directly in the system.
- 04Go through the VAT period together at the start so the rhythm is clear to both sides.