Account statements

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.

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 codes for standardized transaction classification.	Enabled or disabled
Summary		Includes a transaction summary block for an overview of totals.	Included or excluded
Date format		Defines which date is used for transactions in the statement.	Value date or booking date

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. The webhook includes the balanceAccount, fileName, and downloadUrl fields.

2. Use the download URL to retrieve the statement file with a GET request.

Account statement elements

Adyen provides account statements in ISO 20022 CAMT.053 format. Each CAMT.053 statement follows a fixed XML hierarchy. This section explains the key blocks and their corresponding XML tags. The CAMT.053 statement has the following high-level structure:

BkToCstmrStmt
    ├─ GrpHdr
    └─ Stmt
        ├─ Acct
        ├─ Bal
        └─ Ntry
            └─ NtryDtls
                └─ TxDtls

BankToCustomerStatement
    ├─ GroupHeader
    └─ Statement
        ├─ Account
        ├─ Balance
        └─ Entry
            └─ EntryDetails
                └─ TransactionDetails

Each block is described below.

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 component reference

In a CAMT.053 account statement, each transaction entry includes a Bank Transaction Code (<BkTxCd>) element. This element classifies the transaction using the ISO 20022 Bank Transaction Code structure. This structure helps you identify the type and direction of the transaction.

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. On Adyen's balance platform, this is always PMNT (Payments).
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:

BAI codes (optional)

BAI codes are a set of classification codes defined by the Bank Administration Institute. They are widely used in the BAI2 file format and are common across banking systems for categorizing transactions. When enabled, BAI codes are included in the CAMT.053 statement to provide additional transaction classification alongside ISO 20022 codes. This mapping focuses on the series used for active payment and transfer methods:

• 100 to 200 series: Successful inbound deposits and credit returns.
• 400 to 500 series: Successful outbound disbursements and debit reversals.

Credits (inbound)

Transactions where funds are deposited into the business account.

Debits (outbound)

Transactions where funds are sent or withdrawn from the business account.

See also