Softwr

APIs · head to head

Neonomics vs Rutter

Neonomics logo

Neonomics

APIs

Nordic open banking payments and data, now with UK coverage through Ordo

From
On request
Rated
-
Full reviewWebsite
Rutter logo

Rutter

APIs

One API across accounting, commerce, payments and advertising platforms

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Neonomics coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.; Rutter a unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • They diverge on capability: Neonomics covers Payment initiation, Rutter covers Accounting and ERP.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Neonomics and Rutter actually diverge.

Attributes where Neonomics and Rutter differ
AttributeNeonomicsRutter

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, API), user rating (Not yet rated), category (APIs).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Neonomics

  • Payment initiation
  • Account information
  • Nordic bank depth
  • UK coverage via Ordo
  • Variable recurring payments
  • Request to pay
  • White label journeys
  • Reconciliation data

Only in Rutter

  • Accounting and ERP
  • Commerce data
  • Payments data
  • Advertising data
  • Write operations
  • Passthrough requests
  • Observability tooling
  • Sandbox

What people use each for

The jobs each tool is most often brought in to do.

Neonomics

  • A Norwegian or Swedish merchant collecting payments directly from bank accounts to avoid card feesnot Rutter
  • A debt collection agency sending request to pay messages instead of chasing bank transfers manuallynot Rutter
  • A software vendor embedding pay by bank into an accounting or invoicing product for Nordic customersnot Rutter
  • A business needing both UK and Nordic bank payment coverage from one suppliernot Rutter

Rutter

  • A revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facilitynot Neonomics
  • A spend management product that needs to push bills and journal entries back into whichever accounting system its customer runsnot Neonomics
  • A B2B payments platform reconciling invoices across customers using four different ERPsnot Neonomics
  • An insurance or benefits provider that needs verified business financials without asking the customer to upload PDFsnot Neonomics

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Neonomics

  • Coverage outside the Nordics and the UK is comparatively shallow, so a pan European merchant will find gaps and inconsistent bank behaviour in southern and eastern markets.
  • It is a small company relative to Tink and TrueLayer, so supplier viability and the depth of engineering support behind bank API changes are genuine procurement questions.
  • Payment initiation only means the merchant handles settlement, reconciliation and refunds, and there is no chargeback framework to fall back on.
  • Integrating a recently acquired UK business means two regulatory entities and, for a period, two technology stacks, so cross market feature parity is a promise rather than an existing state.
  • Conversion is governed by each bank's own authentication experience, and Nordic BankID flows behave differently from UK app redirects, so a single UX cannot be assumed across the footprint.

Rutter

  • A unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • Write operations into accounting systems are where these products break, because each system validates differently, and a rejected journal entry surfaces as a support ticket against you rather than against the ERP.
  • No pricing is published beyond a sandbox trial, so cost cannot be compared against alternatives without a sales process, and pricing tends to scale with connected accounts.
  • QuickBooks Desktop and other on-premises systems require a local connector or hosted agent, which introduces installation steps your customers must complete and support burden you inherit.
  • Sync freshness varies by platform and by customer authorisation state, so a product promising near real-time figures will find some connections update far less often than the marketing implies.

Pricing, plan by plan

Neonomics

On request
  • Neonomics platform$undefined/year
    • Quoted per customer, typically per initiated payment or per API call
    • Volume commitments and monthly minimums are common
    • Payment initiation only; merchant handles settlement and refunds

Rutter

On request
  • Starter$undefined/month
    • Thirty day sandbox trial
    • Test integrations with QuickBooks, Xero, FreshBooks and Zoho Books
    • Documentation and workflow guides
  • Full Access$undefined/year
    • Production access across all platforms
    • Includes NetSuite, QuickBooks Desktop and Sage Intacct
    • Write operations and passthrough

Which should you pick?

Choose Neonomics if

  • You need payment initiation.
  • You work on Web, API.
  • You also want account information.
Neonomics review

Choose Rutter if

  • You need accounting and erp.
  • You work on Web, API.
  • You also want commerce data.
Rutter review

Questions people ask

Is Neonomics or Rutter better?
Neither clearly leads. Neonomics starts at On request and Rutter at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Neonomics or Rutter?
Neonomics starts at On request and Rutter at On request.
Does Neonomics or Rutter run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Neonomics best used for?
Neonomics is most often used for a norwegian or swedish merchant collecting payments directly from bank accounts to avoid card fees, a debt collection agency sending request to pay messages instead of chasing bank transfers manually, a software vendor embedding pay by bank into an accounting or invoicing product for nordic customers, a business needing both uk and nordic bank payment coverage from one supplier. Of those, a norwegian or swedish merchant collecting payments directly from bank accounts to avoid card fees and a debt collection agency sending request to pay messages instead of chasing bank transfers manually are not what Rutter is typically brought in for.
What can Neonomics do that Rutter cannot?
Neonomics covers Payment initiation, Account information, Nordic bank depth, UK coverage via Ordo. Rutter covers Accounting and ERP, Commerce data, Payments data, Advertising data.

Answered from the vendors’ own pages

Neonomics: Is Neonomics authorised in the UK?

Yes, through the acquisition of Ordo, an FCA authorised open banking payments firm, approved by the FCA and the Norwegian regulator.

Rutter: Does Rutter support QuickBooks Desktop?

Yes, which distinguishes it from unified APIs that only cover cloud accounting, and matters because many small businesses still run it.

Neonomics: Does it support variable recurring payments?

Yes in the UK through the Ordo capability, subject to which banks support commercial VRP; support elsewhere is more limited.

Rutter: Can Rutter write data back?

Yes. Invoices, bills and journal entries can be pushed into supported accounting systems, not only read.

Neonomics: Does Neonomics hold merchant funds?

No. It initiates payments; settlement, reconciliation and refunds remain with the merchant or its payment provider.

Rutter: Is there a free tier?

There is a thirty day sandbox trial with test data. Production access requires a paid plan with quoted pricing.

Rutter: What if the unified model lacks a field I need?

Rutter supports passthrough requests to the underlying platform API, though using them reintroduces platform-specific code.

Share

Related pages

More on Neonomics

More on Rutter

Keep looking

Other head to heads