Nordlet

← Blog

Nordlet vs AccountsIQ for Platform Builders

A grounded comparison for developers and product teams deciding between an embedded accounting API and a mid-market finance system.

Nordlet Team · · 10 min read

Most teams asking "Nordlet or AccountsIQ?" are asking the wrong question. These two products solve adjacent problems that look similar on a feature list and diverge sharply the moment you try to ship. One is an API you build with. The other is a finance system your controller signs into. If you are a marketplace or platform developer, that distinction shapes almost every downstream decision: pricing, integration effort, VAT handling, and what your end users actually see.

The short version: Nordlet is built to be embedded inside your product. AccountsIQ is built to run your finance function. Both handle double-entry, VAT, multi-entity, and reporting. Only one of them is designed for developers to call from their own backend.

What each product actually is

Nordlet is a cloud accounting API. It gives you a real double-entry ledger, invoicing, EU VAT compliance, bank reconciliation, and SEPA payment export (pain.001), exposed through a REST API with typed SDKs and webhooks. The design intent is that your platform, marketplace, or SaaS product runs accounting inside its own UI and workflows. There is an app, but every module is available through the API on every plan. Immutability, per-country VAT (including VIES validation and i.SAF register generation for Lithuania), and idempotency keys are built into the primitive, not bolted on.

AccountsIQ is a cloud accounting and financial management application aimed at mid-market finance teams and multi-entity groups. It handles group consolidation, dimensional reporting, AP automation, BI dashboards, and cash flow forecasting. It is used by controllers and financial accountants in sectors like investment management, hospitality, professional services, and non-profits. Their pricing page and comparison content position it as a step up from small business tools and a step below full ERP.

If you tried to build a marketplace payout ledger on top of AccountsIQ, you would spend most of your time wrestling a finance product into being a platform primitive. If you tried to close monthly group books for a 12-entity investment fund inside Nordlet, you would be missing the finance-team workflows that make that job survivable.

Where the fit actually diverges

The clearest way to see the split is by who logs in and what they are trying to accomplish.

Nordlet fits when:

  • A developer or platform team is building accounting into their own product.
  • End users (sellers, tenants, sub-accounts) never see a general ledger. They see whatever your UI shows them.
  • Bookkeeping needs to happen automatically as transactions flow through your platform.
  • EU VAT needs to be calculated, validated (VIES), and filed with country-specific outputs like i.SAF.
  • You need webhooks such as sale_invoice.paid to drive downstream logic in your own system.
  • Idempotency, immutability, and audit trails matter because your accountant, your auditor, and your platform users all need to trust the same numbers.

AccountsIQ fits when:

  • A finance team, not a product team, is the primary user.
  • The organisation has multiple legal entities and needs group consolidation.
  • The work is closing books, running management accounts, and producing BI dashboards.
  • AP automation, batch invoice processing, and customer portals matter more than programmatic access.
  • Implementation is expected to run through a partner, over weeks, with configuration.

An independent 2026 review describes typical AccountsIQ deployments in the UK mid-market at £400 to £1,200 per entity per month, with implementation via partner in the £5k to £25k range. That is not a criticism. It is a reflection of the segment it serves.

Feature comparison

The table below only marks capabilities where the source material is explicit. Where evidence is thin, it says so.

Capability Nordlet AccountsIQ
Primary interface REST API with typed SDKs Cloud web application
Double-entry ledger Immutable, audit-ready, exposed via API Yes, standard within finance app
EU VAT compliance Per-country VAT, VIES validation, i.SAF register generation UK/EU VAT, MTD recognised per independent review
Multi-entity Multi-company under one account, role-based access Multi-entity consolidation is a core positioning strength
Group consolidation Not publicly detailed Yes, core capability
Webhooks Yes, e.g. sale_invoice.paid Not publicly confirmed
Idempotency keys Yes Not publicly confirmed
Bank reconciliation One-click matching, smart payment matching Yes, within the application
SEPA payments export pain.001 supported Not publicly confirmed
Inventory Multi-warehouse FIFO, BOM production, POS intake Inventory module referenced
Fixed assets Yes, with depreciation and modernization tracking Not publicly detailed
AP automation Purchase invoices with duplicate detection Strong AP automation is a marketed strength
BI and dashboards Reporting suite: trial balance, P&L, cash flow, VAT, debt aging BI reporting and dashboards emphasised
Report export formats XLSX, PDF, JSON with webhook notifications Standard finance reports
Authentication Passwordless email sign-in Standard cloud login
Languages Lithuanian, English English primary
Deployment model API-first, embed in your product Hosted app for finance teams
Trying it out Self-serve signup without card details, unlimited sandbox companies Free trial available, no freemium (G2)

The "not publicly confirmed" cells on the AccountsIQ side are not accusations. They are places where the public material simply does not confirm the capability at the level a developer would need before committing.

Pricing: two different economic models

AccountsIQ publishes indicative pricing across three tiers. Public sources consistently describe:

The official pricing page shows a Core plan from €275 per month with Growth and Scale tiers layered above. TrustRadius notes an entry-level setup fee has historically been part of the package. The 2026 independent review estimates that year-one total cost typically runs 20 to 40 percent above the headline plan once integration and add-ons are counted. AccountsIQ itself has written about avoiding hidden price hikes, which is a useful lens on how buyers should read any quote.

