EU-Ready
Home market · Finland
Built in Finland. Designed to survive European complexity.
Vantnod's first use case grows out of a Finnish founder's day: cash, VAT, invoices, receipts, the rhythm of bookkeeping, and the moment when financial information has to support a decision instead of arriving after it.
But the product's foundation is not built to understand only one country, one company form, one tax rule, or one invoice channel. Vantnod separates company, market, tax profile, obligations, invoice channels, user roles, and the audit trail from each other.
EU-Ready does not mean every country is ready on day one. It means the product's structure does not fall apart at the first border.
Home market: Finland · FI, SE and EE in one structure · ViDA timeline 2025–2035 · Audit trail from day one
Core claim
01 / 11
A new country is a profile, not a new product.
Translating the UI does not make a finance tool European. Vantnod is built on a deeper model where company, market, tax profile, obligations, and invoice channels stay separable.
- [01]
Company
Tenant and legal entity are kept distinct.
- [02]
Market
FI, SE, and EE can live in the same backbone with different obligations.
- [03]
Tax
Tax profile can be bound to time, market, and company status.
- [04]
Obligation
Filings, checks, and deadlines form a timeline.
- [05]
Channel
Peppol, e-invoicing, PDF, email, and local channels are different routes.
- [06]
Audit
Source, Noa suggestion, human approval, and change history stay separable.
Why it matters
02 / 11
A finance tool usually breaks at the first border.
A single-country tool can work fine as long as the company's reality stays simple. One country. One legal entity. One VAT model. One invoice channel. One reporting schedule.
The trouble starts when the company sells into a new country, sets up a second entity, adds a new invoice channel, changes VAT status, switches to e-invoicing, or needs reporting that does not fit the original shape.
Then hard-coded assumptions start surfacing as exceptions. Exceptions turn into manual work. Manual work turns into uncertainty.
A new market must not break the product. It has to open a new obligation profile inside the same structure.
Architecture
03 / 11
EU-Ready is a data model, not a marketing line.
In Vantnod's base, market, tax, obligations, invoice channels, and audit are not the same thing. They are different layers. When a rule changes, the whole product should not become unpredictable. When a country changes, the product should not become a new product.
- [01]
Company layer
A company is not the same thing as a market. A single user, team, or group-like whole may need a view over multiple companies or operating countries without the information blending. The company layer holds the basics: legal entity, ownership, country, currency, company form, users, and responsibilities.
- Architecture layer
- Company
- Role
- permanent base structure
- Outcome
- the same cockpit can carry multiple market profiles
- [02]
Market profile
Finland, Sweden, and Estonia are not the same rule set in a different language. Each market has its own taxation, invoicing, and reporting reality. The market profile defines which obligations, channels, and checks can attach to a given operating environment.
- Architecture layer
- Market
- Role
- local context
- Outcome
- FI, SE, and EE can live in the same backbone with different obligations
- [03]
Tax profile
VAT, registrations, tax treatment, and local rules are not eternal. A company's situation can change, and so can the regulation. The tax profile has to be time-bound. An older transaction has to stay readable even when the current rule or the company's status has already changed.
- Architecture layer
- Tax profile
- Role
- time-bound rule layer
- Outcome
- history stays readable even when obligations change
- [04]
Obligation timeline
VAT, reporting, invoicing, registers, filings, and deadlines are not loose reminders. They attach to events, the company, the market, the tax profile, and a moment in time. An obligation is not just "do this sometime". It is a trackable event with a source, a basis, a due date, a state, and an optional approval.
- Architecture layer
- Obligation
- Role
- timeline of reporting and checks
- Outcome
- the user sees what to verify, when, and why
- [05]
Invoice channels
In Europe an invoice may be a PDF, an e-invoice, a Peppol message, an email attachment, an event through an operator, or a format dictated by local practice. An invoice channel is not just a file. It is a route, a standard, an event, and a possible source for reporting.
- Architecture layer
- Channel
- Role
- invoice route and technical form
- Outcome
- Peppol, local e-invoice channels, PDF, and email can be told apart
- [06]
Audit trail
When a company operates across markets, traceability matters more. The user has to see which source the data came from, who approved the change, what Noa suggested, and what was finally decided. Audit is not an attachment you hunt later. It has to be born during the work itself.
- Architecture layer
- Audit
- Role
- sources, roles, suggestions, approvals, and changes
- Outcome
- a financial decision stays verifiable across markets
Markets
04 / 11
FI, SE, and EE in the same backbone, with different obligations.
Finland is Vantnod's home market and the first practical reality. But the product foundation is not designed so that Finland is the only possible world.
- FI
Home base
Finnish business life, VAT, invoicing, accounting, receipts, bank transactions, and the founder's decision rhythm form the first use model.
- SE
Nordic continuation
The Swedish market brings its own language, currency, tax profiles, invoicing practice, and reporting structures. It has to be a new profile, not a new product.
- EE
Baltic-ready structure
Estonia is not just a lighter version of Finland. Local company, tax, and reporting models must be handlable as their own profile.
The goal is not to pretend all countries are the same. The goal is a cockpit where differences do not break the whole.
ViDA
05 / 11
Reporting is moving toward a more digital Europe.
The EU's VAT in the Digital Age package was adopted on 2025-03-11 and its obligations roll in gradually through January 2035. For Vantnod, ViDA is an architectural signal: invoice data, reporting, obligations, and the audit trail have to be built so they can change over time.
- [01]
Obligations separate from the company
The company basics should not contain all the tax logic. The obligation profile says what to report, when, and on what basis.
- [02]
Time-bound rule model
The tax profile has to be able to change without older history becoming ambiguous.
- [03]
Invoice data as the basis for reporting
There has to be a clear link between e-invoicing and reporting. The same information should not fragment across systems without a trail.
- [04]
Verifiable automation
Noa can help spot missing or unusual material, but critical filings need a human check.
Peppol & channels
06 / 11
Peppol is not a button. It is a channel.
Peppol is a network for exchanging electronic invoices, orders, and other business documents. In Vantnod's EU-Ready model, the invoice channel is modelled as part of the event: the same finance view can tell a PDF, an email, an e-invoice, a Peppol route, and a local operator channel apart.
- [01]
Peppol
A structured invoice channel for European and cross-border use.
- [02]
Local e-invoice channels
Each market may have its own operators, identifiers, and conventions.
- [03]
Email and PDF
A light channel may still be needed, but should not be confused with a structured e-invoice.
- [04]
Payment and banking partners
The state of payment and the state of an invoice have to be told apart, even when they show in the same view.
- [05]
Audit link
There must be a trail between channel, source document, approval, and accounting effect.
A human approves before dispatch
Obligations
07 / 11
An obligation is born from an event, a profile, and time.
Financial obligations do not live in a vacuum. They emerge from what happened, in which country, in which company form, under which tax profile, at which moment.
- 01
Event
An invoice, receipt, payment, purchase, sale, or other financial event happens.
- 02
Profile
The company's country, tax profile, VAT status, and reporting model determine which obligations may attach.
- 03
Timeline
Due dates, check-points, and filings surface for the user to track.
- 04
Check
Noa can raise missing material, uncertainty, or anomalies.
- 05
Approval
A human approves critical information before submission, export, or reporting.
One cockpit
08 / 11
Several markets must not mean several truths.
When a company grows beyond its first market, information tends to fragment. Vantnod's cockpit thinking pulls this into one use model. Not by forcing markets to look identical, by letting their differences be visible inside the same structure.
- [01]
Companies
Several companies or markets can belong to the same whole without the data blending.
- [02]
Users
Roles and rights can follow the company, the team, the market, or the task.
- [03]
Accountants
Verifiable material, sources, and exports must be visible without guesswork.
- [04]
Noa
AI can help across views, but suggestions stay separate from human decisions.
- [05]
Leadership
The key question is not just what happened, but what has to be decided next.
Honest scope
09 / 11
We do not promise a finished Europe. We are building a model that does not break in Europe.
EU-Ready does not mean Vantnod meets every local accounting, tax, invoicing, and reporting requirement of every EU country on day one. It means the base structure does not assume one country. This distinction matters.
- We do not call a roadmap finished.
- We do not call a market profile a complete rule engine.
- We do not claim every local exception is solved before it is solved.
- We do not build the product so that every new country requires a new product.
EU-Ready means company, market, tax profile, obligation, invoice channel, user role, and audit trail can be separated. It is the foundation on which markets can be built, one at a time.
What this means for the user
10 / 11
Less lock-in. Fewer exceptions. A better view of growth.
EU-Ready is not an abstract architecture choice for the user. It shows up in daily life when the company changes.
- 01When the company adds a new market, it should not have to start over.
- 02When VAT status changes, history should not fall apart.
- 03When the invoice channel changes, the event should not disappear.
- 04When the accountant needs material, the sources should be visible.
- 05When Noa suggests something, the user should see what the suggestion rests on.
- 06When a person approves a decision, the trail should be kept.
The company's finance cockpit can grow with the company without every change becoming a new system project.
Start from Finland
Keep expansion open.
Vantnod suits a company that wants a clearer finance cockpit now, but does not want to build everything on a single market. The first use model starts in Finland. The structure looks further.
Home market: Finland · SE and EE: profiles, not promises · jami@vantnod.com