{"title":"Payment accounting report","category":"default","creationDate":1704982920,"content":"<p>The Payment accounting report includes <a href=\"\/pt\/reporting\/reports-and-the-payments-lifecycle\">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 <a href=\"\/pt\/reporting\/invoice-reconciliation\">perform invoice reconciliation<\/a>.<\/p>\n<p><strong>Generating and downloading<\/strong>: Get this report <a href=\"\/pt\/reporting\/manually-get-reports\">manually<\/a> or <a href=\"\/pt\/reporting\/automatically-get-reports\">automatically<\/a>.<\/p>\n<p><strong>Time zone<\/strong>: The <a href=\"\/pt\/reporting\/time-zone-setting\">time zone setting<\/a> of your account.<\/p>\n<p><strong>Multiple reports at once<\/strong>: Generate more than one Payment accounting report at a time in your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/p>\n<p><strong>Availability<\/strong>: Available for <a href=\"\/pt\/account\/account-structure#company-account\">company accounts<\/a> and <a href=\"\/pt\/account\/account-structure#merchant-accounts\">merchant accounts<\/a>.<\/p>\n<h2>Interactive payment accounting report<\/h2>\n<p>You can manually generate an <strong>Interactive payment accounting<\/strong> report. For each report, you can select the date range, the time zone, and the columns you want to include.<\/p>\n<p>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 <a href=\"\/pt\/reporting\/invoice-reconciliation\/payment-processing-invoice\/\">payment processing invoice<\/a>, select the first day of the month until the first day of the next month, select <code>00:00:00<\/code> for both days, and select Central European Time. This because your invoice is always based on the CET time zone.<\/p>\n<p>Each report will have a unique filename. The file name and file extension depend on what you selected when you generated the report. The file name convention is:<br \/>\n<code>payments_accounting_report_filtered_&lt;REPORT_START_DATE&gt;_&lt;REPORT_END_DATE&gt;_&lt;UNIQUE_IDENTIFIER&gt;<\/code><\/p>\n<p>Where:<\/p>\n<ul>\n<li>The default file name extension is <code>.csv<\/code>. We support generating reports in the file types <strong>CSV<\/strong>, <strong>XLS_GEN<\/strong> or <strong>TSV<\/strong>.<\/li>\n<li>The date format is <code>YYYY_MM_DD<\/code>.<\/li>\n<li>The unique identifier is an eight-character alphanumeric string that is generated based on the date range, timezone, and events selected in the report.<\/li>\n<\/ul>\n<div class=\"notices yellow\">\n<p>The file name format of the Interactive payment accounting report has changed in February 2025, and generating a new report no longer overwrites the previous one. If you automatically ingest report data, you may have to update your data ingestion pipeline.<\/p>\n<\/div>\n<p>Because it is interactive, this report contains different columns than the Payment accounting report. For an example, <a href=\"https:\/\/assets.ctfassets.net\/ihg38ochctiz\/27dbQwcglj2GaAEYLGXoX2\/0c73a3a7660d083dbf1f84b5db8074a8\/payments_accounting_report_filtered_2023_08_08_2023_08_08_09b88550.csv\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">download a sample Interactive payment accounting report<\/a>.<\/p>\n<h2>Sample<\/h2>\n<p><a href=\"\/pt\/reporting\/invoice-reconciliation\/payment-accounting-report\/SAMPLE_payment_accounting_report_2019_04_25.csv\">Download a sample Payment accounting report<\/a> for examples of the included data.<\/p>\n<p>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.<\/p>\n<h2 id=\"report-structure\">Report structure<\/h2>\n<h3 id=\"entries\">Entries<\/h3>\n<p>Under the header line, each line in the report is a separate entry.<\/p>\n<h3 id=\"columns\">Columns<\/h3>\n<p>Each column shows specific information about the entries. By default, the report includes <a href=\"#standard-columns\">standard columns<\/a>. You can optionally add <a href=\"#additional-columns\">additional columns<\/a>.<\/p>\n<h4 id=\"standard-columns\">Standard columns<\/h4>\n<div class=\"sticky-table-container\">\n    \n<table>\n<thead>\n<tr>\n<th>#<\/th>\n<th>Column<\/th>\n<th>Data type<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1<\/td>\n<td>Company Account<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The name of your company account as registered in the plataforma de pagamentos da Adyen.<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Merchant Account<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The name of the merchant account that was used to process the original payment request. <br>The report may contain line items for multiple merchant accounts.<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Psp Reference<\/td>\n<td>Unicode Text (16-character)<\/td>\n<td>Adyen'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<tr>\n<td>4<\/td>\n<td>Merchant Reference<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The reference that was specified in the payment request.<\/td>\n<\/tr>\n<tr>\n<td>5<\/td>\n<td>Payment Method<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The payment method used for the transaction. <br> For example: <em>visa<\/em>, <em>mc<\/em>, <em>amex<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>6<\/td>\n<td>Booking Date<\/td>\n<td>Date field + Time field<\/td>\n<td>The timestamp indicating when the event was entered into Adyen's accounting system. The format is <code>YYYY-MM-DD HH:MM:SS<\/code>. <br> For example: <em>2021-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td><\/td>\n<td>TimeZone<\/td>\n<td>Alpha Text (4-character limit)<\/td>\n<td>The time zone of the <strong>Booking Date<\/strong> column. <br>This is the ISO code for your <a href=\"\/pt\/reporting\/time-zone-setting\">time zone setting<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>7<\/td>\n<td>Main Currency<\/td>\n<td>Alpha Text (3-character limit)<\/td>\n<td>The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO code<\/a> for the currency of the main amount.<\/td>\n<\/tr>\n<tr>\n<td><\/td>\n<td>Main Amount<\/td>\n<td>Text field Numeric (16-Character limit)<\/td>\n<td>The amount recorded when the transaction reaches the <strong>Record Type<\/strong>. For example, the main amount of a <code>Settled<\/code> transaction is the amount after deducting payment processing fees.<\/td>\n<\/tr>\n<tr>\n<td>8<\/td>\n<td>Record Type<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The accounting record type.<br>For a list of record types, see <a href=\"#recordtypes\">Record types<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>9<\/td>\n<td>Payment Currency<\/td>\n<td>Alpha Text (3-character limit)<\/td>\n<td>The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO code<\/a> for the currency that was used to process the payment.<\/td>\n<\/tr>\n<tr>\n<td>10<\/td>\n<td>Received (PC)<\/td>\n<td>Fixed point number<\/td>\n<td>The amount (in Payment Currency) debited or credited on the Received accounting register.<\/td>\n<\/tr>\n<tr>\n<td>11<\/td>\n<td>Authorised (PC)<\/td>\n<td>Fixed point number<\/td>\n<td>The amount (in Payment Currency) debited or credited on the Authorised accounting register.<\/td>\n<\/tr>\n<tr>\n<td>12<\/td>\n<td>Captured (PC)<\/td>\n<td>Fixed point number<\/td>\n<td>The amount (in Payment Currency) debited or credited on the Captured accounting register.<\/td>\n<\/tr>\n<tr>\n<td>13<\/td>\n<td>Settlement Currency<\/td>\n<td>Alpha Text (3-character limit)<\/td>\n<td>The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO code<\/a> for the currency that was used when settling the payment.<\/td>\n<\/tr>\n<tr>\n<td>14<\/td>\n<td>Payable (SC)<\/td>\n<td>Fixed point number<\/td>\n<td>The 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<tr>\n<td>15<\/td>\n<td>Commission (SC)<\/td>\n<td>Fixed point number<\/td>\n<td>The commission fee that was withheld by the acquirer (in Settlement Currency)<br>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<tr>\n<td>16<\/td>\n<td>Markup (SC)<\/td>\n<td>Fixed point number<\/td>\n<td>The fee charged by the acquiring bank (in Settlement Currency).<\/td>\n<\/tr>\n<tr>\n<td>17<\/td>\n<td>Scheme Fees (SC)<\/td>\n<td>Fixed point number<\/td>\n<td>The fee charged by, for example, Visa or Mastercard (in Settlement Currency).<\/td>\n<\/tr>\n<tr>\n<td>18<\/td>\n<td>Interchange (SC)<\/td>\n<td>Fixed point number<\/td>\n<td>The fee charged by the issuing bank (in Settlement Currency).<\/td>\n<\/tr>\n<tr>\n<td>19<\/td>\n<td>Processing Fee Currency<\/td>\n<td>Alpha Text (3-character limit)<\/td>\n<td>The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO code<\/a> for the currency in which the processing (or gateway) fee is charged.<\/td>\n<\/tr>\n<tr>\n<td>20<\/td>\n<td>Processing Fee (FC)<\/td>\n<td>Fixed point number<\/td>\n<td>The amount (in Processing Fee Currency) charged on the Processing Fee accounting register.<\/td>\n<\/tr>\n<tr>\n<td>21<\/td>\n<td>User Name<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>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 <em>system<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>22<\/td>\n<td>Payment Method Variant<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The sub-brand of the payment method (if applicable). <br> For example: <em>visaclassic<\/em>, <em>visadebit<\/em>, <em>mccorporate<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>23<\/td>\n<td>Modification Merchant Reference<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The optional modification reference for <a href=\"\/pt\/get-started-with-adyen\/adyen-glossary\/#payment-modifications-definition\">modifications<\/a>, if specified in the transaction.<\/td>\n<\/tr>\n<tr>\n<td>24<\/td>\n<td>Reserved3<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>25<\/td>\n<td>Reserved4<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>26<\/td>\n<td>Reserved5<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>27<\/td>\n<td>Reserved6<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>28<\/td>\n<td>Reserved7<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>29<\/td>\n<td>Reserved8<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>30<\/td>\n<td>Reserved9<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<tr>\n<td>31<\/td>\n<td>Reserved10<\/td>\n<td>-<\/td>\n<td>Reserved for future enhancements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n<h3 id=\"additional-columns\">Additional columns<\/h3>\n<p>You can <a href=\"#configure-report-columns\">configure report columns<\/a> to add these to your report:<\/p>\n<div class=\"sticky-table-container\">\n    \n<table>\n<thead>\n<tr>\n<th>Column<\/th>\n<th>Data type<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Booking Date (AMS)<\/td>\n<td>Date<\/td>\n<td>The timestamp indicating when the event was entered into Adyen's accounting system, in Amsterdam time (CET or CEST). Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br> For example: <em>2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Creation Date<\/td>\n<td>Date<\/td>\n<td>The timestamp indicating when the payment was created on the plataforma de pagamentos da Adyen. Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br> For example: <em>2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Creation Date (AMS)<\/td>\n<td>Date<\/td>\n<td>The <strong>Creation Date<\/strong> in Amsterdam time (CET or CEST). Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br> For example: <em>2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Payable Batch<\/td>\n<td>Numeric<\/td>\n<td>The sequence number of the payout batch.<\/td>\n<\/tr>\n<tr>\n<td>Payout Date<\/td>\n<td>Date<\/td>\n<td>The timestamp indicating the payout date, when available. Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br> For example: <em>2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Gratuity Amount<\/td>\n<td>Numeric<\/td>\n<td>The additional gratuity amount on the payment.<\/td>\n<\/tr>\n<tr>\n<td>Surcharge Amount<\/td>\n<td>Numeric<\/td>\n<td>The surcharge amount on the payment.<\/td>\n<\/tr>\n<tr>\n<td>DCC Markup (SC)<\/td>\n<td>Numeric<\/td>\n<td>The DCC markup (in Settlement Currency).<\/td>\n<\/tr>\n<tr>\n<td>ICSF details<\/td>\n<td>String<\/td>\n<td>The 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 <a href=\"#icsf-definitions\">ICSF key definitions<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Global Card Brand<\/td>\n<td>String<\/td>\n<td>The brand of the card used for the payment.<\/td>\n<\/tr>\n<tr>\n<td>Issuer Country<\/td>\n<td>Alpha Text (2-character limit)<\/td>\n<td>The two-character ISO 3166-1 alpha-2 country code where the card was issued.<\/td>\n<\/tr>\n<tr>\n<td>Shopper Country<\/td>\n<td>Alpha Text (2-character limit)<\/td>\n<td>The two-character ISO country code of the shopper, if available.<\/td>\n<\/tr>\n<tr>\n<td>Card Number<\/td>\n<td>String<\/td>\n<td>Obfuscated card number showing the card BIN, an obfuscated section, and the last four digits. <br>For example: <em>411111****1111<\/em><\/td>\n<\/tr>\n<tr>\n<td>Funding Source<\/td>\n<td>String<\/td>\n<td>The card funding source.<br>Possible values:<br><ul><li markdown=\"1\">CHARGE<\/li><li markdown=\"1\">CREDIT<\/li><li markdown=\"1\">DEBIT<\/li><li markdown=\"1\">DEFERRED_DEBIT<\/li><li markdown=\"1\">PREPAID<\/li><li markdown=\"1\">PREPAID_RELOADABLE<\/li><li markdown=\"1\">PREPAID_NONRELOADABLE<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td>Acquirer<\/td>\n<td>String<\/td>\n<td>The name of the acquirer that processed the original payment. For example: <em>Cielo<\/em>, <em>Redecard<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Acquirer Account<\/td>\n<td>String<\/td>\n<td>The acquirer account that was used for the transaction.<\/td>\n<\/tr>\n<tr>\n<td>MID<\/td>\n<td>String<\/td>\n<td>The Merchant ID from the acquirer that was used to process the payment.<\/td>\n<\/tr>\n<tr>\n<td>Acquirer Auth Code<\/td>\n<td>String<\/td>\n<td>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.<\/td>\n<\/tr>\n<tr>\n<td>Acquirer Reference<\/td>\n<td>String<\/td>\n<td>The acquirer's unique ID for the payment, if available.<\/td>\n<\/tr>\n<tr>\n<td>ARN<\/td>\n<td>String<\/td>\n<td>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).<\/td>\n<\/tr>\n<tr>\n<td>Original Amount<\/td>\n<td>Numeric<\/td>\n<td>The amount of the transaction.<\/td>\n<\/tr>\n<tr>\n<td>Installments (PC)<\/td>\n<td>Numeric<\/td>\n<td>The amount of the installment, in payment currency (PC).<\/td>\n<\/tr>\n<tr>\n<td>Advanced (PC)<\/td>\n<td>Numeric<\/td>\n<td>The installment amount that was advanced. This is the gross amount of the advancement fee, in payment currency (PC).<\/td>\n<\/tr>\n<tr>\n<td>Advancement Code<\/td>\n<td>String<\/td>\n<td>The code of the advancement. An advancement code can contain multiple advancement batches.<\/td>\n<\/tr>\n<tr>\n<td>Advancement Batch<\/td>\n<td>String<\/td>\n<td>The code of the advancement batch.<\/td>\n<\/tr>\n<tr>\n<td>Booking Type<\/td>\n<td>String<\/td>\n<td>Identifies the transaction\/installment that was accelerated or represented. <br> Possible values: <br><em>FIRST<\/em>: Installment first\/original presentment. <br> <em>ACCELL<\/em>: Installment accelerated, for example in case of refunds. <br><em>REPRESENTMENT<\/em>: Installment second presentment in case of dispute defended. <br><em>RETRY<\/em>: If an installment presentment fails, a new one will be created with this booking type.<\/td>\n<\/tr>\n<tr>\n<td>Advancement Fee %<\/td>\n<td>String<\/td>\n<td>The calculated fee for the advancement of an installment, as a percentage.<\/td>\n<\/tr>\n<tr>\n<td>Installments<\/td>\n<td>String<\/td>\n<td>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.<\/td>\n<\/tr>\n<tr>\n<td>Unique Terminal ID<\/td>\n<td>C X30<\/td>\n<td>Point-of-sale terminal identifier, for example <em>P400Plus-123456789<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Metadata<\/td>\n<td>String<\/td>\n<td>The contents of the <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/PaymentSetupAndVerificationService\/latest\/payments__reqParam_metadata\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">metadata<\/a> object of the payment, in the form of key-value pairs.<\/td>\n<\/tr>\n<tr>\n<td>Merchant Order Reference<\/td>\n<td>String<\/td>\n<td>A reference that allows you to link multiple transactions to each other for reporting purposes. See  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments#request-merchantOrderReference\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">merchantOrderReference<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Payment Requester Type<\/td>\n<td>String<\/td>\n<td>Contains the value <code>autorescue<\/code> if there was an auto rescue attempt for the payment.<\/td>\n<\/tr>\n<tr>\n<td>Network Token Used<\/td>\n<td>String<\/td>\n<td>If true, a network token was used to authorize the payment.<\/td>\n<\/tr>\n<tr>\n<td>Network Token Available<\/td>\n<td>String<\/td>\n<td>If true, a network token was available for the payment.<\/td>\n<\/tr>\n<tr>\n<td>Store<\/td>\n<td>String<\/td>\n<td>The store identifier, as configured in point-of-sale.<\/td>\n<\/tr>\n<tr>\n<td>Issuer Name<\/td>\n<td>String<\/td>\n<td>Name of the issuing bank, if available.<\/td>\n<\/tr>\n<tr>\n<td>Risk Premium<\/td>\n<td>Boolean<\/td>\n<td>For payments where the Record Type is <strong>Received<\/strong>, the value of this field indicates if the payment triggered RevenueProtect checks (resulting in charges on your invoice).<br>Possible values:<br><strong>true<\/strong> - A risk fee is charged.<br><strong>false<\/strong> - A risk fee is not charged.<\/td>\n<\/tr>\n<tr>\n<td>Record Type<\/td>\n<td>String<\/td>\n<td>Custom field that is a concatenation between <strong>Record Type<\/strong> and <strong>Booking Type<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td>Modification Psp Reference<\/td>\n<td>String<\/td>\n<td>In 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.<br> 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<tr>\n<td>Split Payment Data<\/td>\n<td>String<\/td>\n<td>Split payment data for the payment, if applicable.<\/td>\n<\/tr>\n<tr>\n<td>Exchange Rate<\/td>\n<td>Numeric<\/td>\n<td>The exchange rate for the payment.<\/td>\n<\/tr>\n<tr>\n<td>Payment Account Reference<\/td>\n<td>String<\/td>\n<td>The Payment Account Reference is a unique identifier that links a <a href=\"\/pt\/online-payments\/network-tokenization\">network token<\/a> with the underlying primary account number (PAN).<\/td>\n<\/tr>\n<tr>\n<td>Tender Reference<\/td>\n<td>String<\/td>\n<td>The tender reference of the point-of-sale payment.<\/td>\n<\/tr>\n<tr>\n<td>Shopper Reference<\/td>\n<td>String<\/td>\n<td>The shopper ID or reference that was specified in the original transaction.<\/td>\n<\/tr>\n<tr>\n<td>Shopper Name<\/td>\n<td>String<\/td>\n<td>The name of the cardholder, as specified in the transaction, if available.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n<h4 id=\"icsf-definitions\">ICSF key definitions<\/h4>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Label<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>t<\/strong><\/td>\n<td style=\"text-align: left;\">The type of the fee. Possible values: <ul><li markdown=\"1\"><strong>ic<\/strong>: Interchange<\/li><li markdown=\"1\"><strong>sf<\/strong>: Scheme fee<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>n<\/strong><\/td>\n<td style=\"text-align: left;\">The name of the fee.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>ipc<\/strong><\/td>\n<td style=\"text-align: left;\">The interchange program code (IPC). Its value varies based on the scheme.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>fc<\/strong><\/td>\n<td style=\"text-align: left;\">The total amount of the scheme fee (fixed and variable).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>fq<\/strong><\/td>\n<td style=\"text-align: left;\">The amount of the fixed fee.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>bps<\/strong><\/td>\n<td style=\"text-align: left;\">The amount of the variable fee, in basis points. For example, 20 bps equals 0.20%.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>min<\/strong><\/td>\n<td style=\"text-align: left;\">The minimum amount of the fee.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>max<\/strong><\/td>\n<td style=\"text-align: left;\">The maximum possible amount of the fee.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>ccy<\/strong><\/td>\n<td style=\"text-align: left;\">The currency of the fee.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"configure-report-columns\">Configure report columns<\/h2>\n<p>If you want to add additional columns or change the order of columns in a report, you can do so in the <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>. If you have an automated system that uses the report's data, configuring the report columns can affect your automated system.<\/p>\n<p>To configure report columns, you need to have one of the following <a href=\"\/pt\/account\/user-roles\">user roles<\/a>:<\/p>\n<ul>\n<li>Merchant admin<\/li>\n<li>Merchant report role<\/li>\n<li>Merchant financial<\/li>\n<li>Merchant POS Report role<\/li>\n<\/ul>\n<p>To configure report columns:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li>\n<li>Go to <strong>Settings<\/strong> &gt; <strong>Report columns<\/strong>.<br \/>\nThis opens a page with all the reports that you can configure.<\/li>\n<li>Find the report that you want to configure and select <strong>Configure<\/strong>.<\/li>\n<li>Select checkboxes to indicate which columns you want to include in the report.<\/li>\n<li>Drag the columns into the order you want them to appear in.<\/li>\n<li>Select <strong>Save configuration<\/strong>.<\/li>\n<\/ol>\n<h2 id=\"recordtypes\">Record types<\/h2>\n<table>\n\n<thead>\n\n<tr class=\"header\">\n\n<th>Record Type<\/th>\n\n<th>Description<\/th>\n\n<\/tr>\n\n<\/thead>\n\n<tbody>\n\n<tr>\n\n<td>\n<p>AuthenticationRequested<\/p>\n<\/td>\n\n<td>\n<p>Authentication (3D Secure 2) was attempted.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Authorised<\/p>\n<\/td>\n\n<td>\n<p>Payment approved by the financial institution.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>AuthorisedPending<\/p>\n<\/td>\n\n<td>\n<p>Payment authorisation is pending acceptance from the issuer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Cancelled<\/p>\n<\/td>\n\n<td>\n<p>Transaction cancelled.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>CaptureFailed<\/p>\n<\/td>\n\n<td>\n<p>Capture of a payment failed. For more information, refer to <a href=\"\/online-payments\/capture#failed-capture\">Failed capture<\/a>.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Chargeback<\/p>\n<\/td>\n\n<td>\n<p>Payment reversed by the bank\/scheme\/consumer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SecondChargeback<\/p>\n<\/td>\n\n<td>\n<p>Unsuccessful defense of first chargeback.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>ChargebackExternally<\/p>\n<\/td>\n\n<td>\n<p>Payment booked as a chargeback with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>ChargebackExternallyWithInfo<\/p>\n<\/td>\n\n<td>\n<p>Payment booked as a chargeback with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>ChargebackReversed<\/p>\n<\/td>\n\n<td>\n<p>Chargeback defended successfully, or the shopper re-paid the funds.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>ChargebackReversedExternallyWithInfo<\/p>\n<\/td>\n\n<td>\n<p>Chargeback defended successfully, or the shopper re-paid the funds.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Error<\/p>\n<\/td>\n\n<td>\n<p>Transaction error.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Expired<\/p>\n<\/td>\n\n<td>\n<p>Payment not captured within time limits.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PaidOut<\/p>\n<\/td>\n\n<td>\n<p>Payout successfully completed.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PaidOutExternally<\/p>\n<\/td>\n\n<td>\n<p>Payout successfully completed with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PaidOutExternallyWithInfo<\/p>\n<\/td>\n\n<td>\n<p>Payout successfully completed with external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PaidOutReversed<\/p>\n<\/td>\n\n<td>\n<p>Payout returned to Adyen's account as it could not be credited to the shopper.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PayoutAuthorised<\/p>\n<\/td>\n\n<td>\n<p>Payout successfully authorised.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PayoutError<\/p>\n<\/td>\n\n<td>\n<p>Payout that resulted in an error.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>PayoutFailed<\/p>\n<\/td>\n\n<td>\n<p>Payout request was returned by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Received<\/p>\n<\/td>\n\n<td>\n<p>Registration of a validated payment attempt.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>ReceivedPayout<\/p>\n<\/td>\n\n<td>\n<p>Payout received by the plataforma de pagamentos da Adyen.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundAuthorised<\/p>\n<\/td>\n\n<td>\n<p>Refund successfully authorised.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Refunded<\/p>\n<\/td>\n\n<td>\n<p>Payment successfully refunded.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedBulk<\/p>\n<\/td>\n\n<td>\n<p>Payment successfully refunded through Adyen Acquiring.<div class=\"sc-notice note\"><div><br \/>\nThis journal type will be deprecated.<\/p>\n<\/div><\/div>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedExternally<\/p>\n<\/td>\n\n<td>\n<p>Payment successfully refunded through an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedExternallyWithInfo<\/p>\n<\/td>\n\n<td>\n<p>Payment successfully refunded through an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundFailed<\/p>\n<\/td>\n\n<td>\n<p>The refund failed. For more information, refer to <a href=\"\/online-payments\/refund#refund-failed\">Failed refund<\/a>.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedInInstallments<\/p>\n<\/td>\n\n<td>\n<p>Payment has been fully refunded in installments.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedInstallment<\/p>\n<\/td>\n\n<td>\n<p>Payment installment has been refunded.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefundedReversed<\/p>\n<\/td>\n\n<td>\n<p>Refund returned to Adyen's account as it could not be credited to the shopper.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n<td>\n<p>RefundNotProcessed<\/p>\n<\/td>\n<td>\n<p>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 <strong>Refunded<\/strong> record.<\/p>\n<\/td>\n<\/tr>\n\n<tr>\n\n<td>\n<p>Refused<\/p>\n<\/td>\n\n<td>\n<p>Payment was refused, either by the acquirer or by the Adyen fraud tool.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>RefusedPayout<\/p>\n<\/td>\n\n<td>\n<p>Payout was refused, either by the Adyen fraud tool or by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Retried<\/p>\n<\/td>\n\n<td>\n<p>Payment request was retried.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SentForPayout<\/p>\n<\/td>\n\n<td>\n<p>Payment sent for payout by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SentForRefund<\/p>\n<\/td>\n\n<td>\n<p>Payment sent for refund by the acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SentForSettle<\/p>\n<\/td>\n\n<td>\n<p>Request to transfer the payment sent to the financial institution.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>Settled<\/p>\n<\/td>\n\n<td>\n<p>Payment has been settled, and the funds have been received by Adyen.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SettledBulk<\/p>\n<\/td>\n\n<td>\n<p>Payment has been settled through Adyen Acquiring.<div class=\"sc-notice note\"><div><br \/>\nThis journal type will be deprecated.<\/p>\n<\/div><\/div>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SettledExternally<\/p>\n<\/td>\n\n<td>\n<p>Payment has been settled with an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SettledExternallyWithInfo<\/p>\n<\/td>\n\n<td>\n<p>Payment has been settled with an external acquirer.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SettledInInstallments<\/p>\n<\/td>\n\n<td>\n<p>Payment has been fully captured in installments.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>SettledInstallment<\/p>\n<\/td>\n\n<td>\n<p>Payment installment has been settled.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n    <td>\n<p>SettledReversed<\/p>\n<\/td>\n    <td>\n<p>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 <strong>Settled<\/strong> record.<\/p>\n<\/td>\n<\/tr>\n\n<tr>\n\n<td>\n<p>SuspendInstallment<\/p>\n<\/td>\n\n<td>\n<p>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<tr>\n\n<td>\n<p>AdvancedInstallment<\/p>\n<\/td>\n\n<td>\n<p>The installment was advanced.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>AdvancedInstallmentCancelled<\/p>\n<\/td>\n\n<td>\n<p>The advancement of the installment was cancelled.<\/p>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>OpenInstallment<\/p>\n<\/td>\n\n<td>\n\nAn installment is still open.\n\nThere are 4 possible states of an OpenInstallment:\n<ul>\n<li>\n<p><strong>Initial<\/strong>: A transaction was captured.<\/p>\n<\/li>\n<li>\n<p><strong>Representment<\/strong>: You successfully defended a dispute, and we have resumed suspended installments.<\/p>\n<\/li>\n<li>\n<p><strong>Retry<\/strong>: A capture failed, and is being retried.<\/p>\n<\/li>\n<li>\n<p><strong>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 <strong>CloseInstallment<\/strong>.<\/p>\n<\/li>\n<\/ul>\n<\/td>\n\n<\/tr>\n\n<tr>\n\n<td>\n<p>CloseInstallment<\/p>\n<\/td>\n\n<td>\n<p>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>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/reporting\/invoice-reconciliation\"\n                        target=\"_self\"\n                        >\n                    Invoice reconciliation\n                <\/a><\/li><li><a href=\"\/reporting\/reports-and-the-payments-lifecycle\"\n                        target=\"_self\"\n                        >\n                    Reports and the payments lifecycle\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/reporting\/invoice-reconciliation\/payment-accounting-report","articleFields":{"description":"Use this report to match up fees to payment statuses and perform invoice reconciliation.","feedback_component":true,"parameters":{"report_name":"Payment accounting report","file_name":"\/reporting\/invoice-reconciliation\/payment-accounting-report\/SAMPLE_payment_accounting_report_2019_04_25.csv","additional_columns":"true","time_zone":"na","ca_type":"ca","automatic":"yes","dates":"bulk","company_level":"yes"},"type":"page","_expandable":{"operations":""},"status":"current","filters_component":false,"decision_tree":"[]","page_id":"0052ca1e-3807-4966-9a9c-2d73dca2534d","last_edit_on":"11-01-2024 15:22"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/reporting\/invoice-reconciliation\/payment-accounting-report","title":"Payment accounting report","content":"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.\nGenerating and downloading: Get this report manually or automatically.\nTime zone: The time zone setting of your account.\nMultiple reports at once: Generate more than one Payment accounting report at a time in your Customer Area.\nAvailability: Available for company accounts and merchant accounts.\nInteractive payment accounting report\nYou can manually generate an Interactive payment accounting report. For each report, you can select the date range, the time zone, and the columns you want to include.\nYou 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.\nEach report will have a unique filename. The file name and file extension depend on what you selected when you generated the report. The file name convention is:\npayments_accounting_report_filtered_&lt;REPORT_START_DATE&gt;_&lt;REPORT_END_DATE&gt;_&lt;UNIQUE_IDENTIFIER&gt;\nWhere:\n\nThe default file name extension is .csv. We support generating reports in the file types CSV, XLS_GEN or TSV.\nThe date format is YYYY_MM_DD.\nThe unique identifier is an eight-character alphanumeric string that is generated based on the date range, timezone, and events selected in the report.\n\n\nThe file name format of the Interactive payment accounting report has changed in February 2025, and generating a new report no longer overwrites the previous one. If you automatically ingest report data, you may have to update your data ingestion pipeline.\n\nBecause it is interactive, this report contains different columns than the Payment accounting report. For an example, download a sample Interactive payment accounting report.\nSample\nDownload a sample Payment accounting report for examples of the included data.\nBased 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.\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 plataforma de pagamentos da Adyen.\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\nYou can configure report columns to add these to your report:\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 plataforma de pagamentos da Adyen. 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\nConfigure report columns\nIf 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.\nTo configure report columns, you need to have one of the following user roles:\n\nMerchant admin\nMerchant report role\nMerchant financial\nMerchant POS Report role\n\nTo configure report columns:\n\nLog in to your Customer Area.\nGo to Settings &gt; Report columns.\nThis opens a page with all the reports that you can configure.\nFind the report that you want to configure and select Configure.\nSelect checkboxes to indicate which columns you want to include in the report.\nDrag the columns into the order you want them to appear in.\nSelect Save configuration.\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 plataforma de pagamentos da Adyen.\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\nSee also\n\n\n                    Invoice reconciliation\n                \n                    Reports and the payments lifecycle\n                \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Reporting","lvl2":"Invoice reconciliation guide","lvl3":"Payment accounting report"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/reporting","lvl2":"https:\/\/docs.adyen.com\/pt\/reporting\/invoice-reconciliation","lvl3":"\/pt\/reporting\/invoice-reconciliation\/payment-accounting-report"},"levels":4,"category":"Reporting","category_color":"green","tags":["Payment","accounting","report"]},"articleFiles":{"SAMPLE_payment_accounting_report_2019_04_25.csv":"<p alt=\"\">SAMPLE_payment_accounting_report_2019_04_25.csv<\/p>"}}
