procedures manual for implementation of the florida … · lacey lowers dhsmv 06/27/2014 version...

PROCEDURES MANUAL FOR IMPLEMENTATION OF

THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW

DAILY REQUIREMENTS

STATE OF FLORIDA DEPARTMENT OF HIGHWAY SAFETY

AND MOTOR VEHICLES * * *

Effective February 2019 Version: 3.4

Page | 2

REVISION HISTORY

Name Company Date Description of Revisions Made

Tiffany Moyal DHSMV 08/28/2012 Version 1.00: Created first draft

Tiffany Moyal DHSMV 09/19/2012 Version 1.01: Revised second draft

Tiffany Moyal DHSMV 10/23/2012 Version 1.02: Added Sections: XSD Validation

(p.5); Successful Upload Confirmation (p.9)

Updated Sections: Filing Record Layout (p.12);

Conditional Field Applicability (p.13); Empty

XML Fields (p.16)

Tiffany Moyal DHSMV 12/03/2012 Version 1.03: Updated Sections: Reload

Overview – Added ‘Test Folder information’

(p.4); PGP Keys – Added ‘Important Note’

(p.5); Filing Record Layout – Verifications

Section (p.13);

Tiffany Moyal DHSMV 12/14/2012 Version 1.04: Updated Sections: Policy Errors

– Output File Names (p.6); TransactionReport

– Output File Name (p.7); Filing Record Layout

– 4o and 4p were reversed (p.13);

Tiffany Moyal DHSMV 12/27/2012 Version 1.04: Updated Sections: Updated

Verifications (p.20)

Tiffany Moyal DHSMV 01/03/2013 Version 1.04: Updated Sections: Updated

Transaction 10 (p.15); Updated Transaction 12

(p.19); Updated Transaction 35 (p.20); Added

Transaction Error Codes (071 and 072) (p.26);

Modified verbiage for error code 035 (p.25)

Tiffany Moyal DHSMV 01/21/2013 Version 1.04: Updated Section: Introduction:

Maximum number of records in a daily file is

100,000 (p.5); Updated Transaction 34 – DLN

no longer required (p.19);

Tiffany Moyal DHSMV 02/25/2013 Version 1.05: Updated Section: Introduction:

Added Reporting Procedures (p. 5);

Page | 3


Lacey Lowers DHSMV 04/30/2013 Version 1.06: Added examples to PH Trans

Type (p. 11-12)

Lacey Lowers DHMSV 05/06/2013 Version 1.07: Updated Holding Errors (p. 27)

Diane Evans and

Lacey Lowers

DHMSV 5/13/2013 Version 1.08: Minor grammar and formatting

fixes throughout document, removed some

error codes (p. 26-28) and clarified others,

updated holding errors (p,28), clarified

transaction type 20 (p.16) and 30 (p.19), and

made minor clarifications throughout manual

Lacey Lowers

DHSMV 06/06/2013 Version 1.08 release: Removed error code 004

and 015, added section steps to validate XML

file (p. 29),

Lacey Lowers

DHSMV 07/29/2013 Version 1.09 release: modified transaction 12

(p.23) to not allow modification of data

Lacey Lowers DHSMV 09/16/2013 Version 1.1 release: removed error 035 and

replaced sections concerning it (p. 17 & 23)

Lacey Lowers DHSMV 02/13/2014 Version 1.2 release: added unregistered VIN

file name to holding errors (p. 27)

Lacey Lowers DHSMV 02/20/2014 Version 1.3 release: modified unregistered VIN

file name for holding errors (p. 27)

Lacey Lowers DHSMV 05/19/2014 Version 1.4: modified empty XML fields (p. 15);

modified through date section (p.8)

Lacey Lowers DHSMV 06/27/2014 Version 1.5: Corrected position field of bullet 1

on PH transaction Type to 4o (p. 11)

Pat Porter DHSMV 10/03/2017 Version 2.0: Updated per modernization

Pat Porter DHSMV 10/16/2017 Version 2.1: Updated per Deliverable 48

Review Cycle One Comments

Pat Porter DHSMV 10/17/2017 Version 2.2: Updated per input from Subject

Matter Experts (SMEs)

Page | 4


Pat Porter DHSMV 10/18/2017 Version 2.3: Further refined by SMEs; Del 48-

revised version

Pat Porter DHSMV 10/18/2017 Version 2.4: Revisions for grammar and

readability applied.

Pat Porter DHSMV 10/20/2017 Version 2.5: Del 48 Review Cycle Two

Comments and SME revisions

Mechell Walker DHSMV 06/11/2018 Version 2.6: Removing old IP address,

correcting length for FED_TIN, adding missing

bullet for Transaction 21, removing error FLAT

format error codes 040 and 041

Mechell Walker DHSMV 06/22/2018 Version 2.7: Changed steps for how companies

should validate a XML file against a XSD file

Mechell Walker DHSMV 07/01/2018 Version 2.8: Removed PIP reference in Level 08

field value definition for Level of Coverage

Koral Griggs DHSMV 07/23/2018 Version 2.9: Added Appendix C – Bulk Policy

Errors for Missing and Cancelled Policies

Koral Griggs DHSMV 07/31/2018 Version 3.0: Updated Appendix B – Transaction

Report File Structure XML

Sebastian Miller DHSMV 08/03/2018 Version 3.1: Removed errors 101, 102, and

070.

Timariel Wiggins DHSMV 08/06/2018 Version 3.2: Updated requirements for

Transaction 21: Recall of Issuance of Coverage.

Timariel Wiggins DHSMV 10/16/2018 Version 3.3: Updated Sections: Added

clarification for FR Sanction Number (p. 15),

Tracking Number, and Required Coverage Date

(p.16). Added clarification for Transaction 12:

SR21/SR22/FR44 Verification Responses (p.18).

Added clarification requirements for

Transaction 15, 22, 33, and 44: Verification

Requests (p. 19). Added clarification for

Transaction 30 (p.22). Added Appendix D: XSD

for Verification Files (p.46).

Page | 5


Timariel Wiggins DHSMV 02/20/2019 Version 3.4: Updated requirements for

Transaction 31 to include (5e) effective date

(p.23). Update requirements for Transaction

34 to include (4p) effective date (p.24).

Updated Item No. for Transaction 35 (p.25).

Table of Contents

REVISION HISTORY ................................................................................................................. 2

Reporting Requirements .......................................................................................................... 8

Document Conventions ............................................................................................................. 8

Daily Reporting ......................................................................................................................... 9

Introduction .......................................................................................................................................... 9

Florida Motor Vehicle SFTP Reporting Procedures ................................................................................... 9

PGP Keys................................................................................................................................................ 9

Setting Up an SFTP Server Account ....................................................................................................... 9

Logging onto the SFTP Server ............................................................................................................... 9

Sending and Receiving Files .................................................................................................................. 9

File Specifications .................................................................................................................................. 9

Transaction Types ................................................................................................................................. 9

Level of Coverage ................................................................................................................................ 11

Policy Cancellation Date Field ............................................................................................................. 12

Insurance Company Notes .................................................................................................................. 12

Policyholder Date of Birth ................................................................................................................... 12

Policyholder Gender ........................................................................................................................... 12

Effective Date of the Policyholder ...................................................................................................... 12

Effective Date of the Vehicle............................................................................................................... 12

Filing Record Layout ................................................................................................................................ 13

Conditional Field Applicability ................................................................................................................ 14

Vehicle Section .................................................................................................................................... 15

Verification Requests .......................................................................................................................... 16

Page | 6

Multiple Company Codes .................................................................................................................... 16

Out-of-State Driver License Numbers ................................................................................................. 16

Accepted Special Characters ............................................................................................................... 16

Adding Drivers and Vehicles ............................................................................................................... 16

Empty XML Fields ................................................................................................................................ 16

Transaction Processing ........................................................................................................................... 17

Transaction 10 – Cancellation/Non-Renewal ..................................................................................... 17

Transaction 11 – Recall of Cancellation .............................................................................................. 17

Transaction 12 – SR21/SR22/FR44 Verification Responses ................................................................ 18

Transaction 13 – Vehicle Totaled or Sold ............................................................................................ 19

Transaction 15, 22, 33, 44 – Verification Requests ............................................................................. 19

Transaction 20 – Initiation of Insurance ............................................................................................. 19

Transaction 21 – Recall of Issuance of Coverage ................................................................................ 20

Transaction 22 – SR22 Bodily Injury Liability/Property Damage Liability/Personal Injury Protection 21

Transaction 26 – SR26 Cancellation of Bodily Injury/ Property Damage Liability/Personal Injury

Protection ........................................................................................................................................... 21

Transaction 30 – Change Effective Date, Level of Coverage, Driver License Number or Policyholder

Address ............................................................................................................................................... 22

Transaction 31 – Add Vehicle .............................................................................................................. 23

Transaction 32 – Delete Vehicle ......................................................................................................... 24

Transaction 33 – SR22 PIP Non-Cancellable 6-Month – Level of Coverage is a minimum of 10/10

only ...................................................................................................................................................... 24

Transaction 34 – Add Driver/Policyholder .......................................................................................... 24

