Data Agreement between Driver and Vehicle Licensing Agency (DVLA) and Motor Insurers’ Bureau (MIB) for the provision of Vehicle Data Exchange via the Motor Insurers Anti-Fraud and Theft Register (“MIAFTR”) – document here.
2023 total los notifications:
MIAFTR notifications process overview
- MIAFTR notifications are submitted in a daily file to DVLA
- DVLA process this file overnight Mon – Fri
- When processing, DVLA will run a series of validation checks to ensure the correct information has been provided and the correct record can be found. Should these fail, the record will be returned in an error file to MIAFTR
Successful notifications:
Upon receipt of a successful notification, DVLA records will be updated to show the relevant accident damaged details provided by an insurer. If provided, we will capture the following information on a vehicle record:
- Salvage category
- Date of accident
- Description of damage
- Cause of loss
- Mileage
- Company code
- Branch code
- Claim reference
- Transaction type
- Insurers address and contact details
If an insurer notifies a salvage category A or B, DVLA update the accident damaged details and will set a marker on the record. This marker will prevent the issue of any future V5C registration certificates as we would expect the vehicle to have been destroyed due to the salvage category assigned.
If an insurer notifies a salvage category S (previously C), although the accident damaged details are updated, the marker referenced above for salvage category A or B is not set. Should DVLA receive and application for a V5C registration certificate, one will be issued however the following literals will be presented in the special notes section – ‘This Vehicle has been salvaged because of structural damage but has been declared suitable for repair following a technical evaluation’.
If an insurer notifies a salvage category N (previously D), although the accident damaged details are updated, and application for a V5C registration certificate will be processed with no additional literals in the special notes section.
Unsuccessful notifications:
Should validation checks fail, the record will be returned in an error file to MIAFTR. The reason why the record has been rejected is included in the response and could be one of the following:
- A = Invalid matching
- C = No vehicle record
- D = Missing mandatory fields
- E = Invalid data format
- F = Invalid Company/Branch Code
- G = Duplicate record – Update status is N (New)
Any records that are returned in the error file do not update DVLA records. DVLA would expect the insurer to take corrective action and if necessary resubmit the notification with the correct details.