Softwr

APIs · head to head

Codat vs Merge

Codat logo

Codat

APIs

One API for small business accounting, banking and commerce data

From
On request
Rated
-
Full reviewWebsite
Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Merge has a free tier, so it costs nothing to try first.
  • 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.; Merge cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • They diverge on capability: Codat covers Normalised accounting API, Merge covers Unified API.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Codat and Merge actually diverge.

Attributes where Codat and Merge differ
AttributeCodatMerge
Starting priceOn requestFree
Pricing modelquoteusage-based
Free tierNoYes
PlatformsAPI, WebApi
CategoryAPIsAutomation Integration
FoundedUnknown2020

Identical on both: user rating (Not yet rated).

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 Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

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 Merge
  • A commercial bank monitoring covenant compliance across a portfolio of small business borrowers continuously rather than quarterlynot Merge
  • A payment company verifying a merchant trading history before extending working capitalnot Merge
  • A B2B platform writing bills and payments back into a customer accounting system so reconciliation happens automaticallynot Merge

Merge

  • Workflow Automationnot Codat
  • Data Integrationnot Codat
  • Process Automationnot Codat
  • App Integrationnot Codat
  • API Connectivitynot 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.

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

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

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/month
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2500/month
    • Unlimited accounts
    • Priority support
    • SLA
  • Enterprise$undefined/month
    • Dedicated support
    • Custom contracts
    • Advanced security

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 Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on Api.
  • You also want hris integrations.
Merge review

Questions people ask

Is Codat or Merge better?
Neither clearly leads. Codat starts at On request and Merge at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Codat or Merge?
Merge has a free tier; the other does not. Paid plans start at On request for Codat and Free for Merge.
Does Codat or Merge run on more platforms?
Codat runs on API, Web. Merge runs on Api.
Can I use Merge for free?
Yes. Merge has a free tier, so you can try it without paying. Codat starts at On request.
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 Merge is typically brought in for.
What can Codat do that Merge cannot?
Codat covers Normalised accounting API, Banking and commerce data, Lending products, Write-back. Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations.

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.

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
Codat: Can Codat write data back?

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

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
Codat: Is pricing published?

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

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

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.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

Share

Related pages

More on Codat

More on Merge

Keep looking

Other head to heads