Transaction 35 – Delete Driver/Policyholder ...................................................................................... 25

Transaction 36 – Cancellation of SR22 PIP Non-Cancellable 6-Month ............................................... 26

Transaction 44 – Non-Cancellable 6-Month Bodily Injury Liability/Property Damage

Liability/Personal Injury Protection .................................................................................................... 26

Transaction 46 – Bodily Injury Liability/Property Damage Liability/Personal Injury Protection ........ 27

Error Message Information ..................................................................................................................... 27

XSD Validation ..................................................................................................................................... 27

Transaction Errors ............................................................................................................................... 27

Transaction Error Codes and Error Messages ..................................................................................... 28

Holding Errors ..................................................................................................................................... 31

Page | 7

Steps to Validate an XML File (Reload or Daily) Against the XSD File ..................................................... 31

Appendix A – Florida Book of Business Reload and Daily File Structure XML ........................................ 33

Appendix B – Transaction Report File Structure XML ............................................................................. 40

Appendix C – Bulk Policy Errors for Missing and Cancelled Policies ....................................................... 44

Appendix D – XSD for Verification File .................................................................................................... 46

Green Verbiage highlighted in green reflects new procedures. Yellow Verbiage highlighted in yellow reflects important informational messages.

Color Coding Key

Page | 8

Reporting Requirements The Florida Department of Highway Safety and Motor Vehicles (DHSMV) is afforded authority by Florida Statute (F.S.), Section 324.0221(1)(a), to develop procedures, rules and regulations to create and maintain an automobile insurance reporting database (insurance file). The purpose of this manual is to set forth the procedures to accommodate insurance company reporting and department processing of reported data. F.S., Section 324.0221(1) (a) reads in part “Each insurer that has issued a policy providing personal injury protection coverage or property damage liability coverage shall report the cancellation or nonrenewal thereof to the department within 10 days after the processing date or effective date of each cancellation or nonrenewal. Upon the issuance of a policy providing personal injury protection coverage or property damage liability coverage to a named insured not previously insured by the insurer during that calendar year, the insurer shall report the issuance of the new policy to the department within 10 days. The report shall be in the form and format and contain any information required by the department and must be provided in a format that is compatible with the data processing capabilities of the department. Failure by an insurer to file proper reports with the department as required by this subsection constitutes a violation of the Florida Insurance Code. These records shall be used by the department only for enforcement and regulatory purposes, including the generation by the department of data regarding compliance by owners of motor vehicles with the requirements for financial responsibility coverage.”

Document Conventions

• DHSMV – Department of Highway Safety and Motor Vehicles

• XML File – XML is an acronym for Extensible Markup Language. XML is a universal format for structured documents and data on the web.

• SFTP – SFTP is an acronym for Secure File Transfer Program. SFTP is used to securely transfer files between the insurance companies and the DHSMV.

• SFTP Site – The SFTP site is the web address the user visits to transfer files.

• Encryption – The process of transforming information to make it unreadable to anyone except those possessing the key.

• Decryption – The process of decoding data, which has been encrypted to make it readable by using the specific key.

• Public Key – The key used either by the insurance company or the DHSMV to lock or encrypt the XML files before transfer.

• Private Key – The key used either by the insurance company or the DHSMV to unlock or decrypt the XML files after transfer.

• FED_TIN– Federal Tax Identification, also known as Federal Employer Identification Number (FEIN).

Page | 9

Daily Reporting Introduction The following are the specifications insurance companies must use to report records, as defined by the DHSMV. This manual is predominantly specific to the XML coding. The latest version of the XML schema and XSD files is located on the Florida Financial Responsibility and Insurance Program website at http://www.flhsmv.gov/FRIP/. The XML schema is what insurance companies will use to create the files prepared for submission to the DHSMV. There is a schema version number located in the XML file. The file insurance companies send to the DHSMV must include that same schema version number for the file to be processed. The XSD file is used for validation. If a modification must be made to the XML schema, the DHSMV will notify the insurance companies at least 90 days in advance. IMPORTANT – All files must be encrypted using the DHSMV’s public key before being placed on the SFTP site; otherwise, the file will not be picked up. Multiple daily files may be sent at any time during the day. Do not send the same daily file more than once.

Florida Motor Vehicle SFTP Reporting Procedures PGP Keys The insurance company must generate two keys. A private key used to decrypt files and a public key, which the DHSMV will use to encrypt files. IMPORTANT – The files uploaded to the server must be encrypted using the DHSMV’s public key; otherwise, the files will not be processed. Setting Up an SFTP Server Account Contact [email protected] to have an SFTP account set up and to exchange PGP keys. Once the public PGP keys have been exchanged, a phone call will be made to the insurance company informing them of their username and password information. Please note, passwords will not be sent via email. Sending passwords through email is a security violation. Logging onto the SFTP Server Companies will log onto the SFTP server using the username and password provided at the time their accounts were initially setup. For example, the logon or username will be “0000FTP,” followed by the provided password. Sending and Receiving Files The encrypted files must be placed on the server, which uses SFTP protocol and port 22. Contact [email protected] for the server IP address.. The transfer results will be placed in the Output folder with “TransactionReport” added at the end of the filename. If the file fails validation at any point, a “ValidationFailed” file will be placed in the Output folder. File Specifications The file may be named according to the insurance company preferences. The submitted file will be downloaded, processed and placed in the Archive folder. Transaction Types The basic purpose of the insurance file is to determine the presence or absence of coverage and the status (issued or cancelled) based on the related information sent by the insurance company. Transactions without errors will be recorded on the insurance database and those with content errors

http://www.flhsmv.gov/FRIP/

mailto:[email protected]

mailto:[email protected]

Page | 10

will be returned to the filing company to be corrected within 30 days. Transaction types developed for formatting and recording the insurance file information are as follows:

• 10 Cancellation/Non-Renewal

• 11 Recall of Cancellation

• 12 SR21/SR22/FR44 Verification Responses

• 15 Verification Requests

• 13 Vehicle Totaled or Sold

• 20 Initiation of Insurance

• 21 Recall of Issuance of Coverage

• 22 SR22 Certificate of Liability Coverage

• 26 Certificate of Cancellation (of SR22)

• 30 Change Effective Date, Level of Coverage or Policyholder Address

• 31 Add Vehicle to Policy

• 32 Delete Vehicle from Policy

• 33 Non-Cancellable PIP

• 34 Add Driver/Policyholder to Policy

• 35 Delete Driver/Policyholder from Policy

• 36 Cancellation of Non-Cancellable PIP (of SR22 PIP)

• 44 FR44 Certificate of Higher Limits Liability Coverage

• 46 FR46 Certification of Cancellation (of FR44)

Information indexes are used to match or identify a vehicle and a policyholder on the file. These indexes are driver license and VIN number, which are collected from information in the DHSMV’s driver license, vehicle registration and insurance files. Financial responsibility cases resulting in notices are “generated,” “not generated” or “cleared” based on information contained in the insurance file using the above-mentioned indexes. Different transaction types for the same policy can be submitted in the same file and will be processed in the order received. The transactions must be submitted in logical order to avoid any unnecessary errors. Listed below are a few examples.

1. If a transaction 10 (Cancellation) and a transaction 11 (Recall of Cancellation) are submitted for the same policy in the same file, but the Recall of Cancellation is listed first, an error will be returned for transaction 11 because the Cancellation was not processed; however, the transaction 10 will process, cancelling the policy.

2. If there is currently one vehicle on a policy and a transaction 31 (Add Vehicle) and a transaction 32 (Delete Vehicle) are submitted for the same policy in the same transaction, but the Delete Vehicle is listed first, an error will be returned because the only vehicle on the policy will be removed. To replace a vehicle, an Add Vehicle must be submitted before the Delete Vehicle. The same logic applies to a transaction 34 (Add Driver) and a transaction 35 (Delete Driver).

3. To update a driver’s name, a transaction 34 (Add Driver) must be listed first with the updated name and then a transaction 35 (Delete Driver) with the original name can follow.

Page | 11

Level of Coverage The “Level of Coverage” field is used to describe the level of coverage contained on a vehicle in a policy. Transactions 20 (Initiation of Insurance) and 31 (Add Vehicle) will require level of coverage for vehicles. Annually, the DHSMV sends approximately one million suspension notices to customers for verifying insurance. Sixty percent of our case types, which means some event occurred, require the customer to provide the DHSMV the levels of insurance coverage to ensure they meet Financial Responsibility requirements. Reporting this threshold in advance would significantly reduce the amount of SR21 verification requests sent out to insurance companies, prevent customer calls to the insurance companies, and provide better overall customer service to the DHSMV’s mutual customers. Vehicles registered as “Commercial Motor Vehicles” as described in F.S., Section. 320.01(26), are required to have certain levels of coverage as described in F.S., Section 627.7415, and these levels must be verified by Florida driver license/tax collector offices at the time of registration, per statute. Currently, the DHSMV’s mutual customers provide this information via a paper document (COI). Reporting these levels through the insurance database will eliminate the need for manual verification and allow customers to utilize online services, thus freeing up phone lines in offices across the state. This level of coverage should have a corresponding value of “01” through “08,” as displayed below.

