Capabilities

Everything it does, without the adjectives

Fifty-two capabilities across seven areas. Where something is limited, the limit is stated. Where a plan is required, the plan is named on the pricing page rather than hidden behind a conversation.

Ingestion

Files as they arrive today, from wherever they arrive from. Nothing upstream changes.

ISO 20022 statements: camt.053 daily, camt.052 intraday, camt.054 debit and credit notifications, across all published versions.
SWIFT MT: MT940 end-of-day and MT942 interim, including multi-page statements and continuation records.
BAI2: For US and correspondent relationships, with type-code mapping onto the same ISO taxonomy.
Payment status reports: pain.002 accepted, rejected and pending statuses reconciled against the originating instruction.
Acquirer and PSP files: Settlement exports in whatever CSV shape the provider uses, with column mapping held per source.
Direct connections: REST and SFTP polling, plus webhook receipt for providers that push.
Ledger side: Scheduled export, database replica or API. Read-only, always.
New formats built for you: If we cannot parse something you receive, we write the parser. It becomes part of the platform at no separate charge.

Normalisation

One canonical record, with guarantees that hold for every source.

Integer minor units: No floating-point representation of money at any point in the pipeline, including intermediate calculations.
Direction from the source field: Taken from CdtDbtInd or the debit/credit mark, never inferred from the sign of an amount.
Reversal handling: Reversal indicators invert direction explicitly rather than being read as ordinary movements.
Both dates retained: Booking date and value date kept separately, because matching needs one and the close needs the other.
Flattened transaction codes: Domain, family and sub-family joined into a single comparable code across every source format.
Reference recovery: Pattern extraction over unstructured remittance text, with the untouched original always retained.
Balance assertion: Opening plus signed entries must equal closing. A statement that fails is rejected whole, never partially ingested.
Source files preserved: Hashed on arrival and kept exactly as received, alongside the records derived from them.

Matching

Six ordered passes. Strongest evidence first, and each pass sees only what the one before could not explain.

Pass 1 · Deterministic: Reference, amount, currency and value date all agree. Confidence 100%, no interpretation involved.
Pass 2 · Reference repair: Amount fixed, reference damaged. Sliding-window trigram similarity recovers truncation and reformatting, scored honestly.
Pass 3 · Fee-adjusted: Directional, contractual tolerance per acquirer. The deduction is posted to its own account, never absorbed.
Pass 4 · Aggregation: Bounded subset-sum reconstructs batch files. Ambiguous cases are declined and listed rather than guessed at.
Pass 5 · Cross-currency: Conversion at settlement rate with a stated tolerance; drift inside it is revalued, drift outside it becomes a break.
Pass 6 · Proposed: Value-only pairings with nothing corroborating them. Always routed to a human, whatever the settings say.
Tolerance profiles: Per source, per counterparty and per channel, each a named parameter with its own change history.
Auto-post threshold: You set the confidence at which a match posts unattended. Below it, everything queues.

Exceptions

A break should arrive as a decision to make, not an investigation to start.

Reason-code library: 34 stable codes across six families, so the queue can be trended rather than only worked.
Root cause in plain language: Two sentences naming the specific records and the specific signal behind the classification.
Evidence attached: Narrative, transaction code, search window and every pass attempted, with the reason each one declined.
Drafted journal entries: Balanced double entry against your own chart of accounts, ready to approve or edit.
Timing suppression: Items inside their channel's clearing window are carried forward with an expiry, not queued as breaks.
Ageing and ownership: Every open item with its age, owner, value and last action, in one register.
Learned autonomy: A reason code becomes eligible for unattended posting after three clean approvals, inside your value and volume caps.
Permanent exclusions: Chargebacks, returns and unidentified cash never post unattended, at any confidence.

Monitoring

The break you catch on the third started on the twenty-eighth.

Settlement lag baselines: Learned clearing distributions per source, channel and weekday, rather than a fixed assumption.
Distributional alerting: Alerts fire on a moved median, not on a single late file. One late payment is noise.
Float and position drift: Expected against actual across every account, projected forward from uncleared instructions.
Return and chargeback trends: Rates measured against each cohort's own baseline instead of an industry average.
Reference quality: The share of incoming lines from which a reference can be recovered, tracked per sender.
Alert budgets: Tuned to a target volume per week. A rule that exceeds it is reported as a bad rule.

Controls and evidence

Built for the conversation you will have eighteen months from now.

Append-only history: Hash-chained record of every match, override, approval and posting, with operator and timestamp.
Replay at original version: A run from last year replays under the rules that were live that day, not today's.
Rules as versioned data: Every parameter change recorded with who changed it, when, and the previous value.
Four-eyes segregation: By value band, reason code and account. The approver can never be the preparer.
Controlled overrides: Reason from a fixed list plus free text, reported separately from ordinary activity.
Evidence packs: Any period exported as structured data with source files included, testable independently.
Attestation records: Dated statements of balance against obligation with the named approver, generated from the run.
Legal hold: Any period can be frozen against retention expiry.

Platform

The parts nobody asks about until procurement.

EU data residency: Single region, no cross-border processing. Single-tenant and customer-VPC options on Enterprise.
SAML SSO and SCIM: Directory-driven provisioning and deprovisioning, so leavers lose access the same day.
Granular roles: Preparer, approver, viewer and administrator, scoped by entity and account.
No seat pricing: Unlimited users on every plan. Shared logins destroy audit trails, so we remove the incentive.
API and webhooks: Every run, match and exception available programmatically, with signed webhook delivery.
Export everything: Your data leaves in structured formats on request, including full history. No exit fee.

Honestly

Against the alternatives

Most teams are not choosing between reconciliation vendors. They are choosing between a spreadsheet, an ERP module they already pay for, and building it themselves.

Approach	Matching	Batch files	Audit trail	Scale
Spreadsheet	Manual, one-to-one		A file and a signature	Breaks around 20k lines
ERP reconciliation module	Rules, one-to-one		Change log	Good, if your data is already clean
In-house rules engine	Rules, extensible	With effort	Whatever you built	Scales; maintenance does not
Finlecy	Six ordered passes		Replayable at original version	2.4M lines per run

If your volumes are small and your sources are two, a spreadsheet is a reasonable answer and we will tell you so on the call. The arithmetic starts favouring us somewhere around a hundred thousand lines a month, or the first time an auditor asks a question the spreadsheet cannot answer.

See which of these you actually need

Send one day of real data. We will tell you which capabilities are relevant to your operation and which are not.

Book a walkthrough See pricing