IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

IDAHO INSURANCE VERIFICATION SYSTEM(IdahoIVS)

Implementation Guide for Insurance Companies
Version 1.0
June 29th, 2023

1

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

TABLE OF CONTENTS
1.

INTRODUCTION ...............................................................................................................................................3

2.

INSURANCE COMPANY WEB SERVICES ...................................................................................................4
2.1
2.2
2.3
2.4
2.5

3.

FILE EXCHANGE AND TESTING..................................................................................................................8
3.1
3.2

4.

WEB SERVICE STRUCTURE .............................................................................................................................4
EXPECTED LEVEL OF SERVICE ........................................................................................................................5
THE VERIFICATION REQUEST AND RESPONSE ................................................................................................5
WEB SERVICE TESTING ..................................................................................................................................6
VIN BROADCASTING ......................................................................................................................................7
FTP ACCOUNTS AND PGP ENCRYPTION .........................................................................................................8
FILE TESTING PROCESS ..................................................................................................................................8

BOOK OF BUSINESS FILE REPORTING .....................................................................................................9
4.1
4.2
4.3
4.4

BOB DATA TO BE REPORTED ........................................................................................................................9
BOB FILE STRUCTURE ...................................................................................................................................9
BOB FILE SUBMISSION................................................................................................................................. 11
BOB RETURN FILES GENERATED FOR INSURANCE COMPANIES ................................................................... 115.

BOB REPORTING BY SMALLER INSURANCE COMPANIES ............................................................... 12

6.

REGISTRATION PROCESS ........................................................................................................................... 12
6.1
6.2
6.3
6.4
6.5

7.

INSURANCE COMPANY REGISTRATION ......................................................................................................... 12
ACCESSING HELP.......................................................................................................................................... 13
LOGIN FOR REGISTERED AND APPROVED INSURANCE COMPANY USERS...................................................... 13
INSURANCE COMPANY PROFILE MANAGEMENT ........................................................................................... 13
INSURANCE COMPANY REPORTS .................................................................................................................. 13

SUPPORT .......................................................................................................................................................... 13

APPENDIX A: SAMPLE VERIFICATION REQUEST AND RESPONSE MESSAGES ................................. 14
APPENDIX B: UNCONFIRMED REASON CODES ............................................................................................ 16
APPENDIX C: VEHICLE TYPES TO BE REPORTED ...................................................................................... 17
APPENDIX D: ERROR CODES IN BOB ROW ERROR FILES ........................................................................ 18
APPENDIX E: DEFINITIONS ................................................................................................................................ 192

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

1.

Introduction

Idaho Statute 49-1234 requires the Idaho Transportation Department (ITD) to establish and maintain an
online insurance verification system for motor vehicle insurance coverage. The ITD Division of Motor
Vehicles (DMV) is implementing an electronic insurance verification system termed the Idaho Insurance
Verification System (IdahoIVS) in order to meet this requirement. IdahoIVS will replace the current Online
Insurance Verification System (OIVS) managed by the DMV. IdahoIVS will provide DMV the ability toperform real-time insurance verification and significantly improve the uninsured identification process.
IdahoIVS will utilize the Insurance Industry Committee on Motor Vehicle Administration (IICMVA)
standards for insurance company reporting.
IdahoIVS insurance company reporting requirements are summarized below:• Web services: Insurance companies insuring more than five hundred (500) vehicles in Idaho shallmake their insurance verification web service available to IdahoIVS.
o
The web services should follow the specifications and standards of the IICMVA.
o Insurance companies are required to make private passenger and commercial policies available
through this web service.
oWhile commercial policies are required, insurance companies are not required to makecommercial non-vehicle specific policies (generally referred to as “all owned” or “blanket policies”)
available through this web service.
•Book of Business: Insurance companies insuring vehicles in Idaho shall provide their Book of
Business (BOB) data to IdahoIVS on a weekly basis.
o The BOB files should include private passenger and commercial policies with liability coverage,
and policies with comprehensive-only coverage.
o Commercial policies (except for Motor Carrier policies) are required to be reported. The Vehicle
Identification Numbers (VINs) are not required for non-vehicle specific policies unless available
for reporting.
o Insurance companies submitting BOB data to IdahoIVS must use the secure file transfer protocol(SFTP) process outlined in this Guide. Insurance companies insuring five hundred (500) or fewer
vehicles in Idaho can either SFTP the BOB file or utilize the IdahoIVS website for BOB reporting.