Field Value Definition

01 PIP/PDL 627.7275 ref. 627.736, which requires PIP and 324.022, which requires PDL. Minimum coverage is $10,000 personal injury protection (PIP) and $10,000 property damage liability (PDL).

02 BIL/PDL 10/20/10 Basic BI 324.021(7) Minimum limits of bodily injury liability of $10,000 per person, $20,000 per crash, $10,000 property damage liability per crash, and PIP limits of $10,000 per person per crash.

03 BIL/PDL 100/300/50 DUI 324.023 Minimum limits of bodily injury liability of $100,000 per person, $300,000 per crash, $50,000 property damage liability per crash, and PIP limits of $10,000 per person per crash.

04 BIL/PDL Commercial 627.7415 (1) 50 CSL (in addition to 10k PIP) Minimum limits of Bodily Injury Liability and $50,000 Combined Single Limits (CSL), and PIP limits of $10,000 per person, per crash (for vehicles > 26k lbs.).



07 BIL/PDL Commercial 627.7415 ref 49 CFR 387.9 (2 and 4), $5 million CSL or 49 CFR 387.9(3), $1 million (in addition to 10k PIP) Minimum limits of Bodily Injury Liability and $5 million or $1 million Combined Single Limits (CSL), and PIP limits of $10,000 per person, per crash (for hazardous materials).

08 Taxi BIL/PDL - 125/250/50 324.032/627.7415

Page | 12

Minimum limits of bodily injury liability of $125,000 per person, $250,000 per crash, $50,000 property damage liability per crash (for taxi cabs).

Policy Cancellation Date Field The “Policy Cancellation Date” field is used to identify when a policy is cancelled, non-renewed, or expired. A transaction 10 (Cancellation/Non-Renewal) will still need to be reported to the DHSMV. The “Policy Through Date” field is no longer being used and has been replaced with the “Policy Cancellation Date” field. Please note, this field is a required field only when a transaction 10 (Cancellation) is being reported to the DHSMV for a policy cancellation or non-renewal. Insurance Company Notes The “Insurance Company Notes” field is an optional field used by the insurance companies. This field will be returned with error files. Policyholder Date of Birth The “Policyholder Date of Birth” field is used if the customer does not have a Florida driver license number. The “Policyholder Date of Birth” is one of three fields, along with “Name” and “Policyholder Gender,” which are required to generate a driver license number when a driver license number has not been provided. Policyholder Gender The “Policyholder Gender” field is used if the customer does not have a Florida driver license number. The “Policyholder Gender” is one of three fields, along with “Name” and “Policyholder Date of Birth,” which are required to generate a driver license number when a driver license number has not been provided. Effective Date of the Policyholder The “Effective Date of the Policyholder” field is used to describe the date the driver/policyholder was added to the policy. In a reload file, the effective date is optional if a transaction 34 (Add Driver/Policyholder) is not used, and will default to the policy effective date if left blank; however, during a daily load, the policyholder effective date for a transaction 34 (Add Driver/Policyholder) will be required. Effective Date of the Vehicle The “Effective Date of the Vehicle” field is used to describe the date the vehicle was added to the policy. In a reload file, the vehicle effective date is optional if a transaction 31 (Add Vehicle) is not used, and will be defaulted to the policy effective date if left blank; however, during a daily load, the vehicle effective date for a transaction 31 (Add Vehicle) will be required.

Page | 13

Filing Record Layout Item No

Node or Element

Field Name Character type

Required Optional Conditional

Length Comments

1 N Insurance Company R Unbounded

1a E Company Code Numeric R 5

2 N Transaction R Unbounded

2a E Transaction Type Numeric R 2

3 N Policy R Unbounded

3a E Policy Number Alphanum R 30

3b E Policy Effective Date Date R 8 MMDDYYYY

3c E Policy Cancellation Date Date O 8 MMDDYYYY

3d E Insurance Company Notes Alphanum O 50

4 N Policyholder R Unbounded

4a E Company Indicator Alpha R 1 Y or N

4b E First Name Alpha C 25

4c E Middle Name Alpha O 16

4d E Last Name Alpha C 35

4e E Name Suffix Alpha O 3

4f E Gender Alpha O 1 M or F or Blank

4g E DOB Date O 8 MMDDYYYY

4h E Street Address Alphanum O 100

4i E City Alpha O 50

4j E State Alpha O 2

4k E Zip Numeric O 9

4l E FL DL Number Alphanum O 13

4m E FED_TIN Numeric O 9 Formerly FEID

4n E Non-Structured Name Alphanum C 50

4o E Transaction Type Numeric C 2

4p E Effective Date Date C 8 MMDDYYYY

4q E FR Sanction Number Alphanum C 12

4r E FR Certification Date Date C 8 MMDDYYYY

4s E FR Prepared Date Date C 8 MMDDYYYY

5 N Vehicle C Unbounded

5a E Fleet Indicator Alpha R 1 Y or N

5b E VIN Alphanum C 21

5c E Year Numeric C 4 YYYY

5d E Make Alphanum C 5

5e E Effective Date Date O 8 MMDDYYYY

5f E Level of Coverage Numeric O 2 01-08

5g E Vehicle Transaction Type Numeric C 2

Page | 14

6 N Verifications C Unbounded

6a E Tracking Number Provided by HSMV (Alphanum)

C 36

6f E Confirmed Alpha C 1 Y or N

Conditional Field Applicability Transaction Type (2a) – Any transaction type can be used here. For transaction types 10, 11, 13, 21, 22, 26, 33, 36, 44 and 46, no other transaction types can be performed within the same transaction; however, another transaction can be used within that same file. For transaction types 20, 30, 31, 32, 34 and 35, insurance companies can include other transaction types within the same transaction. Policyholder Section Last Name (4d) – If Company Indicator = “N,” then the “Policyholder Last Name” is required. A hard error message will be received if the last name is missing. FED_TIN (4m) – Formerly FEID. If Company Indicator = “Y,” then the “FED_TIN” is optional. A warning message will be received if the FED_TIN is missing. Please note, the FED_TIN must be 9 digits. Non-Structured Name (4n) – If Company Indicator = “Y,” then the “Non-Structured Name” is required. A hard error message will be received if the Non-Structured Name is missing. Policyholder Transaction Type (4o) – For a daily submission, there are two possible scenarios.

1. When submitting an initiation, a transaction 20 (Initiation of Insurance) needs to be in position 2a, and a transaction 34 (Add Driver/Policyholder) will need to be in position 4o.

2. A transaction 34 (Add Driver/Policyholder) can be in position 2a if there is already a transaction 20 (Initiation of Insurance) with the same policy number on the database or in the same file.

Please note, the following applies for both policyholders and vehicles:

• In a daily file, if insurance companies are reporting the policy for the first time, AND there are multiple policyholders AND the policyholder effective date is the same as the policy effective date, then all information will be under a transaction 20 (Initiation of Insurance) in position 2a.

• In a daily file, if insurance companies are reporting the policy for the first time, AND there are multiple policyholders AND the policyholder effective date is different than the policy effective date, then a transaction 20 (Initiation of Insurance) will be in position 2a and a transaction 34 (Add Driver/Policyholder) with the policyholder effective date will be needed for any policyholder with a different effective date.

• In a daily file, if insurance companies are NOT reporting the policy for the first time, AND there are one or multiple policyholders AND the policyholder effective date is the same for all policyholders, then all information will be under a transaction 34 (Add Driver/Policyholder) in position 2a and insurance companies can fill out the effective date in position 3b.

• In a daily file, if insurance companies are NOT reporting the policy for the first time, AND there are one or multiple policyholders AND the policyholder effective dates are different from each other, then all information will be under a transaction 34 (Add Driver/Policyholder) in position

Page | 15

2a, and insurance companies can fill out the policyholder effective date in position 4p for each policyholder.

Effective Date Policyholder (4p) – When using a transaction 34 (Add Driver/Policyholder) in position 4p, the effective date is required when performing a daily update to add an additional policyholder to a policy, which is currently on file. Please note, if a transaction 34 (Add Driver/Policyholder) is in position 2a, then insurance companies will use position 3b for the effective date. FR Sanction Number (4q) – For transaction types 22, 26, 33, 36, 44 and 46 for SR22s and FR44s, the associated FR sanction number, if available, can also be submitted in the transaction. The FR sanction number must be present for transaction types 15, 22, 33 and 44 (SR21/SR22/FR44 Verification Requests) from the DHSMV. FR Certification Date (4r) – When submitting transaction types 22, 26, 33, 36, 44 and 46 for SR22s and FR44s, the certification date should be the date the certificate was issued by the insurance company. FR Prepared Date (4s) – When submitting transaction types 22, 26, 33, 36, 44 and 46 for SR22s and FR44s, the prepared date should be the date the certificate was prepared by the insurance company. Vehicle Section VIN (5b) – If Fleet Indicator = “N,” then the VIN is required. A hard error message will be received if the VIN is missing. Vehicle Year (5c) – If a VIN is present, then the vehicle year is required. A hard error message will be received if the vehicle year is missing. Make (5d) – If a VIN is present, then the make of the vehicle is required. A hard error message will be received if the make is missing. Vehicle Effective Date (5e) – When using a transaction 31 (Add Vehicle) in position 5g, the effective date of the vehicle is required when performing a daily update to add an additional vehicle to a policy currently on file. Please note, if a transaction 31 (Add Vehicle) is in position 2a, then insurance companies will use position 3b for the effective date. Level of Coverage (5f) – If a VIN is present, then the level of coverage is required. Please note, Transaction 32 will not require Level of Coverage. Vehicle Transaction Type (5g) – For a daily submission, two possible scenarios exist.

