bank. Listing accounts and movements and recording a reconciliation are private beta on REST. Connecting a bank account and pushing movements are planned, and they are not actions of this tool. Reconciling prepares a journal proposal and does not post it.
The live tool list is authoritative: the company’s plan and your role can narrow this contract. Understand access.
When to use
Usebank for account_update, reconcile, unreconcile. Use bank_read for the companion actions. The live tool list determines availability.
Input
Actions
The tool’s schema combines the fields of every action. Each action accepts only its own fields below; sendaction with them.
Reconciliation actions
These actions record or clear a matching, or map an account in the books, and need a plan with the tools. A reconciliation prepares a journal proposal; it never posts an entry, and posted entries change only by reversal in the app.account_update
account_update
Name a bank account, or set the account in the books it is kept in: a subaccount of 572 (57200001), a savings account (574), cash (570) or a credit line drawn (520). New reconciliations capture this account; existing snapshots and posted entries stay unchanged. Mapping changes are audited. Only when the person asks.
reconcile
reconcile
Record a confirmed movement matching and prepare its journal proposal without posting: with documents (each settles what it still owes unless amount says less; together never more than the movement, what is left over is on account), with lines for what no document says (a tax return, an account of the books; without documents they add up to the movement), or alone as a transfer to or from another of the company’s accounts (each account needs its own account in the books; its other side is reconciled with it). difference proposes a bank’s fee or an exchange difference against the documents (kind bank_fee or exchange, at most 50 € or 5 %). Each bank needs an explicit ledger mapping. A professional reviews and explicitly posts the exact proposal in the app; posted entries remain unchanged. When the person authorizes a batch, process its batch_eligible proposals with their exact displayed amounts after checking both banks are mapped; review conflicts and ambiguous proposals separately. Never invent a document or line the person did not confirm; unexplained movements stay to review. Refusals name their code.
unreconcile
unreconcile
Clear a movement’s matching and return it to review. Its unposted proposal is removed or recalculated; posted entries remain unchanged and require explicit reversal in the app. The other side of a transfer stays matched on its own. Only when the person asks.
Output
reconcile records the confirmed matching and prepares an unposted journal proposal. unreconcile returns the movement to review. account_update returns the renamed or remapped account. These actions never post an entry.
The result uses MCP content blocks; JSON payloads are encoded in text and may also appear in structuredContent. Check isError before reading a success payload. When the server declares an outputSchema, it is reproduced below. Check the action result and its declared fields before reporting success.
Example
Use the actions of this tool in the order shown; its companion tool covers the other actions. These are thearguments of each call, in order.
1
Reconcile it with the expense the person confirmed