Methodology and limitations

From complaints to risk insights

What the analysis sections show

Overview

A summary of the selected complaint population, Consumer Dispute Risk, recorded response measures and key findings. Consumer Dispute Risk helps prioritise review; it is not a credit rating or proof of misconduct.

Complaint Issues

The main complaint categories and their sub-issues, with counts, shares and available CTC evidence. Geographic views show where complaints were recorded.

Complaint Trends

Changes in complaint volume and recorded outcomes over time. Monthly charts can be explored by week and, where access permits, by day.

Company Public Response & Outcomes

How the source records company responses and complaint outcomes, together with supported patterns and areas for review. A recorded response does not establish consumer acceptance or a proven resolution.

Business Process & Controls

Potential weaknesses, their severity, possible business consequences, supporting complaint evidence and recommended controls. Users can distinguish financial-reporting relevance from operational relevance only.

Accounting & Financial Reporting

Potential accounting implications and supporting complaint evidence, including affected financial statement areas with their relevant assertions. Assertions are the claims about financial information that auditors test.

Consumer Redress Exposure

Low, Base and High scenarios for possible consumer redress, with a separate enforcement-risk overlay where supported. These are conditional estimates, not confirmed liabilities.

Company & Peer Comparison

Comparison of available complaint measures for selected companies. Differences should be read in context: complaint counts are not adjusted measures of company size or market share.

Preview shows selected content and clearly marked subscription locks. The amount of detail available depends on the user's access and the evidence supported by the selected scope.

Understanding Consumer Dispute Risk

Consumer Dispute Risk is a complaint-based indicator for prioritising review. It considers how consistently complaints recur, their recent direction and recorded response timeliness within the selected scope. It is not a prediction of future disputes, a measure of all customers’ experiences or proof of misconduct.

Recorded monetary and non-monetary relief remain visible as complaint outcomes. Providing relief does not automatically increase or decrease the risk score. An explanation-only closure or an in-progress complaint does not, by itself, establish a failure or an adverse outcome.

Fewer complaints do not necessarily mean lower risk. With small complaint populations, individual records can materially affect the rating. The source data are not a representative statistical sample, and the indicator is not adjusted for company size or market share. Recurrence describes recorded complaints across months; it does not establish repeated failures of the same control.

The scoring rules and rating bands are analytical judgement tools, not statistically calibrated probabilities. Short or incomplete periods provide less temporal context. Read the rating alongside the selected period, complaint patterns and recorded outcomes.

Periods, filters and comparisons

Preset periods and custom From/To dates define the complaints included in the analysis. Issue, product and geographic filters narrow that scope. Read the period and filter labels alongside each result.

Complete periods are compared with the preceding comparable period. Custom dates and incomplete periods use a matched comparison where the required source evidence is available. A partial current month is compared with the corresponding elapsed part of the prior month, rather than an entire prior month.

Percentage movement is not shown where a reliable comparison cannot be supported or the prior complaint count is zero. Missing evidence is not treated as zero. Some measures may be unavailable for a filter combination that the source cannot reliably support.

Current-month and recent weekly data can change as new complaints are published or existing records are updated. A movement in complaints does not, by itself, explain why it occurred.

Understanding severity and financial-reporting relevance

Potential Weakness Severity (PWS) indicates how concerning a supported process or control weakness appears from the complaint evidence. Its levels run from Minimal to Very High. It helps prioritise investigation; it does not prove that a control failed.

Financial-reporting relevance is a separate assessment. A weakness may have a clear connection to financial reporting, a conditional connection that needs further evidence, or no standalone financial-reporting consequence. An operational concern can still matter even without a direct accounting implication.

Assertion Risk Indicator (ARI) helps prioritise the complaint-derived signal for an identified financial-statement assertion. Its levels run from Limited to Critical. It does not add new assertions or replace an auditor's assessment of the risk of material misstatement.

Detailed findings and consolidated summaries can have different assessments because they cover different supporting populations. Neither severity nor financial-reporting relevance determines materiality, confirms a misstatement or establishes legal liability.

Cost to Consumers (CTC)

CTC is DebitGuard's assessment of qualifying monetary amounts described in available complaint evidence. It can include amounts the consumer disputes or challenges. It is not a verified loss, an amount awarded to the consumer or a confirmed liability of the company.

Monetary evidence does not cover every complaint or every date. CTC is shown only for complaints within the selected scope that also fall within the assessed monetary coverage. Newer or otherwise unassessed complaints are not treated as having zero cost.

A displayed $0 means no qualifying CTC amount was identified in the assessed portion of that scope. It does not mean all consumers were unaffected. Missing or withdrawn public narratives can limit what can be assessed, and previously assessed evidence may support only part of the current complaint population.

Amounts requiring further review, evidence with insufficient monetary detail and legal or compensation claims remain separate from the main CTC measure. CTC and estimated consumer redress are separate measures and should not be added together.

Estimated consumer redress and enforcement exposure

Consumer redress scenarios illustrate possible refunds, compensation, credits, account corrections or debt write-offs if recorded complaints are later upheld. They use product-specific assumptions and evidence-based benchmarks. The model does not assume that every complaint will require redress, and recorded corrective relief is kept separate to avoid counting it twice.

Low, Base and High describe alternative scenarios, not a forecast or a statistical confidence interval. The estimates are not accounting provisions, valuations or confirmed obligations. They do not capture every affected consumer who has not submitted a complaint.

Where supported, a separate enforcement-risk overlay illustrates potential regulatory penalties, external legal costs, and investigation or specialist costs. These categories remain separate from consumer redress; the tool does not combine them into a single headline total or predict that enforcement will occur.

Benchmarks draw on relevant official matters and documented assumptions. Some cost assumptions are for planning because comparable public evidence is limited. Published benchmark changes require evidence, documented approval and a controlled release. Detailed values, adjustments and eligibility rules are not published in this public overview.

Data updates and monitoring

Source updates are checked against the supported complaint population before they become part of the analysis. Complaint records may be added, corrected or reclassified, so later updates can change historical figures.

Subscriber monitoring uses saved company and product scopes, snapshots and configured schedules. Available schedules include weekly, monthly and quarterly reporting, plus critical-change monitoring with a quarterly summary.

Weekly reports cover completed weeks and are marked as preliminary signals. Monthly and quarterly reports use completed periods. Alerts highlight changes against the configured criteria; they do not establish their cause or prove a new weakness. Publication timing and source availability can affect when a report is ready.

Important limitations

• Complaints may contain allegations or perceptions that DebitGuard has not independently verified.
• Complaint counts do not show the number of unique customers, the whole customer base or the rate of problems across all transactions.
• Volumes can be affected by company size, market share, reporting awareness, customer demographics and changes in source coverage.
• The source does not necessarily cover every complaint, jurisdiction or part of a company's business.
• Consistent company names help presentation, but source names and identifiers may still require review. A company-level analysis does not establish that every affiliated entity shares the same risks.
• Recorded responses and relief do not, by themselves, prove complaint validity, consumer satisfaction, wrongdoing or a financial-statement misstatement.
• Missing data, limited evidence and changes in classification can restrict comparisons and conclusions.
• Recurring complaints and statistical relationships are signals for investigation, not proof of the underlying cause.

Your professional judgement remains essential

Use DebitGuard to focus investigation, risk reviews and monitoring. Check the source, scope and supporting complaint evidence, then consider the company's actual circumstances and obtain the evidence needed for your work.

The tool does not provide an audit opinion, an assurance conclusion, legal or investment advice, or a determination that a company has breached a law, accounting standard or contractual obligation.