Case Reconciliation report

This report supports case management by providing details about cases that opened or closed on your platform during the reporting period. Cases include PayPal-initiated reversals, chargebacks, disputes, and dispute claims.

Download a sample report

To review what's available in this report, download a sample in CSV format. This sample may vary from your actual report, depending on your settings.

Report file name

The file name of the Marketplaces Case Reconciliation Report for a single account follows this naming convention:

MCR.yyyymmdd.ReportIdentifier.ReportingWindow.SequenceNumber.MajorVersion.MinorVersion.Format

Field, Information
Field	Information
`MCR`	An abbreviation for Marketplaces Case Reconciliation Report.
`yyyymmdd`	The date for the data in the report. It represents the latest, or ending date, of the data.
`ReportIdentifier`	This is the unique value to identify the report, such as the BN code or organization name.
`ReportingWindow`	The window of time in which the report was generated.
`SequenceNumber`	The sequence number of the report file. The sequence number begins with `0` and continues until all parts of the report are recorded in files. The sequence number is always present in the report filename even if there is only one file.
`MajorVersion`	The major version of the report.
`MinorVersion`	The minor version of the report.
`Format`	The report format is `CSV` (comma-separated values).

Prerequsites

You must be an approved partner to use this report.
This report is available if you onboard your sellers before payment.
This report is generated and placed on SFTP by 9:00 AM daily in the leading time zone of the reporting window.
A single file contains all cases.
The actual amounts in this report are multiplied by 100 to represent the amounts as cents. For instance, a $10 entry appears as 1000 on the report.
Read the report data by column header name instead of column index to maintain backward compatibility.

Format

Each row of the report consists of a 2-letter row type, followed by the details specific to that row type. The following table lists the valid row types and the sections that describe the data for that row type.

Code, Description
Code	Description
FH	File header
SH	Section header
CH	Column header
SB	Section body
SF	Section footer
FF	File footer

File header data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`FH`).
2	Report Generation Date	`Date-time`	The date and time at which the report file was generated, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
3	Reporting Window	`Varchar`, single character, one of: `A`, `H`, `R`, `X`.	The window of time in which the report was generated, as follows: `A`: America/New York to America/Los Angeles. `H`: America/Los Angeles to Asia/Hong Kong. `R`: Asia/Hong Kong to Europe/London. `X`: Europe/London to America/New York.
4	Report Period Start Date	`Date-time`	The beginning date and time for which to include transactions in the report, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
5	Report Period End Date	`Date-time`	The final date and time for which to include transactions in the report, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
6	Partner Account Number	`Varchar`	The partner's PayPal encrypted account number.
7	Report Identifier	`Varchar`	This unique value identifies the report, such as the BN code or organization name.

Section header data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`SH`).

