Skip to main content
POST
Save a bank statement
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.
The opening and closing balances must reconcile with the movements. Read the file first with Read a bank statement to show the person what it holds.

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.

Body

multipart/form-data
file
file
required

Norma 43, CSV, XLSX or PDF, up to 5 MB. CSV and XLSX need a header row naming a date and an amount, or a debit and a credit column.

bank_account_id
string<uuid>

The account. Without it, Melso uses the saved account with the file's IBAN, or creates one.

account_name
string
Maximum string length: 120
opening_balance
string

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

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

"121.00"

closing_balance
string

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

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

"121.00"

Response

The saved statement and how many movements were new.

bank_statement
object
bank_account
object
saved
integer
duplicates
integer