Defaults & credit reporting

First: what exactly is wrong with the credit-file entry?

Do not begin with the word default. Begin with the field, event or decision you are challenging. Several very different problems can produce the same headline complaint: “there is a default on my credit file”.

Those are not interchangeable arguments. A strong complaint identifies each disputed field or process separately and states the correction or investigation required.

What a credit-file default actually means

A default is used to show that the relationship between the customer and the organisation has seriously broken down. It is more severe than an ordinary missed-payment or arrears marker. Defaults can appear in relation to regulated credit, but credit-reference reporting is not confined to Consumer Credit Act products: telecom, utility and other service providers may also share account-performance data where they participate in credit-data sharing.

That is why the first legal question is not “did they issue a Consumer Credit Act default notice?” It is “what kind of account is this, what data was reported, and which legal or industry framework governs that part of the dispute?”

Missed payments, arrears, arrangements and defaults are different

A single missed payment can be reported without the account being placed into default. Arrears can continue for a period while the account remains open. An arrangement to pay can also be reported where the consumer and provider have agreed temporarily reduced or altered payments. A default usually communicates something more serious: that the relationship has broken down.

Do not assume that a lender must either show “up to date” or “default”. Credit files are intended to record payment performance over time. The dispute is therefore often about whether the particular marker accurately and fairly reflects what happened in that month.

The default date matters: sometimes more than the existence of the default

A default is generally retained by CRAs for six years from the recorded default date. This makes the date a critical piece of personal data. If a provider delays recording a default long after the relationship had in substance broken down, the consumer may be left with adverse information for longer than the reporting framework intended.

PRAAD describes three to six months in arrears as a general guide for many ordinary accounts, not a mechanical statutory formula. Some products and circumstances operate differently. The correct question is whether the date fairly reflects the point at which the relationship had broken down, taking account of the account type, arrears history, arrangements, contact and applicable guidance.

Compare the CRA date with the provider's own collections chronology, termination or closure records, correspondence, internal account status, debt-sale history and any notice of intention to file a default. A date that cannot be reconciled with the provider's own records deserves a specific explanation.

Six years does not make an inaccurate default correct

“Defaults stay for six years” describes the usual retention period. It does not answer whether the entry was accurate in the first place. A default with the wrong date, balance, owner, status or account attribution does not become accurate merely because six years is the normal retention period.

Equally, a default that is accurate does not normally disappear just because it has been paid. It can remain as a historical record until the six-year period ends, with the later status updated to show that the debt has been satisfied or otherwise resolved as appropriate.

If a business gives you the stock answer “defaults stay for six years”, bring the discussion back to the disputed field: I am not asking how long an accurate default is retained; I am challenging whether this default date/balance/status is accurate.

PRAAD: industry reporting principles, not a Consumer Credit Act notice

The Principles for the Reporting of Arrears, Arrangements and Defaults at Credit Reference Agencies: usually shortened to PRAAD: explain how lenders and service providers should report arrears, payment arrangements and defaults. The material is now hosted by the Credit Information Governance Body (CIGB), alongside the Principles of Reciprocity and the Data Quality Reference Guide.

PRAAD is not legislation. It should not be described as though Parliament enacted a “PRAAD Act”. But it is highly relevant when testing whether industry reporting practice was followed, particularly around the meaning of a default, timing, arrangements, notification and the continuing accuracy of balances and status information.

The 28-day intention-to-file principle

PRAAD provides for advance notification of an intention to register a default in the ordinary cases to which that notification requirement applies. The public Version 2a states that the lender or provider should notify the customer of the intention to register a default at least 28 days before doing so, giving time to make an acceptable payment or reach an arrangement. The guidance contains exceptions for particular circumstances, so do not treat the 28-day point as an absolute rule detached from the facts.

If notification is disputed, ask for the actual notice, the date generated, the address or electronic destination used, the method of dispatch and the date on which the provider says the default became effective. A database field saying “letter sent” can be relevant evidence, but it is not the same as producing the notice and explaining the chronology.

A Consumer Credit Act default notice is a different document

For certain regulated credit agreements, section 87 of the Consumer Credit Act 1974 requires a compliant statutory default notice before the creditor can take specified enforcement steps. That notice has a different purpose from credit-reference reporting.

The ICO expressly explains that the absence of a Consumer Credit Act default notice does not, by itself, prevent a lender from recording an otherwise accurate credit-file default. Conversely, a telecom or utility provider cannot dismiss a complaint about credit-reporting notification merely by saying “the Consumer Credit Act does not apply”. That answers the wrong question if the consumer is relying on PRAAD or data-accuracy obligations.

ConsumerWise keeps these routes separate because the same word: default, is used for two legally different things. See Default notices for the statutory CCA route.

Telecom and utility defaults, do not force a credit-law framework onto a service contract

A broadband, mobile or energy account can affect a credit file even though the underlying service contract is not itself a conventional regulated loan or credit card. The provider's ability to report account performance and the accuracy of that reporting therefore need to be assessed under the correct framework.