Section body data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`CH`).
2	CASE_ID	`String`	The PayPal-generated ID for the case in either of these formats: `PP-000-111-222-333` or `PP-D-99999`.
3	CASE_TYPE	`Literal`	The case type. Can be one of `CHARGEBACK`, `DISPUTE` or `CHARGEBACK - RDR` (RDR - Rapid Dispute Resolution¹).
4	CASE_REASON	`String`	The reason for the case. Can be one of the following: `Charge not recognized` `Credit not processed` `Duplicate payment` `Inquiry - ACHReturn` `Item not received` `Item not received - ACHReversal` `Merchandise` `Merchandise - ACHReversal` `Not as described` `Other` `Processing error` `Recurring payment cancelled` `Unauthorized` `Unauthorized - ACHReversal` `Unauthorized - ATO` .
5	CASE_FILING_DATE	`Date-time`	Date and time at which the case was filed, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
6	CASE_STATUS	`String`	The status of the case. Can be one of the following: `Being Reviewed By PayPal` `Open` `Requiring your action` `Resolved` `Waiting For Additional Information` `Waiting for Buyer's Response` `Waiting For Seller's Response`
7	PAYPAL_REFERENCE_ID	`String`	The original parent transaction ID.
8	INVOICE_NUMBER	`String`	The invoice number for the transaction.
9	CUSTOM_FIELD	`String`	A field for custom data.
10	CASE_AMOUNT	`Money`	The disputed amount.
11	CASE_CURRENCY	Three-character currency code	The disputed amount currency.
12	RESPONSE_DUE_DATE	`Date-time`	Date and time by which merchant is expected to respond for this case, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
13	CASE_TRANSACTION_ID	`String`	The parent transaction ID.
14	CASE_REFUND_AMOUNT	`Money`	Amount refunded to buyer.
15	CASE_REFUND_CURRENCY	Three-character currency code	The currency of refunded amount to buyer.
16	CASE_UPDATE_DATE	`Date-time`	Date and time at which the case was updated, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
17	FINAL_CASE_OUTCOME	`Literal`	The final outcome of the dispute. The value is one of the following: `RESOLVED_BUYER_FAVOUR` `RESOLVED_SELLER_FAVOUR` `RESOLVED_WITH_REFUND` `CANCELED_BY_BUYER` Left blank if the dispute or chargeback is not resolved.
18	PROCESSOR_REASON_CODE	`String`	The dispute reason code returned by the card network. This value is not normalized. Use `CASE_REASON` for the normalized dispute reason.
19	BUYER_NOTES	`String`	The buyer's reason or notes explaining why they filed the chargeback.

¹Rapid Dispute Resolution (RDR) is a Visa service designed to help merchants prevent chargebacks by automating the resolution of disputes at the pre-dispute stage, often through automatic refunds.

Section footer data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`SF`).

File footer data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`FF`).

Download a sample report

To review what's available in this report, download a sample in CSV format. This sample may vary from your actual report, depending on your settings.

Report file name

The file name of the Marketplaces Case Reconciliation Report for a single account follows this naming convention:

MCR.yyyymmdd.ReportIdentifier.ReportingWindow.SequenceNumber.MajorVersion.MinorVersion.Format

Field, Information
Field	Information
`MCR`	An abbreviation for Marketplaces Case Reconciliation Report.
`yyyymmdd`	The date for the data in the report. It represents the latest, or ending date, of the data.
`ReportIdentifier`	This is the unique value to identify the report, such as the BN code or organization name.
`ReportingWindow`	The window of time in which the report was generated.
`SequenceNumber`	The sequence number of the report file. The sequence number begins with `0` and continues until all parts of the report are recorded in files. The sequence number is always present in the report filename even if there is only one file.
`MajorVersion`	The major version of the report.
`MinorVersion`	The minor version of the report.
`Format`	The report format is `CSV` (comma-separated values).

Prerequsites

You must be an approved partner to use this report.
This report is available if you onboard your sellers before payment.
This report is generated and placed on SFTP by 9:00 AM daily in the leading time zone of the reporting window.
A single file contains all cases.
The actual amounts in this report are multiplied by 100 to represent the amounts as cents. For instance, a $10 entry appears as 1000 on the report.
Read the report data by column header name instead of column index to maintain backward compatibility.

Format

Code, Description
Code	Description
FH	File header
SH	Section header
CH	Column header
SB	Section body
SF	Section footer
FF	File footer

File header data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`FH`).
2	Report Generation Date	`Date-time`	The date and time at which the report file was generated, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
3	Reporting Window	`Varchar`, single character, one of: `A`, `H`, `R`, `X`.	The window of time in which the report was generated, as follows: `A`: America/New York to America/Los Angeles. `H`: America/Los Angeles to Asia/Hong Kong. `R`: Asia/Hong Kong to Europe/London. `X`: Europe/London to America/New York.
4	Report Period Start Date	`Date-time`	The beginning date and time for which to include transactions in the report, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
5	Report Period End Date	`Date-time`	The final date and time for which to include transactions in the report, in the following format: `YYYY/MM/DDHH:MM:SS offset`, where `offset` is the 5-character signed offset from GMT. For example, `+0800`.
6	Partner Account Number	`Varchar`	The partner's PayPal encrypted account number.
7	Report Identifier	`Varchar`	This unique value identifies the report, such as the BN code or organization name.

