Skip to main content
Read-only actions. A company’s bank movements, worked as its adviser does in Contabilidad › Por revisar. accounts lists the bank accounts, each with its assigned ledger account (null means unmapped and blocks reconciliation; account_update assigns a subaccount such as 57200001, cash 570, savings 574 or a credit line 520). Mapping changes are audited; existing reconciliation snapshots and posted entries keep their captured accounts. movements lists the movements newest first (status to_review: those not reconciled, each with the document Melso proposes, its reasons and batch_eligible: identifying evidence with no equally strong candidate); movement reads one; documents lists the open invoices and tickets a movement can settle. reconcile records the confirmed matching and prepares a journal proposal without posting: documents it settles (an invoice less its credit note; a difference for a bank’s fee or an exchange rate), lines for what no document says (kind tax with its model: 303 paid to 4750 or refunded from 4700, 111, 115, 123 and 216 to 4751, 202 to 473, 200 to 4752 or from 4709; kind account with any account of the plan: a loan 170/520 and its interest 662, capital 100, a partner 551, the Seguridad Social 476, a supplier’s or customer’s balance carried from imported books), or a transfer to or from another of the company’s accounts, which pairs both movements and proposes one transfer entry. An authorized batch may reconcile batch_eligible proposals with their exact displayed document amounts; conflicts stay pending. A professional reviews and explicitly posts the exact proposal in the app. unreconcile clears the matching and updates proposals; posted entries remain unchanged and require explicit reversal in the app. Bring statements in with bank_statements. Amounts are EUR decimal strings: movements are positive in, negative out; lines and documents are always positive. Each action accepts only its own fields (* required): accounts; movements(amount, bank_account_id, cursor, from, limit, q, status, to); movement(id*); documents(id*, amount, q). Availability: Empresa. Access: Live in the Melso app and over MCP for a signed-in person. Where the partner REST API covers the same area, that path is private beta until Melso enables your account. See Access and pricing. The live tool list is authoritative: the company’s plan and your role can narrow this contract. Understand access.

When to use

Use bank_read for accounts, documents, movement, movements. Use bank 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; send action with them.

Read actions

These actions only read. They change nothing.
The company’s bank accounts: each one’s id, name, IBAN and account, its assigned ledger account (null means unmapped and blocks reconciliation).
The open documents a movement can settle, the likeliest first: money in with sales (income and invoices), money out with purchases (expenses), and the credit notes that correct them. Each with its type, id, party, number, day, total and what it still owes. q finds a party or number; amount a total or what is owed.
One movement with its reconciliation or proposal. The proposal includes its document evidence and fingerprint; pass that fingerprint as expected_fingerprint when confirming reviewed evidence.
The company’s bank movements, newest first: each with its account, day, amount (positive in, negative out), the bank’s concept, counterparty and reference, and its reconciliation (documents, lines and difference) or, when not reconciled, the document Melso proposes with its reasons and batch_eligible (identifying evidence with no equally strong candidate). status to_review lists only the movements not reconciled. q finds a concept, counterparty, reference, a reconciled document’s party or number, or a line’s concept; amount finds what moved that much either way. A full page carries next_cursor.

Output

accounts returns bank accounts and their ledger mapping. movements returns movements newest first with their reconciliation or proposal and a cursor on a full page. movement returns one; documents returns the open documents it can settle. 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 the arguments of each call, in order.
1

List the movements still to review

2

Find the documents that movement can settle

The first call as a request. Use an OAuth access token issued for this MCP resource and replace the example identifiers with values from your own company.