For telecom disputes in particular, separate the underlying service or billing question from the reporting question. A provider may say a balance is due; the consumer may say it arose from incorrect billing, cancellation or service failure. The sector complaint route may be needed to resolve the bill, while the CRA/provider/ICO route deals with the accuracy and processing of the resulting personal data.

See Telecom credit reporting and Telecom defaults for the sector-specific layer.

A disputed balance does not automatically mean the credit data must disappear

This is one of the most important distinctions on the page. The ICO does not decide ordinary contractual or service disputes simply because they affect a credit file. If a broadband provider says £80 is due and the consumer says the service was poor, the existence of that disagreement does not by itself prove that the CRA entry is factually inaccurate.

But that does not mean the provider can ignore the dispute. If you can show that a payment was made, a credit was promised, a final bill was recalculated, an ombudsman upheld the underlying complaint, the account was cancelled earlier than recorded or another factual premise is wrong, those facts may directly affect the accuracy of the data being shared.

Frame the complaint in layers: (1) why the underlying amount is disputed; (2) which reported facts depend on that amount; (3) what evidence now contradicts those facts; and (4) what correction you require.

When accuracy is contested, rectification and restriction become relevant

UK GDPR Article 16 gives individuals the right to have inaccurate personal data rectified. The ICO says the organisation should take reasonable steps to satisfy itself that the data is accurate, taking account of the arguments and evidence supplied by the individual. The more important the data is to significant decisions, the greater the care that may be appropriate when checking it.

Article 18 can also give a right to request restriction of processing where the accuracy of personal data is contested while the organisation verifies it. The ICO additionally describes restriction during an accuracy investigation as good practice. Restriction is not the same thing as automatically deleting a default or declaring the underlying debt invalid; it is a data-processing safeguard while the accuracy issue is being checked.

Be precise about what you are contesting. “I dispute the account” is weaker than “the CRA records a default balance of £420, but your final-response letter confirms £180 was credited before the default date; please rectify the default balance and restrict processing of the disputed figure while you verify it.”

Provider versus CRA, who is responsible?

The organisation named against an account entry is usually the source of the account-performance data, and it has responsibilities for the data it supplies. The CRA also has responsibilities for its own processing and is expected to take reasonable measures around accuracy. It is therefore often sensible to raise the dispute with both the provider and the CRA, particularly where speed matters.

The ICO also makes clear that providers can make their own updates through CRA facilities. A provider should not tell you that “only the CRA can change it” if the disputed data is information that the provider itself supplied and can correct.

“The provider verified it” is not a complete accuracy investigation

A CRA may refer your dispute back to the organisation that supplied the account data. That can be a sensible part of checking the entry, but simple repetition of the provider's existing position does not resolve contradictory evidence.

If the provider's own records show two different default dates, a later adjustment, a disputed cancellation date or an account classification inconsistent with the CRA entry, identify that conflict expressly. Ask what evidence was checked and why the contradictory record was rejected. The objective is to move the response from “our system confirms it” to a reasoned explanation of the source data.

Default balance and current balance are not the same field

The default balance is a historical figure associated with the point of default. The current balance changes as payments, credits, settlements or other adjustments occur. A credit report can therefore legitimately show a historic default balance and a current balance of £0 after the debt is paid or otherwise resolved.

That does not mean either field is immune from challenge. Check whether the default balance included amounts that had already been paid or credited, and whether the current balance has been updated to reflect subsequent payments or settlement. A historical record can remain historical while still needing accurate context.

Debt sold to a debt purchaser: two entries do not automatically mean two defaults

When a defaulted debt is sold, the purchaser may begin reporting the account in its own name. The original creditor may also remain visible as a historical entry. The ICO indicates that this can be fair where it is clear that both entries relate to the same debt, the original account is shown appropriately and the same original default date is maintained.

The warning sign is where the entries make it look as though there are two separate debts, use different default dates without justification, leave both balances looking currently collectible, or cause the adverse history to survive for longer than six years from the original default date. A debt sale should not restart the default clock merely because ownership changed.

Closed, satisfied and partially satisfied are different from deletion

Paying a defaulted account usually changes how the later status is reported; it does not automatically erase the historical default. A fully paid account may be marked satisfied/settled. Where less than the full contractual balance is accepted and the consumer is no longer being pursued, a partial settlement/satisfaction marker may be appropriate depending on the circumstances.

If the business agrees not to pursue the remainder, check that the current reporting does not misleadingly suggest the same amount remains actively due. The ICO's public credit guidance specifically recognises the importance of reflecting the position where an organisation has stopped pursuing a balance.

An arrangement to pay does not guarantee that a default can never be recorded

A maintained arrangement is important, but it is not a universal lifetime shield against default reporting. The correct treatment depends on the nature and duration of the arrangement, the arrears position and whether the relationship has in substance broken down. PRAAD distinguishes arrangements from ordinary arrears and defaults rather than treating them as interchangeable.

If the organisation agreed an arrangement and you complied with it, preserve the agreement and payment history. If it later says the arrangement never existed or reports the account as though no payments were made, that may create a specific accuracy issue. If the arrangement later failed, the chronology still matters when deciding the appropriate default date.

