Statement files in, a matching ladder, breaks with owners, signed certificates.
Reconciliation usually means a spreadsheet, a bank statement and a long afternoon, repeated every day. Differences found on Monday are found again on Tuesday, because nothing remembers them.
Bridge Reconciliation takes records from every party you deal with, matches them on a ladder of rules, and turns every difference into a break with an owner, an age and a resolution. Breaks carry over between runs, so something raised three weeks ago is three weeks old.
When the queue is in a state you'll stand behind, you sign the period off and get a signed certificate. It never posts to your ledger: it tells you what doesn't match, and you decide what to do.
Your bank, processor, payroll partner or your own ledger. Each sends records the way that suits it.
As a stream, a signed file (CSV, TSV, JSON, camt.053 or MT940), a batch over the API, or a statement you upload.
Exact first, then by reference, amount and date windows, so the obvious matches never need a person.
Every difference is categorised, valued, aged and assigned, and stays until it's resolved with a reason.
You sign, and receive a certificate of the reconciled period.
CSV, TSV, JSON, camt.053 and MT940, mapped to one model.
Seven steps from exact to tolerant, each recorded on the match.
Assigned, aged and resolved with a reason, never re-raised fresh.
A signed statement that the period was reconciled, by your own people.
Files are verified against the sender's key before a row is read.
It reports differences; your ledger stays yours.
Illustrative businesses, not customers. Figures are made up to show the flow.
A payments company in Lagos · Fintechs & neobanks
Finance spends every morning matching the bank statement to the ledger in a spreadsheet. Differences from last week get lost.
Mornings go to the handful of breaks that matter, not to re-matching the same thousands of lines.
A marketplace paying sellers in Kano · Marketplaces
Sellers call when payouts are late, and support can't tell whether the bank actually sent them.
Support sees which payouts the bank confirmed, and which need chasing.
A cooperative society in Ibadan · Cooperatives & groups
Auditors ask every year how the books were reconciled. The answer is a folder of spreadsheets.
The audit question has a signed answer for every month.
Endpoints in the Reconciliation API reference, with every parameter and response.
State changes arrive as signed webhooks. How webhooks work
POST /reconciliation/definition
Bridgecurl -X POST "https://api.bridgemoni.com/reconciliation/definition" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" \
-H "Content-Type: application/json" \
-d '{
"code": "string",
"displayName": "string",
"currencyCode": "string",
"frequency": "string",
"timezone": "string",
"cutOffTime": "string",
"graceHours": 0,
"riskRating": "string",
"absoluteTolerance": "string",
"percentageTolerance": "string",
"autoResolveEnabled": true,
"signOffRequired": true,
"ageingDays": 0,
"overdueDays": 0,
"escalatedDays": 0,
"dateWindowDays": 0,
"sides": [
{
"sideKey": "string",
"entityCode": "string",
"displayName": "string",
"isAuthority": true,
"stageOrder": 0,
"forwardGapCategory": "string"
}
]
}'No. It never posts. It shows you what doesn't match and records how each difference was resolved.
Upload their statement, or let us pull it. Not every party needs to send anything.
Your people. Sign-off stays with the organisation it protects.
We'll come back with what's live for you today, and what's next.