Account statements for business accounts

Adyen provides account statements in the industry-standard CAMT.053 format, which is part of the ISO 20022 financial messaging standard. CAMT.053 uses structured codes to classify the type and status of each transaction. This ensures consistency and interoperability across financial institutions.

Account statements summarize the financial activity in a business account for a specific period, such as a day or a month. You can use these auditable statements to reconcile balances and provide detailed transaction reports to your users. If your balance account is linked to an Adyen-issued card, transactions processed with that card also appear in the statement.

Requirements

Before you begin, take into account the following requirements and preparations.

Account statement settings

When you contact Adyen to enable the feature, you can customize the following statement configurations:

Feature	Required	Description	Options
Timeframe		Sets the reporting frequency.	Daily, monthly, or both
BAI codes		Enables Bank Administration Institute (BAI) codes for standardized transaction classification.	Enabled or disabled
Summary		Includes a transaction summary block for an overview of totals, grouped by bank transaction code.	Included by default
Date format		Defines which date is used for transactions in the statement.	Value date or booking date
Summarized file		Generates an additional daily CAMT.053 file where individual transaction entries are replaced by aggregated totals. These totals are grouped by BAI codes.	Enabled or disabled

Download an account statement

Adyen automatically generates account statements. When a statement is ready:

1. Adyen sends a balancePlatform.report.created webhook message to your configured endpoint in the Customer Area. In the body of the webhook, note the following fields:

   • balanceAccount: An object that contains information about the balance account that the account statement is for.
   • fileName: The name of the file that corresponds to this account statement.
   • downloadUrl: The URL from where you must download the account statement.

2. Download the account statement by making a GET request to the URL included in the downloadUrl field. In the request, you can use the -o flag to specify a custom name for the downloaded file.

Account statement elements

All CAMT.053 statements provided by Adyen have the same XML structure. The high-level structure is:

• BankToCustomerStatement (BkToCstmrStmt)
  • GroupHeader (GrpHdr)
  • Statement (Stmt)
    • Account (Acct)
    • Balance (Bal)
    • Entry (Ntry)
    • Transaction summary (TxsSummry)
      • EntryDetails (NtryDtls)
        • TransactionDetails (TxDtls)

Each element in the hierarchy contains nested child elements. The following sections explain the most relevant child elements within each parent element.

Example account statement

The following example shows a CAMT.053 account statement file. It includes the group header, account details, an opening booked balance (OPBD), and an entry with its corresponding transaction details.

ISO 20022 Bank Transaction Code

Each transaction entry in a CAMT.053 statement includes a Bank Transaction Code (<BkTxCd>) element, which classifies it using the ISO 20022 structure and helps you identify its type and direction.

ISO 20022 uses a three-tier classification system to define Bank Transaction Codes. This hierarchy moves from broad business areas to granular transaction details:

1. Domain: The broad functional area. Most transactions on Adyen's balance platform use the PMNT (Payments) domain. The PMNT domain also includes additional families, such as CCRD (Customer Card Transactions) for issuing-related transactions. Adyen uses additional domains for specific transaction types:

   • ACMT (Account Management) for interest payouts
   • CAMT (Cash Management) for top-ups

2. Family: The category of transaction, for example, RCDT for Received Credit/Inbound.

3. SubFamily: The specific outcome or method, for example, ACDT for Account Deposit.

The following table explains the codes:

The following example shows how ISO 20022 represents an inbound wire transfer. The <BkTxCd> element combines the Domain, Family, and SubFamily codes to classify the transaction:

Transfers API fields and Bank Transaction Codes

The following table shows how the category, type, and priority fields in the Transfers API map to the ISO 20022 Bank Transaction Code used in the statement. Use this table to correlate transactions between the Transfers API and the CAMT.053 statement.

(Optional) Codes from the Bank Administration Institute

BAI codes are a set of classification codes defined by the Bank Administration Institute. Financial institutions use these codes in the BAI file format to categorize transactions.

When enabled, Adyen includes BAI codes in the CAMT.053 statement to provide additional transaction classification alongside ISO 20022 codes. The following tables cover the codes for active payment and transfer methods.

Credits

These transactions deposit funds into the business account.

Debits

These transactions send or withdraw funds from the business account.

Transactions with Adyen-issued cards

A business account and an Adyen-issued card can be linked to the same balance account. In this case, transactions processed with this Adyen-issued card also appear in the CAMT.053 statement.

(Optional) Summarized account statement

In addition to the standard account statement, Adyen can generate a daily summarized account statement. Financial institutions commonly use this format, which makes reconciliation easier when you process transactions with multiple institutions.

The following table shows the differences between the standard and summarized account statements.

Adyen groups transactions that share a BAI code into one <Ntry> and totals their amounts. For example, 69,493 outbound ACH transactions on the same day all share BAI code 466 and appear as one <Ntry>:

The following table describes the fields in each summarized entry.

See also