One missed payment is not automatically a default

A missed payment can be adverse credit information, but a default ordinarily reflects a more serious breakdown. If an account was marked in default immediately after one isolated missed payment, ask the provider to explain the reporting logic, the account status and how the decision fits the applicable reporting standards.

Do not overstate the point in the other direction: a consumer cannot insist that genuine missed-payment history be deleted merely because the account never defaulted. The aim is an accurate history, not the most favourable possible history.

Wrong identity, address or account attribution

A default attached to the wrong person is a fundamentally different problem from a disagreement about a debt you actually incurred. Obtain the full CRA entry and challenge the identifiers: name, date of birth, address links, account number fragment, account opening date and reporting organisation.

If an address link is wrong, ask the CRA to identify the source of the link and break it where appropriate. If the provider has mixed two customers' records, require correction at source as well as at the CRA. Do not let the complaint be reduced to “the score is low”; identify the inaccurate personal data.

Different CRAs can show different information

There is no general requirement for every provider to report every account to all three main consumer CRAs. It is therefore possible for an account to appear with one CRA and not another without anything being wrong. What matters is whether information that is reported is accurate, complete enough for its purpose and updated appropriately.

Where the same account appears with materially different dates, balances or status histories across CRAs, capture each report with the date retrieved. Then ask the provider which CRAs it reports to and what data it supplied to each.

Rectification should follow the data to recipients

Where an organisation rectifies or completes personal data that it has disclosed to others, the UK GDPR contains notification obligations subject to limited exceptions. The ICO's rectification guidance says organisations should have procedures to inform recipients, and the individual can ask which recipients have received the data.

So if a provider accepts that a default date is wrong, ask it not only to amend its internal account but also to send the correction to each CRA to which it supplied the inaccurate data. Then obtain fresh reports after the update cycle and verify the outcome.

A Notice of Correction can add context, but it is not the same as fixing wrong data

A Notice of Correction is a short statement, generally up to 200 words, that can be added to a credit file to explain an entry. It can be useful while a genuine dispute remains unresolved or where context matters to a future lender.

It is not an adequate substitute for rectification where the underlying personal data is factually inaccurate. If the default date is wrong by eight months, the remedy is not simply to attach a paragraph saying you disagree with it. Challenge the data itself.

Evidence: reconstruct the reporting chain

The strongest default disputes are usually chronological. Build a table that allows somebody unfamiliar with the case to compare the account with the CRA entry.

• Credit reports from every CRA showing the entry, with retrieval dates.
• Account statements or ledger showing charges, payments, credits and arrears.
• Original contract/product type and relevant terms.
• Arrears letters, payment-plan agreements and collection correspondence.
• Any notice of intention to file/register a default and evidence of when/how it was sent.
• Any statutory Consumer Credit Act default notice, but keep it identified as a separate document.
• Cancellation, termination or account-closure records.
• Debt-sale or assignment correspondence.
• Complaint correspondence, final response and any ombudsman outcome.
• SAR material showing internal account status, notes, audit trails or conflicting dates.

If the case depends on what the provider knew on a particular date, contemporaneous records are usually more useful than a later generic statement that “our system is correct”.

Useful wording for a default-date or accuracy challenge

I am not asking you to remove accurate adverse information merely because it is damaging. I am challenging the accuracy and reporting chronology of specific personal data.

Your CRA entry records a default date of [date] and a default/current balance of [amount]. Your own records show [contradictory fact]. Please explain the evidence relied upon for each disputed field, reconsider the entry against the applicable credit-reporting standards and data-accuracy obligations, and rectify any inaccurate data.

While the accuracy of the identified data is being verified, please also consider my request to restrict processing of the contested data. If you rectify the entry, please notify each CRA/recipient to which you disclosed it and confirm what correction was sent.

When the underlying debt itself is disputed

Keep the substantive dispute and the data dispute connected but distinguishable. For example, if a telecom provider says a final bill was £300 and you say the contract had already ended, the communications complaint may need to decide the contractual balance. Your credit-reporting complaint then asks whether the CRA data accurately reflects the outcome.

Do not allow either side to use jurisdiction as a loop: the ICO cannot decide whether a broadband bill was contractually owed, but the provider cannot use that fact to avoid investigating objective evidence about the data it is reporting. Where another competent body has already resolved the underlying dispute, give that outcome to the provider and CRA as evidence.

Financial Ombudsman, ICO, sector ADR or court?

Compensation: prove the error, the impact and the route

Removing or correcting an entry and obtaining compensation are separate questions. For an eligible regulated-finance complaint, FOS can consider distress/inconvenience and proven financial consequences as part of deciding what is fair and reasonable. The ICO does not award compensation to individuals merely because it finds a data-protection concern.

If you say an inaccurate default caused a refused mortgage, higher borrowing cost or other financial loss, preserve the lender's decision, quotations, dates and reasons where available. Causation matters: a credit decision may depend on many factors, so the existence of an inaccurate entry does not automatically prove that every later refusal was caused by it.

Evidence worth keeping