Product
One platform for ingesting sources, running checks, tracing payments end to end, configuring how it all reconciles, and investigating every exception that surfaces.
Overview
Every check reports into one dashboard — unresolved differences, match rates, and a 90-day history at a glance.
Integrations
Start with exported files. Integrate only when you're ready.
Connect
Share exported files directly or connect via API — whatever fits your current setup. Drop a settlement file into a secure inbox, point an existing webhook at our endpoint, or use our REST API. 1Layer handles parsing, normalisation, and processing from there.
Sources
Drop in SEPA, SWIFT, card scheme or CSV exports — Sources detects the schema, validates it, and tags it for the checks that need it.
Checks
Reconciliation isn't a month-end job. Each check compares records across sources the moment new data lands.
Configurator
Field mapping is set automatically from the data. Adjust it anytime, with live match preview as you go — no code required.
Payments Map
Follow a settlement end to end — hover any node for its latest sync status and match rate.
How it works
Sources connects to every feed — SEPA, SWIFT, card schemes, CSV ledgers — and detects the schema automatically.
Checks run continuously, matching records exactly across every source in the flow.
Payments Map shows every settlement end to end, from source file through ledger to bank — with breaks flagged in place.
Exceptions
Every mismatch across processors, schemes, and banks becomes a tracked exception — with severity, an assignee, and a suggested cause attached automatically.
Exception opened · duplicate settlement detected against nostro feed
Suggested cause attached · "Duplicate file re-run" at 92% confidence
Assigned to Rani P. and Alex T.
Attached evidence · settlement_file_v2.csv
Escalated to L2 · delta exceeds €1,000 threshold
Confirmed duplicate batch id 88213 — reversing settlement, closing with a €0 net adjustment
Trades settle T+1 across systems. Date window auto-adjusted — no action needed.
Same settlement file uploaded twice under a different batch id. Void the re-run, keep the original.
Rate snapshot taken before the source updated. Recalculate with EOD rate and adjust the delta.
Counterparty field dropped during transformation. Reprocess with the corrected mapping.
How it works
Every break — missing settlements, duplicate files, timing mismatches — is caught the moment it appears, not at month-end close.
Each exception opens as a ticket with the diff, evidence, and a suggested root cause already attached — no manual digging through files.
Assign, adjust, and close with a full audit trail — comments, evidence, and adjustments are kept together for every case.
We use essential cookies to make this site work. We don't use tracking or advertising cookies. Privacy Policy