Credit-file information is personal data, so accuracy, fairness and source records matter as well as industry credit-reporting rules.
Credit reference agencies receive account information from lenders, telecom providers and other data suppliers. The organisations supplying the data and the CRAs have data-protection responsibilities. An incorrect balance, default date, account attribution or status can have a significant effect on a consumer.
Data-protection accuracy analysis overlaps with industry reporting standards such as PRAAD, but the frameworks are not identical. A statutory Consumer Credit Act default notice is also a separate concept from a credit-file default marker.
Key points
- Challenge the source organisation as well as the CRA where appropriate.
- Identify the exact field/status/date that is wrong.
- Use PRAAD where it is relevant to reporting practice, but do not describe it as legislation.
- A Notice of Correction is not a substitute for correcting data that is actually inaccurate.
Who controls the data?
The lender/provider that supplies account performance can usually make updates to the CRA feed. A CRA can investigate disputes, but “the CRA only displays what we are sent” does not mean nobody has responsibility for accuracy.
Default date matters
Defaults are generally retained for six years from the default date. An incorrectly late date can therefore keep adverse information visible longer than reporting practice expects. PRAAD provides industry principles about when the relationship is treated as broken down.
Disputed debt versus inaccurate data
Saying “I dispute the debt” does not automatically make the balance inaccurate. Show the factual/contractual reason the amount, status or attribution is wrong. If the underlying liability is genuinely unresolved, the way the data is represented may still need careful consideration.
In practice
- Get reports from all relevant CRAs because data can differ.
- Save the full account entry and status history.
- Write to the data furnisher with the precise correction sought.
What to do
A practical next-step plan
- Download your credit reports.
- Identify the disputed field.
- Gather account statements/notices/correspondence.
- Dispute with the data furnisher and CRA.
- Request restriction where appropriate while accuracy is checked.
- Escalate to ICO/FOS or relevant ombudsman depending on the organisation and issue.
Common traps
Things that often confuse the issue
- A credit-file default and CCA default notice are not the same thing.
- Do not use a Notice of Correction to paper over objectively wrong data.
- Different CRAs can receive different data, so check all three major agencies.
Evidence worth keeping
Ask for correction at source and propagation to recipients.
Where a lender accepts that data is wrong, ask it to correct the source record and notify the CRAs to which it supplied the information. Where accuracy is actively disputed, a request to restrict processing while the issue is checked may also be relevant. Keep screenshots or full statutory credit reports before and after correction so you can prove what changed.
Useful wording.
“I dispute the factual accuracy of the following fields: [list]. Please investigate them against the underlying account records, correct any inaccurate or misleading data at source, notify each CRA/recipient to whom it was disclosed, and tell me the result of your investigation.”
Do not collapse CCA enforcement rules and credit reporting into one argument.
A statutory default notice under the Consumer Credit Act and a credit-file default are not the same thing. The ICO has specifically explained that the absence of a remembered CCA default notice does not automatically mean a CRA default is inaccurate. If you dispute reporting, challenge the accuracy, fairness and reporting chronology directly and use the relevant credit-reporting principles as well as any separate CCA point.
Accuracy is not the same question as whether you like the entry.
UK data-protection law requires personal data to be accurate and, where necessary, kept up to date. A negative entry can be lawful if it accurately records what happened. Conversely, a balance, default date, payment marker, identity link or account status can be challengeable if it is factually wrong or misleading in context.
| Dispute | Evidence to obtain |
|---|---|
| Wrong balance/status | Statements, payment records, settlement correspondence. |
| Wrong default date | Arrears history, notices, account closure/termination chronology and reporting history. |
| Not my account | Identity/address history and lender application/account records. |
| Account was formally corrected | Complaint decision, court/ombudsman outcome or lender correction confirmation. |
Start by identifying who supplied the disputed entry.
A credit reference agency usually displays information supplied by a lender, telecom provider, utility or other data furnisher. The CRA and the organisation that supplied the data can each have data-protection responsibilities, but they do different things. Obtain the entry from each relevant CRA and identify the account owner, balance, status, dates and source before challenging it.
The practical boundary
Credit-file disputes often involve at least two controllers: the lender or other data furnisher that supplied the entry, and the credit reference agency that displays or uses it. A valid debt can still be reported inaccurately, while an unenforceability argument does not automatically require deletion of accurate credit-history data.
Questions the organisation should be able to answer
- Who supplied the disputed entry?
- Which field is wrong: balance, status, default date, identity or account ownership?
- What evidence supports the correct position?
- Has the dispute been raised with both source and CRA where appropriate?
- Should use be restricted or a notice of dispute added while checks occur?
Route examples
| Situation | Best next step |
|---|---|
| Wrong default date | Ask the furnisher to correct it and propagate the correction to each CRA. |
| Account belongs to another person | Raise an identity/data-matching dispute urgently and seek restriction. |
| Debt is disputed on contractual grounds | Separate the consumer-credit dispute from whether the credit record accurately describes the current status. |
Useful wording
“The disputed credit-file field is [field]. The entry shown is [value], but the accurate position is [value], supported by [evidence]. Please investigate at source, restrict disputed processing where appropriate and notify every recipient of any correction.”
Official sources
Check the rules behind this guide
- Credit information guidance - ICO
- Credit information - ICO
- Accuracy principle - ICO
- PRAAD and credit-reporting principles - CIGB
- ICO: Your right to get data corrected ↗
These are official or primary sources for this topic. Rules, scheme terms and deadlines can change, so check the live source before relying on a formal time limit or procedure.