Welcome to LedgerFlow.ai

Template-driven two-tier matching between partner statement files and your ledger. Configurable column mappings, timezone tolerances, flexible field extraction and automatic duplicate detection — matching across billions of rows in seconds. Strict matches where every criterion agrees, plus a loose fallback that still catches identifier-only agreement instead of dumping it on an analyst.

Import partner statement files and automatically match them against your ledger using configurable templates. Manages exceptions, multi-account matching, and currency validation — built for Reconciliation Officers handling high-volume settlement processing.

Automate recurring financial operations from one administrative view. Schedule account snapshots, housekeeping, reconciliation sweeps and balance roll-ups — configurable, monitored, and included rather than bolted on with a separate scheduling product to run.

Define inheritable configuration templates applied across whole categories of accounts. Each profile encodes 100+ parameters — velocity limits, balance thresholds, transaction size controls and fraud flags — enforced automatically at transaction time. Change a policy once and it applies everywhere it should, instead of being re-implemented per integration.

Build and manage your chart of accounts with hierarchical parent/child aggregation, multi-currency support, and timezone-aware reporting dates. Supports Asset, Liability, Income, and Expense account types with automatic real-time balance propagation.

Behavioural fraud detection that learns each account's own normal rhythm — the hours, days and dates it habitually transacts — and surfaces genuine departures from it in real time. No rule library to write and maintain, and no analyst drowning in false positives.

Every create, update and delete across the platform is captured automatically — the user, their role, client IP, the action, and exactly what changed. Capture is unconditional and cannot be skipped, bypassed or edited by application code, so the audit trail holds up when it is actually needed.

Integrate with any OIDC-compliant identity provider — Keycloak, Auth0, Microsoft Entra, or your own IdP. Federated identities are mapped to internal roles, preserving the platform's granular 25+ permission model. Multi-factor authentication and passkeys are supported.

Create and manage local platform users and role assignments independently of, or alongside, your SSO configuration. Every user is governed by 25+ permission categories with read / read-write / read-write-delete granularity.

Generate paginated, filterable statements showing all postings, running balances, and transaction references for any account. Supports Accounting Managers, Customer Service Representatives, and end-user self-service.

Analyse account fund movements, velocity trends, and throughput patterns over configurable time windows. Visualises inflow and outflow dynamics for treasury monitoring and operational reporting.

Periodically commits a cryptographic fingerprint of your ledger to the Bitcoin blockchain via OpenTimestamps — permanent, public, independently verifiable proof that your ledger held exactly that state at exactly that moment. Evidence the outside world holds about you, not evidence you hold about yourself.

Each confirmed anchor produces a complete, self-contained proof file tying your ledger fingerprint to a specific Bitcoin block. Verification uses open-source tooling against any public Bitcoin node — it needs no LedgerFlow software, no access to this system, and no cooperation from us.

A mobile-first, installable customer wallet running on the same double-entry ledger as the back office — so a customer's balance and your books can never disagree. Six money movements: Send (P2P or to a merchant), Request, Top-up, Settle and Pay-by-QR. A configuration-driven fee engine prices every operation independently — thresholds, percentage or absolute, caps, and who bears the cost — and posts each fee as its own auditable ledger entry, so revenue is never buried inside a net figure. Every customer operates under their own least-privilege identity with record-level isolation enforced beneath the application.

Automated onboarding compliance across five verification types — KYC, KYB, KYM, KYT and CDD. Country-specific requirement sets, three verification tiers, automated document reading and classification, and a hands-off invitation-to-approval workflow with reminder cycles that chase customers so your staff do not have to. Staff review dashboard and customer self-service portal included.

Conversational AI embedded in the platform sidebar. Multi-turn sessions with rolling context, answers grounded in this deployment's own documentation, and live queries against your real ledger — all bounded by exactly the permissions the person asking already has. Ask Flo from any page with a single click.

Eight-dimension behavioural profiling that learns what normal looks like for each individual account — when it transacts, how much, and how often — then scores every transaction against that baseline the moment it posts. A single composite score from 0.0 to 1.0 tells your analysts where to look first. There are no rules to write and keep current, no separate machine-learning platform to buy, staff and operate, and no overnight batch window in which fraud goes unnoticed until morning.

Monitor transaction write latency and execution time distributions across the ledger engine. Identifies performance bottlenecks and validates system responsiveness under load — essential for capacity planning.

Track transaction counts, volumes, and trends over time. Provides operational visibility into peak periods, processing capacity utilisation, and growth trajectories.

Metrics, logs, distributed traces and continuous profiling ship with the platform and start with it — correlated in a single pane. Follow one request from the edge all the way to the query that served it, then jump from a latency spike to the exact trace, its logs, and the code that burned the CPU. Built on OpenTelemetry, so nothing is proprietary: send it to your own monitoring platform instead if you prefer. No external subscription, no extra setup, no separate observability project.

A self-hosted security monitoring layer watches the platform that handles the money. Four independent signal sources — infrastructure and host security, the tamper-evident audit trail, edge web-attack detection, and file-integrity and vulnerability monitoring — feed one detection engine. Alerts are severity-tiered, mapped to MITRE ATT&CK, and tagged for PCI-DSS, GDPR, HIPAA and NIST, so your detections double as continuous compliance evidence instead of a separate annual scramble. Self-hosted means your security telemetry never leaves your boundary.

Flo (Florence) is the conversational AI embedded directly in the operations console — a persistent sidebar on every page, ask-from-anywhere. She grounds every answer two ways. First, she searches this deployment's own documentation before responding, so answers reflect how your platform actually works rather than a generic model's recollection. Second, she queries live data through governed tools spanning the ledger (accounts, transactions, balances, reconciliation, fraud scores), the observability layer (dashboards, metrics, traces, logs) and the security layer (alerts and posture). Every call runs under your own credential and your own permissions, so Flo can never see or change anything you could not — and the observability and security tool families are separately permission-gated and off by default.

The fastest way to connect your own systems to LedgerFlow. Point the connector feature of the tool your developers already use — VS Code, Claude Code, Claude Desktop, Cursor — at this deployment over the open Model Context Protocol. A single read-only credential lets the assistant explore the live platform and its documentation and write correct integration code against what is genuinely there, turning days of specification-reading into an afternoon. Access is curated and bounded by record-level security: the assistant never sees write or administrative surface. Generate a credential and copy ready-made client configuration on the Setup → Agent & MCP page.