Disputes Activity Report | Boulevard Support Center

We're excited to bring you an expanded reporting experience. If you don't see the reporting features described below, don't worry—this updated reporting experience will become available to your account over time.

Resource	Link
Disputes Activity Report	https://dashboard.boulevard.io/reports/disputes_activity

Overview

The Disputes Activity report helps you track the individual actions and stages of a disputed charge from start to finish. Unlike the Disputes Summary report, which shows one row per case, this report shows one row per action, so you can see the full sequence of events as a dispute moves through its lifecycle.

Use this report to follow a specific dispute through the resolution process, confirm responses were submitted on time, and audit the sequence of actions taken from filing through resolution. It's especially useful for tracking high-value or escalated disputes, since you can sort by action date to read a case chronologically and confirm all required steps have been completed.

Note: This report defaults to filtering by Dispute Date, not Action Date — so recent actions on older disputes won't appear until you widen the Dispute Date filter. Dispute Status also reflects the case's current status on every row, not the status at the time each action occurred; use Dispute Action Stage to see where an action fell in the lifecycle. See the Report Caveats section below for how Original Charge Amount repeats on every action row, which can overstate totals if summed across a case.

What this report is best used for

Understand when and why to use this report through common use cases, descriptions, and example questions it can help answer in your day-to-day operations.

Use cases	Description	Example questions this report helps answer
Dispute handling activity tracking	Monitor all actions taken on disputes to ensure cases are being actively managed and followed up with payment processors.	Which actions have been taken on this dispute? When was the last update?
Operational accountability	Track when responses were provided to a dispute.	When was a response provided to this dispute? Are responses being submitted on time?
Response timeliness monitoring	Evaluate how quickly teams are responding to disputes after they are filed.	How long did it take to submit evidence or a response after the dispute date?
Dispute lifecycle auditing	Understand the sequence of actions taken from dispute filing through resolution.	What steps were taken before this dispute moved to the next stage?
Risk and exposure follow-up	Track high-value or escalated disputes by reviewing all actions taken and outstanding steps.	Have all required actions been completed for high-dollar disputes?

Prerequisites

Before using this report, make sure the following are in place. These directly impact whether you can access the report and how accurate the data will be.

Permissions: You must have the appropriate Data & Reporting permissions enabled to see this report: Financials Reporting > Payment & Disputes
- If you don’t see the report, check your permissions first - see Reporting Permissions for more information.
Location and Access Scope: What you see in the report depends on your access:
- You’ll only see data for assigned locations
- Row-level access may further limit visible data
- If it looks like data is missing, verify your location assignments and access settings.
Required Setup: For the report to show meaningful data, your account must have at least one recorded transaction dispute.

Default report configuration

See how the report is structured when first opened. Learn what each field represents, how the data is organized, and which fields can be used to filter results.

Group By (default)

The default fields the report is grouped by when you first open it.

Field name	Definition	Example	Filter?
Merchant Name	Name of the merchant account used to process the disputed transaction.	UES	No
Order Number	Human-readable order number associated with the disputed transaction.	3478074	No
Dispute Action ID (hidden in table, visible in exports)	Unique identifier for the monetary or status-related action recorded on a specific dispute case.	dc6041bf-475a-4c18-bff8-4fb29fc7ffde	No

Columns (default)

The default columns displayed when you first open the report.

Field name	Definition	Example	Filter?
Dispute Case Number	Human-readable case number assigned to a dispute by the payment processor to track the dispute lifecycle.	9928064414	No
Dispute Date	The local date and time when the dispute was initiated by the cardholder or payment processor.	2026-03-23	Yes
Action Date	The local date and time when the dispute action occurred or was recorded.	2026-03-22	No
Dispute action stage	Dispute stage associated with this action One of: chargeback, contested, pre-arbitration, arbitration,	chargeback	No
Dispute Status	Displays the current status of the dispute. One of: Won, Responded, Lost, Lost Pending, New, Contested Pending, Arbitration Pending, Contact BLVD, Pre-Chargeback, Contested.	Responded	Yes
Client Name	Full name of the client associated with the disputed transaction.	Dorothy Stenson	Yes
Original Charge Amount	Dollar amount of the original transaction charged to the client before any refunds or adjustments. Units: dollars.	$120	No
Dispute Action Amount	Dollar amount currently under dispute as reported by the payment processor. Units: dollars.	-$0.58	No
Action Type	Type of monetary action taken on the dispute. One of: Debit or Credit	debit/credit	No
Action Count	Count of dispute actions recorded for the dispute case. Units: count.	1	No

Customizable fields

Explore the fields you can adjust to tailor the report to your needs. Each field includes a definition, example, and whether it can be used in filtering.

