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 Summary Report	https://dashboard.boulevard.io/reports/disputes_summary

Overview

The Disputes report provides a consolidated view of payment dispute cases tied to customer transactions across your locations. It includes key details such as dispute amounts, statuses, related orders, clients, and associated merchant accounts.

Use this report to monitor overall dispute volume, understand financial exposure, and review the current status of each case. It helps teams reconcile disputed transactions, assess risk across locations, and get a clear, high-level view of dispute activity without diving into individual action details.

Note: Dispute Amount reflects what the cardholder's bank placed under dispute — the amount originally paid — not the amount actually debited from your bank account, which will be slightly lower once Boulevard deducts original processing fees. See the Report Caveats section below for more.

For an action-by-action timeline of how a specific dispute was handled, see the Disputes Activity Report.

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 monitoring & resolution tracking	Monitor open and resolved disputes to ensure timely follow-up and resolution with payment processors.	Which disputes are currently open? Which ones are under review or recently closed?
Financial exposure management	Understand the dollar value at risk from disputes and how much revenue is currently under dispute.	How much money is tied up in disputes this week? What is the total disputed amount by location?
Order-level investigation	Quickly trace disputes back to the original order, client, and payment details for root-cause analysis.	Which order triggered this dispute? Who was the client and cardholder?
Location & merchant analysis	Identify patterns in disputes across locations or merchant accounts.	Are certain locations or merchant accounts seeing higher dispute rates?
Customer issue escalation handling	Enable quick response to customer escalations by validating dispute details while context is fresh.	When was the dispute filed? What was the original charge and payment date?

Prerequisites

Before using the 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	Yes
Order Number	Human-readable order number associated with the disputed transaction.	262219	Yes

Columns (default)

The default columns displayed when you first open the report.

Field name	Definition	Example	Filter?
Dispute Case Number	Unique identifier assigned by the payment processor to track a specific dispute case.	9918393103	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
Dispute Date	Local date and time when the dispute was initiated by the cardholder or processor.	2023-10-23	Yes
Order Date	Local date and time when the original order associated with the dispute was created.	2023-10-23	Yes
Location Name	Name of the business location where the disputed transaction originated.	Upper East Side	Yes
Client Name	Full name of the client associated with the disputed transaction.	Emily Schulenburg	Yes
Cardholder Name	Name of the cardholder as provided by the payment processor for the disputed charge.	Emily Schulenburg	No
Original Charge Amount	Original transaction amount charged to the client before any refunds or adjustments. Units: dollars.	$100	No
Dispute Amount	Dollar amount under dispute as reported by the payment processor. Units: dollars.	$159	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 Value	Filter?
Merchant Name	Name of the merchant account used to process the disputed transaction.	UES	Yes
Order Number	Human-readable order number associated with the disputed transaction.	262219	Yes
Dispute Case Number	Unique identifier assigned by the payment processor to track a specific dispute case.	9918393103	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
Dispute Date	Local date and time when the dispute was initiated by the cardholder or processor.	2023-10-23	Yes
Order Date	Local date and time when the original order associated with the dispute was created.	2023-10-23	Yes
Location Name	Name of the business location where the disputed transaction originated.	Upper East Side	Yes
Client Name	Full name of the client associated with the disputed transaction.	Emily Schulenburg	Yes
Cardholder Name	Name of the cardholder as provided by the payment processor for the disputed charge.	Emily Schulenburg	No
Original Charge Amount	Original transaction amount charged to the client before any refunds or adjustments. Units: dollars.	$100	No
Dispute Amount	Dollar amount under dispute as reported by the payment processor. Units: dollars.	$159	No
Dispute ID	Unique identifier assigned by the payment processor to track a specific dispute case.	d453456f-6127-4714-99fa-c9e01545bb44	No
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.	Emily	Yes
Client ID	Unique identifier of the client associated with the disputed transaction.	d453456f-6127-4714-99fa-c9e01545bb44	No
Location ID	Unique identifier for the business location associated with the disputed transaction.	f982e666-0f5e-4769-832b-b3b123ace86a	No
Location External ID	External system identifier for the business location, if provided.	09f9246a-c1eb-4776-ad70-a56e07984235	No
Order ID	Unique internal identifier of the order associated with the disputed transaction.	e0172fcd-3e7c-42e5-9c6c-dec220224395	No
Responded On	Local date and time when the dispute response was submitted.	2023-01-30	Yes
Payment Date	Local date and time when the original payment was captured or settled.	2023-01-30	Yes
Location Tags	Tags associated with the business location for categorization and filtering.	UES	Yes
Order tag	Order tag associated with the order, if applicable.	Member Appt	Yes
Client tag	Client tag associated with the purchasing client, if applicable.	Member	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
Boulevard includes two dispute-related reports	Disputes — one row per dispute case. Use this to see what disputes exist, their current status, the amounts at stake, and who they're linked to. Dispute Monetary Actions — one row per financial action taken on a dispute. Use this if you need to understand the timeline of fund movements for a specific dispute case.
Dispute Amount ≠ Bank Debit Amount	The Dispute Amount shown in this report reflects what the cardholder's bank has placed under dispute — this is the amount the client originally paid. The actual dollar amount debited from your bank account when a dispute is initiated will be slightly lower, because Boulevard deducts the original payment processing fees from that debit. Do not expect these two figures to 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 monitoring & resolution tracking	Monitor open and resolved disputes to ensure timely follow-up and resolution with payment processors.	Use default configuration. Filters: Dispute Status = New, Responded, Contested Pending, or Arbitration Pending for open cases (or Won and Lost for closed);
Financial exposure management	Understand the dollar value at risk from disputes and how much revenue is currently under dispute.	Group by: Location Name, Dispute Status. Columns: Dispute Amount, Original Charge Amount. Filters: Dispute Status = the open statuses; set Dispute Date to the exposure window.
Order-level investigation	Quickly trace disputes back to the original order, client, and payment details for root-cause analysis.	Use default configuration Columns: add Payment Date. Filters: Order Number = the order in question (or Client Name = the client); widen Dispute Date to cover the case.
Location & merchant analysis	Identify patterns in disputes across locations or merchant accounts.	Filters: set Dispute Date to the comparison period. Group by: Location Name, Merchant Name. Columns: Dispute Amount, Original Charge Amount.
Customer issue escalation handling	Enable quick response to customer escalations by validating dispute details while context is fresh.	Use default configuration Columns: add Payment Date. Filters: Client Name = the client; widen Dispute Date if the case is older than a year.

Disputes Summary Report