Key dates for insurance companies are listed below:• June 29th, 2023 – IdahoIVS is available to insurance companies for registration, testing, andproduction integration.
• July 31st, 2023 – Deadline for insurance companies to register on the IdahoIVS website(www.IdahoIVS.com).
• September 30th, 2023 – Deadline for insurance companies to begin testing. Insurance companies
must submit a test BOB file to IdahoIVS and begin web services testing.
• December 1st, 2023 – Deadline for insurance companies to move to production with IdahoIVS,
making their production web services available (if applicable) and begin BOB data submissions.
The current Idaho Online Insurance Verification System (OIVS) will be discontinued after IdahoIVS is
implemented and the uninsured identification process is transferred to IdahoIVS. Until then, insurers
should also continue their current reporting to OIVS. DMV will issue communication informing insurancecompanies when OIVS is discontinued.
This Guide and any future updates will be posted on the IdahoIVS website. Go to www.IdahoIVS.com,
click on the HELP link, and then on Help For Insurance Companies.
3

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Insurance companies are responsible for reading and complying with this Guide and reviewing additional
information posted on the IdahoIVS website. If you have any questions, please contact the IdahoIVS help
desk at support@IdahoIVS.com.

2.

Insurance Company Web Services

Insurance company web services must be capable of verifying the existence of mandatory liability
insurance for vehicles registered/rated in Idaho.

2.1

Web Service Structure

The IdahoIVS Online Verification client is based upon the model developed by the IICMVA that allows ajurisdiction to use web services hosted by insurance companies to verify insurance. This section
describes the overall structure of the web services to be hosted by the insurance companies.
Web Services Description Language (WSDL) File
A WSDL file is an XML file that describes the public interface to a web service. The IICMVA has created
WSDL files for Java, .Net, and Universal web service implementations. To make the verification process
as fast as possible, IdahoIVS uses these WSDL files and does not attempt to read the WSDL file for each
web service every time a verification request is initiated. IdahoIVS manages the endpoints, which are
Uniform Resource Locators (URLs), from a local configuration file.
Insurance companies are required to use one of the WSDLs published by the IICMVA. These WSDLs canbe found at http://www.iicmva.com/IICMVAPublications.html.
SchemaAn XML schema describes the structure of an XML message. IdahoIVS currently supports the ANSI ASC
X12 Insurance Committee’s XML Schema for Online Insurance Verification. Case is not specified in theschema. If an insurance company has particular requirements for upper or lower case, the message
payload must be converted to the required case. Also, the policy number must be converted to therequired format.
Extensible Markup Language (XML) Messages
The XML messages for the insurance verification request and response are derived from the schema.
Appendix A contains a sample verification request message and a sample verification response
message.
Simple Object Access Protocol (SOAP)
SOAP is an XML based protocol that is used by web services to wrap around the XML messages making
them platform and language independent. SOAP 1.1 is required.
Hypertext Transfer Protocol (HTTP) over Transmission Control Protocol/Internet Protocol (TCP/IP)
The XML messages will be transported over the internet via HTTP. Verification requests will utilize HTTP
1.1 and it is strongly suggested that it be used for the verification responses as well.

4

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Security
The XML messages will be encrypted via the Secure Sockets Layer/Transport Layer Security (SSL/TLS).
IdahoIVS will maintain Class 3 X.509 certificates identifying both the test and production environments.
The certificate will be presented in each connection handshake so that the insurance company canauthenticate the client.

2.2

Expected Level of Service•

Insurance companies’ web services are required to respond to verification requests on a 24/7/365
basis. Although a reasonable amount of downtime to maintain and upgrade systems may occur,
the web service availability, measured on a monthly basis, shall be at least 99%.

•

