Ledgerline is the settlement and reconciliation layer for mid-market finance teams — bank feeds, payment rails and the general ledger, aligned in one auditable system of record.
Each module is independently deployable and reports to the same event log. Nothing is inferred; every balance traces to a signed source document.
Direct bank connections across 34 institutions, normalized to a single transaction schema within 90 seconds of the bank posting.
Deterministic matching first, statistical matching second. Every automated match ships with its rule identifier and confidence value.
Breaks are classified, assigned and time-stamped. The close package is generated from the log — it is not a separate artifact to assemble.
Position, exposure and forecast exports in the formats your auditor, your board and your ERP already accept.
Published quarterly from production telemetry across all customer workspaces. No sampling, no rounding in our favour.
| Metric | Definition | Q2 2026 | Q3 2026 | Δ |
|---|---|---|---|---|
| Auto-match rate | Transactions closed without human review | 97.8% | 99.2% | +1.4 |
| Median ingest latency | Bank posting → ledger entry | 142s | 88s | −38% |
| Break rate | Unmatched value / total value | 0.011% | 0.004% | −64% |
| Close package time | Month-end, 12-entity org | 3.2 days | 0.5 days | −84% |
| API availability | Rolling 90-day, all endpoints | 99.98% | 99.99% | +0.01 |
Four stages, fixed scope, published acceptance criteria. Most teams are reconciling production data in week two.
Chart of accounts, entities and bank connections inventoried against our reference schema. Two days, facilitated.
Read-only bank credentials and ERP API keys issued. Historical data backfilled 24 months for rule training.
Matching rules tuned on your own history until the auto-match rate clears the agreed threshold, measured daily.
Parallel run for one close, then cutover. Break queues, audit exports and SLAs take effect the same day.
Aggregate change from each customer's own baseline during the first two quarters on Ledgerline.
Access is granted in cohorts so every implementation gets a named engineer. The next cohort opens in November 2026.