Florida Division of Driver Licenses Issues Advisory On The Addition Of New Vehicles To Existing Insurance Policies
Nov 17, 2009
The Florida Department of Highway Safety and Motor Vehicles, Division of Driver Licenses (“Division”) has issued an advisory to Florida property and casualty insurers regarding an identified glitch relating to the electronic addition of vehicles to insurance policies that do not currently exist in the Division’s database.
The advisory, which provides a technical fix for the problem, is reprinted below.
Should you have any questions or comments, please contact Colodny Fass.
October 1, 2009
TO: All Fire and Property and Casualty Companies
Authorized to Issue Motor Vehicle Policies in Florida
FROM: Deborah Todd, Chief
Bureau of Financial Responsibility
Division of Driver License
SUBJECT: Advisory Bulletin
New Error Instruction for Vehicle Adds
Effective immediately, vehicles being added to policies that do not currently exist on our database are being returned as a policy number error. This error will be returned to you and new procedures will require you to report to us the initiation of insurance transaction type ’20’ for that policy number.
The vehicle add, transaction type ’31’, is currently being returned as an error indicating a ‘1’ in card column 326, located in the Edit Mask. When this is the only error in the Edit Mask, this indicates that the policy number could not be found on our database. However, we are adding these policies to our database with the vehicle information and the vehicle add date, but without an effective date of the policy.
We are making programming changes to only return with a soft error. Meaning a ‘2’ will be found in card column 329, located in the Edit Mask. Correction procedures for this will require you to submit an initiation of insurance, transaction type ’20’. In addition, if you send a transaction type ’20’ and a transaction type’31’ on the same file you will still receive the error on the transaction’31’ due to the database not being update with the ’20’ already. This will happen until we can modify this not to return an error. Note: If the policy number is blank, you will continue to receive an error in card column 326. If you receive an error in this field and an error in card column 311 and 312 (Transaction type and VIN) this will continue to indicate a duplicate error, VIN found on 2 or more policies.
It is possible the original initiation of insurance, transaction type ’20’ was sent in by your company but may have erred and has not been corrected. The expected transaction type ’20’ needed to correct the error will not be mandatory until January 1, 2010. We will continue to update the vehicle add transaction to our database; however it will only have a vehicle add date and will not have a policy effective date. Accurate and complete insurance information is necessary in order to server the customer respectively.
If you have any questions in regards to programming you may contact Bennett White, at bennettwhite@flhsmv.gov or Laura Rogers, at laurarogers@flhsmv.gov. The FTP Manual is updated with these operating procedures and is posted at http://www.flhsmv.gov/FRManualFTP/.
To unsubscribe from this newsletter, please send an e-mail to ccochran@cftlaw.com.