Pesquisar

Are you looking for test card numbers?

Would you like to contact support?

Atenção, esta página não se encontra disponível em Português
Reportin icon

Payment accounting report

Use this report for an overview of financial status changes, events, and modifications for all payments.

About this report

This report is based on the time zone setting of your account.
See Downloading reports.

The Payment accounting report is generated every day and includes financial status changes, events, and modifications for all payments. This includes full bookkeeping and user auditing. Use this report to maintain a copy of all available status changes in your own database, and to replicate Adyen's accounting data for financial reporting. 

Download a sample report

Review the sample report before you begin implementing your own process for managing reports. The sample report will give you an example of the kind of data that will be provided in your own reports.

To download a sample Payment accounting report, click here.

Report structure

A report is broken into multiple columns, each of which represent data associated with a payment accounting transaction. Each field takes a specific data type.

To learn how to add additional columns or change the order of columns, refer to Configure report columns.

Standard columns

# Column Data type Description
1 Company Account Unicode Text (80-character) Name of your company account as registered in the plataforma de pagamentos da Adyen.
2 Merchant Account Unicode Text (80-character) Name of your merchant account used to process the original payment request. The report may contain line items for multiple merchant accounts.
3 Psp Reference Unicode Text (16-character) Unique 16 character reference for the payment. This is the PSP reference for the original authorisation request.
4 Merchant Reference Unicode Text (80-character) Reference number provided when initiating the payment request.
5 Payment Method Unicode Text (30-character) Payment method type of the payment which was processed.
For example: visa, mc, amex.
6 Booking Date Date field + Time field Timestamp of when the event took place as entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.
7 TimeZone Alpha Text (4-character limit) Time zone of the Booking Date column. This is the ISO Code for the timezone set on your company account.
To configure for your company account, open the Customer Area and go to Account > Settings.
8 Main Currency Alpha Text (3-character limit) Three character ISO code for the main amount currency.
9 Main Amount Text field Numeric (16-Character limit) While the accounting record may move funds on multiple account "registers", each record type has a primary register which can be seen as a summary of the record.
For example, 100.00.
10 Record Type Unicode Text (50-character) Accounting record type.
For a list of record types, see Record types.
11 Payment Currency Alpha Text (3-character limit) Three character ISO code for the currency which was used for processing the payment.
12 Received (PC) Fixed point number Amount (in Payment Currency) debited or credited on the Received accounting register.
13 Authorised (PC) Fixed point number Amount (in Payment Currency) debited or credited on the Authorised accounting register.
14 Captured (PC) Fixed point number Amount (in Payment Currency) debited or credited on the Captured accounting register.
15 Settlement Currency Alpha Text (3-character limit) Three character ISO code for the currency which was used when settling the payment.
16 Payable (SC) Fixed point number Amount (in Settlement Currency) debited or credited on the Payable accounting register (i.e. funds which will be paid out to your bank account).
17 Commission (SC) Fixed point number 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.
18 Markup (SC) Fixed point number Fee charged by the Acquiring bank (in Settlement Currency).
19 Scheme Fees (SC) Fixed point number Fee that is charged by, for example, Visa / MC (in Settlement Currency).
20 Interchange (SC) Fixed point number Fee charged by the Issuing bank (in Settlement Currency).
21 Processing Fee Currency Alpha Text (3-character limit) Currency in which the processing (or gateway) fee is charged.
22 Processing Fee (FC) Fixed point number Amount (in Processing Fee Currency) charged on the Processing Fee accounting register.
23 User Name Unicode Text (80-character) 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 "system" is used.
24 Payment Method Variant Unicode Text (30-character) Sub brand of the payment method (if applicable).
For example: visaclassic, visadebit, mccorporate.
25 Modification Merchant Reference Unicode Text (80-character) Optional modification reference for modifications like capture or refund.
26 Risk Premium Unicode Text 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.
27 Reserved4 - Reserved for future enhancements.
28 Reserved5 - Reserved for future enhancements.
29 Reserved6 - Reserved for future enhancements.
30 Reserved7 - Reserved for future enhancements.
31 Reserved8 - Reserved for future enhancements.
32 Reserved9 - Reserved for future enhancements.
33 Reserved10 - Reserved for future enhancements.

Additional columns

To learn how to add additional columns, refer to Configure report columns.

Column Data type Description
Acquirer String 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.
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 Acquirer's unique ID for the payment (if provided).
Advanced (PC) Numeric The installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC).
Advancement Batch String The code of the advancement batch.
Advancement Code String The code of the advancement. An advancement code can contain multiple advancement batches.
Advancement Fee % String The calculated fee for the advancement of an installment, in percentage.
ARN String 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).
Booking Date (AMS) Date Timestamp of when the event took place as entered into Adyen's accounting system, in Amsterdam time (CET or CEST). The format is YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.
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.
Card Number String Obfuscated card number showing the card BIN, an obfuscated section and the last four digits.
For example: 411111****1111
Creation Date Date The creation date. The format is YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.
Creation Date (AMS) Date Creation date in Amsterdam time (CET or CEST). The format is YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.
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.
Installments (PC) Numeric The amount of the installment, in payment currency (PC).
Issuer Country Alpha Text (2-character limit) ISO country code where the card was issued.
Issuer Name String Name of the issuing bank, if available.
Merchant Order Reference String 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.
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.
MID String Merchant ID from the Acquirer that was used for processing 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.
Original Amount Numeric The amount of the transaction.
Payable Batch Numeric Sequence number of the payable batch.
Payout Date Date Timestamp indicating the payout date, when available. The format is YYYY-MM-DD HH:MM:SS.
For example: 2012-07-26 19:58:55.
Payment Requester Type String Contains the value autorescue if there was an auto rescue attempt for the payment.
Record Type String Custom field that is a concatenation between Record Type and Booking Type.
Risk Premium Boolean Indicates if Risk Premium was used for the payment.
Shopper Country Alpha Text (2-character limit) ISO country code of the shopper (if available).
Store String Store identifier, as configured in Point of Sale.
Unique Terminal ID C X30 Point of Sale terminal identifier, for example P400Plus-123456789.

Configure report columns

If you want to add additional columns to a report, you can do so in the Customer Area. You can also change the order of columns, for example if this is required by third-party software that you're using.

Changing report columns can have an impact on automatic reconciliation.

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:

  1. Log in to your Customer Area.
  2. Go to Account > Report columns.
    This opens a page with all reports that can be configured. 1
  3. Find the report that you want to configure and select Configure.
  4. Select check boxes to indicate which columns should be included in the report.
  5. Drag the columns into the order you want them to appear in.
  6. Select Save configuration to save your changes.

1 If you don't see the page, go to the report overview page and toggle Automatic generation on for the report for which you want to configure the columns. You can leave automatic generation on, or turn it off again if you don't want to generate the report automatically.

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. For more information, see our FAQ.
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.
Refused Payment was refused, either by the Adyen fraud tool or by the acquirer.
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. For more information, see our FAQ.
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:
  • Initial: A transaction was captured.
  • Representment: You successfully defended a dispute, and we have resumed suspended installments.
  • Retry: A capture failed, and is being retried.
  • Acceleration: The shopper requested a refund, but the amount in the refund request is greater than the amount received, so future installments are accelerated and the installment is closed. See **CloseInstallment**.
CloseInstallment The installment will no longer be sent to the scheme and the OpenInstallment is closed.