LexisNexis MVR Fixed Length Input File Mapping Insurance Solutions Portal February 2014

Transcription

1 LexisNexis MVR Fixed Length Input File Mapping Insurance Solutions Portal February 2014

2 LexisNexis MVR Fixed Length Input File Mapping Insurance Solutions Portal February 2014 CONFIDENTIAL & PROPRIETARY The recipient of this material (hereinafter "the Material") acknowledges that it contains confidential and proprietary data the disclosure to, or use of which by, third parties will be damaging to LexisNexis Inc. and its subsidiary companies (hereinafter "LexisNexis"). Therefore, recipient agrees to hold the Material in strictest confidence, not to make use of it other than for the purpose for which it is being provided, to release it only to employees requiring such information, and not to release or disclose it to any other party. Upon request, recipient will return the Material together with all copies and modifications, if any. All names in the text, or on the sample reports and screens shown in this document, are of fictitious persons and entities. Any similarity to the name of any real person, address, school, business or other entity is purely coincidental. The trademarks, logos and service marks (collectively the "Marks" or "Mark") appearing in this document are registered and unregistered Marks of LexisNexis Risk Solutions and others. The information contained herein does not constitute a grant of any license or right to use any Mark displayed on this document. LexisNexis aggressively enforces its intellectual property rights. Copyright 2014 LexisNexis. All rights reserved.

3 Table of Contents Introduction... 4 MVR Batch Fixed Length Input File Format... 4 Data Type Description... 4 For Additional Information... 4 Key Order Information... 5 Explanation for Keys on the Order Information... 5 Example for Key Order Information... 5 Packet Header Information... 6 Explanation for Keys on the Packet Header Information... 6 Example for Packet Header Information... 6 General Header Information... 7 Explanation for Keys on the General Header Information... 7 Example for Packet Header Information... 8 Order Data Information... 9 Explanation for Keys on the Order Data Information... 9 Example for Order Data Information... 9 Copyright 2014 LexisNexis. All rights reserved. 3

4 Introduction The Insurance Solutions web-portal will support two exclusive file formats, fixed length and comma delimited. Customers have the option to use one or the other format to load the input data to process the inquiries in batch mode. This document provides details for the fixed length file format. Please refer to LexisNexis MVR Comma Delimited Input File Mapping Insurance Solutions Portal for variable length file specifications. MVR Batch Fixed Length Input File Format MVR order information contained in the fixed length file format is a 255 bytes record. The record is virtually divided in 4 sections to group information accordingly. These four sections are: Key Order This section is 50 bytes which consists of customer specific information such as Case ID, Sequence number, userid, and other information. Packet Header Information This section is 11 bytes which consist of the product identifier General Order Information This section is 23 bytes which consists of Account Number, Account Suffix, Special Billing ID, etc. Order Data Information This section is 141 bytes which consists of MVR Applicant/Subject details such as Last Name, First Name, Middle Name, etc. Each state has its own specifications on what is required and which fields are optional. Insurance portal will inform the user if a record fails the minimum data requirements to submit the order. Data Type Description This section explains the different codes to describe the data types. A N A/N Data Type Description Alpha characters including underscore and punctuation marks. Numeric (does not include decimals) Alpha and numeric characters. For Additional Information For additional information about the state specific information please refer to the following documents. MVR Order Edits MVR State Activity Files Copyright 2014 LexisNexis. All rights reserved. 4

5 Key Order Information This section is 50 bytes which consists of Administration information such as Prepare Date, Time, User Id and Case ID. Explanation for Keys on the Order Information 0 2 A Filler (always a space) Reserved of future use 2 5 A Product ID always 'MVR ' 7 11 A Reserved for future use (spaces) 18 3 A/N User ID, Reserved, space fill 21 1 A/N Filler (always space) 22 6 N Order Sequence number identifying each record/unit in the file A/N Case ID (user defined i.e. policy #, etc.) is a user defined field for your unit of business (i.e. policy number, etc). Case Id is a required field; every order within the batch must contain a Case Id. For blank CaseId, system will auto generate a single CaseId for the entire batch. This setup is configured at the Node/Account setup level. The caseid does not accept underscore _, less than sign <, or greater than sign > A/N Filler (space fill) Example for Key Order Information Product ID(5) User Id(3) Order Sequence(6) ^] ^] MVR^^] ^^^^^^^^^^^] ^^^] ^ ] ^ ] TEST ] ^^] Filler/Space(11) Case ID(20) ^ = Space Copyright 2014 LexisNexis. All rights reserved. 5

6 Packet Header Information is 11 record bytes. Packet Header Information Explanation for Keys on the Packet Header Information 50 1 N Product Line (must be a 4). Product Code 4 identifies that this is a MVR order 51 1 A/N Group Code (must be a space) reserved for future use 52 3 A/N Process Code (must be spaces) reserved for future use 55 2 N Packet Number blank/space. Reserved for future use (value 98 is acceptable to support legacy systems) 57 4 N Filler reserved for future use Example for Packet Header Information Product Line(1) 4 ] ^ ] ^^^] 98] ^^^^] Packet Number(2) ^ = Space Copyright 2014 LexisNexis. All rights reserved. 6

