A dispute is a request to review and correct credit-file information that appears inaccurate or incomplete.
Dispute means a request to review and correct credit-file information that appears inaccurate, incomplete, or not properly associated with the consumer. In credit-reporting context, the word usually refers to a formal challenge raised with a bureau or another reporting party.
Dispute matters because inaccurate reporting can affect approvals, pricing, stress levels, and how a borrower understands their own file. If readers do not know the language of disputes, they may leave bad information unchallenged or take the wrong next step.
It also matters because “something looks wrong” is not specific enough on its own. A dispute works best when the borrower can identify which account, inquiry, balance, or status is being questioned and why.
In Canada, dispute activity often begins after the borrower reviews a Consumer Disclosure from Equifax Canada or TransUnion Canada. The borrower identifies the item that appears inaccurate, gathers supporting context, and asks for review through the relevant process, which can lead into a Bureau Investigation.
The exact path can vary depending on whether the issue lies with the bureau file, the furnisher, or both. That is why borrowers often need to understand the disputed item clearly before sending anything. A vague complaint is harder to investigate than a focused request tied to one tradeline, inquiry, or collection entry.
A borrower reviews a disclosure and sees a Collection Account they do not recognize. Instead of assuming the file will fix itself, the borrower identifies the entry, gathers account details, and starts a dispute asking the bureau to review that specific reporting item.
Dispute is not the same as general frustration with a credit decision. A dispute is about the accuracy or completeness of reporting information, not simply disagreement with a lender’s business judgment.
It is also not limited to fraud. Fraud can create reasons for a dispute, but disputes also arise from ordinary reporting errors, outdated statuses, or mixed-file problems.