ACCOUNTING SOFTWARE · FOR SMALL COMPANIES
01 / 07Accounting software for small companies.
One workspace can help turn receipts, invoices, and VAT work into an understandable queue. Vantnod is pre-launch: this page shows development work and local examples, not a promise of open production use.
Every figure and name is illustrative. The example contains no customer or production data.- Source
- Example image
- Suggestion
- Office expense · draft
- Amount
- €124.00 · example
- STAGE
- Pre-launch
- ACCESS
- By request
- BANKS
- Not connected
LOCAL RECEIPT FLOW
See how a source stays separate from a suggestion and decision.
This working example changes only local page state. It does not upload an image, create an entry, or change company data.
Example receipt
The source remains its own layer.
Image · local exampleWORKFLOW REGISTER
One table shows both what is built and what is missing.
Development evidence is not public availability. Every row therefore carries a visible state and boundary.
- 01Receipt review surfaceBUILT IN DEVELOPMENTDevelopment evidence · not public availability
Source, recognized fields, and the handling suggestion remain separate reviewable layers.
- 02Customer and product register structureBUILT IN DEVELOPMENTDevelopment evidence · not public availability
Dedicated development surfaces exist for invoicing base data.
- 03Invoice-draft structureBUILT IN DEVELOPMENTDevelopment evidence · not public availability
Draft, lines, and document state can be shown without claiming public sending.
- 04VAT-breakdown draftBUILT IN DEVELOPMENTDevelopment evidence · not public availability
Period, source rows, and incomplete classifications can be shown as a reviewable draft.
- 05Decision-trail modelBUILT IN DEVELOPMENTDevelopment evidence · not public availability
The product model separates source, Aino suggestion, and human decision. Production implementation must be verified before release.
- 06Bank connectionsNOT PUBLICLY AVAILABLERequires separate verification
No bank is shown as connected before a verified connection, permission, and production path exist.
- 07E-invoicing and payment connectionsNOT PUBLICLY AVAILABLERequires separate verification
Providers and sending rails are not shown as activated before separate verification.
- 08Tax-return filingNOT PUBLICLY AVAILABLERequires separate verification
This page files nothing and does not claim a production tax-authority connection.
ILLUSTRATIVE WORKSPACE
Finance appears as a queue, not a mystery.
The large view shows the intended direction: what needs review, what remains a draft, and which source a row belongs to.
- To review
- 3 example rows
- Sent
- 0
- Banks
- No connection
- 01Receipt · exampleSource visibleREVIEW
- 02Invoice draft · exampleNot sentDRAFT
- 03VAT breakdown · exampleLocal calculationINCOMPLETE
BANK CONNECTION BOUNDARY
NOT AVAILABLENo fake bank.
Vantnod will not show a connected bank until the connection, permission, and production path are actually verified.
WHAT THIS MEANS
A bank row starts with a source, not an animation.
The platform migration is ongoing, but it does not itself open a bank connection. Bank-data availability and responsibilities are verified separately before release.
- No synthetic bank transactions.
- No provider-approval claim.
- No automatic matching before a real source exists.
THREE LAYERS TO VERIFY
A good interface also shows responsibility.
These are product-design principles. At release, every layer needs a working implementation and evidence.
- 01VISIBLE IN PROTOTYPE
Source
A document, transaction, or other verifiable basis stays beside the claim.
- 02LOCAL INTERACTION
Human decision
Aino suggests. A consequential decision belongs to a human.
- 03VERIFY BEFORE RELEASE
Server-side trail
Actor, time, and company context must be confirmed at the server boundary.
ACCESS BY REQUEST
Tell us which finance task slows down your day.
A request does not create a workspace, subscription, trial, or charge. It tells us where you would want Vantnod first.
Request access