1. To submit an initiation, a transaction 20 (Initiation of Insurance) needs to be in position 2a and a transaction 31 (Add Vehicle) will need to be in position 5g.

2. A transaction 31 (Add Vehicle) can be in position 2a if there is already a transaction 20 (Initiation of Insurance) with the same policy number on the database or in the same file.

3. Please note, transaction type 2a should never be left blank.

Page | 16

Verification Requests When Financial Responsibility certificates, SR22 and FR44, cannot be located on the insurance database, verification requests will be sent to insurance companies for confirmation or denial. Tracking Number (6a) – Only used for verification requests or a transaction 15, 22, 33, & 44 (SR21/SR22/FR44 Verification Requests). When a transaction 15, 22, 33, & 44 (SR21/SR22/FR44 Verification Requests) is sent to an insurance company, it will contain a tracking number. The tracking number should not be altered. Required Coverage Date – Only used for verification requests or transaction types 15, 22, 33 and 44 (SR21/SR22/FR44 Verification Requests). When transaction types 15, 22, 33 and 44 (SR21/SR22/FR44 Verification Requests) are sent to the insurance company, they will contain the required coverage date. The required coverage date should not be altered. Please note, if a verification request “Denial” is received, the customer associated with that denial will receive a suspension notification. Confirmed (6f) – Only used for verification requests or a transaction 12 (SR21/SR22/FR44 Verification Responses). When set to “Y,” this means the driver/vehicle did have coverage with insurance companies on the SR21 Required Coverage Date. Multiple Company Codes For each file, companies can submit multiple Florida company codes, as insurance companies have done in the past. For each identified Florida company code, companies can submit multiple transactions. For each transaction, companies can submit the policy information. Within the policy node, companies can include all policyholders and vehicles associated with policy. Out-of-State Driver License Numbers If the driver license number is located outside of the state of Florida or outside of the United States, please leave the driver license number field blank, so insurance companies will not receive any errors. If insurance companies do have a Florida driver license number, please provide the DHSMV with the information. Accepted Special Characters There are few errors referencing “invalid characters.” The acceptable special characters are a space, a hyphen (-) or an apostrophe (’). Adding Drivers and Vehicles The following is an example of when a transaction 31 (Add Vehicle) can be used in a daily load file: For a daily submission, insurance companies can submit their “Add” and “Deletes” individually or can have multiple transactions. If insurance companies are submitting them individually, they will use transaction type 2a. If insurance companies are adding a vehicle and driver, they would put a transaction 34 (Add Driver/Policyholder) in the transaction type 2a and a transaction 31 (Add Vehicle) in the vehicle transaction type 5g. If insurance companies wanted to add a driver to an existing policy, they would put a transaction 34 (Add Driver/Policyholder) in the transaction type 2a field. IMPORTANT – Transaction type 2a should never be left blank. Empty XML Fields In XML, an empty element or an empty space may be submitted.

Page | 17

For example, if the policy does not have an FED_TIN number, any of the following will work: <FED_TIN/> OR <FED_TIN></FED_TIN> OR <FED_TIN> </FED_TIN>

Transaction Processing Error codes are referenced in the transaction details below. The error code list begins on page 26. Please note, transaction type 2a should never be left blank. Transaction 10 – Cancellation/Non-Renewal A transaction 10 is used when cancelling or non-renewing an initial policy, transaction 20 (Initiation of Insurance). It must never be used to delete a vehicle or a driver from an existing multiple vehicle or driver policy on the file, as it results in a cancellation of the entire policy. Please note, a transaction 10 (Cancellation) will not cancel an SR22/FR44. If a cancellation is submitted for the policy, which is not on the insurance database, the transaction will be returned with an error (050). If the policy is currently cancelled on the database, but another transaction 10 (Cancellation) is sent with a different cancellation date, the cancellation date will NOT be updated and the transaction will be returned in the error file with a warning (051). The effective date of the cancellation must be equal to, or greater than, the effective date of the policy. When this occurs, the status of the policy will be changed to “Cancelled.” If the effective date of the cancellation is earlier than the effective date of the policy, the policy will remain active and will be returned in the error file with an error (013). If the policy effective date was not previously populated in the database, the policy effective date will be populated with the provided date in the transaction. Please note, the policy was imported in the database with a blank policy effective date in the previous system. Once a current, successful reload is accepted from a company with policies on the DHSMV database with this scenario, this statement will no longer apply. The required fields for a transaction 10 (Cancellation) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE

• (2a) TRANSACTION TYPE

• (3a) POLICY NUMBER

• (3c) EFFECTIVE DATE OF CANCELLATION Transaction 11 – Recall of Cancellation A transaction 11 is used when the filing company recognizes that a transaction 10 (Cancellation) has been filed in error or the policy has been reinstated. If a “Recall of Cancellation” is submitted for the policy that is not in the insurance database, the transactions will be returned in the error file with an error (050).

Page | 18

If the policy is not in a “cancelled status” already, the transaction will be returned in the error file with an error (022). The effective date of the recall transaction must be equal to, or greater than, the cancellation date filed with the transaction 10 (Cancellation). When this occurs the status of the policy will be changed to “Active.” If the effective date of the recall is less than the cancellation date, the policy will remain cancelled and will be returned in the error file with an error (026). If the policy effective date was not previously populated in the database, the policy effective date will be populated with the provided date in the transaction. The required fields for a transaction 11 (Recall of Cancellation) are listed below and correspond to the Filing Record Layout. REQUIRED




• (3b) EFFECTIVE DATE OF RECALL OF CANCELLATION

Please note, the “vehicle_transaction_type” and/or “policyholder_transaction_type” element fields in the XML layout must be NULL (empty) for a recall transaction 11 (Recall of Cancellation) to be successful; however, when vehicle and/or policyholder data is supplied, these elements must be populated. Transaction 12 – SR21/SR22/FR44 Verification Responses Transaction types 15, 22, 33 and 44 are verification requests and will be returned by the insurance companies as a transaction type 12. Insurance companies must verify if the customer had the appropriate insurance on the requested need date. Appropriate insurance is identified by the level of coverage in the request and/or the coverage date. Please refer to the following scenarios:

• If Level of Coverage (5f) is a “01,” confirm the vehicle(s) present (5b) or, if none are present, confirm the individual (4b-e) has a minimum coverage of PIP/PDL. (Minimum coverage is $10,000 personal injury protection (PIP) and $10,000 property damage liability (PDL).)

• If Level of Coverage (5f) is a “02,” confirm the vehicle(s) present (5b) or, if none are present, confirm the individual (4b-e) has a minimum coverage of BI/PDL 10/20/10. (Minimum limits of bodily injury liability of $10,000 per person, $20,000 per crash, $10,000 property damage liability per crash, and PIP limits of $10,000 per person, per crash.)

• If Level of Coverage (5f) is a “03,” confirm the vehicle(s) present (5b) or, if none present, confirm the individual (4b-e) has a minimum coverage for a DUI of BIL/PDL 100/300/50. (Minimum limits of bodily injury liability of $100,000 per person, $300,000 per crash, $50,000 property damage liability per crash, and PIP limits of $10,000 per person, per crash.)

Page | 19

When verification is sent to the insurance company, all fields with data will be populated. When submitting a transaction 12 (SR21/SR22/FR44 Verification Responses), the following field must have a value of either “Y” or “N:” CONFIRMED (6f). Please do not modify any of the supplied data. Transaction 13 – Vehicle Totaled or Sold A transaction 13 is used when a vehicle filed with the policy initiation transaction has been reported sold by the insured, or determined to be a total loss by the insuring company due to an accident. If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the vehicle reported sold/totaled is the only vehicle on the policy, the status of the policy will remain “Active,” as to allow the insurance company to add a vehicle later. If there are additional vehicles on the policy other than the vehicle being reported sold/totaled, only the vehicle being reported will be removed and the policy will remain “Active.” The required fields for a transaction 13 (Vehicle Totaled or Sold) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE OF THE SOLD/TOTALED VEHICLE • (5b) VIN • (5c) VEHICLE YEAR • (5d) MAKE

Transaction 15, 22, 33, 44 – Verification Requests

Transaction types 15, 22, 33 and 44 are verification requests generated by the DHSMV and sent to insurance companies to verify SR21, SR22 and FR44 reported policy information. Insurance companies must verify if the customer had the appropriate insurance on the requested need date. Appropriate insurance is also identified by the level of coverage in the request and/or the coverage date. When a verification is sent to the insurance company, all fields with data will be populated. Please do not modify any of the supplied data. Transaction 20 – Initiation of Insurance A transaction 20 is used to create the insurance record when filing an insurance policy initiation or policy origination. Please note, when filing a non-owner’s policy, an insurance company must use the dummy VIN information provided in the requirements below. Once the transaction 20 (Initiation of Insurance) record is populated, no further action will be required from the insurance company. The dummy VIN will bypass all validations allowing the generation of the non-owner’s policy, which will capture and maintain the level of coverage required for the policyholder.