7 General Header Information This section is 23 bytes which consists of Account Number, Account Suffix, Special Billing ID, etc. Explanation for Keys on the General Header Information 61 1 A/N The Activity File Bit is primarily used to override the account setup for the number of months considered in the activity file search. Use of the activity file varies by the state. The following codes are used to specify the activity file search period, but not all are available in each state. For California, this bit is required because there is no account option setup for California. A - bypass Activity File Search B or 9-1 month search C or 1-6 month search D or 2-12 month search E or 3-36 month search F or 4-60 month search 62 1 A Use an "M" for MVR orders 63 1 A Force DMV Order (Y=Yes, N=NO) will force the order to go the state DMV A Filler (space) reserved for future use 65 6 N Account # (right justified, zero filled) 71 3 A Account Suffix (space fill) will be 3 alpha numeric characters. If there is no suffix then this field will be filled with spaces A/N Special Billing ID contains any alpha/numeric string which can be quoted back on your billing invoice. Copyright 2014 LexisNexis. All rights reserved. 7

8 79 1 MVR Type option is only applicable to the following state DMVs. The system will not allow MVRs ordered for Employment purposes. Arkansas ( or or 5) 0 = Regular MVR 5 = Commercial MVR Georgia (3 or blank) 3 or blank = Insurance Oregon (C, D or blank) C = Court D = Driver Blank = Driver Pennsylvania (R or blank) R = regular 3 year insurance Blank = Regular Virginia (I) I = Insurance Washington (C, N or blank) C = Commercial N or blank = non commercial New Hampshire (I) I = Insurance 80 1 A/N Amplified MVR bit for the states of Florida and Georgia. If a 7 year record is needed (amplified MVR), use a 1 or Y. For 3 year record, use 0 or N 81 1 A/N Soundexing used to identify the Soundexing bit for the states of Illinois, Maryland, New Hampshire and Florida (Batch only). If desired, use 1 or Y. If not desired use 0 or blank 82 2 A U.S State Postal Code * must contain the alpha state postal code designating the state from which the driver's license was issued. Example for Packet Header Information Renewal*(1) Force DMV(1) Account Suffix(3) MVR Type*(1) Soundexing*(1) 1 ] M ] Y ] ^] ] ABC] 12345] C] N] Y] GA] MVR Only Code(1) Account # (6) Special Billing Id(5) Amplified*(1) State Code*(1) * = State Specific ^ = Space Copyright 2014 LexisNexis. All rights reserved. 8

9 Order Data Information This section is 141 bytes which consists of MVR Applicant details such as Last Name, First Name, Middle Name, etc. Explanation for Keys on the Order Data Information 84 4 Underwriter/User Id: Optional field to identify the user A/N Drivers License Number A Last Name - Last name is a required field A First Name - First name is a required field A Middle Name A Suffix N Date of Birth mmddyy A Gender Code (M/F) N SSN A/N Quoteback is a user defined field for information that would assist in matching the MVR report to the proper application. This is an optional field. The value entered / auto generated in the Case ID field is automatically populated. User will have the ability to override this field CR/LF Example for Order Data Information Underwriter ID(4) DLN*(21) FName(20) Suffix(3) Gender(1) Quoteback(40) JTUW ] ] LName ] FName] MName ] Sr ] MMDDYY] M ] ] Quoteback ] CR/LF] LName (20) MName (15) DOB(6) SSN(9) CR/LF(2) * = State Specific ^ = Space Copyright 2014 LexisNexis. All rights reserved. 9