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.
Get the report
To generate and download the report, you must have the Merchant report user role.
- Log in to Essentials.
- Go to Finances > Interactive payment accounting.
- Select Generate report and select the date range.
Under the header line, each line in the report is a separate entry.
|1||Company Account||Unicode Text (80-character)||Name of your company account as registered in the Adyen payments platform.|
|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)||Adyen's 16-character unique reference associated with the transaction. This is the pspReference from the response to the original payment request.|
|4||Merchant Reference||Unicode Text (80-character)||Your reference for the transaction. This is the reference from the original payment request.|
|5||Payment Method||Unicode Text (50-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: 2021-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 Settings > 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)||The amount recorded when the transaction reaches the Record Type. For example, the main amount of a
|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. This 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 (50-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.|
|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).
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.|
|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.
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 payout 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
|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.|
|Authorised||Payment approved by the financial institution.|
|AuthorisedPending||Payment authorisation is pending acceptance from the issuer.|
|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.|
|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 Adyen payments platform.|
|RefundAuthorised||Refund successfully authorised.|
|Refunded||Payment successfully refunded.|
|RefundedBulk||Payment successfully refunded through Adyen Acquiring.|
|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.|
|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.|
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.|