Page | 20

When filing a transaction 20 (Initiation of Insurance) for fleet coverage policies, vehicle information is optional for this transaction; however, it is strongly recommended. Fleet policies are defined as those policies insuring more than 25 vehicles. The fleet indicator field is in the vehicle entity on the XML schema. This transaction should not be used to reinstate a policy, which has been cancelled and reinstated under the same policy number. To reinstate a cancelled policy, submit a transaction 11 (Recall of Cancellation). This transaction should not be used to update a policy, which has already been initiated and submitted. To update an existing policy, submit the appropriate updating transaction type. If the policy already exists in the insurance database, the transaction will be returned in the error file with an error (047). If a driver license number is not provided, first, middle and last names, date of birth and gender are required. The required fields for a transaction 20 (Initiation of Insurance) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE OF POLICY • (4a) COMPANY INDICATOR • (4b* AND 4d* OR 4n) NAME OR COMPANY NAME • (4c*) MIDDLE NAME • (4f*) GENDER • (4g*) DATE OF BIRTH • (4o) POLICYHOLDER TRANSACTION TYPE • (5a) FLEET INDICATOR • (5b) VIN (Use Dummy VIN, FRN0N0WNERSP0LICY, ONLY for a non-owner’s filing.) • (5c) VEHICLE YEAR (Use current year as the vehicle year ONLY for a non-owner’s policy filing.) • (5d) MAKE (Use vehicle make, VEH, ONLY for a non-owner’s policy filing.) • (5f) LEVEL OF COVERAGE

Please note, if a driver license number is provided, first, middle and last names, date of birth and gender are optional. Transaction 21 – Recall of Issuance of Coverage A transaction 21 is an update or change to the transaction 20 (Initiation of Insurance). This transaction is filed only in the case of a transaction 20 (Initiation of Insurance) being filed in error. An example of a condition which can cause a policy to be filed in error is the transmission of transaction 20 (Initiation of Insurance) before the underwriter reviews and declines the insurance based on the past driving history of the intended insured.

Page | 21

• If a transaction 21 (Recall of Issuance of Coverage) is submitted, but a transaction 20 (Initiation of Insurance) does not exist on the insurance database, the transaction will be returned in the error file with an error (050).

• If a transaction 21 (Recall of Issuance of Coverage) is submitted and the policy is currently in a cancelled status, the transaction will be returned in the error file with an error (031).

• If a transaction 21 (Recall of Issuance of Coverage) is submitted 90 days after the effective date of the policy, the transaction will be returned in the error file with an error (032). At this point, you must submit a transaction 10 (Cancellation) to cancel the policy.

The required fields for a transaction 21 (Recall of Issuance of Coverage) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE • (3a) POLICY NUMBER • (3b) POLICY EFFECTIVE DATE

Transaction 22 – SR22 Bodily Injury Liability/Property Damage Liability/Personal Injury Protection A transaction 20 (Initiation of Insurance) must accompany this transaction or be present on the database. Please note, a stand-alone SR22 (without an initiation) can be reported; however, an error will be returned to have the company submit a transaction 20 (Initiation of Insurance) if there is not an associated policy for the SR22 currently on the database. The transaction 22 (SR Certificate of Liability Coverage) is used for the insurance company to report SR22 certificate of liability coverage (BIL limits of at least 10/20/10). This transaction is only needed if a customer did not have the required liability coverage at the time of an event (FR1 Crash with Injury, FR3 Crash Judgment, FR4 Non-DUI Sanctions, FR5 Point Revocations, and FR6 Habitual Traffic Revocations). When filing a new SR22 with the same policy number, which has been cancelled or expired, the new SR22’s prepare date must be one day after the last SR26’s prepare date. The required fields for a transaction 22 (SR22 Certificate of Liability Coverage) are listed below and correspond to the Filing Record Layout. REQUIRED




• (4l) DRIVER LICENSE NUMBER

• (4r) SR/FR CERTIFICATION DATE (4s) SR/FR PREPARED DATE

Transaction 26 – SR26 Cancellation of Bodily Injury/ Property Damage Liability/Personal Injury Protection A transaction 26 is used for the insurance company to report an SR26 Certificate of Cancellation of an SR22.

Page | 22

The required fields for a transaction 26 (Certificate of Cancellation) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE • (3a) POLICY NUMBER • (4l) DRIVER LICENSE NUMBER • (4r) SR/FR CERTIFICATION DATE • (4s) SR/FR PREPARED DATE

Transaction 30 – Change Effective Date, Level of Coverage, Driver License Number or Policyholder Address A transaction 30 is used to modify an existing policy in the DHSMV database. The policy number must exist in the insurance database and be in an “Active” status. If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the policy is not in an “Active” status, the transaction will be returned in the error file with an error (011). Please note, if there has not been a lapse in coverage and no other changes need to be made to the policy, there is no need to submit a renewal. However, if a transaction 30 (Change Effective Date/Level of Coverage/Address) is submitted for a change of address, or level of coverage, please indicate the effective date change for that event in the required field (3b), otherwise the date change will update to the policy’s effective date. Transaction 30 cannot be used to update the company address or FED_TIN. A transaction 30 is used to

1. Change a policy effective date (e.g., renewal of a policy). 2. Change a policyholder’s address. 3. Correct a policyholder’s driver license number. 4. Change the level of coverage for a vehicle.

If a change to the policyholder’s address is desired, then the driver’s name on the filing must be the same as the original filing driver’s name. If the driver’s names do no match, the transaction will be returned in the error file with an error (048). To perform a driver license number correction, a transaction 30 (Change Effective Date, Level of Coverage, Driver License Number or Policyholder Address) must be submitted with the updated driver license number. The required fields for a transaction 30 (Change Effective Date/Level of Coverage/Address) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE OF THE UPDATE • (4a) COMPANY INDICATOR

Page | 23

• (4b & 4d OR 4n) NAME OR COMPANY NAME (Only applicable if updating a policyholder address). Please note, submit all name details (first, middle, last, suffix).

• (4h, 4i, 4j, 4k) ADDRESS (Only applicable if updating a policyholder address.) • (5b) VIN (Only applicable if updating the level of coverage.) • (5f) LEVEL OF COVERAGE (Only applicable if updating the level of coverage.)

Transaction 31 – Add Vehicle A transaction 31 is used when a newly acquired or replacement vehicle is added to a previously filed initiation policy, or a vehicle that was not sent with the original policy transmission. The effective policy date required in the filing record should be the date the vehicle was added to the policy, and not the original effective date of the policy, unless the vehicle was on the policy from origination but was not filed with the origination. This transaction should only be used to add a vehicle to a policy, which has been successfully filed on the insurance database. If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the policy is not in an “Active” status, the transaction will be returned in the error file with an error (011). If the VIN submitted already exists on the policy, the transaction will be returned in the error file with an error (034). If the add date or any other vehicle information needs to be modified, a transaction 32 (Delete Vehicle) should be submitted, followed by a transaction 31 (Add Vehicle) with the updated information. If the VIN submitted is present on two or more active policies for the same insurance company, the transaction will be returned in the error file with an error (043). The required fields for a transaction 31 (Add Vehicle) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE or (5g) VEHICLE TRANSACTION TYPE (Use 5g if more than one

transaction type is occurring on the record (e.g. adding a vehicle and driver).) • (3a) POLICY NUMBER • (3b) POLICY EFFECTIVE DATE • (5a) FLEET INDICATOR • (5b) VIN • (5c) VEHICLE YEAR • (5d) MAKE • (5e) EFFECTIVE DATE OF ADDING THE VEHICLE • (5f) LEVEL OF COVERAGE

Page | 24

Transaction 32 – Delete Vehicle A transaction 32 is used when the company or the insured elects to delete, drop or eliminate a vehicle(s) from a policy. When a transaction 32 (Delete Vehicle) is received and the submitted VIN number is located on the insurance database on the existing policy number, the vehicle will be deleted. If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the policy is not in an “Active” status, the transaction will be returned in the error file with an error (011). If the VIN submitted does not exist on the policy provided in the file, the transaction will be returned in the error file with an error (044). The required fields for a transaction 32 (Delete Vehicle) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE or (5g) VEHICLE TRANSACTION TYPE (Use 5g if more than one

transaction type is occurring on the record (e.g., adding a vehicle and driver).) • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE OF REMOVING VEHICLE • (5b) VIN

Transaction 33 – SR22 PIP Non-Cancellable 6-Month – Level of Coverage is a minimum of 10/10 only A transaction 33 is used for the insurance company to report a Non-Cancellable SR22 Certificate of Personal Injury Protection/Property Damage Liability. This transaction is only needed if a customer was convicted of a “No Proof of Insurance” charge and subsequently was unable to show proof of the minimum state required coverage at the time of the offense. The required fields for a transaction 33 (Non-Cancellable PIP) are listed below and correspond to the Filing Record Layout. REQUIRED


