SaaS ERP: What It Is and How It Differs From Traditional ERP

A plain definition of SaaS ERP, a side-by-side comparison with on-premise and hosted ERP, and the API-first subcategory that platforms build on.

SaaS ERP is enterprise resource planning software that the vendor runs on its own infrastructure and sells as a subscription, so every customer uses the same continuously updated version through a browser or an API. Traditional ERP is software you license once, install on servers you control, and upgrade as a project of your own.

That is the whole definition. The rest of this article is about what follows from it: who does the upgrades, how the price is calculated, who owns the data, how other systems connect, and the cases where the traditional model is still the right choice.

The three deployment models

"Cloud ERP" is used loosely for two different things, and the difference matters when you compare quotes.

	SaaS ERP (multi-tenant)	Hosted ERP (single-tenant)	On-premise ERP
Who runs the servers	The vendor	The vendor or a hosting partner	You
Software version	One version for all customers	Your own copy, upgraded on your schedule	Your own copy, upgraded on your schedule
How upgrades arrive	Continuously, without a project	As a scheduled project	As a scheduled project
Customisation	Configuration and API; code changes are rare	Code changes possible	Code changes possible
Typical commercial model	Subscription per user, per entity or per usage	Subscription or licence plus hosting fee	Perpetual licence plus annual maintenance
Compliance updates (tax rates, filing formats)	Delivered by the vendor to everyone at once	Delivered as patches you apply	Delivered as patches you apply

A hosted single-tenant product that a vendor calls "cloud" has the operational profile of on-premise software with somebody else's data centre. It is still your version, and upgrades are still your project. Ask which column a product belongs to before comparing it with a multi-tenant one.

Who runs the upgrades

In a multi-tenant SaaS ERP there is one version of the software, and the vendor moves everyone to it. You do not schedule an upgrade, test a new release against your customisations, or pay an integrator to migrate. The trade-off is that you also cannot refuse the upgrade.

For accounting this has a specific consequence. Tax rates change, filing formats change, and e-invoicing mandates arrive on dates set by governments rather than by your IT calendar. In a SaaS model those changes ship to every customer as a product update. In a traditional model each one is a patch that someone in your organisation has to apply before the deadline.

Nordlet is an example of the SaaS pattern applied to the finance core: the changelog lists each change, and the country-by-country filing table is generated from the code, so what the product sends and what the public page says come from the same source.

How the price is calculated

Traditional ERP pricing is a perpetual licence (often priced per named or concurrent user) plus annual maintenance of roughly a fifth of the licence value, plus an implementation project, plus hardware. The implementation project is usually the largest line and the hardest to estimate. How much ERP software costs in 2026 covers the full cost model.

SaaS ERP pricing comes in three shapes:

Per user per month. The common model for suites aimed at finance and operations teams. Cost grows with headcount, not with business volume. A platform that generates thousands of transactions a day with two finance staff pays little; a company with forty warehouse users pays a lot.
Per entity per month. Each legal company is a separate subscription. Groups with many small entities pay for each one, whatever its volume.
Metered by usage. Cost grows with the number of operations the system performs. This fits software that is driven by other software rather than by people typing.

Nordlet uses the third model. Pricing is metered by API request: Starter is €10 per month with 3,000 requests, Business €50 with 30,000, Scale €300 with 200,000, and extra requests cost between €0.004 and €0.002 depending on the plan. Users and companies are unlimited, and the plans differ only by request volume, SLA and included storage. There is no feature gating: invoicing, ledger, inventory, payroll, consolidation and the full API are in every plan.

Who owns the data, and how you get it out

In the traditional model the database sits on your server, and you can query it directly. In SaaS the data sits with the vendor, and what you can get out is whatever the vendor exposes. Before signing, check three things:

Is there a complete read API? If you can only download reports, you cannot rebuild your books elsewhere.
Are the exports in formats your accountant and the next system accept? For an EU company that means statutory statements, VAT registers and, where relevant, national audit-file formats.
What happens when you leave? Archiving, retention periods and deletion should be published.

Nordlet exposes every module through the same API the application uses, with no private endpoints. Ledger exports exist in DATEV format for Germany, FEC for France and SIE for Sweden, and reports generate as XLSX, PDF or JSON. An archived company costs €1 per month and keeps all its data.

