Softwr

APIs · head to head

Codat vs Skaleet

Codat logo

Codat

APIs

One API for small business accounting, banking and commerce data

From
On request
Rated
-
Full reviewWebsite
Skaleet logo

Skaleet

APIs

Cloud-native core banking and payment hub with deployments measured in months

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Codat the accounting platforms are metering developer access themselves, with Xero introducing tiered connection based developer pricing from 2 March 2026, so a cost you do not control has been inserted between you and the data and it scales with the number of customers you connect.; Skaleet the installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • They diverge on capability: Codat covers Normalised accounting API, Skaleet covers Cloud-native core.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Codat and Skaleet actually diverge.

Attributes where Codat and Skaleet differ
AttributeCodatSkaleet
PlatformsAPI, WebWeb, REST API, Linux

Identical on both: starting price (On request), pricing model (quote), free tier (No), 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 Codat

  • Normalised accounting API
  • Banking and commerce data
  • Lending products
  • Write-back
  • Business verification
  • Supplier onboarding
  • Connection management
  • Data quality handling

Only in Skaleet

  • Cloud-native core
  • Payment hub
  • Card management
  • Lending
  • API-first
  • Configurable products

What people use each for

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

Codat

  • A business lender that wants live ledger data for underwriting rather than a borrower emailing exported PDF accountsnot Skaleet
  • A commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterlynot Skaleet
  • A payment company verifying a merchant trading history before extending working capitalnot Skaleet
  • A B2B platform writing bills and payments back into a customer accounting system so reconciliation happens automaticallynot Skaleet

Skaleet

  • A banking group launching a digital savings or deposit brand in a new country within a yearnot Codat
  • A bank modernising payments to ISO 20022 without replacing its whole corenot Codat
  • A payroll or HR software company adding embedded banking to its productnot Codat
  • A payment service provider needing a ledger and accounts under its existing licencenot Codat

Where each one falls short

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

Codat

  • The accounting platforms are metering developer access themselves, with Xero introducing tiered connection based developer pricing from 2 March 2026, so a cost you do not control has been inserted between you and the data and it scales with the number of customers you connect.
  • Pricing is opaque and enterprise shaped for a product developers expect to evaluate technically first, so build decisions get made before anyone knows the unit economics.
  • Normalisation hides but does not remove the underlying differences between accounting systems, and edge cases in multi-currency, journals and tax handling surface as data quality problems that your team must reason about in each source system anyway.
  • Data quality depends on the small business keeping its books properly, so a lender using ledger data for underwriting inherits the bookkeeping standard of its worst borrower and needs its own validation layer regardless.
  • Connection breakage from expired tokens and platform API changes is an ongoing operational load, and a borrower whose connection lapses stops being monitored silently, which is the failure mode that matters most in a lending portfolio.

Skaleet

  • The installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • Speed references are mostly greenfield launches inside large groups, which is an easier problem than migrating an existing book off a legacy core.
  • It is European-centric, with payment rails and regulatory work concentrated on SEPA and EU requirements rather than global coverage.
  • As a smaller vendor carrying a bank core, it attracts hard concentration and viability questions in procurement that larger competitors do not face.
  • Pricing is unpublished and scaled by accounts and transactions, so a bank whose volumes grow faster than forecast faces cost escalation it did not model.

Pricing, plan by plan

Codat

On request
  • Codat Platform$undefined/year
    • Priced by connected companies, data types and products
    • Lending and verification products priced above core data access
    • Annual enterprise agreements

Skaleet

On request
  • Skaleet Core Banking Platform$undefined/year
    • Subscription licence scaled by accounts and transaction volume
    • Payment hub licensable separately from the full core
    • Implementation and configuration charged as a project

Which should you pick?

Choose Codat if

  • You need normalised accounting api.
  • You work on API, Web.
  • You also want banking and commerce data.
Codat review

Choose Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.
Skaleet review

Questions people ask

Is Codat or Skaleet better?
Neither clearly leads. Codat starts at On request and Skaleet at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Codat or Skaleet?
Codat starts at On request and Skaleet at On request.
Does Codat or Skaleet run on more platforms?
Codat runs on API, Web. Skaleet runs on Web, REST API, Linux.
What is Codat best used for?
Codat is most often used for a business lender that wants live ledger data for underwriting rather than a borrower emailing exported pdf accounts, a commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterly, a payment company verifying a merchant trading history before extending working capital, a b2b platform writing bills and payments back into a customer accounting system so reconciliation happens automatically. Of those, a business lender that wants live ledger data for underwriting rather than a borrower emailing exported pdf accounts and a commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterly are not what Skaleet is typically brought in for.
What can Codat do that Skaleet cannot?
Codat covers Normalised accounting API, Banking and commerce data, Lending products, Write-back. Skaleet covers Cloud-native core, Payment hub, Card management, Lending.

Answered from the vendors’ own pages

Codat: What is changing with Xero in 2026?

Xero is introducing a tiered, usage based developer pricing model effective 2 March 2026, with tiers based on the number of customer connections an app holds. That is a new cost in the chain for anyone reading Xero data at scale, whether directly or through Codat.

Skaleet: What was Skaleet called before?

TagPay. The company rebranded to Skaleet while keeping the same platform lineage.

Codat: Can Codat write data back?

Yes. It supports pushing bills, payments and journal entries into accounting systems, not only reading from them.

Skaleet: Can I buy just the payment hub?

Yes. The payment engine is licensable standalone and can sit over an existing core, which is a common first step.

Codat: Is pricing published?

No. It is quoted by connected companies, data types and products, and users consistently describe it as opaque.

Skaleet: How fast are real deployments?

Named European deployments have gone live in six to twelve months, including a Crédit Agricole savings platform live in Germany in eight months.

Codat: Does it replace bank data aggregation?

Not entirely. It covers banking alongside accounting and commerce, but lenders commonly run it beside a bank aggregator for transaction level cash flow.

Share

Related pages

More on Codat

More on Skaleet

Keep looking

Other head to heads