Section header data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`SH`).

Section body data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`CH`).
2	CASE_ID	`String`	The PayPal-generated ID for the case in either of these formats: `PP-000-111-222-333` or `PP-D-99999`.
3	CASE_TYPE	`Literal`	The case type. Can be one of `CHARGEBACK`, `DISPUTE` or `CHARGEBACK - RDR` (RDR - Rapid Dispute Resolution¹).
4	CASE_REASON	`String`	The reason for the case. Can be one of the following: `Charge not recognized` `Credit not processed` `Duplicate payment` `Inquiry - ACHReturn` `Item not received` `Item not received - ACHReversal` `Merchandise` `Merchandise - ACHReversal` `Not as described` `Other` `Processing error` `Recurring payment cancelled` `Unauthorized` `Unauthorized - ACHReversal` `Unauthorized - ATO` .
5	CASE_FILING_DATE	`Date-time`	Date and time at which the case was filed, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
6	CASE_STATUS	`String`	The status of the case. Can be one of the following: `Being Reviewed By PayPal` `Open` `Requiring your action` `Resolved` `Waiting For Additional Information` `Waiting for Buyer's Response` `Waiting For Seller's Response`
7	PAYPAL_REFERENCE_ID	`String`	The original parent transaction ID.
8	INVOICE_NUMBER	`String`	The invoice number for the transaction.
9	CUSTOM_FIELD	`String`	A field for custom data.
10	CASE_AMOUNT	`Money`	The disputed amount.
11	CASE_CURRENCY	Three-character currency code	The disputed amount currency.
12	RESPONSE_DUE_DATE	`Date-time`	Date and time by which merchant is expected to respond for this case, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
13	CASE_TRANSACTION_ID	`String`	The parent transaction ID.
14	CASE_REFUND_AMOUNT	`Money`	Amount refunded to buyer.
15	CASE_REFUND_CURRENCY	Three-character currency code	The currency of refunded amount to buyer.
16	CASE_UPDATE_DATE	`Date-time`	Date and time at which the case was updated, in the following format: `YYYY/MM/DD HH:MM:SS offset`. `YYYY` is the 4-digit year. `MM` is the 2-digit month of the year. `DD` is the 2-digit day of the month. `HH` is the hour in 24-hour notation. `MM` is minutes. `SS` is seconds. `offset` is the 5-character signed offset from GMT, such as `+0800`.
17	FINAL_CASE_OUTCOME	`Literal`	The final outcome of the dispute. The value is one of the following: `RESOLVED_BUYER_FAVOUR` `RESOLVED_SELLER_FAVOUR` `RESOLVED_WITH_REFUND` `CANCELED_BY_BUYER` Left blank if the dispute or chargeback is not resolved.
18	PROCESSOR_REASON_CODE	`String`	The dispute reason code returned by the card network. This value is not normalized. Use `CASE_REASON` for the normalized dispute reason.
19	BUYER_NOTES	`String`	The buyer's reason or notes explaining why they filed the chargeback.

¹Rapid Dispute Resolution (RDR) is a Visa service designed to help merchants prevent chargebacks by automating the resolution of disputes at the pre-dispute stage, often through automatic refunds.

Section footer data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`SF`).

File footer data

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	Column Type	`Literal`	The column type (`FF`).

Case Reconciliation report

Download a sample report

Report file name

Prerequsites

Format

File header data

Section header data

Section body data

Section footer data

File footer data

On this page

On this page

On this page

Case Reconciliation report

Download a sample report

Report file name

Prerequsites

Format

File header data

Section header data

Section body data

Section footer data

File footer data

On this page

On this page

Case Reconciliation report

On this page

On this page

On this page

If you accept cookies, we’ll use them to improve and customize your experience and enable our partners to show you personalized PayPal ads when you visit other sites. Manage cookies and learn more

Case Reconciliation report

On this page

On this page