The Platform

Built for every corner of
financial reconciliation

From raw transaction files to signed audit reports — Reconrails covers the entire reconciliation lifecycle without stitching together multiple tools.

Get a Demo See Pricing

Multi-pass matching
engine

Reconrails's engine runs multiple matching passes — exact reference match, fuzzy amount+date match, MSISDN-based match — cascading from strictest to most lenient. You control the tolerance rules per payment rail.

  • Configurable per-rail tolerance rules in YAML
  • One-to-many and many-to-one match support
  • Fee decomposition (gross / net / fee split)
  • Real-time pipeline — matches within seconds of ingest
// mpesa_to_ledger.yaml
passes:
- name: exact_ref
keys: [receipt_no, txn_ref]
- name: amount_date
tolerance_minor: 100
date_window_days: 2
- name: msisdn_amount
msisdn_required: true

// Result: 98.9% matched ✓

Exceptions that
explain themselves

Every break is automatically classified, severity-scored, and SLA-stamped. Your team knows exactly what happened, why, and how long they have to fix it.

  • Break types: UNMATCHED, AMOUNT_MISMATCH, DUPLICATE, TIMING
  • Severity: HIGH (4h SLA), MEDIUM (24h), LOW (72h)
  • Bulk resolution with reason codes and notes
  • Email + webhook alerts when HIGH-severity breaks arise
HIGH · UNMATCHED_TRANSACTION
QDR9021X7B — KES 200,000
M-Pesa C2B · No matching ledger entry found
⏱ SLA expires in 2h 14m
MEDIUM · AMOUNT_MISMATCH
QDR9021X8A — KES 12,500 vs KES 12,450
Difference: KES 50 (likely fee)
⏱ SLA expires in 18h
LOW · DUPLICATE
QDR9021X3F — KES 8,750 (×2)
Duplicate receipt detected, flagged for review

Know your position
before settlement

Reconrails computes net settlement positions per rail, per counterparty, per currency — updated in real time after every matching run, so you're never surprised at the settlement window.

  • Multi-rail: M-Pesa, SWIFT, card schemes, core banking
  • Net and gross positions with fee decomposition
  • Exportable settlement advices and MT940 feeds
  • Historical position archive for regulatory review
Settlement Position · 30 Jun 2025
Rail
Credits
Debits
Net
M-Pesa C2B
+5.2M
-4.8M
+400K
Core Banking
+12.1M
-12.4M
-300K
VISA/MC
+2.3M
-0.1M
+2.2M

Visibility into every
data pipeline

Know the health of every feed before your reconciliation team starts work. Stale connectors, missing files, and failed uploads surface instantly — with webhook alerts to your ops team.

  • Per-source freshness indicators with staleness alerts
  • Daraja C2B webhook receiver built-in
  • CSV, SFTP, and API connectors supported
  • Slack + email + webhook notifications
Data Sources · Pipeline Status
M-Pesa Statement
Last ingested 2 min ago
● Live
Core Banking Ledger
Last ingested 8 min ago
● Live
VISA Card Scheme
Last ingested 3h ago — stale
⚠ Stale

Audit-ready from
day one

Every action — every resolution, every approval, every login — is logged in a cryptographic hash chain. Regulators and auditors get instant, verifiable evidence without manual pack preparation.

  • SHA-256 hash chaining — tampering is detectable
  • Who did what, when, and from where
  • Maker-checker for all financial adjustments
  • Filterable by actor, object type, date range
Audit Log
#2847 BREAK_RESOLVED amara@equity.ke
hash: a3f8c2d1... prev: b4e9f3a2...
#2846 ACTION_APPROVED david@reconrails.com
hash: b4e9f3a2... prev: c5f1a4b3...
#2845 USER_LOGIN fatima@ncba.co.ke
hash: c5f1a4b3... prev: d6a2b5c4...
● Chain integrity: ✓ VALID

Built for enterprise scale

50M+
Transactions per day
<2s
Match latency p99
99.97%
Uptime SLA
AES-256
Data encryption at rest
TLS 1.3
Encryption in transit
RBAC
5 role levels

Integrations

Connects to your entire
financial stack

📱

Daraja / M-Pesa

C2B webhook, B2C, paybill, buy goods

🏦

Core Banking (CBS)

T24, Finacle, Oracle FLEXCUBE via CSV/API

💳

Card Schemes

Visa, Mastercard, Kenswitch, AfriGO

🌐

SWIFT / MT940

Nostro reconciliation, correspondent banking