Bank to customer statement (Camt.053)

Camt.053 is a Bank to Customer Statement used for end of day reconciliation. It adheres to the ISO20022 standard and will give an overview of all transactions for a given time period in an XML format.

Below you will find an overview of the fields and parameters Banking Circle supports through the endpoint, as well as an implementation guide.

Link to camt.053 documentation.

GET/api/v1/reports/iso20022/bank-to-customer-end-of-day/{TransactionDate}

Bank To Customer Statement V02  
camt.053.001.02  
xml file

📘

Please note:

We will soon be deprecating v1 of this endpoint and therefore its recommended to use v2.

V2 of an endpoint to fetch camt.053:

GET/api/v2/reports/iso20022/bank-to-customer-end-of-day/{TransactionDate}

Parameters in bank to customer statement request

Upcoming breaking change:

Splitting Camt.053

Currently , this change is planned for SFTP clients only.

Today, SFTP clients receive a single Camt.053 report at a given end of day. With an upcoming change, Camt.053 report larger than 250 MB will be split into multiple files. Each file can be maximum of size 250MB. Based on volume of payments for a given day, client may receive one or multiple files for a single Camt.053 report. All of Camt.053 reports generated files will be delivered in a Zip file to a respective Out folder for a client.

For example:
Current behavior: Today client receives a single file of size 700MB for large number of transactions for a given end of day.
After enhancement: For the above scenario, client will receive three files, two of each size 250MB and third with size 200MB. All these three files will be delivered in a Zip file. Client will have to unzip it to retrieve these files at their end.

Below are the additional tags included in group header of Camt.053 report to support the split functionality.

: 'PageNumber' will indicate information of Number of Files generated for a day.
: LastPageIndicator' will indicate if the generated Camt.053 is last file for a Day.

Implementation of XML Schema Validations for Camt.053 Reports

This change applies to both API and SFTP clients.

We have implemented XML Schema Validations (XSD validations) to enhance our Camt.053 report content. It validates the structure of XML documents and ensures proper data interpretation.

Detailed information is available in our ISO 20022 Message Implementation Guide.

Examples of an upcoming change:

Upcoming enhancement:

Generating Camt.053 per account/accounts via SFTP and API

With an upcoming enhancement, clients will now have the possibility to request a Camt.053 report for a single or multiple accounts. Providing the account Id while requesting a report is optional. Generated report will provide the data for the requested account Ids. If the report request doesn’t provide any account ids then, report will include the transaction details for all the accounts for which the user has access to.

User can provide one or multiple account Ids in the newly added parameter AccountIds. Multiple accounts Ids can be provided in a comma separated list. It should be an exact match of the Id of an account.

Parameter to be added in bank to customer statement request

Camt.053 via reports on request

Post: api/v2/reports/requests/bank-to-customer-report

Example:

 {  
  "reportFormatType": "Xml",
  "transactionDate": "2024-07-22",
  "name": "Test report",
  "reportVersion": 1,
  "accountIds": ["9e1436a5-9bab-4042-bc3c-974afc06ec76", "b46b848e-1bb5-44f7-b0e4-c4bce76530fb"] 
}

Post: api/v2/reports/requests

Example:

 {  
   "name": "Test report",
	 "reportType": "bank-to-customer-report",
	 "reportFormatType": "xml",
	 "bankToCustomerReportRequest": {
	 "transactionDate": "2024-07-31",
	 "accountIds": ["794D9641-869A-8854-1303-01E9C8A59AF0", "CB3A0417-D862-63FB-9C91-02E071AFD267"]
	 }
}