Treasury · Bank Reconciliation
Every bank line, matched to its record.
Reconcile continuously. Investigate only what differs.
Donnerstag connects each bank statement line to the finance record behind it, applies your matching rules and value-date tolerances, and clears what agrees, leaving unmatched and disputed items surfaced with their context attached.
From bank statement to reconciled ledger.
Statement lines against finance records.
Matched lines clear automatically. The unmatched line is isolated with its candidates ranked.
Running
Bank line
Amount
Matched to
Status
Matched
Matched
Unmatched
Timing
Matched
What reconciliation runs on every statement.
Every line is ingested, matched and verified against the finance record before anyone opens the worklist.
Ingest statements
Read MT940, CAMT, BAI2 and bank API feeds, and normalise them into a single statement model.
Multi-signal matching
Match on amount, reference, counterparty, value date and payment method against ledger and subledger entries.
Value-date tolerance
Clear timing differences inside your approved window instead of raising them as breaks.
Many-to-one matching
Reconcile batched settlements and split transfers without forcing a single-line match.
Duplicate detection
Catch the same movement arriving twice across overlapping feeds or files.
Break typing
Classify what did not match and route each type toward the right investigation.
What reaches an analyst.
Each break arrives typed and quantified, with candidate matches already ranked.
Unmatched
No corresponding record
A bank line has no matching entry in the finance records at all.
Resolution:
Assign for research with ranked candidates and the source feed attached.
Amount
Value differs
The records correspond but the amount falls outside tolerance.
Resolution:
Investigate the difference, then adjust or dispute with evidence.
Timing
Value date difference
The movement settles in a different period than the ledger expects.
Resolution:
Explain the timing and carry it into the correct period.
Duplicate
Repeated movement
The same transaction appears more than once across feeds.
Resolution:
Isolate the duplicate and confirm the true balance.
How a break reaches a cleared line.
Select an action to see what it does, and the authority it runs under.
01
Isolate
Separate the break so the rest still clears.
02
Type
Classify the reason and quantify the difference.
03
Candidates
Rank the possible matching records.
04
Assign
Route to the right owner with a next action.
05
Clear
Match, adjust or escalate, and record it.
Act on a break
Reconciled lines build the position.
Once statement lines clear, the balances roll straight into the consolidated cash position.
See every account. Drill to any line.
An overview of reconciliation at operation level, then open to the statement line, rule and record behind every figure.
Running
Bank line
Amount
Matched to
Status
Matched
Matched
Unmatched
Timing
Matched
Keep every line answerable.
Know what cleared, what broke, and why.
What cleared?
The lines matched within tolerance.
What broke?
The unmatched line and its type.
Why?
The rule applied and the difference found.
What supports it?
The statement feed and ledger entry.
Who owns it?
The analyst assigned to the break.
How did it end?
Matched, adjusted, escalated or written off.
What bank reconciliation gains
Reconciliation is either current or a backlog. These are the outcomes the operation is built to produce.
Continuous reconciliation
Statements reconcile as they arrive rather than in an end-of-period scramble.
Fewer manual matches
Multi-signal rules clear the routine lines, so analysts only touch genuine breaks.
Timing handled properly
Value-date differences clear inside tolerance instead of becoming false breaks.
Ranked candidates
Unmatched lines arrive with likely matches suggested, not a blank search.
Duplicates caught
Overlapping feeds no longer inflate the balance with repeated movements.
Traceable clearing
Every cleared line keeps the rule, record and actor that resolved it.