The Settlement details report includes the details of payments that have been settled and paid out to you by Adyen. You can use this report to see the costs of each transaction and perform reconciliation on a transaction level.
File name format: Includes the batch number, date, and/or a unique identifier, depending on how you generate the report.
Generating and downloading: Get this report manually or automatically.
Time zone: The time zone setting of your account.
Multiple reports at once: Generate more than one Settlement details report at a time in your Customer Area.
Availability: Only available for (one or multiple) merchant accounts.
We have migrated to a new technology platform to make report generation faster.
Generate and download reports
You can generate the Settlement details report for one or for multiple merchant accounts. If you select multiple merchant accounts, the generated report will contain settlement data for all merchant accounts that you selected. This can be useful if your business requires reconciliation across multiple merchant accounts, for example in the hospitality or food and beverage industry.
The default setting is to generate the report per merchant account, per batch. Next payout (Payable) batches close according to the payout frequency defined for a merchant account. Any previously configured generation settings and schedules remain unchanged.
To manually or automatically generate a Settlement details report, or download a previously generated report, you need the Merchant Report user role. You need this role for each merchant account that you want to include in the report.
Manually generate a report
To manually generate a report:
-
Log in to your Customer Area, and switch to a merchant account.
-
Select Reports > Settlement details.
-
Select Manage report > Manual (generate once).
-
Under Accounts, configure for which accounts you want to generate the report:
- Current account: generate only for the current merchant account.
- All accounts: generate for all merchant accounts that you have access to.
- Specific accounts: select the merchant accounts to include in the report.
-
Under Data filtering, select one of the following:
- Date: generate for a specific date.
- Single batch: generate a single batch (Current account only).
- Multiple batches: generate multiple batches (Current account only).
-
Under File type, select one of the following:
- CSV (default)
- XLS_GEN
- TSV
- XML
- XMLE
-
Select Generate report. At the top of your screen you will see a pop-up message that says Report is successfully queued.
Automatically generate a report
To automatically generate a report:
-
Log in to your Customer Area, and switch to a merchant account.
-
Select Reports > Settlement details.
-
Select Manage report > Automatic (generate on a schedule).
-
Under Frequency, configure when you want to generate the report:
- Daily
- Weekly > select a day of the week
- Monthly > select a day of the month from the calendar
- At batch close
-
Under Accounts, configure for which accounts you want to generate the report:
- Current account: generate only for the current merchant account.
- All accounts: generate for all merchant accounts that you have access to.
- Specific accounts: select the merchant accounts to include in the report.
-
Under File type, select one of the following:
- CSV (default)
- XLS_GEN
- TSV
- XML
- XMLE
-
Select Schedule.
Download reports
To download a previously generated report:
- Log in to your Customer Area, and switch to a merchant account.
- Select Reports > Settlement details.
- Under Generated reports, select the name of the report you want to download.
The file name and file name format of the report depend on what you selected when you generated the report. See the table for more details.
In general:
- The default file name extension is
.csv
. - If a date is included, the format is
YYYY-MM-DD
. - If a unique identifier is included, it is an eight-character alphanumeric string. This identifier is added to the file name when you generate a report for multiple accounts.
Report type | File name format |
---|---|
Batch closing report | settlement_detail_report_batch_<BATCH_NUMBER> |
Single day report | settlement_detail_report_<REPORT_END_DATE> |
Multiple day report (scheduled reports only) | settlement_detail_report_<REPORT_START_DATE>_<REPORT_END_DATE> |
Sample report
Download a sample Settlement details report for examples of the included data.
Based on your account and settings, a report you generate in your account can contain additional data or columns that are not included in the sample report.
Report structure
Entries
Under the header line, each line in the report is a separate entry. The types of entries include:
Transactions
Each transaction entry shows the status of the transaction. For example: Settled or Chargeback.
TestCompany,TestMerchant,1813702551707653,3vpzf7,visa,2013-06-03 11:26:49,CET,Settled,1713702551795048,GBP,,5.00,1,GBP,,4.88,,0.04,0.01,0.07,visaclassic,,,,,,,,,
TestCompany,TestMerchant,1313642467023511,324959451,visa,2013-03-26 22:37:26,CET,Chargeback,2313642467170922,EUR,349.99,,1,EUR,357.49,,7.5,,,,visaclassic,,,,,,,,,
Transaction fees
The report includes a transaction fee entry for each month that has transactions in the settlement batch.
TestCompany,TestMerchant,,,,2013-06-11 04:55:40,CET,Fee,Transaction Fees May 2013,EUR,,,,GBP,1.46,,,,,,,,,,,,,,,
Deposit corrections
The report includes an entry with the DepositCorrection journal type when a deposit change happens in your account. This can be a credit or a debit.
TestCompany,TestMerchant,,,,2012-05-10 05:37:03,CET,DepositCorrection,Deposit Correction,EUR,,,,EUR,78.93,,,,,,,,,,,,,,,
The report includes another type of deposit correction with the ReserveAdjustment
journal type if your Reserve balance changes.
Invoice deductions
The report includes an entry with the InvoiceDeduction journal type if we debit an amount that you owe or credited an amount that you overpaid. This can include your amount due, point-of-sale terminal hardware costs, and in-person payment service costs.
The entry includes a column with the invoice number associated it and a column with a description explanation.
Descriptive explanations include:
- "Discounts and additional costs" for the amount due from your Payment processing invoice.
- "Terminal hardware sale invoice amount" for point-of-sale terminal hardware sales.
- "Terminal services invoice amount" for in-person payment services.
A deduction is in the debit column, and a credit is in the credit column.
TestCompany,TestMerchant,,,,2013-05-10 12:59:53,CET,InvoiceDeduction,Invoice 201111000553,EUR,,,,EUR,,250.22,,,,,,,4,,,,,,,
Merchant payout
The entry with the MerchantPayout journal type shows the payout from Adyen to your bank account. It includes a reference, batch number, and the bank account.
In this example, Adyen paid out EUR 1842.21 to the TestMerchant merchant account. In your bank account statement, TX4313726XT batch 4, TestMerchant is the transaction message.
TestCompany,TestMerchant,,,,2013-06-11 04:55:40,CET ,MerchantPayout,"TX4313726XT batch 4, TestMerchant batch 4, TestMerchant",EUR,,,,EUR,1842.21,,,,,,,,,,,,,,,
Columns
Each column shows specific information about the entries. By default, the report includes standard columns. You can optionally add additional columns.
Standard columns
The table below reflects the standard columns that are included in the report, and the default order. You can add more columns, or change the order of the default columns.
# | Column | Data type | Description |
---|---|---|---|
1 | Company Account | Unicode Text (80-character) | The name of your company account as registered in the plataforma de pagamentos da Adyen. |
2 | Merchant Account | Unicode Text (80-character) | The name of the merchant account that was used to process the original payment request. |
3 | Psp Reference | Unicode Text (16-character limit) | Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with us about this request. |
4 | Merchant Reference | Unicode Text (80-character) | The reference that was specified in the payment request. |
5 | Payment Method | Unicode Text (30-character) | The payment method used for the transaction. For example: visa, mc, amex. |
6 | Creation Date | Date field + Time field | The timestamp indicating when the payment was created on the plataforma de pagamentos da Adyen. Format: YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
TimeZone | Numeric or String (only in .XLS and .XLSX report files) |
The time zone of the Creation Date. This is the ISO code for your time zone setting. |
|
7 | Type* | Alpha Text (50-character) | The Journal type of the entry. |
8 | Modification Reference* | Unicode Text |
|
9 | Gross Currency* | Alpha Text (3-character limit) | The three-character ISO currency code for the transaction currency. |
Gross Debit (GC)* | Numeric or String (only in .XLS and .XLSX report files) |
The amount submitted in the transaction request. For example, 100.00. |
|
Gross Credit (GC)* | Numeric or String (only in .XLS and .XLSX report files) |
The amount submitted in the transaction request. For example, 100.00. |
|
Exchange Rate | Numeric or String (only in .XLS and .XLSX report files) |
The exchange rate used for converting the gross amount into the net amount. This will be 1 if you process and settle in the same currency. For externally settled payments, the listed exchange rate is Adyen's reference exchange rate, not the actual rate applied by the external acquirer. |
|
10 | Net Currency | Alpha Text (3-character limit) | The three-character ISO currency code for the settlement currency. |
Net Debit (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The net amount debited from the Payable batch. For example, for a Refunded booking, this is the amount sent as part of the refund request plus any additional costs withheld. | |
Net Credit (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The amount submitted in the transaction request minus transaction costs and fees. For example, 98.26. |
|
11 | Commission (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The commission fee that was withheld by the acquirer. This should be the difference between the gross and net amounts.
In this case, the Commission column is empty and columns Markup (12), Scheme Fees (13), and Interchange (14) are populated. For externally settled refunds (for example, American Express refunds), this amount will be negative. If you are automating your reconciliation, make sure your system can handle negative values. |
12 | Markup (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The fee charged by the acquiring bank. If the acquirer does not provide the transaction information at the interchange level, this field is empty. |
13 | Scheme Fees (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The fee charged by, for example, Visa or Mastercard. If the acquirer does not provide the transaction information at the interchange level, this field is empty. |
14 | Interchange (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The fee charged by the issuing bank. If the acquirer doesn't provide the transaction information at the interchange level, this field is empty. |
15 | Payment Method Variant | Unicode Text (50-character) | The sub-brand of the payment method (if applicable). For example: visaclassic, visadebit, mccorporate. |
16 | Modification Merchant Reference | Unicode Text (80-character) | The optional modification reference for modifications, if specified in the transaction. |
17 | Batch Number | Integer | The sequence number of the settlement. |
18 | Reserved4 | - | Reserved for future enhancements. |
19 | Reserved5 | - | Reserved for future enhancements. |
20 | Reserved6 | - | Reserved for future enhancements. |
21 | Reserved7 | - | Reserved for future enhancements. |
22 | Reserved8 | - | Reserved for future enhancements. |
23 | Reserved9 | - | Reserved for future enhancements. |
24 | Reserved10 | - | Reserved for future enhancements. |
Additional columns
You can configure report columns to add these to your report:
Column | Data type | Description |
---|---|---|
Authorised Date | Date | The timestamp indicating when the payment was authorised. Format: YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
Authorised Date TimeZone | Numeric or String (only in .XLS and .XLSX report files) |
The time zone of the Authorised Date. |
Creation Date (AMS) | Numeric or String (only in .XLS and .XLSX report files) |
The Creation Date in Amsterdam time (CET or CEST). Format: YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
Balance Currency | String | The three-character ISO currency code for the balance account currency. This column is only relevant if your company has (split) payments that are partly processed over Adyen for Platforms. |
Net Debit (BC) | Numeric or String (only in .XLS and .XLSX report files) |
The net debit (in Balance Currency) of the balance account. This column is only relevant if your company has (split) payments that are partly processed over Adyen for Platforms. |
Net Credit (BC) | Numeric or String (only in .XLS and .XLSX report files) |
The net credit (in Balance Currency) of the balance account. This column is only relevant if your company has (split) payments that are partly processed over Adyen for Platforms. |
Payment Fees (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The total amount (in Net Currency) in fees, commissions, and interchange costs for the transaction. |
DCC Markup (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The DCC markup (in Net Currency). |
Global Card Brand | String | The brand of the card used for the payment. |
Gratuity Amount | Numeric or String (only in .XLS and .XLSX report files) |
The additional gratuity amount on the payment. |
Surcharge Amount | Numeric or String (only in .XLS and .XLSX report files) |
The surcharge amount on the payment. |
Advanced (NC) | Numeric or String (only in .XLS and .XLSX report files) |
The installment amount that was advanced. This is the gross amount of the advancement fee (in Net Currency). |
Advancement Code | String | The code of the advancement batch. |
Advancement Batch | String | The code of the advancement. An advancement code can occur in multiple batches. |
Booking Type | String | Identifies the transaction/installment that was accelerated or represented. Possible values: FIRST: Installment first/original presentment. ACCELL: Installment accelerated, for example in case of refunds. REPRESENTMENT: Installment second presentment in case of dispute defended. RETRY: If an installment presentment fails, a new one will be created with this booking type. |
Reserved1 | - | Reserved for future enhancements. |
Reserved2 | - | Reserved for future enhancements. |
Reserved3 | - | Reserved for future enhancements. |
Acquirer | String | The name of the acquirer that processed the original payment. For example: Cielo, Redecard. |
Split Settlement | String | Contains detailed information about split settlements in the form of key value pairs. |
Split Payment Data | String | Split payment data for the payment, if applicable. |
Funds Destination | String | This column is only relevant if you are upgrading your Adyen for Platforms integration from the classic Platforms integration. This column shows the destination platform system for each settlement line item. You can use this column to support a period of parallel reconciliation. |
Balance Platform Debit | Numeric or String (only in .XLS and .XLSX report files) |
The total amount debited to the Balance Platform for a split payment. This column is only relevant if your company has (split) payments that are partly processed over Adyen for Platforms. |
Balance Platform Credit | Numeric or String (only in .XLS and .XLSX report files) |
The total amount credited to the Balance Platform for a split payment. This column is only relevant if your company has (split) payments that are partly processed over Adyen for Platforms. |
Booking Date | Date | The timestamp indicating when the event was entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
Booking Date TimeZone | Numeric or String (only in .XLS and .XLSX report files) |
The time zone of the Booking Date. This is the ISO code for your time zone setting. You can view the time zone setting for your company account in the Customer Area > Settings > Account settings. |
Booking Date (AMS) | Numeric or String (only in .XLS and .XLSX report files) |
The timestamp indicating when the event was entered into Adyen's accounting system, in Amsterdam time (CET or CEST). Format: YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
AdditionalType | String | Additional journal type that gives more information about the entry. |
Installments | String | Where installment transactions are applicable, this field will show the installment that this entry pertains to. For example, 6/9 to indicate that this is the sixth of nine installments. |
Issuer Country | Alpha Text (2-character limit) | The ISO country code of the issuer. |
Shopper Country | Alpha Text (2-character limit) | The ISO country code of the shopper, if available. |
Clearing Network | String | The clearing network. For example: Maestro, MasterCard, MoneySend, VISA, VISA Returns, VISA OCT. |
Terminal ID | C X30 | Point-of-sale terminal identifier, for example P400Plus-123456789. |
Tender Reference | C X30 | The tender reference of the point-of-sale payment. |
Merchant Order Reference | String | A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference. |
Metadata | String | Contents from the metadata object related to the payment, in the form of key value pairs. |
Pos Transaction Date | Date field + Time field | The transaction date for a point-of-sale transaction. Format: YYYY-MM-DD HH:MM:SS . For example: 2012-07-26 19:58:55. |
Pos Transaction Date TimeZone | Numeric or String (only in .XLS and .XLSX report files) |
The time zone of the Pos Transaction Date. |
Store | String | The identifier assigned to the store in your point-of-sale account. |
Dispute Reference | String | Adyen's unique 16 character reference for the dispute. |
Register Booking Type | String | This is a custom field, a concatenation between Record Type and Booking Type. |
ARN | String | The Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from your bank (the acquiring bank) to the card scheme at the cardholder's bank (the issuing bank). |
Shopper Reference | String | The shopper ID or reference that was specified in the original transaction. |
Payment Transaction Group | String | A custom value that corresponds with a merchant-specific transaction group. This value is for specific use cases, and can be configured on request via your account manager or our Support Team. |
Settlement Flow | String | The Adyen flow into which the transaction was booked. |
Authorisation Code | String | The authorisation code returned for a successful payment. |
Card Number | String | Obfuscated card number showing the card BIN, an obfuscated section and the last four digits. For example: 411111****1111 |
Configure report columns
If you want to add additional columns or change the order of columns in a report, you can do so in the Customer Area. If you have an automated system that uses the report's data, configuring the report columns can affect your automated system.
To configure report columns, you need to have one of the following user roles:
- Merchant admin
- Merchant report role
- Merchant financial
- Merchant POS Report role
To configure report columns:
- Log in to your Customer Area.
- Go to Settings > Report columns.
This opens a page with all the reports that you can configure. - Find the report that you want to configure and select Configure.
- Select checkboxes to indicate which columns you want to include in the report.
- Drag the columns into the order you want them to appear in.
- Select Save configuration.
Journal types
The journal types listed below correspond to the Type field in the report structure above.
Journal Type | Occurrence | Description |
---|---|---|
Fee* | Debit | The Adyen transaction fees for Received and SentForRefund transactions booked during the specified batch period. |
MiscCosts* | Debit/Credit | The costs from externally settled payments that could not be matched with any specific transactions. |
MerchantPayout* | Debit | The amount that is paid for a settlement currency from the payout batch to your bank account. |
Refunded | Debit | A debit for a payment that was SentForRefund. |
Settled | Credit | A credit for a payment that was SentForSettle. |
Chargeback | Debit | A debit for a payment that is reversed by the bank/scheme/consumer. |
SecondChargeback | A debit | Debit for an unsuccessful defense of a first chargeback. |
ChargebackReversed | Credit | A previous chargeback that is credited to you after a payment is successfully defended, or after the shopper re-pays the funds. |
RefundedReversed | Credit | A refund that is returned to our account because it cannot be credited to the shopper by the scheme/bank or is returned by the shopper. |
DepositCorrection* | Debit/Credit | The funds being withheld from/released to the account due to a change in the required security deposit (coverage of the exposure on the account). |
InvoiceDeduction* | Debit/Credit | A payment processing invoice that is credited/deducted from the account.If an invoice includes VAT/GST charges, you will see two separate bookings: costs/discounts and taxes. Details are specified in the Modification Reference column. |
MatchedStatement | Debit/Credit | A wire transfer from merchant booked in the account. |
ManualCorrected | Debit/Credit | A manual booking/adjustment by Adyen. |
BankInstructionReturned | Credit | A credit for previous merchant payouts that were not processed successfully or that were returned to Adyen. |
EpaPaid | Debit/Credit | An Electronic Payment Advice (EPA) from an external acquirer that was confirmed by the acquirer but not settled through Adyen. |
Balancetransfer | Debit/Credit | A balance transfer to or from subsequent payout batches in order to process negative payable/capture balances or for batches that could not be paid out. |
PaymentCost | Debit/Credit | The PaymentCost journal type is used only to book the following fees:
|
PaidOut | Debit | The net debit for a payout that was SentForPayout. |
PaidOutReversed | Credit | A payout returned to Adyen's account because it could not be credited to the shopper by the scheme/bank or is returned by the shopper. |
RefundedInstallment | Debit | The debit amount for a payment that was SentForRefund. This journal is used for credit transactions using an Adyen installments-capable acquirer (like Brazil and Mexico), regardless of whether the transaction is one-off or an installment. |
SettledInstallment | Credit | The credit amount being settled for a credit card transaction created in installments. For installment-based transactions, the settled credit amount does not equal the whole amount that was SentForSettle. When it is a one-off transaction, then the credit amount that will be settled for this payment will equal the whole amount that was SentForSettle. If you have made an advancement, then the credit amount for this journal SettledInstallment will be zero. |
SuspendInstallment | Debit | Indicates that submitting subsequent installments to the scheme has been suspended due to a chargeback requested by the issuing bank. If you have made an advancement of the installment settlement, then this journal will appear in the Settlement details report to indicate the debit to compensate the advanced amount. |
CaptureFailed (Sales Day payout) | Debit | Capturing funds has failed for a transaction. In other words, these funds will not be received yet from the card scheme or payment method. A debit booking will be made to the next payout, because Adyen doesn't receive the pre-financed transaction amount from the card scheme or payment method. |
RefundFailed (Sales Day payout) | Credit | A refund to a card or payment method has failed. If your account has already been debited for the refund, a credit booking is made to the next merchant payout (because Adyen will not have to pay for the refunded amount). |
RefundNotCleared (Sales Day payout) | Credit | A refund hasn't been settled because the acquirer hasn't processed the refund 30 days after initiation. However, the customer has received the funds. No action is needed; adjustments to your balance happen automatically. If the refund is processed after 30 days, you will see an additional Refunded booking. This journal type was formerly called RefundNotProcessed. |
SettledReversed (Sales Day payout) | Debit | A debit that reverses a Settled transaction for which Adyen hasn't received the funds from the card scheme or payment method within 30 days of capture. No action is needed; adjustments to your balance happen automatically. If Adyen receives the funds after 30 days, you will see an additional Settled booking. |
MerchantPayin | Credit | A credit transfer or direct debit booked in the account to fund the Reserve. |
ReserveAdjustment | Debit/Credit | The funds being withheld from or released to the account due to funding or for using the Reserve register. |
MerchantPayinReversed | Debit | A payment that was meant to top up or fund an account, goes through a chargeback. |
XASTransfer | Debit | The funds debited to your platform's liable account. Used in classic Adyen for Platforms integrations. For more information, refer to Reconcile your platform's accounts receivable. |
*The data type for these fields is Unicode Text (80-character) instead of Alpha Text (50-character).