Cloud Accounting for EEA Startups With Multiple Entities

Most EEA startups do not stay a single legal entity for long. A Baltic parent picks up an Estonian OÜ for cross-border invoicing, a French SAS gets spun up for hiring, a Dutch BV holds the IP. By the time the founders talk to an accountant seriously, they are running two or three companies, in two or three currencies, with VAT obligations in more than one jurisdiction. The question is not whether the accounting software supports "multiple companies" in a generic sense. The question is what "multi-company" actually means inside each tool, and how much of the operational accounting work it can carry without armies of manual reconciliation.

This piece walks through the cloud accounting tools most relevant to EEA-based startups with multi-entity needs, what each is genuinely good at, and where an API-first option like Nordlet belongs in the stack.

What "multi-company support" actually means

Vendors use the phrase loosely. In practice, there are three distinct models, and they are not interchangeable:

1. Multiple companies under one login. Each entity is a separate ledger; the software just lets one user switch between them. Xero and QuickBooks Online sit here.
2. True multi-entity ledger with intercompany and consolidation. One system holds all entities, handles intercompany transactions, and produces consolidated statements. Sage Intacct, NetSuite, Business Central, AccountsIQ, and Xledger sit here.
3. Embedded, API-first accounting inside your own product. The books are not a separate application at all. They live behind an API that your platform calls when things happen. This is where Nordlet operates.

Which model a startup needs depends less on headcount and more on structure. A three-person team running a marketplace with sellers in five EEA countries has more accounting complexity than a fifty-person single-entity SaaS.

The tools worth comparing

Xero

Xero is the default recommendation for small EEA startups that want good UX and a large app marketplace. Bank feeds work, invoicing is clean, multi-currency is solid, and accountants in most EU countries know it.

The catch on multi-company: each entity is a separate Xero organization with its own subscription. Consolidation across entities is not native; teams either export to spreadsheets or bolt on a consolidation tool. For a group of three EEA companies, that is three subscriptions and manual group reporting. Roundups like the Web2Ireland guide to accounting software for EU tech companies put Xero on the list precisely for early-stage teams, not for groups that have outgrown single-entity thinking.

Best for: Pre-seed to Series A startups with one or two entities and a preference for a mature app ecosystem.

QuickBooks Online

Similar shape to Xero, larger global footprint, and often cheaper at the entry tier. Multi-company follows the same "one company per subscription" model. EU VAT handling exists but generally requires more configuration than tools built primarily for European tax regimes. Strong choice if the founding team's accountant already lives in QBO, weaker if the group has cross-border VAT obligations from day one. It shows up consistently in 2026 cloud accounting roundups as a small-business default.

Pennylane

Pennylane is worth knowing about for EEA teams with French operations. It combines bookkeeping, invoicing, and a working relationship with accountants inside one product, with strong local tax handling. Multi-company support exists but the product is opinionated around French GAAP and French accountants. Outside France, it is a harder sell.

Sage Intacct

Intacct is the serious multi-entity option for scaleups. Native intercompany, multi-currency consolidations, and the kind of audit trail a Big Four auditor will not push back on. It is also expensive, sold through partners, and not something a five-person seed-stage team should buy. AccountsIQ's comparison of mid-market cloud accounting places Intacct clearly in scaleup territory alongside NetSuite.

Best for: Series B and beyond, or earlier if the group already has four or more entities and a real finance team.

Oracle NetSuite

The full ERP path. Everything Intacct does plus inventory, projects, and a broader operational surface. NetSuite is a serious commitment: implementation projects are measured in months, not weeks. For a startup with a clear ERP need (physical goods, complex revenue recognition, global subsidiaries), it can be the right first hire for the finance stack. For most EEA seed-stage companies, it is early.

Microsoft Dynamics 365 Business Central