Integration: API-first versus connector

Traditional ERP integrates through database access, file drops and a middleware layer. SaaS ERP integrates through its API, and the quality of that API decides how much of your process can be automated.

There is a meaningful split inside the SaaS category:

App-first SaaS ERP has a user interface as the product and an API as a companion. Some operations exist only on screen. Integrations tend to be built by partners as connectors.
API-first SaaS ERP has the API as the product and the interface as one client of it. Every operation the screen performs is a documented call another program can make.

The difference shows up when your own software is the source of the transactions. A marketplace recording seller payouts, a subscription product recognising revenue each month, or an e-commerce platform invoicing into several EU countries needs the second kind. What an accounting API is explains the category in more depth.

In Nordlet every operation is a POST /v1/{module}/{resource}/{action} call with a JSON body. Keys carry scopes such as sales:write. An Idempotency-Key header makes retries safe: the same key with the same payload replays the stored response, and the same key with a different payload is rejected. Webhooks are written in the same database transaction as the change they report, so a rolled-back document never emits an event. Typed SDKs are generated from the OpenAPI specification in nine languages, with installation instructions for each.

When traditional ERP still wins

SaaS is not the right answer for every organisation. The traditional model holds in three situations:

Deep process customisation. A manufacturer whose planning logic is itself a competitive advantage may need code-level changes that a multi-tenant product cannot allow.
Isolated networks. Defence, some utilities and some public bodies run systems that must not reach the internet.
Regulatory data-residency rules that a vendor cannot meet. Many can; check the data-processing agreement rather than assuming.

Outside those cases the cost of running your own ERP version, and of applying every compliance patch yourself, is paid for no benefit. Why ERP implementations fail looks at where that cost usually appears.

The API-first subcategory

A full ERP suite covers finance, inventory, manufacturing, CRM, HR and more in one product. Many companies that search for "SaaS ERP" need the finance and operations core and already have, or do not want, the rest.

Nordlet covers that core: sales and purchase invoicing with gapless numbering, a double-entry general ledger with period locking, bank feeds and statement import with payment matching, FIFO inventory across warehouses, production with bills of materials, fixed assets and depreciation, employees and payroll, agreements with recurring billing, revenue recognition under IFRS 15, cost centers, group consolidation, and the EU VAT, e-invoicing and statutory filings for 30 countries. Each module is reachable through the API, and the application is built on the same endpoints.

It is a young product, in early access in 2026 and onboarding design partners. That is worth knowing when you compare it with suites that have been sold for decades. How ERP systems work shows what the data flow through such a core looks like in practice.

How to compare quotes

Put each product in the right column of the table above. Hosted single-tenant is not SaaS.
Ask who applies tax and filing updates and by when. Get it in writing for the countries you operate in.
Model the price at three times your current volume and headcount. Per-user, per-entity and metered pricing diverge sharply as you grow.
Export a full set of data from a trial or sandbox before buying.
Build one real integration flow against the API in a sandbox. A pre-production test plan lists what to check.

FAQ

Is SaaS ERP the same as cloud ERP?

Not always. Cloud ERP covers both multi-tenant SaaS and single-tenant hosted products. Only multi-tenant SaaS gives you vendor-run upgrades without a project of your own. Ask which one a product is.

Can SaaS ERP be customised?

Through configuration and the API, yes. Code-level changes to the product itself are usually not possible, because every customer runs the same version. If your requirement needs code changes, you are looking at hosted or on-premise software.

Is my data safe with a SaaS ERP vendor?

The answer depends on the vendor's contract and controls, not on the category. Check the data-processing agreement, where the data is stored, what the retention and deletion rules are, and whether a full read API exists so you can take everything out.

How long does it take to start using a SaaS ERP?

Signing up takes minutes; a sandbox lets you test the same day. A production rollout still involves data migration, chart-of-accounts decisions and integration work. Realistic ERP implementation timelines breaks this down by project shape.

Does SaaS ERP replace an accountant?

No. It records, calculates and files. Classification judgements, provisions, and in most countries the signing of statutory accounts remain with a qualified person.