What is a chargeback report?

A chargeback report is a processor, acquirer, gateway, or payment-platform record that organizes dispute cases and their related transaction details. Merchant teams can use it to track case activity, coordinate responses, and connect dispute events with internal order and accounting records.

Direct answer

What the report is designed to show

A chargeback report provides a structured view of disputes associated with a merchant's payment activity. Depending on the provider, the report may be called a chargeback report, dispute report, case report, or chargeback and retrieval details report. It may appear in an online dashboard, a downloadable file, or a reporting interface.

The report is not necessarily a single snapshot of one row per case. Some systems report each case once, while others create separate rows when a dispute changes status or has a financial-impact event. Read the provider's field definitions before using row counts as case counts.

Report anatomy

Fields a merchant may encounter

Names, availability, and definitions vary, but current provider documentation shows several recurring field groups.

Case identifiers

A case ID, case number, or dispute transaction reference helps staff connect a report row with the corresponding case in the provider portal. Keep the provider's identifier separate from the merchant's order number.

Original transaction details

Reports can include the original transaction reference, transaction date, payment method, currency, or invoice identifier. These values help locate the sale in order, customer-service, and accounting systems.

Reason and status

A dispute reason, reason code, case type, status, filing date, or resolution indicator can describe why the case exists and where it stands. Use the provider's current glossary because labels are not universal.

Response and impact details

Some reports show a respond-by date, requested evidence, disputed amount, currency, or debit and credit events. Treat these fields as provider-specific records and reconcile them with the related statement or financial-impact report when available.

Working method

How to review a chargeback report

1. Confirm the reporting window

Check whether the file is based on cases opened, updated, resolved, or financially affected during the selected dates. A single case may appear outside the original sale date or across more than one report period.

2. Match the case to the sale

Use non-sensitive references such as the order number, transaction ID, invoice ID, and transaction date to find the internal record. Do not copy full card numbers or authentication credentials into a shared reconciliation file.

3. Check status and required action

Open the corresponding case in the provider's dispute interface and verify the current status, response instructions, and any deadline displayed there. The downloadable report may not be the system used to submit a response.

4. Reconcile related events

Where the provider supplies separate statement, settlement, or financial-impact reporting, match the case identifier and amounts across those records. Investigate unmatched entries rather than assuming every report row represents a new debit.

Team controls

Build a repeatable review routine

Assign an owner for downloading or reviewing the report, matching each case, confirming action status, and documenting the outcome. Limit report access to people who need it, follow the provider's access controls, and store exports according to the business's approved data-retention practices.

Create a small internal field map that translates each provider column into the business's order, support, and accounting references. Record whether a row represents a new case, a status update, or a financial event. This prevents teams from treating unlike events as duplicates or counting one dispute multiple times.

Provider-specific guidance matters: Report names, columns, delivery schedules, access methods, and dispute workflows differ. Confirm current instructions inside the merchant's own provider portal before acting.

Practical questions

Common chargeback report questions

Is a chargeback report the same as a processing statement?

Not usually. A chargeback report focuses on dispute cases or related events, while a processing statement summarizes broader account activity. Providers may require both records for complete reconciliation.

Why can one case appear more than once?

Some providers create a row for each status or financial-impact event. Group records by the provider's case identifier and use its documentation to interpret the event type.

Does the report replace the dispute portal?

Not automatically. A report can support tracking and reconciliation, but the provider may require merchants to review instructions or submit evidence through a separate portal or API.

Related guidance

Connect reporting with dispute operations

Statements, Reporting & ReconciliationExplore practical guidance for reviewing processor records and matching payment activity. Chargebacks & DisputesReview the dispute lifecycle, terminology, evidence, and operational questions. What Is a Chargeback?Start with a plain-language explanation of the underlying payment reversal. How the Chargeback Process WorksSee how a dispute can move through review and response stages.

Next step

Map your provider's report to your workflow

Download the current field guide or glossary from your provider, identify the case key and event types, and document who reviews each actionable row.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.