Business Central sits between Intacct and NetSuite in ambition and is a common choice for EEA companies already in the Microsoft ecosystem. Strong multi-company support, decent EU localization through partners, and integrates naturally with the rest of Microsoft's business stack. Implementation is partner-led and the quality varies significantly by partner.

AccountsIQ

UK-headquartered, mid-market, cloud-native, and explicit about multi-entity consolidation as a core value. Less known outside the UK and Ireland but genuinely capable for EEA groups with five to fifty entities that find Xero too thin and Intacct too heavy.

Xledger

Nordic-built, cloud-first, multi-entity by design. Good fit for Scandinavian-headquartered groups. Pricing and implementation sit closer to Intacct than to Xero.

Odoo

Odoo Accounting is worth mentioning because it comes up in every EU list. Multi-company and multi-currency work, and the open-source ecosystem is real. The tradeoff is that Odoo is a modular ERP, not a focused accounting tool. Someone on the team ends up owning the Odoo configuration, and that person's time is not free.

Zoho Books

Cheapest credible option in the multi-org space. Fine for a small group with simple needs. EU VAT handling is comparatively basic. Not the tool a growing marketplace should build on, but a defensible choice for a bootstrapped two-entity setup.

Where Nordlet fits

The tools above assume the accounting system is a separate application that humans log into. That assumption breaks for a specific class of EEA startup: marketplaces, SaaS platforms, and e-commerce products where accounting events are generated by the product itself.

If a marketplace processes 4,000 seller payouts a month across seven EEA countries, the question is not "which UI does the finance team prefer." The question is how those payout events, VAT calculations, and reconciliations enter the books without a human copy-pasting anything.

Nordlet is built for that shape of problem. The core positioning:

• Real double-entry books exposed as an API. Not a reporting layer over a spreadsheet, and not a CSV export from a third-party checkout. An immutable ledger with proper debits and credits, callable from the platform's own code.
• Per-country EU VAT built in. Automated VAT calculation, VIES validation for cross-border B2B, i.SAF register generation where required, plus OSS/IOSS returns and EU small-business scheme thresholds tracked straight from the books. This matters concretely for EEA startups selling into multiple member states, where the tax treatment depends on the buyer's country, VAT status, and the type of supply.
• Multi-company under one account. Role-based access across owner, admin, accountant, manager, developer, and viewer. Group consolidation is included: several companies roll up into one consolidated balance sheet and P&L. Multi-language interface (currently Lithuanian and English) per user and company.
• Developer tools that assume production use. Typed SDKs, webhooks for events like sale_invoice.paid, and idempotency keys so retries do not create duplicate entries. These are not marketing features; they are what separates an API a team will actually build on from one they will fight with.
• Audit-ready by construction. Period locking, immutable ledger, and a full audit trail. The kind of thing that stops being optional the first time a serious investor runs diligence.

Nordlet is in early access in 2026 and onboarding design partners, which is worth naming plainly: the product is younger than anything else on this list. Pricing, though, is published and metered — plans start at €10 per month with 3,000 requests included, and every plan includes every module and the full API — and sandbox companies are unlimited, with self-serve signup and no card details. Design partners get a system built for the exact problem most EEA marketplace founders describe: embedded accounting, real compliance, no dependency on someone else's checkout.

Comparison at a glance

Tool	Multi-company model	EEA VAT depth	Developer surface	Best fit
Nordlet	Multi-company under one account, role-based access	Per-country VAT, VIES, i.SAF, OSS/IOSS	API-first, typed SDKs, webhooks, idempotency keys	Marketplaces and platforms embedding accounting in their product
Xero	Separate org per entity	Configurable, not prescriptive	Public API, large app store	Small teams, one or two entities
QuickBooks Online	Separate company file per entity	Configurable	Public API	US-influenced startups, single entity
Pennylane	Multi-company	Strong for France, weaker elsewhere	Not publicly confirmed as API-first	French or France-heavy groups
Sage Intacct	True multi-entity with intercompany	Depends on partner localization	API available	Scaleups with real finance teams
NetSuite	True multi-entity, full ERP	Strong with localization	API available	Groups needing full ERP
Business Central	Multi-company, partner-led localization	Strong with EU partner	API available	Microsoft-ecosystem groups
AccountsIQ	Multi-entity with consolidation	UK/Ireland strong, EU varies	Not publicly confirmed as API-first	Mid-market groups, 5+ entities
Xledger	Multi-entity native	Nordic strong	Not publicly confirmed as API-first	Nordic-headquartered groups
Odoo	Multi-company native	Configurable per country	Open source, extensive	Teams willing to own configuration
Zoho Books	Multi-org	Comparatively basic	Public API	Bootstrapped small groups