Scheduled downtime must be reported via e-mail to support@IdahoIVS.com as early as possible,
describing the reason for the downtime, the time the web service will become unavailable, andthe time it is expected to become available again.

•

Unscheduled downtime must be reported via e-mail to support@IdahoIVS.com immediately,
describing the reason for the downtime, the time the web service became unavailable, and theestimated time it will become available again.

•

Insurance companies should design their web services to provide a response within 2 seconds ofreceipt of an inquiry. Contributing factors to slow responses outside the control of the insurancecompanies, such as Internet response time, will be taken into account. Responses not received ina timely manner will be logged and used for evaluating the insurance company's web services
performance.

•

Accuracy is critical to the success of the program. Therefore, each insurance company’s web
service must provide the correct response to an inquiry. Each web service will be monitored andtested for accurate responses, including testing for false confirmations.

2.3

The Verification Request and Response

IdahoIVS supports the current and previous versions of the IICMVA specifications and plans to include
future versions as they are issued. Prior to implementation of a schema, a WSDL created from theschema must be tested and approved.

2.3.1 The Verification Request
The verification request is sent to the appropriate insurance company by IdahoIVS in the XML message
format that is valid for the schema employed by the insurance company’s web service. Verification thatthe request is from an authorized entity can be established from the certificate that IdahoIVS will
present when the connection is initiated.
The following data elements will be in the verification request message:•

Tracking/Reference Number (ties the request to the response)•

National Association of Insurance Commissioners (NAIC) Code (identifies insurance company)•

Vehicle Identification Number (VIN)•

Policy Number (“UNKNOWN” will be provided, if not available)•

Verification Date5

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

The Verification Date may be the current date or a date in the past. Insurance companies are required
to verify insurance for dates up to one year in the past.

2.3.2 The Verification Response
For each verification request sent by IdahoIVS, a verification response should be issued by the
insurance company’s web service. Because of front end edits, IdahoIVS will not send inquiries thatwould result in a response from the insurance company that the request was invalid.
If minimum Idaho motor vehicle liability coverage is present and active on the requested verification
date, the insurance company should respond with the following coverage confirmation result:
CONFIRMED.
If minimum Idaho motor vehicle liability coverage is not present or is not active on the requested
verification date, the insurance company should respond with the following coverage confirmation
result: UNCONFIRMED.
The required data elements in a verification response are:•ResponseCode•

NAIC: This is the NAIC of the insurance company insuring the vehicle.

We also recommend including the following data elements. However, these data elements are notmandatory.

2.4•

UnconfirmedReasonCode•

TrackingNumber (return the number received in the verification request)•

VerificationDate•

UniqueKey (policy number)•

PolicyStateWeb Service Testing

Before testing begins, each insurance company will have to register on the IdahoIVS website as
described in Section 6. After registration is complete, the insurance company will be contacted by the
IdahoIVS team to schedule a conference call to discuss the testing process and address any questions
about the IdahoIVS requirements. The following information will be collected during the call:•

NAIC codes that will be supported by the web service.

•

The web service URL(s).

•The IICMVA WSDL that is used by the web service.

•

A time frame during which insurance companies would like to conduct the testing.

Following the call, the insurance company will be sent the following:•

The SSL certificates that identify the IdahoIVS web service Client.

6

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0•

The IP addresses that identify the source of the verification requests.

The testing will consist of the following steps:
Basic connectivity test•

Connectivity between endpoints to ensure that endpoints are reachable.

Test ability to send and receive messages•

Test verification requests and responses formatted in XML and wrapped in SOAP are exchanged.

Testing with security•

The SSL encryption and authentication via the X.509 certificates will be enabled. Testing will bedone to ensure that the functionality is not impacted for insurance companies who haveconfigured the IdahoIVS SSL certificate in their web service. For companies who choose to install
the certificate from the jurisdiction, they must install the public key from the IdahoIVS SSL
certificate and the root certificate from the issuing certificate authority.

Test Cases and Data
IdahoIVS will run the insurance company’s web service through a set of test cases. If required, theinsurance company will provide the data necessary for these test cases.
•

2.5

After all the above testing has been completed, the insurance company can make theirproduction web service available to IdahoIVS for insurance verification.

