{"title":"Interactive payment accounting report","category":"default","creationDate":1778669839,"content":"
\n
Time zones<\/h5>

This report is based on the time zone setting of your account.<\/p><\/div><\/div>\n\n

The Payment accounting report includes Payments lifecycle<\/a> 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.<\/p>\n

Get the report<\/h2>\n

To generate and download the report, you must have the Merchant report<\/strong> user role.<\/p>\n

    \n
  1. Log in to Essentials<\/a>.<\/li>\n
  2. Go to Finances<\/strong> > Interactive payment accounting<\/strong>.<\/li>\n
  3. Select Generate report<\/strong> and select the date range.<\/li>\n<\/ol>\n

    Report structure<\/h2>\n

    Entries<\/h3>\n

    Under the header line, each line in the report is a separate entry.<\/p>\n

    Columns<\/h3>\n

    Each column shows specific information about the entries. By default, the report includes standard columns<\/a>. You can optionally add additional columns<\/a>.<\/p>\n

    Standard columns<\/h4>\n
    \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    #<\/th>\nColumn<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    1<\/td>\nCompany Account<\/td>\nUnicode Text (80-character)<\/td>\nThe name of your company account as registered in the Adyen payments platform.<\/td>\n<\/tr>\n
    2<\/td>\nMerchant Account<\/td>\nUnicode Text (80-character)<\/td>\nThe name of the merchant account that was used to process the original payment request.
    The report may contain line items for multiple merchant accounts.<\/td>\n<\/tr>\n
    3<\/td>\nPsp Reference<\/td>\nUnicode Text (16-character)<\/td>\nAdyen's 16-character unique reference associated with the transaction\/the request.\u00a0This value is globally unique; quote it when communicating with us about this request.<\/td>\n<\/tr>\n
    4<\/td>\nMerchant Reference<\/td>\nUnicode Text (80-character)<\/td>\nThe reference that was specified in the payment request.<\/td>\n<\/tr>\n
    5<\/td>\nPayment Method<\/td>\nUnicode Text (50-character)<\/td>\nThe payment method used for the transaction.
    For example: visa<\/em>, mc<\/em>, amex<\/em>.<\/td>\n<\/tr>\n
    6<\/td>\nBooking Date<\/td>\nDate field + Time field<\/td>\nThe timestamp indicating when the event was entered into Adyen's accounting system. The format is YYYY-MM-DD HH:MM:SS<\/code>.
    For example: 2021-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
    <\/td>\nTimeZone<\/td>\nAlpha Text (4-character limit)<\/td>\nThe time zone of the Booking Date<\/strong> column.
    This is the ISO code for your time zone setting<\/a>.<\/td>\n<\/tr>\n
    7<\/td>\nMain Currency<\/td>\nAlpha Text (3-character limit)<\/td>\nThe three-character ISO code<\/a> for the currency of the main amount.<\/td>\n<\/tr>\n
    <\/td>\nMain Amount<\/td>\nText field Numeric (16-Character limit)<\/td>\nThe amount recorded when the transaction reaches the Record Type<\/strong>. For example, the main amount of a Settled<\/code> transaction is the amount after deducting payment processing fees.<\/td>\n<\/tr>\n
    8<\/td>\nRecord Type<\/td>\nUnicode Text (50-character)<\/td>\nThe accounting record type.
    For a list of record types, see Record types<\/a>.<\/td>\n<\/tr>\n
    9<\/td>\nPayment Currency<\/td>\nAlpha Text (3-character limit)<\/td>\nThe three-character ISO code<\/a> for the currency that was used to process the payment.<\/td>\n<\/tr>\n
    10<\/td>\nReceived (PC)<\/td>\nFixed point number<\/td>\nThe amount (in Payment Currency) debited or credited on the Received accounting register.<\/td>\n<\/tr>\n
    11<\/td>\nAuthorised (PC)<\/td>\nFixed point number<\/td>\nThe amount (in Payment Currency) debited or credited on the Authorised accounting register.<\/td>\n<\/tr>\n
    12<\/td>\nCaptured (PC)<\/td>\nFixed point number<\/td>\nThe amount (in Payment Currency) debited or credited on the Captured accounting register.<\/td>\n<\/tr>\n
    13<\/td>\nSettlement Currency<\/td>\nAlpha Text (3-character limit)<\/td>\nThe three-character ISO code<\/a> for the currency that was used when settling the payment.<\/td>\n<\/tr>\n
    14<\/td>\nPayable (SC)<\/td>\nFixed point number<\/td>\nThe amount (in Settlement Currency) debited or credited on the Payable accounting register. This will be paid out to your bank account.<\/td>\n<\/tr>\n
    15<\/td>\nCommission (SC)<\/td>\nFixed point number<\/td>\nThe 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.<\/td>\n<\/tr>\n
    16<\/td>\nMarkup (SC)<\/td>\nFixed point number<\/td>\nThe fee charged by the acquiring bank (in Settlement Currency).<\/td>\n<\/tr>\n
    17<\/td>\nScheme Fees (SC)<\/td>\nFixed point number<\/td>\nThe fee charged by, for example, Visa or Mastercard (in Settlement Currency).<\/td>\n<\/tr>\n
    18<\/td>\nInterchange (SC)<\/td>\nFixed point number<\/td>\nThe fee charged by the issuing bank (in Settlement Currency).<\/td>\n<\/tr>\n
    19<\/td>\nProcessing Fee Currency<\/td>\nAlpha Text (3-character limit)<\/td>\nThe three-character ISO code<\/a> for the currency in which the processing (or gateway) fee is charged.<\/td>\n<\/tr>\n
    20<\/td>\nProcessing Fee (FC)<\/td>\nFixed point number<\/td>\nThe amount (in Processing Fee Currency) charged on the Processing Fee accounting register.<\/td>\n<\/tr>\n
    21<\/td>\nUser Name<\/td>\nUnicode Text (80-character)<\/td>\nThe 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<\/em>.<\/td>\n<\/tr>\n
    22<\/td>\nPayment Method Variant<\/td>\nUnicode Text (50-character)<\/td>\nThe sub-brand of the payment method (if applicable).
    For example: visaclassic<\/em>, visadebit<\/em>, mccorporate<\/em>.<\/td>\n<\/tr>\n
    23<\/td>\nModification Merchant Reference<\/td>\nUnicode Text (80-character)<\/td>\nThe optional modification reference for modifications<\/a>, if specified in the transaction.<\/td>\n<\/tr>\n
    24<\/td>\nReserved3<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    25<\/td>\nReserved4<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    26<\/td>\nReserved5<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    27<\/td>\nReserved6<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    28<\/td>\nReserved7<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    29<\/td>\nReserved8<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    30<\/td>\nReserved9<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
    31<\/td>\nReserved10<\/td>\n-<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

    Additional columns<\/h3>\n
    \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Column<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    Booking Date (AMS)<\/td>\nDate<\/td>\nThe 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<\/code>.
    For example: 2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
    Creation Date<\/td>\nDate<\/td>\nThe timestamp indicating when the payment was created on the Adyen payments platform. Format: YYYY-MM-DD HH:MM:SS<\/code>.
    For example: 2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
    Creation Date (AMS)<\/td>\nDate<\/td>\nThe Creation Date<\/strong> in Amsterdam time (CET or CEST). Format: YYYY-MM-DD HH:MM:SS<\/code>.
    For example: 2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
    Payable Batch<\/td>\nNumeric<\/td>\nThe sequence number of the payout batch.<\/td>\n<\/tr>\n
    Payout Date<\/td>\nDate<\/td>\nThe timestamp indicating the payout date, when available. Format: YYYY-MM-DD HH:MM:SS<\/code>.
    For example: 2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
    Gratuity Amount<\/td>\nNumeric<\/td>\nThe additional gratuity amount on the payment.<\/td>\n<\/tr>\n
    Surcharge Amount<\/td>\nNumeric<\/td>\nThe surcharge amount on the payment.<\/td>\n<\/tr>\n
    DCC Markup (SC)<\/td>\nNumeric<\/td>\nThe DCC markup (in Settlement Currency).<\/td>\n<\/tr>\n
    ICSF details<\/td>\nString<\/td>\nThe detailed specification of each applicable interchange and scheme fee for the payment, if available. The data is included in this columns in JSON format, with an object for each fee applied to the transaction. Each object contains key-value pairs that provide the fee level information. For the key definitions, see ICSF key definitions<\/a>.<\/td>\n<\/tr>\n
    Global Card Brand<\/td>\nString<\/td>\nThe brand of the card used for the payment.<\/td>\n<\/tr>\n
    Issuer Country<\/td>\nAlpha Text (2-character limit)<\/td>\nThe two-character ISO 3166-1 alpha-2 country code where the card was issued.<\/td>\n<\/tr>\n
    Shopper Country<\/td>\nAlpha Text (2-character limit)<\/td>\nThe two-character ISO country code of the shopper, if available.<\/td>\n<\/tr>\n
    Card Number<\/td>\nString<\/td>\nObfuscated card number showing the card BIN, an obfuscated section, and the last four digits.
    For example: 411111****1111<\/em><\/td>\n<\/tr>\n
    Funding Source<\/td>\nString<\/td>\nThe card funding source.
    Possible values:
    • CHARGE<\/li>
    • CREDIT<\/li>
    • DEBIT<\/li>
    • DEFERRED_DEBIT<\/li>
    • PREPAID<\/li>
    • PREPAID_RELOADABLE<\/li>
    • PREPAID_NONRELOADABLE<\/li><\/ul><\/td>\n<\/tr>\n
    Acquirer<\/td>\nString<\/td>\nThe name of the acquirer that processed the original payment. For example: Cielo<\/em>, Redecard<\/em>.<\/td>\n<\/tr>\n
    Acquirer Account<\/td>\nString<\/td>\nThe acquirer account that was used for the transaction.<\/td>\n<\/tr>\n
    MID<\/td>\nString<\/td>\nThe Merchant ID from the acquirer that was used to process the payment.<\/td>\n<\/tr>\n
    Acquirer Auth Code<\/td>\nString<\/td>\nThe Acquirer Authorisation Code. Can be included and used to match Auth Code on the merchant gateway side with the Auth Code in this report.<\/td>\n<\/tr>\n
    Acquirer Reference<\/td>\nString<\/td>\nThe acquirer's unique ID for the payment, if available.<\/td>\n<\/tr>\n
    ARN<\/td>\nString<\/td>\nThe 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).<\/td>\n<\/tr>\n
    Original Amount<\/td>\nNumeric<\/td>\nThe amount of the transaction.<\/td>\n<\/tr>\n
    Installments (PC)<\/td>\nNumeric<\/td>\nThe amount of the installment, in payment currency (PC).<\/td>\n<\/tr>\n
    Advanced (PC)<\/td>\nNumeric<\/td>\nThe installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC).<\/td>\n<\/tr>\n
    Advancement Code<\/td>\nString<\/td>\nThe code of the advancement. An advancement code can contain multiple advancement batches.<\/td>\n<\/tr>\n
    Advancement Batch<\/td>\nString<\/td>\nThe code of the advancement batch.<\/td>\n<\/tr>\n
    Booking Type<\/td>\nString<\/td>\nIdentifies the transaction\/installment that was accelerated or represented.
    Possible values:
    FIRST<\/em>: Installment first\/original presentment.
    ACCELL<\/em>: Installment accelerated, for example in case of refunds.
    REPRESENTMENT<\/em>: Installment second presentment in case of dispute defended.
    RETRY<\/em>: If an installment presentment fails, a new one will be created with this booking type.<\/td>\n<\/tr>\n
    Advancement Fee %<\/td>\nString<\/td>\nThe calculated fee for the advancement of an installment, as a percentage.<\/td>\n<\/tr>\n
    Installments<\/td>\nString<\/td>\nWhere 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.<\/td>\n<\/tr>\n
    Unique Terminal ID<\/td>\nC X30<\/td>\nPoint-of-sale terminal identifier, for example P400Plus-123456789<\/em>.<\/td>\n<\/tr>\n
    Metadata<\/td>\nString<\/td>\nThe contents of the metadata<\/a> object of the payment, in the form of key-value pairs.<\/td>\n<\/tr>\n
    Merchant Order Reference<\/td>\nString<\/td>\nA reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference<\/a>.<\/td>\n<\/tr>\n
    Payment Requester Type<\/td>\nString<\/td>\nContains the value autorescue<\/code> if there was an auto rescue attempt for the payment.<\/td>\n<\/tr>\n
    Network Token Used<\/td>\nString<\/td>\nIf true, a network token was used to authorize the payment.<\/td>\n<\/tr>\n
    Network Token Available<\/td>\nString<\/td>\nIf true, a network token was available for the payment.<\/td>\n<\/tr>\n
    Store<\/td>\nString<\/td>\nThe store identifier, as configured in point-of-sale.<\/td>\n<\/tr>\n
    Issuer Name<\/td>\nString<\/td>\nName of the issuing bank, if available.<\/td>\n<\/tr>\n
    Risk Premium<\/td>\nBoolean<\/td>\nFor payments where the Record Type is Received<\/strong>, the value of this field indicates if the payment triggered RevenueProtect checks (resulting in charges on your invoice).
    Possible values:
    true<\/strong> - A risk fee is charged.
    false<\/strong> - A risk fee is not charged.<\/td>\n<\/tr>\n
    Record Type<\/td>\nString<\/td>\nCustom field that is a concatenation between Record Type<\/strong> and Booking Type<\/strong>.<\/td>\n<\/tr>\n
    Modification Psp Reference<\/td>\nString<\/td>\nIn most instances, this is Adyen's unique 16 character code child reference that is associated with the modification request, for example, capture, refund, or chargeback. This is returned to you through the direct API response of the modification request and webhooks.
    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.<\/td>\n<\/tr>\n
    Split Payment Data<\/td>\nString<\/td>\nSplit payment data for the payment, if applicable.<\/td>\n<\/tr>\n
    Exchange Rate<\/td>\nNumeric<\/td>\nThe exchange rate for the payment.<\/td>\n<\/tr>\n
    Payment Account Reference<\/td>\nString<\/td>\nThe Payment Account Reference is a unique identifier that links a network token<\/a> with the underlying primary account number (PAN).<\/td>\n<\/tr>\n
    Tender Reference<\/td>\nString<\/td>\nThe tender reference of the point-of-sale payment.<\/td>\n<\/tr>\n
    Shopper Reference<\/td>\nString<\/td>\nThe shopper ID or reference that was specified in the original transaction.<\/td>\n<\/tr>\n
    Shopper Name<\/td>\nString<\/td>\nThe name of the cardholder, as specified in the transaction, if available.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

    ICSF key definitions<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Label<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    t<\/strong><\/td>\nThe type of the fee. Possible values:
    • ic<\/strong>: Interchange<\/li>
    • sf<\/strong>: Scheme fee<\/li><\/ul><\/td>\n<\/tr>\n
    n<\/strong><\/td>\nThe name of the fee.<\/td>\n<\/tr>\n
    ipc<\/strong><\/td>\nThe interchange program code (IPC). Its value varies based on the scheme.<\/td>\n<\/tr>\n
    fc<\/strong><\/td>\nThe total amount of the scheme fee (fixed and variable).<\/td>\n<\/tr>\n
    fq<\/strong><\/td>\nThe amount of the fixed fee.<\/td>\n<\/tr>\n
    bps<\/strong><\/td>\nThe amount of the variable fee, in basis points. For example, 20 bps equals 0.20%.<\/td>\n<\/tr>\n
    min<\/strong><\/td>\nThe minimum amount of the fee.<\/td>\n<\/tr>\n
    max<\/strong><\/td>\nThe maximum possible amount of the fee.<\/td>\n<\/tr>\n
    ccy<\/strong><\/td>\nThe currency of the fee.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Record types<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n\n\n
    Record Type<\/th>\n\nDescription<\/th>\n\n<\/tr>\n\n<\/thead>\n\n
    \n

    AuthenticationRequested<\/p>\n<\/td>\n\n

    		\n

    Authentication (3D Secure 2) was attempted.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Authorised<\/p>\n<\/td>\n\n

    		\n

    Payment approved by the financial institution.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    AuthorisedPending<\/p>\n<\/td>\n\n

    		\n

    Payment authorisation is pending acceptance from the issuer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Cancelled<\/p>\n<\/td>\n\n

    		\n

    Transaction cancelled.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    CaptureFailed<\/p>\n<\/td>\n\n

    		\n

    Capture of a payment failed. For more information, refer to Failed capture<\/a>.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Chargeback<\/p>\n<\/td>\n\n

    		\n

    Payment reversed by the bank\/scheme\/consumer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SecondChargeback<\/p>\n<\/td>\n\n

    		\n

    Unsuccessful defense of first chargeback.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    ChargebackExternally<\/p>\n<\/td>\n\n

    		\n

    Payment booked as a chargeback with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    ChargebackExternallyWithInfo<\/p>\n<\/td>\n\n

    		\n

    Payment booked as a chargeback with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    ChargebackReversed<\/p>\n<\/td>\n\n

    		\n

    Chargeback defended successfully, or the shopper re-paid the funds.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    ChargebackReversedExternallyWithInfo<\/p>\n<\/td>\n\n

    		\n

    Chargeback defended successfully, or the shopper re-paid the funds.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Error<\/p>\n<\/td>\n\n

    		\n

    Transaction error.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Expired<\/p>\n<\/td>\n\n

    		\n

    Payment not captured within time limits.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PaidOut<\/p>\n<\/td>\n\n

    		\n

    Payout successfully completed.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PaidOutExternally<\/p>\n<\/td>\n\n

    		\n

    Payout successfully completed with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PaidOutExternallyWithInfo<\/p>\n<\/td>\n\n

    		\n

    Payout successfully completed with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PaidOutReversed<\/p>\n<\/td>\n\n

    		\n

    Payout returned to Adyen's account as it could not be credited to the shopper.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PayoutAuthorised<\/p>\n<\/td>\n\n

    		\n

    Payout successfully authorised.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PayoutError<\/p>\n<\/td>\n\n

    		\n

    Payout that resulted in an error.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    PayoutFailed<\/p>\n<\/td>\n\n

    		\n

    Payout request was returned by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Received<\/p>\n<\/td>\n\n

    		\n

    Registration of a validated payment attempt.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    ReceivedPayout<\/p>\n<\/td>\n\n

    		\n

    Payout received by the Adyen payments platform.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundAuthorised<\/p>\n<\/td>\n\n

    		\n

    Refund successfully authorised.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Refunded<\/p>\n<\/td>\n\n

    		\n

    Payment successfully refunded.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundedBulk<\/p>\n<\/td>\n\n

    		\n

    Payment successfully refunded through Adyen Acquiring.


    \nThis journal type will be deprecated.<\/p>\n<\/div><\/div>\n<\/td>\n\n<\/tr>\n\n
    \n

    RefundedExternally<\/p>\n<\/td>\n\n

    		\n

    Payment successfully refunded through an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundedExternallyWithInfo<\/p>\n<\/td>\n\n

    		\n

    Payment successfully refunded through an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundFailed<\/p>\n<\/td>\n\n

    		\n

    The refund failed. For more information, refer to Failed refund<\/a>.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundedInInstallments<\/p>\n<\/td>\n\n

    		\n

    Payment has been fully refunded in installments.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundedInstallment<\/p>\n<\/td>\n\n

    		\n

    Payment installment has been refunded.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundedReversed<\/p>\n<\/td>\n\n

    		\n

    Refund returned to Adyen's account as it could not be credited to the shopper.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefundNotProcessed<\/p>\n<\/td>\n

    		\n

    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<\/strong> record.<\/p>\n<\/td>\n<\/tr>\n\n

    \n

    Refused<\/p>\n<\/td>\n\n

    		\n

    Payment was refused, either by the acquirer or by the Adyen fraud tool.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    RefusedPayout<\/p>\n<\/td>\n\n

    		\n

    Payout was refused, either by the Adyen fraud tool or by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Retried<\/p>\n<\/td>\n\n

    		\n

    Payment request was retried.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SentForPayout<\/p>\n<\/td>\n\n

    		\n

    Payment sent for payout by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SentForRefund<\/p>\n<\/td>\n\n

    		\n

    Payment sent for refund by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SentForSettle<\/p>\n<\/td>\n\n

    		\n

    Request to transfer the payment sent to the financial institution.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    Settled<\/p>\n<\/td>\n\n

    		\n

    Payment has been settled, and the funds have been received by Adyen.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SettledBulk<\/p>\n<\/td>\n\n

    		\n

    Payment has been settled through Adyen Acquiring.


    \nThis journal type will be deprecated.<\/p>\n<\/div><\/div>\n<\/td>\n\n<\/tr>\n\n
    \n

    SettledExternally<\/p>\n<\/td>\n\n

    		\n

    Payment has been settled with an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SettledExternallyWithInfo<\/p>\n<\/td>\n\n

    		\n

    Payment has been settled with an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SettledInInstallments<\/p>\n<\/td>\n\n

    		\n

    Payment has been fully captured in installments.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SettledInstallment<\/p>\n<\/td>\n\n

    		\n

    Payment installment has been settled.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    SettledReversed<\/p>\n<\/td>\n

    		\n

    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<\/strong> record.<\/p>\n<\/td>\n<\/tr>\n\n

    \n

    SuspendInstallment<\/p>\n<\/td>\n\n

    		\n

    The installment will no longer be sent to the scheme due to a dispute in the transaction.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    AdvancedInstallment<\/p>\n<\/td>\n\n

    		\n

    The installment was advanced.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    AdvancedInstallmentCancelled<\/p>\n<\/td>\n\n

    		\n

    The advancement of the installment was cancelled.<\/p>\n<\/td>\n\n<\/tr>\n\n

    \n

    OpenInstallment<\/p>\n<\/td>\n\n

    		\n\nAn installment is still open.\n\nThere are 4 possible states of an OpenInstallment:\n
      \n
    • \n

      Initial<\/strong>: A transaction was captured.<\/p>\n<\/li>\n

    • \n

      Representment<\/strong>: You successfully defended a dispute, and we have resumed suspended installments.<\/p>\n<\/li>\n

    • \n

      Retry<\/strong>: A capture failed, and is being retried.<\/p>\n<\/li>\n

    • \n

      Acceleration<\/strong>: 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<\/strong>.<\/p>\n<\/li>\n<\/ul>\n<\/td>\n\n<\/tr>\n\n

    \n

    CloseInstallment<\/p>\n<\/td>\n\n

    		\n

    The installment will no longer be sent to the scheme and the OpenInstallment is closed.<\/p>\n<\/td>\n\n<\/tr>\n\n<\/tbody>\n\n<\/table>","url":"https:\/\/docs.adyen.com\/essentials\/interactive-payment-accounting-report","articleFields":{"description":"Use this report to match up fees to payment statuses and perform invoice reconciliation.","type":"page","_expandable":{"operations":""},"status":"current","parameters":{"report_name":"Interactive payment accounting report","additional_columns":"true","time_zone":"na","payments_lifecycle_link":"Payments lifecycle<\/a>"}},"algolia":{"url":"https:\/\/docs.adyen.com\/essentials\/interactive-payment-accounting-report","title":"Interactive payment accounting report","content":"\nTime zonesThis report is based on the time zone setting of your account.\n\nThe 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.\nGet the report\nTo generate and download the report, you must have the Merchant report user role.\n\nLog in to Essentials.\nGo to Finances > Interactive payment accounting.\nSelect Generate report and select the date range.\n\nReport structure\nEntries\nUnder the header line, each line in the report is a separate entry.\nColumns\nEach column shows specific information about the entries. By default, the report includes standard columns. You can optionally add additional columns.\nStandard columns\n\n \n\n\n\n#\nColumn\nData type\nDescription\n\n\n\n\n1\nCompany Account\nUnicode Text (80-character)\nThe name of your company account as registered in the Adyen payments platform.\n\n\n2\nMerchant Account\nUnicode Text (80-character)\nThe name of the merchant account that was used to process the original payment request. The report may contain line items for multiple merchant accounts.\n\n\n3\nPsp Reference\nUnicode Text (16-character)\nAdyen's 16-character unique reference associated with the transaction\/the request.\u00a0This value is globally unique; quote it when communicating with us about this request.\n\n\n4\nMerchant Reference\nUnicode Text (80-character)\nThe reference that was specified in the payment request.\n\n\n5\nPayment Method\nUnicode Text (50-character)\nThe payment method used for the transaction. For example: visa, mc, amex.\n\n\n6\nBooking Date\nDate field + Time field\nThe 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.\n\n\n\nTimeZone\nAlpha Text (4-character limit)\nThe time zone of the Booking Date column. This is the ISO code for your time zone setting.\n\n\n7\nMain Currency\nAlpha Text (3-character limit)\nThe three-character ISO code for the currency of the main amount.\n\n\n\nMain Amount\nText field Numeric (16-Character limit)\nThe 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.\n\n\n8\nRecord Type\nUnicode Text (50-character)\nThe accounting record type.For a list of record types, see Record types.\n\n\n9\nPayment Currency\nAlpha Text (3-character limit)\nThe three-character ISO code for the currency that was used to process the payment.\n\n\n10\nReceived (PC)\nFixed point number\nThe amount (in Payment Currency) debited or credited on the Received accounting register.\n\n\n11\nAuthorised (PC)\nFixed point number\nThe amount (in Payment Currency) debited or credited on the Authorised accounting register.\n\n\n12\nCaptured (PC)\nFixed point number\nThe amount (in Payment Currency) debited or credited on the Captured accounting register.\n\n\n13\nSettlement Currency\nAlpha Text (3-character limit)\nThe three-character ISO code for the currency that was used when settling the payment.\n\n\n14\nPayable (SC)\nFixed point number\nThe amount (in Settlement Currency) debited or credited on the Payable accounting register. This will be paid out to your bank account.\n\n\n15\nCommission (SC)\nFixed point number\nThe 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.\n\n\n16\nMarkup (SC)\nFixed point number\nThe fee charged by the acquiring bank (in Settlement Currency).\n\n\n17\nScheme Fees (SC)\nFixed point number\nThe fee charged by, for example, Visa or Mastercard (in Settlement Currency).\n\n\n18\nInterchange (SC)\nFixed point number\nThe fee charged by the issuing bank (in Settlement Currency).\n\n\n19\nProcessing Fee Currency\nAlpha Text (3-character limit)\nThe three-character ISO code for the currency in which the processing (or gateway) fee is charged.\n\n\n20\nProcessing Fee (FC)\nFixed point number\nThe amount (in Processing Fee Currency) charged on the Processing Fee accounting register.\n\n\n21\nUser Name\nUnicode Text (80-character)\nThe 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.\n\n\n22\nPayment Method Variant\nUnicode Text (50-character)\nThe sub-brand of the payment method (if applicable). For example: visaclassic, visadebit, mccorporate.\n\n\n23\nModification Merchant Reference\nUnicode Text (80-character)\nThe optional modification reference for modifications, if specified in the transaction.\n\n\n24\nReserved3\n-\nReserved for future enhancements.\n\n\n25\nReserved4\n-\nReserved for future enhancements.\n\n\n26\nReserved5\n-\nReserved for future enhancements.\n\n\n27\nReserved6\n-\nReserved for future enhancements.\n\n\n28\nReserved7\n-\nReserved for future enhancements.\n\n\n29\nReserved8\n-\nReserved for future enhancements.\n\n\n30\nReserved9\n-\nReserved for future enhancements.\n\n\n31\nReserved10\n-\nReserved for future enhancements.\n\n\n\n\n\n\nAdditional columns\n\n \n\n\n\nColumn\nData type\nDescription\n\n\n\n\nBooking Date (AMS)\nDate\nThe 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.\n\n\nCreation Date\nDate\nThe timestamp indicating when the payment was created on the Adyen payments platform. Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55.\n\n\nCreation Date (AMS)\nDate\nThe Creation Date in Amsterdam time (CET or CEST). Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55.\n\n\nPayable Batch\nNumeric\nThe sequence number of the payout batch.\n\n\nPayout Date\nDate\nThe timestamp indicating the payout date, when available. Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55.\n\n\nGratuity Amount\nNumeric\nThe additional gratuity amount on the payment.\n\n\nSurcharge Amount\nNumeric\nThe surcharge amount on the payment.\n\n\nDCC Markup (SC)\nNumeric\nThe DCC markup (in Settlement Currency).\n\n\nICSF details\nString\nThe detailed specification of each applicable interchange and scheme fee for the payment, if available. The data is included in this columns in JSON format, with an object for each fee applied to the transaction. Each object contains key-value pairs that provide the fee level information. For the key definitions, see ICSF key definitions.\n\n\nGlobal Card Brand\nString\nThe brand of the card used for the payment.\n\n\nIssuer Country\nAlpha Text (2-character limit)\nThe two-character ISO 3166-1 alpha-2 country code where the card was issued.\n\n\nShopper Country\nAlpha Text (2-character limit)\nThe two-character ISO country code of the shopper, if available.\n\n\nCard Number\nString\nObfuscated card number showing the card BIN, an obfuscated section, and the last four digits. For example: 411111****1111\n\n\nFunding Source\nString\nThe card funding source.Possible values:CHARGECREDITDEBITDEFERRED_DEBITPREPAIDPREPAID_RELOADABLEPREPAID_NONRELOADABLE\n\n\nAcquirer\nString\nThe name of the acquirer that processed the original payment. For example: Cielo, Redecard.\n\n\nAcquirer Account\nString\nThe acquirer account that was used for the transaction.\n\n\nMID\nString\nThe Merchant ID from the acquirer that was used to process the payment.\n\n\nAcquirer Auth Code\nString\nThe Acquirer Authorisation Code. Can be included and used to match Auth Code on the merchant gateway side with the Auth Code in this report.\n\n\nAcquirer Reference\nString\nThe acquirer's unique ID for the payment, if available.\n\n\nARN\nString\nThe 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).\n\n\nOriginal Amount\nNumeric\nThe amount of the transaction.\n\n\nInstallments (PC)\nNumeric\nThe amount of the installment, in payment currency (PC).\n\n\nAdvanced (PC)\nNumeric\nThe installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC).\n\n\nAdvancement Code\nString\nThe code of the advancement. An advancement code can contain multiple advancement batches.\n\n\nAdvancement Batch\nString\nThe code of the advancement batch.\n\n\nBooking Type\nString\nIdentifies 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.\n\n\nAdvancement Fee %\nString\nThe calculated fee for the advancement of an installment, as a percentage.\n\n\nInstallments\nString\nWhere 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.\n\n\nUnique Terminal ID\nC X30\nPoint-of-sale terminal identifier, for example P400Plus-123456789.\n\n\nMetadata\nString\nThe contents of the metadata object of the payment, in the form of key-value pairs.\n\n\nMerchant Order Reference\nString\nA reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference.\n\n\nPayment Requester Type\nString\nContains the value autorescue if there was an auto rescue attempt for the payment.\n\n\nNetwork Token Used\nString\nIf true, a network token was used to authorize the payment.\n\n\nNetwork Token Available\nString\nIf true, a network token was available for the payment.\n\n\nStore\nString\nThe store identifier, as configured in point-of-sale.\n\n\nIssuer Name\nString\nName of the issuing bank, if available.\n\n\nRisk Premium\nBoolean\nFor 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.\n\n\nRecord Type\nString\nCustom field that is a concatenation between Record Type and Booking Type.\n\n\nModification Psp Reference\nString\nIn most instances, this is Adyen's unique 16 character code child reference that is associated with the modification request, for example, capture, refund, or chargeback. This is returned to you through the direct API response of the modification request and webhooks. 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.\n\n\nSplit Payment Data\nString\nSplit payment data for the payment, if applicable.\n\n\nExchange Rate\nNumeric\nThe exchange rate for the payment.\n\n\nPayment Account Reference\nString\nThe Payment Account Reference is a unique identifier that links a network token with the underlying primary account number (PAN).\n\n\nTender Reference\nString\nThe tender reference of the point-of-sale payment.\n\n\nShopper Reference\nString\nThe shopper ID or reference that was specified in the original transaction.\n\n\nShopper Name\nString\nThe name of the cardholder, as specified in the transaction, if available.\n\n\n\n\n\n\nICSF key definitions\n\n\n\nLabel\nDescription\n\n\n\n\nt\nThe type of the fee. Possible values: ic: Interchangesf: Scheme fee\n\n\nn\nThe name of the fee.\n\n\nipc\nThe interchange program code (IPC). Its value varies based on the scheme.\n\n\nfc\nThe total amount of the scheme fee (fixed and variable).\n\n\nfq\nThe amount of the fixed fee.\n\n\nbps\nThe amount of the variable fee, in basis points. For example, 20 bps equals 0.20%.\n\n\nmin\nThe minimum amount of the fee.\n\n\nmax\nThe maximum possible amount of the fee.\n\n\nccy\nThe currency of the fee.\n\n\n\nRecord types\n\n\n\n\n\n\nRecord Type\n\nDescription\n\n\n\n\n\n\n\n\n\n\nAuthenticationRequested\n\n\n\nAuthentication (3D Secure 2) was attempted.\n\n\n\n\n\n\n\nAuthorised\n\n\n\nPayment approved by the financial institution.\n\n\n\n\n\n\n\nAuthorisedPending\n\n\n\nPayment authorisation is pending acceptance from the issuer.\n\n\n\n\n\n\n\nCancelled\n\n\n\nTransaction cancelled.\n\n\n\n\n\n\n\nCaptureFailed\n\n\n\nCapture of a payment failed. For more information, refer to Failed capture.\n\n\n\n\n\n\n\nChargeback\n\n\n\nPayment reversed by the bank\/scheme\/consumer.\n\n\n\n\n\n\n\nSecondChargeback\n\n\n\nUnsuccessful defense of first chargeback.\n\n\n\n\n\n\n\nChargebackExternally\n\n\n\nPayment booked as a chargeback with external acquirer.\n\n\n\n\n\n\n\nChargebackExternallyWithInfo\n\n\n\nPayment booked as a chargeback with external acquirer.\n\n\n\n\n\n\n\nChargebackReversed\n\n\n\nChargeback defended successfully, or the shopper re-paid the funds.\n\n\n\n\n\n\n\nChargebackReversedExternallyWithInfo\n\n\n\nChargeback defended successfully, or the shopper re-paid the funds.\n\n\n\n\n\n\n\nError\n\n\n\nTransaction error.\n\n\n\n\n\n\n\nExpired\n\n\n\nPayment not captured within time limits.\n\n\n\n\n\n\n\nPaidOut\n\n\n\nPayout successfully completed.\n\n\n\n\n\n\n\nPaidOutExternally\n\n\n\nPayout successfully completed with external acquirer.\n\n\n\n\n\n\n\nPaidOutExternallyWithInfo\n\n\n\nPayout successfully completed with external acquirer.\n\n\n\n\n\n\n\nPaidOutReversed\n\n\n\nPayout returned to Adyen's account as it could not be credited to the shopper.\n\n\n\n\n\n\n\nPayoutAuthorised\n\n\n\nPayout successfully authorised.\n\n\n\n\n\n\n\nPayoutError\n\n\n\nPayout that resulted in an error.\n\n\n\n\n\n\n\nPayoutFailed\n\n\n\nPayout request was returned by the acquirer.\n\n\n\n\n\n\n\nReceived\n\n\n\nRegistration of a validated payment attempt.\n\n\n\n\n\n\n\nReceivedPayout\n\n\n\nPayout received by the Adyen payments platform.\n\n\n\n\n\n\n\nRefundAuthorised\n\n\n\nRefund successfully authorised.\n\n\n\n\n\n\n\nRefunded\n\n\n\nPayment successfully refunded.\n\n\n\n\n\n\n\nRefundedBulk\n\n\n\nPayment successfully refunded through Adyen Acquiring.\nThis journal type will be deprecated.\n\n\n\n\n\n\n\n\nRefundedExternally\n\n\n\nPayment successfully refunded through an external acquirer.\n\n\n\n\n\n\n\nRefundedExternallyWithInfo\n\n\n\nPayment successfully refunded through an external acquirer.\n\n\n\n\n\n\n\nRefundFailed\n\n\n\nThe refund failed. For more information, refer to Failed refund.\n\n\n\n\n\n\n\nRefundedInInstallments\n\n\n\nPayment has been fully refunded in installments.\n\n\n\n\n\n\n\nRefundedInstallment\n\n\n\nPayment installment has been refunded.\n\n\n\n\n\n\n\nRefundedReversed\n\n\n\nRefund returned to Adyen's account as it could not be credited to the shopper.\n\n\n\n\n\n\nRefundNotProcessed\n\n\nRefund 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.\n\n\n\n\n\n\nRefused\n\n\n\nPayment was refused, either by the acquirer or by the Adyen fraud tool.\n\n\n\n\n\n\n\nRefusedPayout\n\n\n\nPayout was refused, either by the Adyen fraud tool or by the acquirer.\n\n\n\n\n\n\n\nRetried\n\n\n\nPayment request was retried.\n\n\n\n\n\n\n\nSentForPayout\n\n\n\nPayment sent for payout by the acquirer.\n\n\n\n\n\n\n\nSentForRefund\n\n\n\nPayment sent for refund by the acquirer.\n\n\n\n\n\n\n\nSentForSettle\n\n\n\nRequest to transfer the payment sent to the financial institution.\n\n\n\n\n\n\n\nSettled\n\n\n\nPayment has been settled, and the funds have been received by Adyen.\n\n\n\n\n\n\n\nSettledBulk\n\n\n\nPayment has been settled through Adyen Acquiring.\nThis journal type will be deprecated.\n\n\n\n\n\n\n\n\nSettledExternally\n\n\n\nPayment has been settled with an external acquirer.\n\n\n\n\n\n\n\nSettledExternallyWithInfo\n\n\n\nPayment has been settled with an external acquirer.\n\n\n\n\n\n\n\nSettledInInstallments\n\n\n\nPayment has been fully captured in installments.\n\n\n\n\n\n\n\nSettledInstallment\n\n\n\nPayment installment has been settled.\n\n\n\n\n\n \nSettledReversed\n\n \nPayment 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.\n\n\n\n\n\n\nSuspendInstallment\n\n\n\nThe installment will no longer be sent to the scheme due to a dispute in the transaction.\n\n\n\n\n\n\n\nAdvancedInstallment\n\n\n\nThe installment was advanced.\n\n\n\n\n\n\n\nAdvancedInstallmentCancelled\n\n\n\nThe advancement of the installment was cancelled.\n\n\n\n\n\n\n\nOpenInstallment\n\n\n\n\nAn installment is still open.\n\nThere are 4 possible states of an OpenInstallment:\n\n\nInitial: A transaction was captured.\n\n\nRepresentment: You successfully defended a dispute, and we have resumed suspended installments.\n\n\nRetry: A capture failed, and is being retried.\n\n\nAcceleration: 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.\n\n\n\n\n\n\n\n\n\nCloseInstallment\n\n\n\nThe installment will no longer be sent to the scheme and the OpenInstallment is closed.\n\n\n\n\n\n\n","type":"page","locale":"en","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Essentials","lvl2":"Interactive payment accounting report"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/essentials","lvl2":"\/essentials\/interactive-payment-accounting-report"},"levels":3,"category":"","category_color":"","tags":["Interactive","payment","accounting","report"]}}