Transaction 34 – Add Driver/Policyholder A transaction 34 is used either when the primary policyholder is being submitted with an initiation, a new driver, or a driver that was not sent with the original policy transmission is added to a previously filed initiation policy.

Page | 25

The effective policy date required in the filing record should be the date the driver was added to the policy and not the original effective date of the policy, unless the driver was on the policy from origination, but was not filed with the origination. This transaction should only be used to add a driver to a policy, which has been successfully filed on the insurance file. If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the policy is not in an “Active” status, the transaction will be returned in the error file with an error (011). If the provided driver license number cannot be verified, the transaction will be returned in the error file with an error (00L). If the driver license number submitted already exists on the policy, the transaction will be returned, in the error file, with an error (046). If multiple drivers/policyholders currently exist on the policy, and a name needs to be corrected, then transaction 35 (Delete Driver) should be submitted to delete the driver with the incorrect name, followed by submission of a transaction 34 (Add Driver) with the correct name. Please note, if only one driver/policyholder exists on the policy, the driver cannot be deleted. The required fields for a transaction 34 (Add Driver/Policyholder) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE or (4o) TRANSACTION TYPE (Use 4o if more than one transaction type is

occurring on the record (e.g., deleting a vehicle and driver).) • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE or (4p) EFFECTIVE DATE OF ADDING THE POLICY HOLDER if (4o) was used

above. • (*4b AND *4d OR 4n) NAME OR COMPANY NAME • (*4c) MIDDLE NAME • (*4f) GENDER • (*4g) DATE OF BIRTH

Please note, if a driver license number is not provided, first, middle and last names, date of birth and gender are required. Transaction 35 – Delete Driver/Policyholder A transaction 35 is used when the company or the insured elects to delete, drop or eliminate a driver(s) from a policy. When a transaction 35 (Delete Driver/Policyholder) is received and the driver license number is located on the insurance database with the existing policy number, the driver is deleted. If removing a driver who was originally submitted without a driver license number is desired, then the driver’s name on the filing must be the same as the original filing driver’s name. If the driver’s names do

Page | 26

not match and the Florida driver license number field is blank, the transaction will be returned in the error file with an error (048). If the policy does not exist in the database, the transaction will be returned in the error file with an error (050). If the policy is not in an “Active” status, the transaction will be returned in the error file with an error (011). If the driver license number submitted does not exist on the policy, the transaction will be returned in the error file with an error (045). If there is only one driver on the policy, the driver cannot be deleted. The transaction will be returned in the error file with an error. A transaction 34 (Add Driver/Policyholder) must be submitted prior to the transaction 35 (Delete Driver/Policyholder). The required fields for a transaction 35 (Delete Driver/Policyholder) are listed below and correspond to the Filing Record Layout. REQUIRED

• (1a) COMPANY CODE • (2a) TRANSACTION TYPE or (4o) POLICYHOLDER TRANSACTION TYPE (Use 4o if more than one

transaction type is occurring on the record (e.g., deleting a vehicle and driver).) • (3a) POLICY NUMBER • (3b) EFFECTIVE DATE or (4p) EFFECTIVE DATE POLICY HOLDER REMOVED if (4o) was used above. • (4b and 4d or 4N) NAME OR COMPANY NAME (Only applicable if deleting a driver with no driver

license number on record.)

Transaction 36 – Cancellation of SR22 PIP Non-Cancellable 6-Month A transaction 36 is used for the insurance company to report a Certificate of Cancellation of an SR22 non-cancellable 6-month policy. A transaction 36 (Cancellation of Non-Cancellable PIP) will only be accepted if the cancellation date is within one month of the issued effective date. The required fields for a transaction 36 (Cancellation of Non-Cancellable PIP) are listed below and correspond to the Filing Record Layout. REQUIRED


Transaction 44 – Non-Cancellable 6-Month Bodily Injury Liability/Property Damage Liability/Personal Injury Protection A transaction 20 (Initiation of Insurance) must accompany this transaction or be present on the database.

Page | 27

A 44 transaction is used for the insurance company to report FR44 Non-Cancellable Certificate of Liability Coverage (BIL limits of 100/300/50). The required fields for a transaction 44 (FR44 Certificate of Higher Limits Liability Coverage) are listed below and correspond to the Filing Record Layout. REQUIRED


Transaction 46 – Bodily Injury Liability/Property Damage Liability/Personal Injury Protection A transaction 46 is used for the insurance company to report an FR46 Certificate of Cancellation of an FR44. A transaction 46 (FR46 Certification of Cancellation of FR44) will only be accepted if the cancellation date is within one month of the issued effective date. The required fields for a transaction 46 (FR46 Certification of Cancellation of FR44) are listed below and correspond to the Filing Record Layout. REQUIRED


Error Message Information XSD Validation Prior to processing the file, the DHSMV validates the XML schema is correct. If there is an issue with the schema, a text file will be generated and placed in the Output folder. The file naming convention is as follows: ValidationFailed_Timestamp.pgp. Transaction Errors An output file will be generated and placed in the Output folder for the insurance companies. Within the output file is the transaction report. The transaction report naming convention is as follows: YourFileName_TimeStamp_DL_TransactionReport.pgp. The transaction report will contain the total number of records submitted, the total number of records imported and the total number of records with errors. Once the records with errors have been corrected by the insurance company, the records can be resubmitted in a daily reporting file.

Page | 28

Transaction Error Codes and Error Messages Below are the transaction error codes and error messages, and if the error terminates the import of the record.

Error Code Error Message Will Import Y/N

001 VIN not registered with FL DHSMV. DHSMV will attempt to validate the VIN, as registered, again in 30 days

Y

002 Partial 15-digit match on VIN Y

003 Unable to locate single VIN match; multiple partial matches found N

004 VIN is not valid N

005 VIN must be at least 17 characters for a vehicle year greater than 1980

N

006 VIN is required for non-fleet policies N

007 Company code is not registered with FL DHSMV N

008 Company code must be 5 digits N

009 Transaction type is not valid for reloads, transaction type must be set to “20,” “31” or “34”

N

010 Reload policy is cancelled on database N

011 Policy is currently cancelled N

012 Vehicle Effective Date is required on “31” transaction types N

013 Policy Cancellation Date cannot be prior to Policy Effective Date N

014 Cancellation Date is not a valid date (MMDDYYYY) N

015 Found active policy on the database with an Effective Date after the submitted Effective Date

Y

016 On an Initiation, at least one policyholder is required N

017 Level of Coverage is not in the correct format N

018 VIN contains invalid characters N

019 Policyholder first name contains invalid characters N

020 Active policy not found on reload N

021 Policy is currently cancelled and needs to be recalled N

022 Cannot recall cancellation, policy is currently active N

023 Policyholder last name contains invalid characters N

024 Vehicle Effective Date cannot be in the future N

025 Vehicle Effective Date must be a valid date (MMDDYYYY) N

026 Recall of cancellation date cannot be prior to the cancellation date N

027 30 Day Notice: Second attempt to validate the VIN, as registered, has not been successful

N

028 Last attempt to validate the VIN, as registered, was unsuccessful, the record will be removed from our database. Please verify the VIN and resubmit the updated information through a Dailyload

N

029 Policy number contains invalid characters N

030 In a reload, cannot submit a transaction type “31” without submitting a “20”

N

031 Cannot recall initiation of insurance, policy is currently cancelled N

032 The recall of initiation date is 90 days after the policy effective date

N

Page | 29


033 On an Initiation at least one vehicle is required N

034 Vehicle already exists on the policy N

036 In a reload, cannot submit a transaction type “34” without submitting a “20”

N

037 Policyholder Effective Date must be a valid date (MMDDYYYY) N

038 Policyholder Effective Date is required on “34” transaction types N

039 Policyholder effective date cannot be in the future N

042 Vehicle Make is required N

043 Vehicle exists on multiple active policies N

044 Vehicle does not exist on the policy N

045 Driver does not exist on the policy N

046 Driver already exists on the policy N

047 Policy already exists in the insurance database N

048 Cannot update policy, driver’s name does not match N

049 Cannot add driver or vehicle, initiation record had an error N

050 Initiation of Insurance is not present

N

051 Cancellation updated, policy was already cancelled N

052 Invalid Transaction Type N

053 Cancellation processed. Driver license number supplied was invalid Y

054 Cannot delete driver from the policy, only one driver currently exists

N

056 VIN does not exist on the policy N

057 VIN is required when updating the Level of Coverage N

059 SR22 not required, no sanctions requiring BIL exist for the DLN provided

N

060 Certification Date must be a valid date (MMDDYYYY) N

061 SR/FR Prepared Date must be a valid date (MMDDYYYY) N

062 Duplicate SR22/26 or SR33/36 or FR44/46 found N

063 Time Requirement has been met, a SR/FR Certificate is no longer required

N

064 A newer SR/FR Certificate has been found N

065 No matching SR/FR Certificate could be found when attempting to process the cancellation

N

066 Level of Coverage insufficient, must have at least a “04” Level of Coverage

N


N


N

069 Level of Coverage insufficient, Level of Coverage must be set to “08”