VIN Broadcasting

If the VIN in the verification request message matches an insured vehicle but the policy number in therequest does not match the insurance policy number, then the insurance company’s web service shouldbe able to indicate that the vehicle is covered (this is known as “VIN Broadcasting” or “Unknown Carrier
Request”). The insurance company can indicate that the vehicle is covered in one of the following ways:••

Returning a value of “UNCONFIRMED” in the ResponseCode field and a value of “10” or “VIN3”
in the UnconfirmedReasonCode field of the CoverageResponse document.
Returning a value of “CONFIRMED” in the ResponseCode field of the CoverageResponse
document.

It is recommended that insurance company web services support VIN broadcasting.

7

IdahoIVS Implementation Guide for Insurance Companies - Version 1.03.

File Exchange and Testing

3.1

FTP Accounts and PGP Encryption

Insurance companies must send text files to IdahoIVS using Secure File Transfer Protocol (SFTP – FTP
over SSH). Secure FTP accounts will be created for each insurance company after registering with
IdahoIVS. If the insurance company prefers, the same FTP account can be shared by companies withdifferent NAIC numbers that are under the same insurance group. Login information and the IP addressesof the FTP servers will be provided after registration.
Each FTP account will have the following folders:•

BOB_Inbound•

BOB_OutboundAll files exchanged between IdahoIVS and insurance companies will also be encrypted by the Pretty
Good Privacy (PGP) digital data encryption program. Public PGP keys will be exchanged with the
IdahoIVS Help Desk prior to exchanging insurance data.

3.2

File Testing Process

Before testing begins, each insurance company participating in IdahoIVS must register on the IdahoIVS
website as described in Section 6. After completing registration, insurance companies will be contacted
by the IdahoIVS team to schedule a conference call to discuss the testing process and address anyquestions about the IdahoIVS reporting requirements. FTP User IDs and passwords will be provided, andpublic PGP keys will be exchanged.
The testing process includes the following:•

Connectivity Testing: The insurance company should be able to connect to the designatedIdahoIVS FTP server, login to the insurance company’s FTP account, and transfer files to theappropriate folders. The insurance company should be able to retrieve IdahoIVS return files.

•

Decryption: IdahoIVS should be able to successfully decrypt files. The insurance company
should be able to successfully decrypt IdahoIVS return files.

•

File Format: The insurance company files should be formatted according to IdahoIVS
requirements.

•

File Content: The insurance company file should contain valid test data and the data elements
should meet the IdahoIVS rules. During testing, it is not necessary to provide production data (inforce policies).

The IdahoIVS team will work with insurance companies and provide information to assist in the
resolution of any errors.

8

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

4.

Book of Business File Reporting

BOB data should contain all active motor vehicle liability insurance policies rated for Idaho. The format
and method of submitting BOB data is covered in this section.

4.1

BOB Data To Be Reported

The following information should be included in the BOB files:

4.2•

All active Idaho motor vehicle insurance policies with the minimum liability coverage required by
the State of Idaho and the associated vehicles and customers.

•

Policies with only comprehensive coverage. For policies with comprehensive coverage only, the
COMPREHENSIVE INDICATOR should be set to “Y”.

•

Commercial policies (except for Motor Carrier policies) are required to be reported. The Vehicle
Identification Number (VIN) is not required for non-vehicle specific policies.

•

VINs are not required to be reported for non-vehicle specific policies unless available forreporting.

•

Vehicle types exempt from reporting are provided in Appendix C.

BOB File Structure

The BOB file structure is based upon Version 1.2 of the Insurance Data Transfer Guide published by the
IICMVA on January 3, 2017. The BOB file is a text file with rows of fixed length. All rows will be 300
characters long with spaces used as filler. Each row must be followed by a carriage return line feedcharacter (Hexadecimal ‘0D 0A’). A separate file should be submitted for each NAIC number.
File Name
The file name should include the following fields:• NAIC Number: Insurance company’s NAIC Number• File Creation Date: Date file was created in the YYYYMMDD format• Environment: “P” – Production; “T” - Test
• Extension: File extension such as “pgp”, “asc”, ”txt” or any other 3 character file extension
File Name format should be in the NAIC_ Date_Environment.extension format.
For example: 12345_20190815_P.pgp
Detail Rows
The detail rows show the policy data being submitted by the insurance company. One record should be
generated per each customer, vehicle, and policy combination. For example, if policy number 12345 is
associated with customers Jane and John Doe on a 2004 Jeep and a 2005 GMC, then four records withthe following combinations should be created:•