"Not publicly confirmed" here means the research reviewed for this piece did not verify the specific capability at the depth needed to make a hard claim. Treat it as a prompt to check directly, not as a negative signal.

How to choose, in the order that actually matters

1. Start from structure, not headcount. A two-person team with three entities and cross-border VAT has different needs from a fifteen-person team with one entity. Count entities and VAT jurisdictions first.
2. Decide whether accounting is an application your team uses, or infrastructure your product depends on. If your product generates the events (payouts, sales, refunds), you probably want infrastructure. If your finance function generates the events (bills, expenses, payroll), you want an application.
3. Look at what breaks at 10x your current volume. Xero at 200 invoices a month is fine. Xero at 20,000 seller payouts a month is a much harder proposition. This is where API-first infrastructure earns its place.
4. Confirm VAT depth against your actual jurisdictions. "EU VAT support" in a feature list is not the same as automated per-country calculation, VIES validation, and local register generation. Ask for specifics.
5. Treat developer tooling as a real requirement, not a nice-to-have. Webhooks, idempotency, and typed SDKs are the difference between a working integration and a fragile one.

What we would do first

For a small EEA team with one or two entities and no engineering-heavy product: pick Xero, accept the per-entity subscription cost, and plan to revisit at the next funding round.

For a growing group with four or more entities and a proper finance team: shortlist Sage Intacct, Business Central, and AccountsIQ, and expect a partner-led implementation.

For a marketplace, SaaS platform, or e-commerce product where the accounting events come from your own software, and especially where EU VAT across multiple countries is a daily problem: spin up a sandbox company and talk to Nordlet about design partner access before committing to a general-purpose tool that will need custom middleware later.

FAQ

Is Nordlet a replacement for Xero or Sage Intacct?

For a traditional finance-team-uses-an-app workflow, no. For a platform that needs accounting inside its own product, yes. Some teams end up running both: Nordlet for the operational ledger driven by the product, and a traditional tool where the accountant lives. The right answer depends on where the events originate.

How does multi-company work in Nordlet compared to Xero?

Xero uses one organization per entity, each with its own subscription. Nordlet supports multiple companies under one account with role-based access across those companies, and group consolidation is included: several companies roll up into one consolidated balance sheet and P&L, with ownership weighting, non-controlling interest, currency translation, and intra-group elimination flags.

Does Nordlet handle VAT for all EEA countries out of the box?

Nordlet provides per-country VAT calculation, VIES validation for cross-border B2B, i.SAF register generation, and OSS/IOSS returns. Coverage depth varies by country and evolves as the product matures. For any given jurisdiction, the honest answer is to verify against the current documentation rather than assume parity across all 30 EEA states.

What is the pricing?

Nordlet publishes metered pricing: plans start at €10 per month with 3,000 requests included, €50 with 30,000, and €300 with 200,000, plus a custom tier on request. Every plan includes every module and the full API — plans differ by request volume, SLA, and storage, not by features. Signup is self-serve with no card details, and sandbox companies are unlimited.

Can Nordlet coexist with an existing accounting tool during migration?

Yes, and this is often the pragmatic path. Teams typically start by routing new operational events through Nordlet while keeping their existing tool for historical books and accountant workflows, then decide over time how much to consolidate.