N

071 When responding to verifications, the values for Confirmed must be set to either “Y” or “N”

N

075 Verification Not Requested or Already Received N

Page | 30


076 Cancellation Date cannot be more than 45 days in the future for Commercial Policy

N

077 Cancellation Date cannot be in the future for Non-Commercial Policy

N

078 Effective Date cannot be prior to current effective date N

103 A person is deceased N

00A Transaction Type contains invalid characters N

00B Policyholder middle name contains invalid characters N

00C Vehicle Year not a valid year N

00D Vehicle Year required when VIN is present N

00E Insurance policy number is required N

00F Policyholder first name required N

00G Policyholder last name required N

00H Policyholder state not valid N

00I Policyholder zip code not valid N

00J Policyholder zip code is not complete Y

00K Florida Driver License is not in correct format Y

00L No matching FL DLN found Y

00M DLN is not required on Fleet policy Y

00N Current Driver License Number Found Y

00O Company FED_TIN is missing Y

00P Company FED_TIN must be 9 digits Y

00Q No matching FED_TIN number found Y

00R Company name is missing N

00S Company indicator is invalid, please choose “Y” or “N” N

00T Effective Date must be a valid date N

00U Effective Date cannot be in the future N

00V DOB must be a valid date (MMDDYYYY) N

00W DOB cannot be in the future N

00X Gender must be “M” or “F” or blank N

00Z Fleet Indicator is invalid, please choose “Y” or “N” N

A01 Cancellation must post before recall of Cancellation N

A02 Cannot recall cancellation because cancellation has not been processed

N

A03 No other transaction types can be submitted within same record N

A05 Please include FR Sanction Number N

A06 SR21 has already been received N

A07 A policy already exists, use transaction “31” to add vehicles to this policy

N

A11 Sanction number not valid N

A13 SR/FR Certificate cannot be cancelled within one month of the Certificate being issued

N

A16 Policy has been voided, no further transactions will be accepted N

A26 Policy must be in active status to perform a “Vehicle sold/totaled” transaction

N

Page | 31


A27 Recall of Initiation Date must match Policy Effective Date N

A40 Only SR22 BIL required, a FR44 Certificate is not required N

A41 FR44 not required, no open FR suspensions exist for the DLN provided

N

A42 Need a higher level of coverage, a SR22 BIL Certificate is required N

A43 Need a higher level of coverage, a FR44 certification is required N

A45 Newer SR/FR Certificate on file – SR/FR Certificate of Cancellation not accepted

N

A46 SR/FR Certificate Cancellation Date is prior to SR/FR Effective Date on file – SR/FR Certificate Cancellation no accepted

N

A47 SR/FR Prepared Date is prior to SRFR Prepared Date on file – SR/FR not accepted

N

A50 Unable to determine DLN/ID Number. Name/DOB/Gender is required

N

A51 This tracking number cannot be found N

A52 Unknown system error, resubmit transaction N

A53 Policy Number not found, must report Initiation of Insurance, Trans 20

Y

A54 Level of coverage must be included N

A55 Transaction Type is not valid for a business N

Holding Errors When a VIN is submitted through a reload or daily reporting file and cannot be located in the DHSMV database, the system will import the record into the insurance database and place the VIN in the “Holding” location. The insurance company will receive a warning message, which will be placed in the Output folder on the server. The VIN will be checked again in 30 days to see if it has been registered with the DHSMV. If the VIN is still not registered, we will send another file with a warning notification to the Output folder, informing insurance companies the system tried to verify the VIN again and was unsuccessful. The VIN will remain in the “Holding” location and will be flagged to be checked again in another 30 days. If the VIN has still not been registered after 60 days, the DHSMV will send the final file with an error message to the Output folder, notifying the insurance company the final attempt to verify the VIN was unsuccessful and the record is going to be removed from the DHSMV database. When the insurance company receives any of these warning messages, it must verify the VIN with the policyholder and resubmit any changes made to the record. At any time, during the three checks, if the VIN is verified, the record will be imported and the insurance company does not have to resubmit. The file naming convention for these VIN errors is as follows: Unregistered_Vins_timestamp_DL_TransactionReport.xml. In addition, when the DHSMV receives a valid transaction 10 (Cancellation) or a valid transaction 21 (Recall of Issuance of Coverage), the DHSMV will update the database and put the vehicle information in the “Holding” location to be checked 20 days later. The DHSMV is checking to ensure the vehicle is insured. The insurance companies will not need to perform any action after submitting the cancellation. Steps to Validate an XML File (Reload or Daily) Against the XSD File

1. Copy the FLBOB_Template_Reload_and_Daily_Inputs.xsd from the rear of the Procedure Manual, paste to a file naming the file with an .xsd extension.

http://www.flhsmv.gov/FRIP/

Page | 32

2. Open the XML tool, if insurance companies are using Notepad ++, on the File menu, go to Plugins > XML Tools > Validate Now. Browse to the location of the FLBOB_Template_Reload_and_Daily_Inputs.xsd file.

3. Click “OK” to validate.

You will either receive a transaction report, which serves as confirmation that your file was validated successfully, or a ValidationFailed_Timestamp.pgp file with validation errors. If there are errors, correct the errors and then revalidate the file. Repeat this process until the transaction report is received.

Page | 33

Appendix A – Florida Book of Business Reload and Daily File Structure XML

See FLBOB_Template_Reload_and_Daily_Inputs.xsd

<?xml version="1.0" encoding="UTF-8"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0"> <xs:element name="submitted_file"> <xs:complexType> <xs:sequence> <xs:element name="schema_version" type="xs:decimal" /> <xs:element maxOccurs="unbounded" name="company"> <xs:complexType> <xs:sequence> <xs:element name="company_code" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:pattern value ="[0-9][0-9][0-9][0-9][0-9]"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element maxOccurs="unbounded" name="transaction"> <xs:complexType> <xs:sequence> <xs:element name="transaction_type" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:length value ="2" /> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="policy"> <xs:complexType> <xs:sequence> <xs:element name="policy_number" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="30"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="policy_effective_date" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType>

Page | 34

</xs:element> <xs:element name="policy_cancellation_date" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="insurance_company_notes" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="policy_holder" maxOccurs="unbounded" nillable="true" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="company_indicator" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="1"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="first_name"> <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="25"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="middle_name" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="16"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="last_name"> <xs:simpleType> <xs:restriction base ="xs:string">

Page | 35

<xs:minLength value ="0"/> <xs:maxLength value ="35"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="name_suffix" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="3"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="gender" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="1"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="dob" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="street_address" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="city"> <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="state" > <xs:simpleType> <xs:restriction base ="xs:string">

Page | 36

<xs:minLength value ="0"/> <xs:maxLength value ="2"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="zipcode" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="9"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="fl_dln" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="13"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="fed_tin" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="13"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="non_structured_name" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ph_transaction_type" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="2"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="effective_date" > <xs:simpleType> <xs:restriction base ="xs:string">

Page | 37

<xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="fr_sanction_number" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="12"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="fr_certification_date" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="fr_prepared_date"> <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="vehicle" maxOccurs="unbounded" nillable="true" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="fleet_indicator" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="1"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="vin"> <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="21"/>

Page | 38

</xs:restriction> </xs:simpleType> </xs:element> <xs:element name="year"> <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="4"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="make" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="5"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="vehicle_effective_date" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="8"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="level_of_coverage" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="2"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="vehicle_transaction_type" > <xs:simpleType> <xs:restriction base ="xs:string"> <xs:minLength value ="0"/> <xs:maxLength value ="2"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="verification" nillable="true" minOccurs="0"> <xs:complexType>

Page | 39

<xs:sequence> <xs:element name="tracking_number" /> <xs:element name="required_coverage_dt" /> <xs:element name="status_message" /> <xs:element name="days_late" /> <xs:element name="yes_confirmed" /> <xs:element name="confirmed" /> <xs:element name="unconfirmed" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>

Page | 40

Appendix B – Transaction Report File Structure XML See TransactionReport.xsd

<?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified"> <xsd:element name="XMLOutputEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="InsuranceFileUploadLogID" type="xsd:int" nillable="true" minOccurs="0" /> <xsd:element name="InsuranceSubmissionCompanyCode" type="xsd:string" /> <xsd:element name="UploadedFileName" type="xsd:string" /> <xsd:element name="Comments" type="xsd:string" /> <xsd:element name="CompaniesTransactions"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" name="XMLOutputCompaniesTransactionsEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="Transactions"> <xsd:complexType> <xsd:sequence> <xsd:element name="OutputTransactionEntity" maxOccurs="unbounded" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="InsuranceCompanyCode" type="xsd:string" /> <xsd:element name="TransactionGUID" type="xsd:string" /> <xsd:element name="TransactionType" type="xsd:string" /> <xsd:element name="InsurancePolicy"> <xsd:complexType> <xsd:sequence> <xsd:element name="InsurancePolicyGUID" type="xsd:string" /> <xsd:element name="PolicyNumber" type="xsd:string" /> <xsd:element name="PolicyEffectiveDateOriginal" type="xsd:string" /> <xsd:element name="PolicyCancellationDateOriginal" type="xsd:string"/> <xsd:element name="InsuranceCompanyNotes" type="xsd:string"/> <xsd:element name="PolicyHolders"> <xsd:complexType> <xsd:sequence> <xsd:element name="OutputPolicyHolderEntity" maxOccurs="unbounded" nillable="true" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="PolicyHolderGUID" type="xsd:string" /> <xsd:element name="InsurancePolicyGUID" type="xsd:string" /> <xsd:element name="CompanyIndicator" type="xsd:string" />