Jane Doe, 2004 Jeep, policy 12345•

Jane Doe, 2005 GMC, policy 12345•

John Doe, 2004 Jeep, policy 12345•

John Doe, 2005 GMC, policy 12345

9

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Each field’s length is specified in the table below with any unused length filled by trailing spaces. Any
fields for which a value is not being provided should be filled with spaces. Provide the following fields ineach row:
Field
Field Name
Lengt Begin End
Type
Mandatory Description
Idh(AN –Alpha/Optional
numeric
N- Numeric)1
POLICY TYPE
2
1
2
AN
M
‘VS’ = Vehicle Specific‘NS’ = Non-Vehicle Specific
2
NAIC
5
3
7
N
M
NAIC Code
3
POLICY NUMBER
30
8
37
AN
M
Policy Number
4
EFFECTIVE DATE
8
38
45
N
M
Effective Date – YYYYMMDD
formatDate coverage was added forthe vehicle. There should
not be any time out of force(lapse of coverage) between
the Effective Date and thetransmission date. If thevehicle had any time out offorce, then the effective datethat coverage was resumed
or reinstated should bereported.
5
VIN
25
46
70
AN
O
VIN (optional for non-vehicle
specific fleet policy)
6
LAST NAME or
40
71
110
AN
M
ORGANIZATION
7
PREFIX NAME
3
111
113
AN
O
ABBR
8
MIDDLE NAME
20
114
133
AN
O
9
FIRST NAME
40
134
173
AN
O
Mandatory if customer is anindividual
10
SUFFIX NAME
3
174
176
AN
O
Abbreviated Name Suffix (JR,SR, etc.)
11
FEIN
9
177
185
AN
O
12
ADDRESS
50
186
235
AN
M
13
CITY
35
236
270
AN
M
14
STATE
2
271
272
AN
M
15
ZIP
5
273
277
N
M
16
COMMERCIAL
1
278
278
AN
O
"Y" for commercial policies
INDICATOR
17
COMPREHENSIVE 1
279
279
AN
O
“Y” for Comprehensive
INDICATOR
Coverage Only
18
FILLER
21
280
300
AN
M
Space Filled10IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Trailer Row
Each file should have one trailer row with the following fields:
Field Name

Length

Begin

End

Type

TYPE
RECORD
COUNTPROCESS DATE

2
12

1
3

2
14

AN
N

Mandatory/Optiona
l
M
M

8

15

22

N

M

FILLER

278

23

300

AN

M

4.3

Description‘TR’ = Trailer
Record count not including
Trailer Record
Date the file was created –YYYYMMDD Format
Space Filled

BOB File Submission

Each insurance company will be assigned an FTP account (see Section 3.1). There will be two folders
under each FTP account for exchanging BOB files. Place all BOB files into the BOB_Inbound folder. All
return files created by IdahoIVS in response to the BOB files will be placed in the BOB_Outbound folder.

4.4

BOB Return Files Generated for Insurance Companies

This section describes the types of files that may be generated by IdahoIVS and placed in the
BOB_Outbound folder of the insurance company. These files will inform insurance companies if their files
were successfully processed or if any errors were encountered in the processing. For each BOB filesubmitted by the insurance company, at least one of the following files will be generated by IdahoIVS:
1. OK file: If there are no errors in the BOB file submitted by the insurance company, an OK file will be
generated. The OK file name will be named OK_NAIC_DatetimeStamp.pgp (e.g. OK_12345_
20190806121501.pgp).
2. Decryption Error File: This file will be generated if a PGP decryption error occurs. Decryption errors
can happen for the following reasons:a. File sent by insurance company was not encrypted.
b. File sent by insurance company was improperly encrypted.
c.

