What to do when two vehicle history reports disagree

Keep both reports, identify the exact disagreement and seek the original record that could resolve it. Do not choose the more reassuring report or count every different entry as another crash. An omitted event, a differently labelled date and incompatible statements about the same fact require different follow-up.

Decide whether the reports actually contradict each other

First check that both reports refer to the same vehicle and note when each was generated. Then compare the same kind of information. A claim, an estimate, a police record and an administrative brand are different record types.

For example, CARFAX Canada describes a police-reported accident entry as information from a collision report filed by law enforcement. Its fields can include incident date, jurisdiction, description and recorded severity; some fields may be absent. A different kind of record should not silently replace that description.

Classify the issue before asking anyone to investigate:

carVertical describes reasons events can be missing, including unrecorded events and unavailable source data. That supports keeping omissions separate from direct contradictions in your log.

For US administrative records, the NMVTIS FAQ notes that state update intervals vary. That is a reason to record retrieval dates; it does not prove that a particular disagreement is merely a delay.

Build a blank contradiction log

This method has no completed vehicle example. Repeat the following record for each disagreement; do not merge unresolved entries into a single preferred history.

Identify the pair

• Report A: provider, report reference, generation date and retrieval date: fill in.
• Report B: provider, report reference, generation date and retrieval date: fill in.
• Vehicle match: identifiers compared privately and any mismatch: fill in.
• Disputed field: record type, exact wording and associated event reference: fill in.
• Classification: omission, different clocks, possible duplicate, direct contradiction or unresolved: fill in.

Test the disagreement

• Date labels and units: preserve each report's wording; leave missing labels unknown.
• Proposed explanation: write it as a question, not a finding.
• Decisive evidence needed: identify the original document or issuer that could answer that question.
• Request record: provider or issuer, request date and case reference: fill in.
• Written response: what was explained, changed or left unresolved: fill in.
• Buying consequence: which decision depends on resolving this fact: fill in.

A seller's account belongs in the log as an account, with its own date. It should not overwrite either report. Keep personal and ownership documents out of public listings.

Ask the right source a narrow question

Ask for an explanation of the particular field, its date and its source. CARFAX Canada's investigation guidance asks owners to identify disputed record dates, types and reasons. NMVTIS directs report questions to the service provider. Use the route for the product actually involved.

An explanation may show that the entries describe different things. An amendment may resolve one record while leaving another question open. Preserve both the old version and the response so the change has a traceable basis.

Decide what cannot wait

If identity, ownership documents or an administrative restriction remain contradictory, make resolving that issue a condition of your buying decision. For questions about current condition, ask a qualified independent provider to assess the vehicle with the available history and record the limits of that assessment. A physical assessment cannot rewrite a historical event.

The existing damage-record reading guide covers interpreting one report. For US research layers, use the NMVTIS, NICB and VIN decoder comparison. When shortlisting vehicles, keep the unresolved log with the candidate rather than presenting a disputed history as settled.

If the disagreement points to a specific error, use the record-correction request guide while preserving the earlier report version.