Settler

Overview

Settler is reconciliation software for teams that need transaction matching to produce repeatable results and an evidence trail. It is best suited to finance and engineering groups building reconciliation into their own systems or operating it at substantial volume. Its strongest case is control over rules, replay and deployment; teams seeking a simple, ready-made web app may find it more infrastructure than they need.

Key features

Rules, exceptions and approvals

Settler applies configurable policies and field-level tolerances through a rules-as-code engine, making matching results repeatable for the same inputs. That is useful when finance and risk teams need a result they can explain and reproduce, rather than a one-off match. Exceptions carry deterministic context, and operator decisions are auditable; approval controls and exception workflows support review rather than leaving disputed items buried in a run. AI assistance is advisory, with humans retaining final authority, a sensible boundary for consequential financial decisions.

Evidence and replay

Runs can generate hash-linked manifests, provenance chains, structured evidence and export-ready audit bundles. The API supports tenant-scoped runs, evidence retrieval, replay and health checks, giving developers a way to integrate reconciliation and later inspect how a result was produced. Append-only audit records and SHA-256 evidence hash chains are intended to make post-run changes detectable. Settler says its audit exports can support SOC 2 evidence collection; it is not itself a compliance certification.

Integrations and security

Adapters include Stripe, PayPal, Square, Shopify, QuickBooks, Xero, NetSuite, SAP, Plaid, TrueLayer and Chargebee, with 14 more stated on the page. This is a broad starting set for payment, commerce and accounting flows, though teams should confirm their specific systems are covered. Tenant data is partitioned at database, API and runtime layers, with row-level PostgreSQL security and tenant-scoped API keys. Data residency and configurable retention controls are described alongside those safeguards.

Pricing

Settler has a free, open-source self-hosted tier and paid hosted and managed plans. The meaningful differences are monthly run capacity, deployment, evidence handling and support, not simply access to matching.

Open Source is the clearest fit for teams able to deploy and support their own software: it preserves self-hosting and replay while capping volume at 10,000 monthly reconciliations and limiting support to the community. Cloud API raises that ceiling to 100,000 and moves evidence to hosted infrastructure for $99.00 USD per month, but its baseline includes 1,000 exceptions. Managed Operations costs $399.00 USD per month at the stated starting rate and is aimed at higher-volume teams that want operator help and a business-hours SLA; its 1,000,000+ monthly capacity is a different scale. Enterprise Dedicated is for contractual volume or deployment and retention requirements that do not fit those standard options. A free trial is offered, but its length and terms are not established here.

Platforms

Settler supports API, Linux, web and self-hosted use. Docker Compose and Kubernetes are deployment targets. Self-hosted mode has no telemetry by default and is licensed under Apache 2.0, which will matter to teams weighing operational control against hosted convenience.

Who it's for

Settler is aimed at finance teams that need reproducible reconciliation, with distinct developer, operator, finance/risk and InfoSec/admin workflows. It makes most sense when teams can make use of an API-first system, need traceable exception decisions, or have deployment and data-control requirements. Smaller organizations that only need occasional spreadsheet-style checks may not benefit from taking on reconciliation infrastructure.

Pros and cons

• Pros: Repeatable rules and field-level tolerances make matching outcomes explainable and replayable.
• Pros: Hash-linked evidence and auditable exception decisions support investigation and evidence collection without claiming certification.
• Pros: Self-hosting, hosted API and managed operations cover materially different deployment and support needs.
• Cons: The free tier requires self-hosting and stops at 10,000 monthly reconciliations, so it is not a no-operations hosted starter.
• Cons: Cloud API's 1,000-exception baseline may constrain teams whose review queues grow faster than run volume.
• Cons: Enterprise Dedicated has custom pricing, while higher-touch support begins with Managed Operations.

Alternatives

For a broader category comparison, browse Account Reconciliation Software. OneCap is another web option with a free plan and paid pricing; speedRecon may suit an individual looking for a free web workspace, though its free forever tier is capped at three reconciliations per month and 300 rows per file. FIS Data Integrity Manager is a paid web alternative without a free plan. SahiSay Reconciliation offers a free plan and web, Windows, iOS and Android platforms. BankRecon is a paid web option with a free trial; its Standard plan covers 1–3 entities, 3–10 bank accounts and up to about 10,000 transactions per month. Eko Recon is a free API, self-hosted, web and Windows alternative with pricing by quote. Reiterate OS is worth considering when invoice processing is the priority: its Mini plan is 19.00 EUR per month per client and includes invoice gathering and accounting-agent chat. ReconArt is a paid option with API, self-hosted and web platforms, annual subscription billing and a stated 25 million transactions per year on Essentials.

Verdict

Settler is the right choice for finance and engineering teams that want reconciliation rules, exception decisions and replayable evidence under their control, especially when self-hosting or high-volume API workflows matter. The main reason to look elsewhere is operational simplicity: a small team that needs a conventional web tool rather than infrastructure may be better served by a narrower alternative. Choose Settler when traceability and deployment flexibility justify owning a more technical workflow.