File sent by insurance company was encrypted using the wrong PGP key.

Decryption error file will be identified based on the file name prefix DE. The file will be named
DE_NAIC_DatetimeStamp.pgp (e.g. DE_12345_ 20190806121501.pgp).
3. Reject File: This file will be generated if IdahoIVS cannot read the file or if the file is improperly
formatted and the whole file is being rejected. The file may be rejected for the following reasons:a. File is not formatted properly.
b. Trailer has a non-zero record count but detail records of the file are missing.
c.

Length of each record (row) is not up to the length specified in this guide.

d. End of a record (row) missing carriage return and line feed (Hexadecimal ‘0D 0A’).
The reject file will contain the description of the error at the top followed by the contents of the file.
The reject file can be identified based on the file name prefix REJ. File will be named
REJ_NAIC_DatetimeStamp.pgp (e.g. REJ_12345_ 20190806121501.pgp).

11

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

4. Row Error File: Row error files are generated when the overall file format sent by the insurancecompany is okay but some of the rows have errors including:a. Mandatory fields missing.
b. Invalid field formats or values.
The row error file will contain only the records that are in error. The remaining records sent withthe original file will be processed by IdahoIVS and will not appear in the file. Each error record will
have the original row sent by the insurance company followed by a 3 digit Error Code. The formatof the Error Code will be E followed by the Field ID of the invalid/missing field. For example, theError Code for a row with an invalid NAIC number will be “E02”. A complete list of Error Codes isprovided in Appendix D.
The Row Error file can be identified based on the file name prefix ERR. File will be named
ERR_NAIC_DatetimeStamp (e.g. ERR_12345_20190806121501.pgp).
5. VIN No-Match File: The VIN No–Match files are generated if any of the VINs submitted by the
insurance company do not match VINs of vehicles registered in Idaho. The VIN No-Match file will
include all the records where the VIN did not match. Each record will have the original row sent by
the insurance company followed by “E05”, the 3 digit Error Code indicating VIN mismatch. VIN NoMatch files are sent to insurance companies for informational purposes and insurance companies are
not required to take action based on these files.
The VIN No-Match file can be identified based on the file name prefix VIN. File will be named
VIN_NAIC_DatetimeStamp (e.g. VIN_12345_ 20190806121501.pgp).

5.

BOB Reporting By Smaller Insurance Companies

Smaller insurance companies insuring five hundred (500) or less vehicles in Idaho are not required tohost insurance verification web services and report BOB files via FTP. If the smaller insurance companies
are not reporting BOB files by FTP, these companies shall perform a one-time entry of all policies via the
IdahoIVS website. After the initial entry, these insurance companies will only be required to update theirpolicies on the IdahoIVS website whenever a policy is added, modified or cancelled/expired.

6.

Registration Process

Insurance companies must register on the IdahoIVS website before testing with IdahoIVS. The IdahoIVS
website can be accessed at https://www.IdahoIVS.com. Cookies should be enabled for the website toproperly function after the user has logged in. The IdahoIVS website is used for user registration, accountmanagement, reporting, user management, and providing help to insurance companies.

6.1

Insurance Company Registration

To register, go to the IdahoIVS website home page and click on the “Register” link in the menu.
Registration is only available to insurance companies that are licensed in Idaho. Please follow the
instructions below:•

Fill in all the insurance company information and functional contact details.

•

Fill in the technical contact details.

12

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0•

Fill in the compliance contact details. The compliance contact is used to verify insurance by the
IdahoIVS Help Desk.

•

Provide the password in the Web Login Section.

•

Provide a secret question and answer which will be used with the Forgot Password functionality.

After the insurance company submits the registration request, the web account is created and the
IdahoIVS team will review and verify it. If the registration requirements are not met, the contact
information submitted during registration will be used to notify the registrant and collect any
missing/incorrect information. Once verification is complete, the insurance company will be contacted by aIdahoIVS representative to start the testing process.

6.2

Accessing Help

The IdahoIVS website help function is available to users at all times and does not require the user to log
in to the website. In order to get help, click on the “Help” link from the menu on any screen. The following
information is available through the help function:•

