SWIFT MT940 field
MT940 field :64: Closing Available Balance
Optional: the funds the account owner can use at the end of the statement. It differs from the booked balance when items are not yet available (float) or funds are held.
| :64: (optional) | Closing Available Balance: Funds available to the account owner at the end of the statement. |
|---|---|
| Format | 1!a6!n3!a15d |
| Message | MT940 customer statement (also used by MT942 where the field exists there) |
| In camt.053 | Bal with Tp CLAV |
Format
The format is written in SWIFT notation: 1!a6!n3!a15d. n digits; a capital letters; c capital letters and digits; x any character of the SWIFT set; d a decimal amount with a comma; 16x up to 16 of them; 6!n exactly 6; [ ] optional; 6*65x up to 6 lines of 65.
Annotated example
From the sample MT940 the viewer opens with “Try a sample”:
:64:C261028EUR20044,38| Part | Meaning |
|---|---|
:64: | The tag. |
C261028EUR20044,38 | Mark, date, currency and amount, as in :62F:. Here equal to the booked balance. |
Where it goes in camt.053
The MT940 Viewer and the API convert MT940 to camt.053.001.08. For this field:
| MT940 | camt.053.001.08 | Note |
|---|---|---|
| :64: | Bal Tp CLAV |
Becomes a balance of type CLAV (closing available).
The whole mapping, field by field, is in camt.053 vs MT940.
Checks the viewer runs
mt.currency: Currency (Balances and entries share one ISO 4217 currency)mt.date: Invalid date (SWIFT dates YYMMDD / MMDD)mt.field.format: Field format (SWIFT MT940/MT942 field specifications)
Worth knowing
- The available balance is not part of the roll-forward check; only booked balances are.
Read :64: from a script or an AI agent
Scripts and AI agents can do the same without a browser: POST /api/v1/parse or the MCP tool parse_mt940 returns every statement as JSON: balances, each :61: split into its subfields and each :86: with its structured parts. No key is needed, and the file is processed in memory and never stored (API and MCP docs).
curl -s --data-binary @statement.sta https://iso20022-navigator.com/api/v1/parse{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "parse_mt940",
"arguments": {
"content": "<the file text>"
}
}
}