Priced per legal entity. Not per reconciliation.
Reconciliation count is the wrong meter for the close. Every legal entity needs its own period, its own sign-off, its own audit trail. Pricing tracks the work you actually do.
Free wedge
1 entity, 50 transactions / month
Run the wedge case on your own data.
- AR-to-GL subset-sum matching
- Schema auto-detection on AR aging + GL extract
- Tolerance configurable per rule
- Single-user review
- CSV / Excel export
- Document Intelligence — 10 pages / month (try Textract + Vision AI)
- —Multi-entity close
- —Intercompany mirror matching
- —Audit-grade explainability export
- —Cross-period exception memory
Ledger
2-entity floor (₹39,998 entry) · billed monthly
For controllers who close every month.
- Everything in Free, multiplied per entity
- Subset-sum matching (AR-to-GL, AP-to-GL, bank-to-GL)
- Cross-period exception memory + counterparty patterns
- Stateful agent modes (Investigate + Ask)
- Audit-grade explainability export (Big Four-ready)
- Multi-entity close dashboard (Q3 GA — included on launch)
- Intercompany mirror matching (Q3 GA — included on launch)
- Document Intelligence — 200 pages / month (PDF + image extraction via AWS Textract + Vision AI)
- Bayesian confidence per match group
- Role-based access for finance team
- Priority support, onboarding within 1 week
USD pricing for global customers: Ledger from $499 / entity / month, 2-entity floor.
Closing 10+ entities? Custom integrations? On-prem?
Enterprise deployments — dedicated SaaS or on-prem, custom reconciliation rules, direct connectors to your ERP, SSO/SAML, audit log retention up to 7 years, and a dedicated solution architect — are scoped per customer.
Talk to Enterprise salesFrequently asked
Why per legal entity instead of per reconciliation?
Reconciliation count scales unevenly with finance team workload. A 2-entity company doing weekly bank rec runs more reconciliations than a 10-entity company closing monthly. Per-entity pricing tracks the actual operating surface — every legal entity needs its own period workspace, its own sign-off, its own audit trail. It also makes pricing predictable: you know your monthly bill from your org chart, not from your matching velocity.
What's included that isn't built yet?
Multi-entity close dashboard and intercompany mirror matching are GA in Q3 — explicitly marked on the tier. Direct ERP connectors are on the roadmap and not promised on any tier. We don't bill for vapourware. AR-to-GL subset-sum matching, bank-to-GL, cross-period memory, agent modes, and audit explainability are all live today.
Free tier limits?
1 entity, 50 transactions / month, AR-to-GL only. Enough to run the wedge case (one GL JE summing twelve AR invoices) on your own data and decide if the engine fits. No credit card. No expiration on the free tier.
Can I run AP-to-GL on Ledger tier?
Yes. AP-to-GL uses the same SUM_AGGREGATE rule type as AR-to-GL — Ledger tier includes it. The difference is workflow ergonomics: AR is collection-side (customer-receivables-driven), AP is payment-side (vendor-payables-driven). Same engine, different rule templates.
Do you have a marketplace plan? Settlement reconciliation?
That's the other product surface — see /pricing for the marketplace tiers (Free, Starter, Growth, Enterprise). Same underlying engine; different starting position. Ledger and the marketplace tiers are billed separately because the operating surfaces don't overlap; you can have both if you operate both. Enterprise scope (dedicated SaaS, on-prem, custom rules) is unified at /enterprise/ regardless of which product surface you start from.