Users can download the latest version of the IdahoIVS Implementation Guide that provides
detailed information on interacting with IdahoIVS.

•

A Frequently Asked Questions section will be populated based on queries that the IdahoIVS Help
Desk receives most often.

•

If these sources listed above are not sufficient, click on the “Contact” link to write an email to the
IdahoIVS Help Desk.

The IdahoIVS Help Desk can be contacted directly at support@IdahoIVS.com

6.3

Login for Registered and Approved Insurance Company Users

The insurance company must be registered with the IdahoIVS website and the account must be activatedbefore a user can login. To login, enter the user name and password on the IdahoIVS website home page
and then click the Login button.

6.4

Insurance Company Profile Management

Once logged in, the User can click on the Account Information link to access the company profile
information. The User can change the address, contact, and password information.

6.5

Insurance Company Reports

This section will provide reports that will allow the insurance companies to determine the processing
status of the files that were submitted.

7.

SupportInsurance companies with questions about IdahoIVS or needing any clarification about information
provided in this guide should send an email to support@IdahoIVS.com.

13

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Appendix A: Sample Verification Request and Response Messages
Please Note: The sample request and response messages included in this guide are for illustrative
purposes and is based on the IICMVA Web Service WSDL Version Java 1.1 (00200809).
Sample Verification Request Message<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance"><soapenv:Body><CoverageRequest xmlns="http://www.iicmva.com/CoverageVerification/"
PublicationVersion="00200809" PublicationDate="2008-11-05"><RequestorInformation><Organization><Name>IdahoIVS</Name></Organization><ReasonDetails><ReasonCode>BIVER</ReasonCode><TrackingNumber>CTTRK-150219-144041-4-31-101-85-1</TrackingNumber></ReasonDetails></RequestorInformation><Detail><PolicyInformation><OrganizationDetails><NAIC>12345</NAIC></OrganizationDetails><PolicyDetails><VerificationDate>2018-02-19T00:00:00.000</VerificationDate><PolicyKey>UNKNOWN</PolicyKey><PolicyState>ID</PolicyState></PolicyDetails></PolicyInformation><VehicleInformation><VehicleDetails><VIN>VINTEST123</VIN></VehicleDetails></VehicleInformation></Detail></CoverageRequest></soapenv:Body></soapenv:Envelope>Sample Verification Response Message<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAPENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><CoverageResponseDocument PublicationVersion="00200809" PublicationDate="2008-11-05"
xmlns="http://www.iicmva.com/CoverageVerification/"><RequestorInformation>

14

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0<!-- this section can be echoed from the request --><Organization><Name>IdahoIVS</Name></Organization><ReasonDetails><ReasonCode>BIVER</ReasonCode><TrackingNumber>CTTRK-150219-144041-4-31-101-85-1</TrackingNumber></ReasonDetails></RequestorInformation><Detail><PolicyInformation><CoverageStatus><ResponseDetails><ResponseCode>Unconfirmed</ResponseCode><UnconfirmedReasonCode>VIN1</UnconfirmedReasonCode></ResponseDetails></CoverageStatus><OrganizationDetails><NAIC>12345</NAIC></OrganizationDetails><PolicyDetails><!-- this section can be echoed from the request --><VerificationDate>2018-02-19T00:00:00.000</VerificationDate><PolicyKey>UNKNOWN</PolicyKey><PolicyState>ID</PolicyState></PolicyDetails></PolicyInformation></Detail></CoverageResponseDocument></SOAP-ENV:Body></SOAP-ENV:Envelope>15

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Appendix B: Unconfirmed Reason Codes
Original Unconfirmed Reason Codes from ASC X12 Schema
1 Incorrect Data Format
2 Missing Unique Key
3 Missing NAIC Code4 Missing VIN
5 Missing Verification Date
6 Unauthorized Requestor
7 System Cannot Locate Unique Key Information
8 System Found Unique Key - No Coverage on Date
9 System Found Unique Key - VIN Cannot Be Verified
10 System Found VIN - Unique Key Cannot Be Verified
11 System Cannot Locate Policy Information - Manual Search In Progress
12 System Unavailable
Newer Unconfirmed Reason Codes from ASC X12 Schema 00200706 and later
IDF
SYSU
UREQ
NAIC1
NAIC2
PKEY1
PKEY2
PKEY3
PKEY4
POL1
VDT1
VDT2
VIN1
VIN2
VIN3
VIN4

