{"title":"Received Payments Report","category":"default","creationDate":1627458960,"content":"
\n

The Received Payments Report has been deprecated. Use the Accounting Report<\/a> instead.<\/p>\n<\/div>\n

The Received Payments Report shows all the payments made during the selected day, and their final state.<\/p>\n

Because it can take some time for payments to reach a final state<\/a>, we recommend that you generate a Received Payments Report two weeks after the day for which you want that report. For example, to reconcile the payments from June 15th, you should generate the report in July. This way you can ensure that payments that were in Authorised<\/strong><\/span> state are now in their final state, for example, Captured<\/strong><\/span> or Expired<\/strong><\/span>.<\/p>\n

You can generate<\/a> a Received Payments Report automatically based on a schedule, or manually for a specific day or consecutive days in your Customer Area<\/a>.<\/p>\n

Sample<\/h2>\n

Download a sample BalancePlatform Received Payments Report<\/a> for examples of the included data.
\nBased on your platform settings, the report you generate in your account can contain additional data or columns that are not included in the sample report.<\/p>\n

Report structure<\/h2>\n

Every row in the Received Payments Report represents one payment with its final state reached when the report was generated.<\/p>\n

The first three rows of the report contain the following information.<\/p>\n

BalancePlatform Received Payments as at\nYYYY-MM-DD\nPayments<\/code><\/pre>\n
The header row is in the fourth row and contains the following information.<\/p>\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
#<\/th>\nColumn<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
1<\/td>\nBalance Platform<\/td>\nUnicode Text<\/td>\nName of your Balance Platform account.<\/td>\n<\/tr>\n
2<\/td>\nAccount Holder<\/td>\nUnicode Text<\/td>\nUnique identifier of the account holder that owns the balance account.<\/td>\n<\/tr>\n
3<\/td>\nBalance Account<\/td>\nUnicode Text<\/td>\nUnique identifier of the balance account associated with the payment instrument.<\/td>\n<\/tr>\n
4<\/td>\nTransaction Id<\/td>\nAlpha text
(16-character limit)<\/td>\n		Unique transaction id in Adyen's accounting systems.<\/td>\n<\/tr>\n
5<\/td>\nJournal Type<\/td>\nUnicode Text<\/td>\nThe latest available status of the payment.
When the report is generated 2 weeks after the report date, expect only final states (Captured, Refused, Expired, Cancelled, and Refunded). When the report is generated less than 2 weeks after the report date, expect also non-final states, for example, Authorised.<\/td>\n<\/tr>\n
6<\/td>\nAuthorisation PSP Reference<\/td>\nAlpha text
(16-character limit)<\/td>\n		Adyen's 16-character unique reference associated with the authorization request.<\/td>\n<\/tr>\n
7<\/td>\nPayment Instrument Type<\/td>\nUnicode text<\/td>\nThe type of the payment instrument used in the payment.<\/td>\n<\/tr>\n
8<\/td>\nPayment Reference<\/td>\nUnicode Text 
(16-character limit)<\/td>\n		Unique identifier of the payment instrument used in the payment.<\/td>\n<\/tr>\n
9<\/td>\nAuthorisation Date<\/td>\nDate field + Time field<\/td>\nTimestamp of the date and time of the payment.<\/td>\n<\/tr>\n
10<\/td>\nAuthorisation TimeZone<\/td>\nAlpha text
(4-character limit)<\/td>\n		Time zone of the Authorisation Date<\/em> column.<\/td>\n<\/tr>\n
11<\/td>\nTransaction Date<\/td>\nDate field<\/td>\nTimestamp indicating when the transaction was created in Adyen's accounting systems.<\/td>\n<\/tr>\n
12<\/td>\nTransaction TimeZone<\/td>\nAlpha text
(4-character limit)<\/td>\n		The time zone of the Transaction Date<\/em>.<\/td>\n<\/tr>\n
13<\/td>\nOriginal Currency<\/td>\nAlpha text
(3-character limit)<\/td>\n		The currency of the payment amount as received from the acquirer. 
Its value is a three-character ISO 4217 currency code.<\/td>\n<\/tr>\n
14<\/td>\nOriginal Amount<\/td>\nFixed point number<\/td>\nThe payment amount in the currency defined in Original Currency<\/em>.<\/td>\n<\/tr>\n
15<\/td>\nInstructed Currency<\/td>\nAlpha text
(3-character limit)<\/td>\n		The currency of the amount deducted from the balance account for this payment.<\/td>\n<\/tr>\n
16<\/td>\nInstructed Amount<\/td>\nText field numeric
(16-character limit)<\/td>\n		The amount deducted from the balance account, in the currency defined in Instructed Currency<\/em>.<\/td>\n<\/tr>\n
17<\/td>\nDescription<\/td>\nUnicode text<\/td>\nA unique description generated for the payment.<\/td>\n<\/tr>\n
18<\/td>\nEntrymode<\/td>\nUnicode text<\/td>\nThe point-of-sale entry mode as reported by the acquirer.
Possible values: MANUAL<\/code>, CHIP<\/code>, MAGSTRIPE<\/code>, MAGSTRIPE_FALLBACK<\/code>, CONTACTLESS<\/code>, CONTACTLESS_MAGSTRIPE<\/code>, COF<\/code>, TOKEN<\/code>, E_COMMERCE<\/code>, SERVER<\/code>, BARCODE<\/code>, OCR<\/code>, UNKNOWN<\/code>.<\/td>\n<\/tr>\n
19<\/td>\nAuth Code<\/td>\nText field numeric<\/td>\nA unique authorisation code generated for the payment. This code should be included when canceling or refunding a payment.<\/td>\n<\/tr>\n
20<\/td>\nShopper Interaction<\/td>\nAlpha text
(30-character limit)<\/td>\n		Transaction type. Possible values: Ecommerce<\/code>, ContAuth<\/code>, POS<\/code>, Moto<\/code>.<\/td>\n<\/tr>\n
21<\/td>\nCounterparty Name<\/td>\nUnicode text<\/td>\nThe name of the merchant that initiated the payment.<\/td>\n<\/tr>\n
22<\/td>\nCounterparty Address<\/td>\nUnicode text<\/td>\nThe address of the merchant that initiated the payment.<\/td>\n<\/tr>\n
23<\/td>\nCounterparty City<\/td>\nUnicode text<\/td>\nThe city of the merchant that initiated the payment.<\/td>\n<\/tr>\n
24<\/td>\nCounterparty Country<\/td>\nUnicode text<\/td>\nThe location of the merchant that initiated the payment. Its value is a three-character ISO 3166-1 alpha-3<\/a> country code.<\/td>\n<\/tr>\n
24<\/td>\nMCC<\/td>\nText field numeric<\/td>\nThe merchant category code of the merchant that initiated the payment.<\/td>\n<\/tr>\n
25<\/td>\nCounterparty iban<\/td>\nUnicode text<\/td>\nThe IBAN of the merchant that initiated the payment.<\/td>\n<\/tr>\n
26<\/td>\nCounterparty bic<\/td>\nAlpha text<\/td>\nThe BIC of the bank of the merchant that initiated the payment.<\/td>\n<\/tr>\n
27<\/td>\nCounterparty Account Number<\/td>\nUnicode Text<\/td>\nThe account number of the merchant that initiated the payment.<\/td>\n<\/tr>\n
28<\/td>\nBeneficiary Balance Account<\/td>\nUnicode Text<\/td>\nThe unique identifier of the beneficiary balance account associated with your platform.<\/td>\n<\/tr>\n
29<\/td>\nReserved2<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
30<\/td>\nReserved3<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
31<\/td>\nReserved4<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
32<\/td>\nReserved5<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
33<\/td>\nReserved6<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
34<\/td>\nReserved7<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
35<\/td>\nReserved8<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
36<\/td>\nReserved9<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n
37<\/td>\nReserved10<\/td>\n-<\/td>\nReserved for future enhancements<\/td>\n<\/tr>\n<\/tbody>\n<\/table>","url":"https:\/\/docs.adyen.com\/pt\/issuing\/report-types\/received-payments-report","articleFields":{"description":"Get the details of the payments and transactions made by card users.","feedback_component":true,"last_edit_on":"05-11-2021 13:02","parameters":{"directoryPath":"\/issuing"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/report-types\/received-payments-report","title":"Received Payments Report","content":"\nThe Received Payments Report has been deprecated. Use the Accounting Report instead.\n\nThe Received Payments Report shows all the payments made during the selected day, and their final state.\nBecause it can take some time for payments to reach a final state, we recommend that you generate a Received Payments Report two weeks after the day for which you want that report. For example, to reconcile the payments from June 15th, you should generate the report in July. This way you can ensure that payments that were in Authorised state are now in their final state, for example, Captured or Expired.\nYou can generate a Received Payments Report automatically based on a schedule, or manually for a specific day or consecutive days in your Customer Area.\nSample\nDownload a sample BalancePlatform Received Payments Report for examples of the included data.\nBased on your platform settings, the report you generate in your account can contain additional data or columns that are not included in the sample report.\nReport structure\nEvery row in the Received Payments Report represents one payment with its final state reached when the report was generated.\nThe first three rows of the report contain the following information.\nBalancePlatform Received Payments as at\nYYYY-MM-DD\nPayments\nThe header row is in the fourth row and contains the following information.\n\n\n\n#\nColumn\nData type\nDescription\n\n\n\n\n1\nBalance Platform\nUnicode Text\nName of your Balance Platform account.\n\n\n2\nAccount Holder\nUnicode Text\nUnique identifier of the account holder that owns the balance account.\n\n\n3\nBalance Account\nUnicode Text\nUnique identifier of the balance account associated with the payment instrument.\n\n\n4\nTransaction Id\nAlpha text(16-character limit)\nUnique transaction id in Adyen's accounting systems.\n\n\n5\nJournal Type\nUnicode Text\nThe latest available status of the payment.When the report is generated 2 weeks after the report date, expect only final states (Captured, Refused, Expired, Cancelled, and Refunded). When the report is generated less than 2 weeks after the report date, expect also non-final states, for example, Authorised.\n\n\n6\nAuthorisation PSP Reference\nAlpha text(16-character limit)\nAdyen's 16-character unique reference associated with the authorization request.\n\n\n7\nPayment Instrument Type\nUnicode text\nThe type of the payment instrument used in the payment.\n\n\n8\nPayment Reference\nUnicode Text (16-character limit)\nUnique identifier of the payment instrument used in the payment.\n\n\n9\nAuthorisation Date\nDate field + Time field\nTimestamp of the date and time of the payment.\n\n\n10\nAuthorisation TimeZone\nAlpha text(4-character limit)\nTime zone of the Authorisation Date column.\n\n\n11\nTransaction Date\nDate field\nTimestamp indicating when the transaction was created in Adyen's accounting systems.\n\n\n12\nTransaction TimeZone\nAlpha text(4-character limit)\nThe time zone of the Transaction Date.\n\n\n13\nOriginal Currency\nAlpha text(3-character limit)\nThe currency of the payment amount as received from the acquirer. Its value is a three-character ISO 4217 currency code.\n\n\n14\nOriginal Amount\nFixed point number\nThe payment amount in the currency defined in Original Currency.\n\n\n15\nInstructed Currency\nAlpha text(3-character limit)\nThe currency of the amount deducted from the balance account for this payment.\n\n\n16\nInstructed Amount\nText field numeric(16-character limit)\nThe amount deducted from the balance account, in the currency defined in Instructed Currency.\n\n\n17\nDescription\nUnicode text\nA unique description generated for the payment.\n\n\n18\nEntrymode\nUnicode text\nThe point-of-sale entry mode as reported by the acquirer.Possible values: MANUAL, CHIP, MAGSTRIPE, MAGSTRIPE_FALLBACK, CONTACTLESS, CONTACTLESS_MAGSTRIPE, COF, TOKEN, E_COMMERCE, SERVER, BARCODE, OCR, UNKNOWN.\n\n\n19\nAuth Code\nText field numeric\nA unique authorisation code generated for the payment. This code should be included when canceling or refunding a payment.\n\n\n20\nShopper Interaction\nAlpha text(30-character limit)\nTransaction type. Possible values: Ecommerce, ContAuth, POS, Moto.\n\n\n21\nCounterparty Name\nUnicode text\nThe name of the merchant that initiated the payment.\n\n\n22\nCounterparty Address\nUnicode text\nThe address of the merchant that initiated the payment.\n\n\n23\nCounterparty City\nUnicode text\nThe city of the merchant that initiated the payment.\n\n\n24\nCounterparty Country\nUnicode text\nThe location of the merchant that initiated the payment. Its value is a three-character ISO 3166-1 alpha-3 country code.\n\n\n24\nMCC\nText field numeric\nThe merchant category code of the merchant that initiated the payment.\n\n\n25\nCounterparty iban\nUnicode text\nThe IBAN of the merchant that initiated the payment.\n\n\n26\nCounterparty bic\nAlpha text\nThe BIC of the bank of the merchant that initiated the payment.\n\n\n27\nCounterparty Account Number\nUnicode Text\nThe account number of the merchant that initiated the payment.\n\n\n28\nBeneficiary Balance Account\nUnicode Text\nThe unique identifier of the beneficiary balance account associated with your platform.\n\n\n29\nReserved2\n-\nReserved for future enhancements\n\n\n30\nReserved3\n-\nReserved for future enhancements\n\n\n31\nReserved4\n-\nReserved for future enhancements\n\n\n32\nReserved5\n-\nReserved for future enhancements\n\n\n33\nReserved6\n-\nReserved for future enhancements\n\n\n34\nReserved7\n-\nReserved for future enhancements\n\n\n35\nReserved8\n-\nReserved for future enhancements\n\n\n36\nReserved9\n-\nReserved for future enhancements\n\n\n37\nReserved10\n-\nReserved for future enhancements\n\n\n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Report types","lvl3":"Received Payments Report"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"https:\/\/docs.adyen.com\/pt\/issuing\/report-types","lvl3":"\/pt\/issuing\/report-types\/received-payments-report"},"levels":4,"category":"Issuing","category_color":"green","tags":["Received","Payments","Report"]},"articleFiles":{"SAMPLE_balanceplatform_received_payments_report_2022_01_01.csv":"
SAMPLE_balanceplatform_received_payments_report_2022_01_01.csv<\/p>"}}