Plans are based on data sources, reconciliation workspaces, automation, transaction volume, and deployment needs. Growth is the default starting point.
One data source, one reconciliation workspace, limited assisted mapping, and about 50k transactions each month. No card required.
Starter moves one recurring payment reconciliation from local files into a managed cloud workspace.
This plan includes these controls.
Growth runs scheduled payment reconciliations across multiple business workspaces without an enterprise contract.
This plan includes these controls.
Scale supports higher-volume payment reconciliation with more workspaces, support priority, and lightweight SSO.
This plan includes these controls.
Enterprise moves Reconify into your approved environment when you need custom connectors, VPC deployment, SLA scope, or full SSO.
This plan includes these controls.
The comparison shows how each plan handles transaction matching, exception management, audit trail, data sources, deployment, and support.
| Capability | CLI | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Transaction matching | Manual CLI runs | Manual runs | Scheduled runs | Scheduled runs | Custom workflow scope |
| Exception management | Local reports | Basic review | Finance exports | Priority review workflow | Custom review workflow |
| Audit trail | Local files | Run history | Run history and exports | Run history, exports, and SSO-lite | Custom retention and controls |
| Data sources | Files you supply | 2 data sources | Unlimited data sources | Unlimited data sources | Unlimited and custom connectors |
| Reconciliation workspaces | Local only | 1 workspace | 3 workspaces | 10 workspaces | Unlimited workspaces |
| Private deployment | Local CLI | Cloud | Cloud | Cloud | Self-hosted or VPC |
| Support | Community | Basic support | Standard support | Priority support | SLA and implementation support |
Reconify supports managed cloud workflows, private deployment for sensitive financial data, and local CLI reconciliation for technical teams.
Reconify hosts the workspace for teams that want scheduled payment reconciliation without managing infrastructure.
This deployment model supports these workflows.
Reconify runs in an approved private environment for teams with stricter financial data controls.
This deployment model supports these workflows.
Engineering teams run payment reconciliation from files when they need local execution and source-controlled configuration.
This deployment model supports these workflows.
These details help finance operations teams choose between Growth, Scale, and Enterprise.
Data sources and reconciliation workspaces reflect the setup work customers buy. Maintained connectors and normalized mappings carry implementation cost, while transaction volume mainly protects the service from abuse.
A workspace is a distinct business, subsidiary, operating unit, or ledger context that needs its own reconciliation rules, mappings, and reporting view.
The transaction limit acts as an abuse guardrail, not the main pricing meter. Teams that regularly exceed the guardrail should move to the next tier or discuss Enterprise scope.
Enterprise fits teams that need self-hosting, VPC deployment, custom connectors, SLA commitments, full SSO, or unlimited reconciliation workspaces.
The CLI stays free when your team supplies files, owns YAML mappings, and wants exception reports without managed data sources.
The CLI includes these local payment reconciliation controls.