The Payment accounting report includes Payments lifecycle status changes, events, and modifications for all transactions. You can use this report to see the costs associated with different statuses and perform invoice reconciliation.
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 Payment accounting report at a time in your Customer Area.
Availability: Available for company accounts and merchant accounts.
Interactive payment accounting report
You can manually generate the Interactive payment accounting report. For this report, you can select the date range, the time zone, and the columns you want to include. Every time you manually generate the Interactive payment accounting report, any previously generated report is overwritten.
You can generate the Interactive payment accounting report using the time zone setting of your account, or Central European Time. If you want to use the report to reconcile your payment processing invoice, select the first day of the month until the first day of the next month, select 00:00:00 for both days, and select Central European Time. This because your invoice is always based on the CET time zone.
Because it is interactive, this report contains different columns than the Payment accounting report. Download a sample Interactive payment accounting report for an example.
We have migrated to a new technology platform to make report generation faster. You may have to update your data ingestion pipeline if you automatically ingest report data. To determine if you have to take action, check the migration overview.
Sample
Download a sample Payment accounting 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.
Columns
Each column shows specific information about the entries. By default, the report includes standard columns. You can optionally add additional columns.
Standard 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. The report may contain line items for multiple merchant accounts. |
| 3 | Psp Reference | Unicode Text (16-character) | 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 (50-character) | The payment method used for the transaction. For example: visa, mc, amex. |
| 6 | Booking Date | Date field + Time field | The timestamp indicating when the event was entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS. For example: 2021-07-26 19:58:55. |
| TimeZone | Alpha Text (4-character limit) | The time zone of the Booking Date column. This is the ISO code for your time zone setting. |
|
| 7 | Main Currency | Alpha Text (3-character limit) | The three-character ISO code for the currency of the main amount. |
| Main Amount | Text field Numeric (16-Character limit) | The amount recorded when the transaction reaches the Record Type. For example, the main amount of a Settled transaction is the amount after deducting payment processing fees. |
|
| 8 | Record Type | Unicode Text (50-character) | The accounting record type. For a list of record types, see Record types. |
| 9 | Payment Currency | Alpha Text (3-character limit) | The three-character ISO code for the currency that was used to process the payment. |
| 10 | Received (PC) | Fixed point number | The amount (in Payment Currency) debited or credited on the Received accounting register. |
| 11 | Authorised (PC) | Fixed point number | The amount (in Payment Currency) debited or credited on the Authorised accounting register. |
| 12 | Captured (PC) | Fixed point number | The amount (in Payment Currency) debited or credited on the Captured accounting register. |
| 13 | Settlement Currency | Alpha Text (3-character limit) | The three-character ISO code for the currency that was used when settling the payment. |
| 14 | Payable (SC) | Fixed point number | The amount (in Settlement Currency) debited or credited on the Payable accounting register. This will be paid out to your bank account. |
| 15 | Commission (SC) | Fixed point number | The commission fee that was withheld by the acquirer (in Settlement Currency) If the acquirer provides the transaction information at the interchange level, Adyen will split the commission into the Markup, Scheme Fees and Interchange registers instead. |
| 16 | Markup (SC) | Fixed point number | The fee charged by the acquiring bank (in Settlement Currency). |
| 17 | Scheme Fees (SC) | Fixed point number | The fee charged by, for example, Visa or Mastercard (in Settlement Currency). |
| 18 | Interchange (SC) | Fixed point number | The fee charged by the issuing bank (in Settlement Currency). |
| 19 | Processing Fee Currency | Alpha Text (3-character limit) | The three-character ISO code for the currency in which the processing (or gateway) fee is charged. |
| 20 | Processing Fee (FC) | Fixed point number | The amount (in Processing Fee Currency) charged on the Processing Fee accounting register. |
| 21 | User Name | Unicode Text (80-character) | The user (interactive or webservice user) who performed the action resulting in the accounting record. If the record was created by an automated internal process, the value will be system. |
| 22 | Payment Method Variant | Unicode Text (50-character) | The sub-brand of the payment method (if applicable). For example: visaclassic, visadebit, mccorporate. |
| 23 | Modification Merchant Reference | Unicode Text (80-character) | The optional modification reference for modifications, if specified in the transaction. |
| 24 | Reserved3 | - | Reserved for future enhancements. |
| 25 | Reserved4 | - | Reserved for future enhancements. |
| 26 | Reserved5 | - | Reserved for future enhancements. |
| 27 | Reserved6 | - | Reserved for future enhancements. |
| 28 | Reserved7 | - | Reserved for future enhancements. |
| 29 | Reserved8 | - | Reserved for future enhancements. |
| 30 | Reserved9 | - | Reserved for future enhancements. |
| 31 | Reserved10 | - | Reserved for future enhancements. |
Additional columns
You can configure report columns to add these to your report:
| Column | Data type | Description |
|---|---|---|
| Booking Date (AMS) | Date | 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. |
| Creation Date | Date | 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. |
| Creation Date (AMS) | Date | The Creation Date in Amsterdam time (CET or CEST). Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55. |
| Payable Batch | Numeric | The sequence number of the payout batch. |
| Payout Date | Date | The timestamp indicating the payout date, when available. Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55. |
| Gratuity Amount | Numeric | The additional gratuity amount on the payment. |
| Surcharge Amount | Numeric | The surcharge amount on the payment. |
| DCC Markup (SC) | Numeric | The DCC markup (in Settlement Currency). |
| ICFS details | String | The detailed specification of each applicable interchange and scheme fee for the payment, if available. |
| Global Card Brand | String | The brand of the card used for the payment. |
| Issuer Country | Alpha Text (2-character limit) | The two-character ISO country code where the card was issued. |
| Shopper Country | Alpha Text (2-character limit) | The two-character ISO country code of the shopper, if available. |
| Card Number | String | Obfuscated card number showing the card BIN, an obfuscated section and the last four digits. For example: 411111****1111 |
| Funding Source | String | The card funding source. Possible values:
|
| Acquirer | String | The name of the acquirer that processed the original payment. For example: Cielo, Redecard. |
| Acquirer Account | String | The acquirer account that was used for the transaction. |
| MID | String | The Merchant ID from the acquirer that was used to process the payment. |
| Acquirer Auth Code | String | The Acquirer Authorisation Code. Can be included and used to match Auth Code on the merchant gateway side with the Auth Code in this report. |
| Acquirer Reference | String | The acquirer's unique ID for the payment, if provided. |
| ARN | String | The Acquirer Reference Number, a unique number that tags a credit card transaction when it goes from your bank (The Acquiring Bank) through to the card scheme at the cardholder's bank (The Issuer). |
| Original Amount | Numeric | The amount of the transaction. |
| Installments (PC) | Numeric | The amount of the installment, in payment currency (PC). |
| Advanced (PC) | Numeric | The installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC). |
| Advancement Code | String | The code of the advancement. An advancement code can contain multiple advancement batches. |
| Advancement Batch | String | The code of the advancement batch. |
| 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: In the scenario an installment presentment fails, a new one will be created with this booking type. |
| Advancement Fee % | String | The calculated fee for the advancement of an installment, in percentage. |
| Installments | String | Where installment transactions are applicable, this field will show the installment that this line item pertains to. For example, 6/9 to indicate that this is the 6th of 9 installments. |
| Unique Terminal ID | C X30 | Point-of-sale terminal identifier, for example P400Plus-123456789. |
| Metadata | String | The contents of the metadata object of the payment, in the form of key value pairs. |
| Merchant Order Reference | String | A reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference. |
| Payment Requester Type | String | Contains the value autorescue if there was an auto rescue attempt for the payment. |
| Network Token Used | String | If true, a network token was used to authorise the payment. |
| Network Token Available | String | If true, a network token was available for use for the payment. |
| Store | String | The store identifier, as configured in point-of-sale. |
| Issuer Name | String | Name of the issuing bank, if available. |
| Risk Premium | Boolean | For payments where the Record Type is Received, the value of this field indicates if the payment triggered RevenueProtect checks (resulting in charges on your invoice). Possible values: true - A risk fee is charged. false - A risk fee is not charged. |
| Record Type | String | Custom field that is a concatenation between Record Type and Booking Type. |
| Modification Psp Reference | String | In most instances, this is Adyen's unique 16 character code child reference that is associated with the modification request (capture, refund, chargebacks, etc). This will be returned to you via the direct soap response of the modification request and the notification server. For Unmatched transactions, this field may be populated with a reference from the acquiring bank and the Data Type format may vary to match the format of the acquiring bank. |
| Split Payment Data | String | Split payment data for the payment, if applicable. |
| Exchange Rate | Numeric | The exchange rate for the payment. |
| Payment Account Reference | String | The Payment Account Reference is a unique identifier that links a network token with the underlying primary account number (PAN). |
| Tender Reference | String | The tender reference of the point-of-sale payment. |
| Shopper Reference | String | The shopper ID or reference that was specified in the original transaction. |
| Shopper Name | String | The name of the cardholder, as specified in the transaction, if available. |
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.
Record types
| Record Type | Description |
|---|---|
|
Authorised |
Payment approved by the financial institution. |
|
AuthorisedPending |
Payment authorisation is pending acceptance from the issuer. |
|
Cancelled |
Transaction cancelled. |
|
CaptureFailed |
Capture of a payment failed. For more information, refer to Failed capture. |
|
Chargeback |
Payment reversed by the bank/scheme/consumer. |
|
SecondChargeback |
Unsuccessful defense of first chargeback. |
|
ChargebackExternally |
Payment booked as a chargeback with external acquirer. |
|
ChargebackExternallyWithInfo |
Payment booked as a chargeback with external acquirer. |
|
ChargebackReversed |
Chargeback defended successfully, or the shopper re-paid the funds. |
|
ChargebackReversedExternallyWithInfo |
Chargeback defended successfully, or the shopper re-paid the funds. |
|
Error |
Transaction error. |
|
Expired |
Payment not captured within time limits. |
|
PaidOut |
Payout successfully completed. |
|
PaidOutExternally |
Payout successfully completed with external acquirer. |
|
PaidOutExternallyWithInfo |
Payout successfully completed with external acquirer. |
|
PaidOutReversed |
Payout returned to Adyen's account as it could not be credited to the shopper. |
|
PayoutAuthorised |
Payout successfully authorised. |
|
PayoutError |
Payout that resulted in an error. |
|
PayoutFailed |
Payout request was returned by the acquirer. |
|
Received |
Registration of a validated payment attempt. |
|
ReceivedPayout |
Payout received by the plataforma de pagamentos da Adyen. |
|
RefundAuthorised |
Refund successfully authorised. |
|
Refunded |
Payment successfully refunded. |
|
RefundedBulk |
Payment successfully refunded through Adyen Acquiring. This journal type will be deprecated. |
|
RefundedExternally |
Payment successfully refunded through an external acquirer. |
|
RefundedExternallyWithInfo |
Payment successfully refunded through an external acquirer. |
|
RefundFailed |
The refund failed. For more information, refer to Failed refund. |
|
RefundedInInstallments |
Payment has been fully refunded in installments. |
|
RefundedInstallment |
Payment installment has been refunded. |
|
RefundedReversed |
Refund returned to Adyen's account as it could not be credited to the shopper. |
|
RefundNotProcessed |
Refund has not been settled because the acquirer has not process the refund 30 days after initiation; however, the customer has received the funds. If the refund is processed after 30 days, you will see an additional Refunded record. |
|
Refused |
Payment was refused, either by the acquirer or by the Adyen fraud tool. |
|
RefusedPayout |
Payout was refused, either by the Adyen fraud tool or by the acquirer. |
|
Retried |
Payment request was retried. |
|
SentForPayout |
Payment sent for payout by the acquirer. |
|
SentForRefund |
Payment sent for refund by the acquirer. |
|
SentForSettle |
Request to transfer the payment sent to the financial institution. |
|
Settled |
Payment has been settled, and the funds have been received by Adyen. |
|
SettledBulk |
Payment has been settled through Adyen Acquiring. This journal type will be deprecated. |
|
SettledExternally |
Payment has been settled with an external acquirer. |
|
SettledExternallyWithInfo |
Payment has been settled with an external acquirer. |
|
SettledInInstallments |
Payment has been fully captured in installments. |
|
SettledInstallmentSuspendInstallment |
Payment installment has been settled. |
|
SettledReversed |
Payment has not been settled because Adyen has not received the funds 30 days after capture. If Adyen receives the funds more than 30 days after capture, then you will see a Settled record. |
|
SuspendInstallment |
The installment will no longer be sent to the scheme due to a dispute in the transaction. |
|
AdvancedInstallment |
The installment was advanced. |
|
AdvancedInstallmentCancelled |
The advancement of the installment was cancelled. |
|
OpenInstallment |
An installment is still open.
There are 4 possible states of an OpenInstallment:
|
|
CloseInstallment |
The installment will no longer be sent to the scheme and the OpenInstallment is closed. |