Page | 41

<xsd:element name="FirstName" type="xsd:string" /> <xsd:element name="MiddleName" type="xsd:string" /> <xsd:element name="LastName" type="xsd:string" /> <xsd:element name="NameSuffix" type="xsd:string" /> <xsd:element name="Gender" type="xsd:string" /> <xsd:element name="DOBOriginal" type="xsd:string" /> <xsd:element name="StreetAddress" type="xsd:string" /> <xsd:element name="City" type="xsd:string" /> <xsd:element name="State" type="xsd:string" /> <xsd:element name="ZipCode" type="xsd:string" /> <xsd:element name="FLDLN" type="xsd:string" /> <xsd:element name="FLDLNCrossRef" type="xsd:string" /> <xsd:element name="FedTIN" type="xsd:string" /> <xsd:element name="NonStructuredName" type="xsd:string" /> <xsd:element name="EffectiveDateOriginal" type="xsd:string" /> <xsd:element name="TransactionType" type="xsd:string"/> <xsd:element name="FRSanctionNumber" type="xsd:string" /> <xsd:element name="FRCertificationDateOriginal" type="xsd:string" /> <xsd:element name="FRPreparedDateOriginal" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="Vehicles"> <xsd:complexType> <xsd:sequence> <xsd:element name="OutputVehicleEntity" maxOccurs="unbounded" nillable="true" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="VehicleGUID" type="xsd:string" /> <xsd:element name="InsurancePolicyGUID" type="xsd:string" /> <xsd:element name="Vin" type="xsd:string" /> <xsd:element name="VehicleYear" type="xsd:string" /> <xsd:element name="Make" type="xsd:string" /> <xsd:element name="VehicleEffectiveDateOriginal" type="xsd:string" /> <xsd:element name="LevelOfCoverageOriginal" type="xsd:string" /> <xsd:element name="FleetIndicator" type="xsd:string" /> <xsd:element name="TransactionType" type="xsd:string"/> <xsd:element name="MatchingVin" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element>

Page | 42

<xsd:element name="Verifications"> <xsd:complexType> <xsd:sequence> <xsd:element name="OutputVerificationEntity" maxOccurs="unbounded" nillable="true" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="TrackingNumber" type="xsd:string" /> <xsd:element name="RequiredCoverageDate" type="xsd:string" /> <xsd:element name="StatusMessage" type="xsd:string" /> <xsd:element name="DaysLate" type="xsd:string" /> <xsd:element name="ConfirmedAndActive" type="xsd:string" /> <xsd:element name="Confirmed" type="xsd:string" /> <xsd:element name="Unconfirmed" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="HasError" type="xsd:boolean" /> <xsd:element name="Errors" nillable="true" minOccurs="0"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" name="ErrorLogEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="ErrorLogGUID" type="xsd:string" /> <xsd:element name="TransactionGUID" type="xsd:string" /> <xsd:element name="PolicyGUID" type="xsd:string" /> <xsd:element name="PolicyHolderGUID" type="xsd:string" nillable="true" /> <xsd:element name="VehicleGUID" type="xsd:string" nillable="true"/> <xsd:element name="InsuranceData" type="xsd:string" /> <xsd:element name="ErrorCode" type="xsd:string" /> <xsd:element name="ErrorMessage" type="xsd:string" /> <xsd:element name="ErrorType" type="xsd:string" /> <xsd:element name="Imported" type="xsd:string" /> <xsd:element name="CreatedDate" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence>

Page | 43

</xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="CompanyCode" type="xsd:string" /> <xsd:element name="TotalRecordCount" type="xsd:int" /> <xsd:element name="TotalImportedCount" type="xsd:int" /> <xsd:element name="TotalNotImportedCount" type="xsd:int" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xs:schema>

Page | 44

Appendix C – Bulk Policy Errors for Missing and Cancelled Policies BulkPolicyErrors.xsd

<?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified"> <xsd:element name="XMLOutputEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="InsuranceFileUploadLogID" type="xsd:unsignedInt" /> <xsd:element name="InsuranceSubmissionCompanyCode" type="xsd:string" /> <xsd:element name="FailureReason" type="xsd:string" /> <xsd:element name="UploadedFileName" type="xsd:string" /> <xsd:element name="CompaniesTransactions"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" name="XMLOutputCompaniesTransactionsEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="Transactions"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" name="OutputTransactionEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="InsuranceCompanyCode" type="xsd:string" /> <xsd:element name="InsurancePolicy"> <xsd:complexType> <xsd:sequence> <xsd:element name="PolicyNumber" type="xsd:string" /> <xsd:element name="PolicyEffectiveDateOriginal" type="xsd:string" /> <xsd:element name="PolicyCancellationDateOriginal" type="xsd:string" /> <xsd:element name="InsuranceCompanyCode" type="xsd:string" /> <xsd:element name="PolicyHolders"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="unbounded" name="OutputPolicyHolderEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="CompanyIndicator" type="xsd:string" /> <xsd:element name="FirstName" type="xsd:string" /> <xsd:element name="MiddleName" type="xsd:string" /> <xsd:element name="LastName" type="xsd:string" /> <xsd:element name="NameSuffix" type="xsd:string" /> <xsd:element name="Gender" type="xsd:string" /> <xsd:element name="DOBOriginal" type="xsd:string" /> <xsd:element name="StreetAddress" type="xsd:string" />

Page | 45

<xsd:element name="City" type="xsd:string" /> <xsd:element name="State" type="xsd:string" /> <xsd:element name="ZipCode" type="xsd:unsignedInt" /> <xsd:element name="FLDLN" type="xsd:string" /> <xsd:element name="CurrentDLNumber" /> <xsd:element name="FedTIN" type="xsd:string" /> <xsd:element name="NonStructuredName" type="xsd:string" /> <xsd:element name="EffectiveDateOriginal" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="Vehicles"> <xsd:complexType> <xsd:sequence minOccurs="0"> <xsd:element maxOccurs="unbounded" name="OutputVehicleEntity"> <xsd:complexType> <xsd:sequence> <xsd:element name="Vin" type="xsd:string" /> <xsd:element name="VehicleYear" type="xsd:string" /> <xsd:element name="Make" type="xsd:string" /> <xsd:element name="VehicleEffectiveDateOriginal" type="xsd:string" /> <xsd:element name="LevelOfCoverageOriginal" type="xsd:string" /> <xsd:element name="FleetIndicator" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence>

Page | 46

Appendix D – XSD for Verification File <?xml version="1.0" encoding="utf-8"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="Verifications"> <xs:complexType> <xs:sequence> <xs:element name="fl_company_code" type="xs:string" /> <xs:element name="transactions"> <xs:complexType> <xs:sequence> <xs:element name="transaction" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="tracking_number" type="xs:string" /> <xs:element name="fl_company_code" type="xs:string" /> <xs:element name="transaction_type" type="xs:string" /> <xs:element name="insurance_policy_number" type="xs:string" /> <xs:element name="days_late" type="xs:string" /> <xs:element name="ph_street_address" type="xs:string" minOccurs="0" /> <xs:element name="ph_city" type="xs:string" minOccurs="0" /> <xs:element name="ph_state" type="xs:string" minOccurs="0" /> <xs:element name="ph_zip" type="xs:string" minOccurs="0" /> <xs:element name="ph_id_number" type="xs:string" minOccurs="0" /> <xs:element name="company_indicator" type="xs:string" minOccurs="0" /> <xs:element name="process_date" type="xs:string" minOccurs="0" /> <xs:element name="first_name" type="xs:string" minOccurs="0" /> <xs:element name="middle_name" type="xs:string" minOccurs="0" /> <xs:element name="last_name" type="xs:string" minOccurs="0" /> <xs:element name="fr_certification_date" type="xs:string" minOccurs="0" /> <xs:element name="fr_preparation_date" type="xs:string" minOccurs="0" /> <xs:element name="sanctions"> <xs:complexType> <xs:sequence> <xs:element name="sanction"> <xs:complexType> <xs:sequence> <xs:element name="fr_sanction_number" type="xs:string" /> <xs:element name="vehicle" minOccurs="0"> <xs:complexType> <xs:sequence minOccurs="0"> <xs:element name="vin" type="xs:string" minOccurs="0" /> <xs:element name="year" type="xs:string" minOccurs="0" /> <xs:element name="make" type="xs:string" minOccurs="0" /> <xs:element name="fleet_indicator" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType>

Page | 47

</xs:element> <xs:element name="level_of_coverage" type="xs:string" minOccurs="0" /> <xs:element name="coverage_date" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>

procedures manual for implementation of the florida … · lacey lowers dhsmv 06/27/2014 version...

Documents