Incorrect Data Format
System Unavailable
Unauthorized Requestor
NAIC Code Not Submitted
System Cannot Locate NAIC
Policy Key Not Submitted
System Cannot Locate Policy Key Information
System Found Policy Key - Coverage on Verification Date Cannot Be Confirmed
System Found Policy Key - VIN Cannot Be Verified
System Cannot Locate Policy Information - Manual Search in Progress
Coverage on Verification Date Cannot Be Confirmed
Verification Date Not Submitted
System Cannot Locate VIN
System Found VIN - Coverage on Verification Date Cannot Be Confirmed
System Found VIN - Policy Key Cannot Be Verified
VIN Not Submitted

16

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Appendix C: Vehicle Types to be Reported
Vehicle types to be reported:• Passenger vehicles• Trucks• Motorcycles• Motorhomes• Buses• Neighborhood Electric Vehicles / Low Speed Vehicles
Vehicle types not required to be reported:• All vehicle types not included above17

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Appendix D: Error Codes in BOB Row Error Files
Error Code
E01
E02
E03
E04
E05
E06
E07
E08
E09
E10
E11
E12
E13
E14
E15
E16
E17

Field Id
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

Field Name
POLICY TYPE
NAIC
POLICY NUMBER
EFFECTIVE DATEVINLAST NAME or ORGANIZATIONPREFIX NAME ABBR
MIDDLE NAMEFIRST NAMESUFFIX NAMEFEIN
ADDRESS
CITY
STATE
ZIP
COMMERCIAL INDICATORCOMPREHENSIVE INDICATOR

18

IdahoIVS Implementation Guide for Insurance Companies - Version 1.0

Appendix E: Definitions
Book of Business (BOB): File that includes specified policy, vehicle, and customer information for all
active policies with minimum liability coverage or comprehensive-only coverage.
Decryption Error (DE) File: This file will be generated if a PGP decryption error occurs. Decryption
errors can happen for the following reasons: the file sent by insurance company was not encrypted, thefile sent by insurance company was improperly encrypted, or the file sent by insurance company wasencrypted using the wrong PGP key.
FTP: File Transfer Protocol - standard network protocol used to transfer computer files from one host toanother host over a TCP-based network.
IdahoIVS: Idaho Insurance Verification System – the new insurance reporting system covered by thisGuide.
IICMVA: Insurance Industry Committee on Motor Vehicle Administration.
NAIC Number: The Number issued by the National Association of Insurance Commissioners to licensed
and affiliated insurance companies across the U.S.
OIVS: Online Insurance Verification System – the legacy insurance reporting system run by DMV. OIVS
will be replaced by IdahoIVS after successful implementation of IdahoIVS.
DMV: Idaho Division of Motor Vehicles
ITD: Idaho Transportation Department
Non Vehicle Specific Policy: A policy where VIN information is not maintained. However, if theinsurance company does maintain the VIN, the filing must be reported on a vehicle-by-vehicle basis.
OK file: If there are no errors in the BOB file submitted by the insurance company, an OK file will be
generated.
Reject (REJ) File: This file will be generated if IdahoIVS cannot read the file or if the file is improperly
formatted and the whole file is being rejected.
Row Error File: Row error files are generated when the overall BOB file format sent by the insurancecompany is okay but some of the rows have errors including mandatory fields missing and invalid fieldformats.
VIN Broadcasting: If the VIN in the verification request message matches an insured vehicle but thepolicy number in the request does not match the insurance policy number, then the insurance company’s
web service should be able to indicate that the vehicle is covered. This is known as “VIN Broadcasting”
or “Unknown Carrier Request”.
VIN No-Match File: The VIN No–Match files are generated if any of the VINs submitted by the insurancecompany in the BOB files do not match VINs of vehicles registered in Idaho.

19