Skip to main content
POST
Reconcile a bank movement
Live capability. Melso runs this in production today. Partner keys reach it once your partner account is enabled. See Availability.
A person decides. The company’s owner makes this call, signed in to Melso. Partner keys cannot make it: send the person the approval link instead. See Approvals and filing.
Money in settles income and invoices; money out settles expenses. A document without amount is settled for what is still outstanding. Whatever the movement does not settle stays on account.

Authorizations

Authorization
string
header
required

Your partner secret key, mk_live_… for real companies or mk_test_… for test companies. Keep it on your servers. See Authentication.

Path Parameters

company_id
string<uuid>
required

The company's ID. Every company-scoped call works in exactly this company.

bank_movement_id
string<uuid>
required

Body

application/json
documents
object[]
required
Required array length: 1 - 100 elements

Response

The movement with its reconciliation.

id
string<uuid>
required
bank_account_id
string<uuid>
required
source
enum<string>
required
Available options:
statement,
connection
booked_on
string<date>
required
amount
string
required

An amount in euros as a decimal string with two decimals, such as "121.00".

Pattern: ^-?[0-9]+\.[0-9]{2}$
Example:

"121.00"

currency
string
required
concept
string
required
created_at
string<date-time>
required
statement_id
string<uuid> | null
external_id
string | null
value_on
string<date> | null
balance_after
string | null
counterparty_name
string
counterparty_iban
string | null
reference
string
reconciliation
object | null
proposal
object | null

Melso's proposed match, for a movement not reconciled yet. It needs the exact outstanding amount.