Reconcile a bank statement
reconcile_statementMatch an ISO 20022 bank statement (camt.053.001.08) or notification (camt.054.001.08) against the payments you expected (open invoices, a payment run, a ledger export) and list the exceptions: amount mismatches (short or over payments, charges taken), entries on the statement nobody expected, and expected items not on it. Matches by reference (EndToEndId, InstrId, TxId, AcctSvcrRef, UETR, creditor reference), by remittance text, one payment for several invoices when they add up exactly, and by amount within a date window; each match says why. Exact decimal arithmetic. Nothing is stored. Same code as https://iomarkets.tech/reconcile. Pass sample: true to run the built-in demo.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "reconcile_statement"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days apart the expected date and the booking date may be for a match on amount alone (default 3). | |
| sample | No | Ignore statement and expected and reconcile the built-in sample (a made-up EUR account) to see how it works. | |
| expected | No | What was expected: CSV text with a header row, or a list of objects. Columns: reference, amount (required), currency (default: the statement's), direction (credit/debit or in/out; without it a negative amount is a debit), date (YYYY-MM-DD), counterparty. Up to 5000 rows. | |
| statement | No | The camt.053 or camt.054 XML. |