Nordlet publishes metered pricing: plans start at €10 per month with 3,000 requests included, €50 with 30,000, and €300 with 200,000, with additional requests billed at a per-request price and a custom tier on request. A request is any action performed through the API or the app — issuing an invoice, adding a ledger entry, generating a report. 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.

That difference matters for the decision. A finance team can look at AccountsIQ, see €275 to £1,200 per entity per month plus implementation, and budget accordingly. A platform team looking at Nordlet is pricing accounting the way it prices any other infrastructure: metered by usage, scaling with the transaction volume its own customers generate. Different math, different buyer, different unit economics.

The developer experience question

This is where the two products stop being comparable in a straight sense.

Nordlet's product surface is the API. The predictable REST endpoints, typed SDKs, webhooks for real-time events, and idempotency-key support are the entire point. When something like sale_invoice.paid fires, your system reacts immediately instead of polling. Idempotency means a network hiccup does not create a duplicate ledger entry, which is the kind of detail that only matters until it saves you from a very bad Tuesday.

AccountsIQ does offer API access — its pricing page markets an Open API for connecting tools like Salesforce, payroll, and banking. But that API is positioned as integration plumbing for the finance application, not as an embeddable accounting backend. Whether it offers webhook events, typed SDKs, and idempotency guarantees at the depth a platform integration needs is not something the public sources confirm. A platform team evaluating it for embedded use would need to validate that directly with AccountsIQ before committing.

For a marketplace, "not publicly confirmed" is a real problem. You cannot ship an integration on a maybe.

VAT and EU compliance in practice

Both products handle EU VAT. They handle it at different levels of abstraction.

AccountsIQ handles VAT the way a finance system does: rate configuration, VAT returns, MTD submission in the UK, output for the accountant. That is the right level for a controller closing books.

Nordlet handles VAT the way a platform needs to. Per-country rules are enforced in the ledger. VIES validation is an API call. i.SAF register generation is automated. If your platform is invoicing on behalf of thousands of sellers across multiple EU countries, and each of them has different VAT obligations, you need the compliance layer at the API, not in a finance app someone opens on Tuesdays. This is the gap between "our finance team files VAT" and "our product files VAT correctly, at scale, per transaction, for tenants we may never speak to."

Which one to choose

Choose AccountsIQ if you are a finance leader at a mid-market group, you have multiple entities to consolidate, you want strong AP automation and BI, and you are comfortable with a partner-led implementation and per-entity pricing. It is a serious finance product for finance people. The GetApp overview and reviews on G2 give a fair picture of how it lands in practice.

Choose Nordlet if you are building a marketplace, SaaS platform, or e-commerce product and you need accounting to run inside your own product. If your developers are the buyers, if your users should never see a general ledger, if you need webhooks and idempotency and audit-ready books as programmable primitives, this is the shape of tool that fits. It is the option that treats accounting as infrastructure rather than as a department.

For platform developers specifically, which is who this comparison is aimed at, Nordlet is the natural fit. AccountsIQ is a strong product in its own segment. It is not, on the public evidence, built to be the accounting backend of somebody else's product.

What we would validate before signing

If we were making this decision next week, here is the short list we would push on:

  1. Ask both vendors for a concrete integration example that matches your actual data flow. Not a demo. A sequence diagram.
  2. For Nordlet, create a sandbox company and test the specific EU countries you operate in. Confirm VIES, i.SAF, and any per-country register outputs you need.
  3. For AccountsIQ, get written confirmation of API scope, webhook events, and rate limits. Do not assume based on the app.
  4. Model total year-one cost including implementation, not just the headline monthly price.
  5. Test idempotency by deliberately retrying a payment webhook. See what happens to the ledger.
  6. Look at multi-entity: is it consolidation for a finance team, or is it per-tenant isolation for a platform? These sound similar and are not the same.

FAQ

Is AccountsIQ a competitor to Nordlet?

Only partially. They overlap on core accounting concepts, but they serve different buyers. AccountsIQ competes with cloud finance systems like Xero, Sage Intacct, and Xledger. Nordlet competes in the embedded-accounting-API category, which is a smaller and newer field.

Can AccountsIQ be used inside a marketplace platform?

Public sources do not describe it as an embedded API product. It markets an Open API for integrating the finance application with other tools, but if embedded accounting is your requirement, you need to validate that directly rather than assume it.

Does Nordlet replace a finance team?

No. It automates the plumbing so the finance team stops doing manual reconciliation and data entry. Someone still needs to close the month, review reports, and file returns. Nordlet makes their books trustworthy and their VAT compliant. It does not make judgment calls.

What about smaller vendors like Xero or QuickBooks?

Those are strong small-business finance tools with APIs, but their APIs are secondary to the app. Nordlet's API is the product. For embedded use in a platform, that distinction usually decides the choice within a few weeks of building against them.

How does Nordlet pricing work for a platform?

Plans are metered by requests rather than per user or per entity, starting at €10 per month, and every plan includes every module and the full API. Additional requests past the included volume are billed at the plan's per-request price, so nothing gets blocked. For a platform, that means accounting cost tracks the transaction volume your product actually generates.

Further reading