Field name	Definition	Example	Filter?
Merchant Name	Name of the merchant account used to process the disputed transaction.	UES	No
Order Number	Human-readable order number associated with the disputed transaction.	3478074	No
Dispute Action ID	Unique identifier for the monetary or status-related action recorded on a specific dispute case.	dc6041bf-475a-4c18-bff8-4fb29fc7ffde	No
Dispute Case Number	Human-readable case number assigned to a dispute by the payment processor to track the dispute lifecycle.	9928064414	No
Dispute Date	The local date and time when the dispute was initiated by the cardholder or payment processor.	2026-03-23	Yes
Action Date	The local date and time when the dispute action occurred or was recorded.	2026-03-22	No
Dispute action stage	Dispute stage associated with this action. One of: chargeback, contested, pre-arbitration, arbitration.	Chargeback	No
Dispute Status	Displays the current status of the dispute. One of: Won, Responded, Lost, Lost Pending, New, Contested Pending, Arbitration Pending, Contact BLVD, Pre-Chargeback, Contested.	Responded	Yes
Client Name	Full name of the client associated with the disputed transaction.	Dorothy Stenson	Yes
Original Charge Amount	Dollar amount of the original transaction charged to the client before any refunds or adjustments. Units: dollars.	$120	No
Dispute Action Amount	Dollar amount currently under dispute as reported by the payment processor. Units: dollars.	-$0.58	No
Action Type	Type of monetary action taken on the dispute. One of: Debit or Credit	debit/credit	No
Action Count	Count of dispute actions recorded for the dispute case. Units: count.	1	No
Dispute ID	Unique identifier assigned by the payment processor to track a specific dispute case.	dc6041sbf-475a-4c18-bfsf8-4fb29fc7ffde	No
Client ID	Unique identifier of the client associated with the disputed transaction.	6dd4ab82-3f9c-488b-ac28-87e19ebbfc15	No
Location Name	The official name of the business location where the disputed transaction originated.	Upper East Side	Yes
Location Group	Logical grouping of business locations used for reporting rollups and segmentation.	NYC	Yes
Client First Name	First name of the client associated with the disputed transaction.	Dorothy	Yes
Cardholder Name	Name of the cardholder as provided by the payment processor for the disputed charge.	CARDHOLDER/VISA	No
Order Date	The local date and time when the original order associated with the dispute was created.	2026-03-01	Yes
Order ID	Unique internal identifier for the order associated with the disputed transaction.	9fdde28c-f40e-4961-9a1a-42f5cd120242	No
Location ID	Unique identifier for the business location associated with the disputed transaction.	177a3007-6b2b-4455-801e-d5f554e2ebd7	No
Location External ID	External system identifier for the business location, if provided.	177a3007-6b2b-4455-801e-d5f554e2esssbd7	No
Responded On	The local date and time when a dispute response was submitted to the processor.	2026-03-22	Yes
Payment Date	The local date and time when the original payment was captured or settled.	2026-03-01	Yes
Location Tags	Tags associated with the business location for categorization and filtering.	NYC	Yes
Order Tag	Tag associated with the order, if applicable, used for categorization and filtering.	First Appointment	Yes
Client Tag	Tag associated with the client, if applicable, used for categorization and filtering.	First Time Client	Yes

Report Caveats

There are a few important caveats and limitations to be aware of when using this report. Use these details to better understand how the data behaves and how to interpret it correctly.

Caveats	Details and Impact
One row per action, not per dispute	Each row is a single monetary or status action on a dispute. A single case appears multiple times as it moves through stages, so row counts reflect actions, not disputes.
Original Charge Amount repeats on every action	The original charge is attached to each action row for the same case. Summing it across a grouped case multiplies the charge; use it at the action level or in views grouped by case, not as a totaled column across actions.
The default date filter is the dispute date, not the action date	Dispute Date defaults to Last Week and filters on when the dispute was initiated. Recent actions on older disputes will not appear until you widen Dispute Date; use Action Date to scope by when activity occurred.
Dispute Status reflects the current status of the case	Every action row shows the dispute's status today, not the status at the time the action was taken. Use Dispute action stage for where each action occurred in the lifecycle.
Bank debits will be slightly lower than disputed amounts	When a dispute is initiated, the amount debited from your bank account is reduced by the original payment processing fees, so action amounts will not match your bank statement exactly.

Use Case Example Configurations

Learn how to set up the report for specific scenarios with practical examples. Follow along to create views that answer common questions and support your workflows.

Use case	Description	How to configure the report
Dispute handling activity tracking	Monitor all actions taken on disputes to ensure cases are being actively managed and followed up with payment processors.	Use default configuration. Filters: widen Dispute Date to cover the case; Client Name = the client to locate a specific dispute. Sort by: Action Date descending for the latest update.
Operational accountability	Track when responses were provided to a dispute.	Use default configuration Columns: add Responded On. Filters: set Dispute Date to the review period. (Staff attribution is not available in this report; only action and response dates are shown.)
Response timeliness monitoring	Evaluate how quickly teams are responding to disputes after they are filed.	Use default configuration. Columns: add Responded On. Filters: set Dispute Date to the period. Compare Responded On against Dispute Date per case. (No computed response-time measure exists; export to calculate the gap.)
Dispute lifecycle auditing	Understand the sequence of actions taken from dispute filing through resolution.	Use default configuration. Filters: Client Name = the client or widen Dispute Date to include the case. Sort by: Action Date ascending to read the case chronologically; Dispute action stage is already included.
Risk and exposure follow-up	Track high-value or escalated disputes by reviewing all actions taken and outstanding steps.	Use default configuration. Filters: Dispute Status = New, Contested Pending, or Arbitration Pending; set Dispute Date to the exposure window. Sort Original Charge Amount descending to review the highest-dollar cases first.