ums batch manual - mass.gov manual.pdf · 3. work with patricia bennett to send in some test data...

Registry of Motor Vehicles

UMS

Batch Manual November 2008

Doc. # T21495-0912

TABLE OF CONTENTS

SECTION 1 USER INFORMATION

CHAPTER 1 INTRODUCTION TO UMS BATCH PROCESSING

SCOPE OF MANUAL .................................................................................................................. 1-1 BATCH TRANSACTION PROCESSING ........................................................................................ 1-2 INSURANCE COMPANY BATCH PROCEDURES VIA A DATA TRANSFER METHOD ................... 1-3 UMS PROCESSING REQUEST FORM ........................................................................................ 1-4 RESPONSE RECORDS ................................................................................................................ 1-4 EDIT CATEGORIES.................................................................................................................... 1-5

POLICY INFORMATION ..................................................................................................... 1-5 POLICYHOLDER INFORMATION........................................................................................ 1-5 VEHICLE/REGISTRATION INFORMATION......................................................................... 1-6 VEHICLE OWNER INFORMATION ..................................................................................... 1-6 CANCEL & REINSTATEMENT DETAIL.............................................................................. 1-7 BIND VERIFICATION DETAIL............................................................................................ 1-7

CHAPTER 2 NEW BUSINESS TRANSACTION

NEW BUSINESS TRANSACTION ( TRANSACTION TYPE 1 ) ....................................................... 2-1 INPUT ....................................................................................................................................... 2-1 EDITS ....................................................................................................................................... 2-2 POLICY INFORMATION ............................................................................................................. 2-2 POLICYHOLDER INFORMATION ............................................................................................... 2-3

MASSACHUSETTS LICENSE NUMBER ........................................................................... 2-3 OUT-OF-STATE LICENSE NUMBER.............................................................................. 2-3 NO LICENSE NUMBER .................................................................................................. 3-3 POLICYHOLDER SURNAME AND DATE OF BIRTH ........................................................ 2-3 NOWN POLICYHOLDERS ............................................................................................ 2-4 VIN EDIT...................................................................................................................... 2-4 REGISTRATION/OWNER EDIT ...................................................................................... 2-4 REGISTRATION EDIT .................................................................................................... 2-4

VEHICLE OWNER INFORMATION............................................................................................. 2-5 INDIVIDUAL VEHICLE OWNERS ................................................................................... 2-5 NOWN VEHICLE OWNERS.......................................................................................... 2-5

OUTPUT..................................................................................................................................... 2-5 TIMING ISSUES.......................................................................................................................... 2-6

EXAMPLE 1 ................................................................................................................... 2-6 EXAMPLE 2 ( FOR A LARGE NUMBER OF RECORDS )................................................. 2-6

iii

CHAPTER 3 BIND VERIFICATION TRANSACTION

BIND VERIFICATION TRANSACTION ( TRANSACTION TYPE 2 ) .............................................. 3-1 INPUT ....................................................................................................................................... 3-1 EDITS ....................................................................................................................................... 3-2

POLICY INFORMATION ................................................................................................. 3-2 POLICYHOLDER INFORMATION ................................................................................... 3-2 BIND VERIFICATION DETAIL........................................................................................ 3-2


EXAMPLE ...................................................................................................................... 3-3

CHAPTER 4 POLICY RENEWAL TRANSACTION

POLICY RENEWAL TRANSACTION ( TRANSACTION TYPE 3 ) ................................................. 4-1 INPUT ....................................................................................................................................... 4-1 EDITS ....................................................................................................................................... 4-2 OUTPUT..................................................................................................................................... 4-2 TIMING ISSUES.......................................................................................................................... 4-2

EXAMPLE 1 ................................................................................................................... 4-2 EXAMPLE 2 ( FOR A LARGE NUMBER OF RECORDS )................................................. 4-3

CHAPTER 5 POLICY AMEND TRANSACTION

POLICY AMEND TRANSACTION ( TRANSACTION TYPE 4 )...................................................... 5-1 VEHICLE-RELATED AMEND TRANSACTIONS .......................................................................... 5-2 EDITS ....................................................................................................................................... 5-2

POLICY INFORMATION ................................................................................................. 5-3 POLICYHOLDER INFORMATION ................................................................................... 5-3 VEHICLE/REGISTRATION INFORMATION ( ADD/DELETE/AMEND ) ........................... 5-3 VEHICLE OWNER INFORMATION................................................................................. 5-3

POLICYHOLDER RELATED AMEND TRANSACTIONS ............................................................... 5-3 EDITS ....................................................................................................................................... 5-4

POLICY INFORMATION ................................................................................................. 5-4 POLICYHOLDER INFORMATION ................................................................................... 5-4

POLICY AMEND TRANSACTION DETAIL .................................................................................. 5-4 OUTPUT..................................................................................................................................... 5-4 TIMING ISSUES.......................................................................................................................... 5-5

EXAMPLES .................................................................................................................... 5-5 VEHICLE-RELATED AMEND TRANSACTIONS .............................................................. 5-5 NON-VEHICLE-RELATED AMEND TRANSACTIONS ..................................................... 5-5

iv

CHAPTER 6 POLICY CANCELLATION TRANSACTION

POLICY CANCELLATION TRANSACTION ( TRANSACTION TYPE 5 )........................................ 6-1 INPUT ....................................................................................................................................... 6-1 EDITS ....................................................................................................................................... 6-2

POLICY INFORMATION ................................................................................................. 6-2 POLICYHOLDER INFORMATION ................................................................................... 6-2 CANCELLATION/REINSTATEMENT DETAIL INFORMATION ........................................ 6-2


ACTIVE AND EXPIRED POLICIES.................................................................................. 6-3 ACTIVE EXAMPLES........................................................................................... 6-3 EXPIRED EXAMPLES......................................................................................... 6-4

ADVANCE POLICIES.................................................................................................................. 6-4 EXAMPLES ........................................................................................................ 6-4

CHAPTER 7 POLICY REINSTATEMENT TRANSACTION

POLICY REINSTATEMENT TRANSACTION ( TRANSACTION TYPE 6 ) ..................................... 7-1 INPUT ....................................................................................................................................... 7-1 EDITS ....................................................................................................................................... 7-2

POLICY INFORMATION ................................................................................................. 7-2 POLICYHOLDER INFORMATION ................................................................................... 7-2 CANCELLATION/REINSTATEMENT DETAIL INFORMATION ........................................ 7-2

OUTPUT..................................................................................................................................... 7-3 EXAMPLE ...................................................................................................................... 7-3

CHAPTER 8 POLICY CLEAR & AMEND UNPAID PREMIUM TRANSACTION

POLICY CLEAR & AMEND UNPAID PREMIUM TRANSACTION ( TRANSACTION TYPE 7 ) ..... 8-1 INPUT ....................................................................................................................................... 8-1 EDITS ....................................................................................................................................... 8-2

POLICY INFORMATION ................................................................................................. 8-2 POLICYHOLDER INFORMATION ................................................................................... 8-2 CLEAR AND AMEND UNPAID PREMIUM ....................................................................... 8-2


EXAMPLE ...................................................................................................................... 8-3

CHAPTER 9 POLICY INQUIRY TRANSACTION

POLICY INQUIRY TRANSACTION ( TRANSACTION TYPE 8 ) ................................................... 9-1 INPUT ....................................................................................................................................... 9-1 EDITS ....................................................................................................................................... 9-2

POLICY INFORMATION ................................................................................................. 9-2 OUTPUT..................................................................................................................................... 9-2 TIMING ISSUES.......................................................................................................................... 9-2

EXAMPLE ...................................................................................................................... 9-2 v

CHAPTER 10 RECORD DESCRIPTIONS

UMS TRANSACTION INPUT RECORD DESCRIPTIONS ........................................................... 10-1 POLICY INFORMATION ............................................................................................... 10-3 POLICYHOLDER INFORMATION ................................................................................. 10-3 VEHICLE/REGISTRATION INFORMATION .................................................................. 10-4 VEHICLE OWNER INFORMATION............................................................................... 10-5 CANCELLATION/REINSTATEMENT DETAIL ............................................................... 10-5 BIND VERIFICATION DETAIL ..................................................................................... 10-6 AMEND POLICY INFORMATION DETAIL .................................................................... 10-6

UMS TRANSACTION INPUT RECORD DEFINITIONS ............................................................. 10-7 RECORD HEADER ....................................................................................................... 10-7 POLICY INFORMATION ............................................................................................... 10-8 POLICYHOLDER INFORMATION ................................................................................. 10-9 VEHICLE/REGISTRATION INFORMATION ................................................................ 10-10 VEHICLE OWNER INFORMATION............................................................................. 10-11 CANCELLATION REINSTATEMENT DETAIL ............................................................. 10-12 BIND VERIFICATION DETAIL ................................................................................... 10-12 AMEND POLICY INFORMATION DETAIL .................................................................. 10-12

UMS TRANSACTION RESPONSE RECORD DESCRIPTIONS .................................................. 10-13 POLICYHOLDER INFORMATION ............................................................................... 10-13 VEHICLE/REGISTRATION INFORMATION ................................................................ 10-14 VEHICLE OWNER INFORMATION............................................................................. 10-15

UMS TRANSACTION RESPONSE RECORD DEFINITIONS ..................................................... 10-16 POLICY INFORMATION ............................................................................................. 10-16 POLICYHOLDER INFORMATION ............................................................................... 10-17 VEHICLE/REGISTRATION INFORMATION ................................................................ 10-18 VEHICLE OWNER INFORMATION............................................................................. 10-19

CHAPTER 11 Batch Related FAQ’s (Frequently Asked Questions)

SCOPE ..................................................................................................................................... 11-1 FAQ’S ..................................................................................................................................... 11-2

vi

SECTION 2 REFERENCE INFORMATION

APPENDIX A PROCESSING REQUEST FORM

SAMPLE OF FORM ................................................................................................................... A-2

APPENDIX B COBOL TRANSACTION RECORD LAYOUTS

UMS COBOL TRANSACTION INPUT RECORD..........................................................................B-2 UMS COBOL TRANSACTION RESPONSE RECORD...................................................................B-8

APPENDIX C INPUT RECORD EDITS

NEW BUSINESS AND POLICY RENEWAL TRANSACTIONS (CODES 1 AND 3) .......................... C-2 BIND VERIFICATION TRANSACTION (CODE 2) ....................................................................... C-4 POLICY AMEND TRANSACTION (CODE 4)............................................................................... C-5 POLICY CANCELLATION TRANSACTION (CODE 5)................................................................. C-7 POLICY REINSTATEMENT TRANSACTION (CODE 6)............................................................... C-8 CLEAR AND AMEND UNPAID PREMIUM TRANSACTION (CODE 7) ......................................... C-9 POLICY INQUIRY TRANSACTION........................................................................................... C-10

APPENDIX D ERROR CODES

TABLE OF UMS BATCH ERROR CODES ................................................................................D-2

APPENDIX E UMS RESPONSE RECORD & UMS INSURANCE COMPANY SUMMARY REPORT

EXAMPLE OF UMS RESPONSE RECORD .................................................................................E-2 UMS RESPONSE RECORD FIELD DESCRIPTION......................................................................E-3

INFORMATION FROM INPUT RECORD..........................................................................E-3 INFORMATION FROM RMV RESPONSE RECORD........................................................E-4

UMS INSURANCE COMPANY SUMMARY REPORT...................................................................E-5

vii

APPENDIX F UMS BATCH DATE CODES

NEW BUSINESS TRANSACTION: TRANSACTION CODE 1 ........................................................F-2 BIND VERIFICATION TRANSACTION: TRANSACTION CODE 2.................................................F-2 POLICY RENEWAL TRANSACTION: TRANSACTION CODE 3 ...................................................F-3 POLICY AMEND TRANSACTION: TRANSACTION CODE 4 .......................................................F-3

ADDING OR DELETING A VEHICLE ..............................................................................F-3 POLICY CANCELLATION TRANSACTION: TRANSACTION CODE 5 ..........................................F-4 POLICY REINSTATEMENT TRANSACTION: TRANSACTION CODE 6 ........................................F-5 CLEAR AND AMEND UNPAID PREMIUMS TRANSACTION: TRANSACTION CODE 7.................F-5 POLICY INQUIRY TRANSACTION..............................................................................................F-5

APPENDIX G U. S. STATE, CANADIAN PROVINCE & MEXICAN COUNTY CODES

U. S. STATE CODES ................................................................................................................. G-2 CANADIAN PROVINCE CODES ................................................................................................. G-2 MEXICAN COUNTIES................................................................................................................ G-3

APPENDIX H REGISTRATION DATA FILE RECORD LAYOUT

REGISTRATION DATA FILE RECORD LAYOUT .......................................................................H-1

APPENDIX I REGISTRATION FILE SUBMITTAL FORM

SAMPLE REGISTRATION FILE FOR INSURANCE COMPANY......................................................I-2

viii

Section 1

User Information

1 Registry of Motor Vehicles – UMS Batch Manual

Introduction to UMS Batch Processing

Scope of Manual

The UMS Batch Manual describes the batch processing of policy and vehicle information to the Uninsured Motorist System (UMS). This manual is intended for use by anyone who performs batch processing for UMS at any automobile insurance carrier or Service Bureau doing business in the Commonwealth of Massachusetts. Timely reporting of new and changed insurance information to the Registry of Motor Vehicles (RMV) is critical to the registration revocation process for uninsured private passenger and commercial vehicles. The Uninsured Motorist System (UMS) maintains a database of insurance policy information received from system subscribers. The chapters in this manual describe the eight possible UMS transactions and their corresponding edits. The individual edits are grouped into separate general categories. These categories and their related edits are listed at the end of this chapter.

Chapter One – Introduction and Overview 1-1

Registry of Motor Vehicles – UMS Batch Manual

Batch Transaction Processing The UMS batch system processes transactions nightly which ensures a timely response. UMS accepts batch transactions from insurance companies or service bureaus in one media, which is file data transfer. The batch system processes eight types of transactions. The corresponding transaction number (in the following list) precedes each transaction type: Transaction Number Transaction Type 1. New Business 2. Bind Verification 3. Policy Renewal 4. Amend Policy 5. Policy Cancellation 6. Policy Reinstatement 7. Clear and Amend Unpaid Premiums 8. Policy Inquiry UMS allows you to submit multiple transaction types as a data set on a single medium. For example, you can include New Business, Policy Cancellation and Policy Reinstatement transactions in the same file data transfer. Data sets that contain a mixture of transaction types must be sent to the Registry sorted in the following order:

1. Submitting Insurance Company 2. Insurance Company Code 3. Policy Number 4. Policy Type 5. Policy Effective Month, Day, and Year

Input transactions are limited to 15,000 per submission. These restrictions are necessary to provide scheduling flexibility during the narrow overnight batch processing window.



Insurance Company Batch Procedures via a File Data Transfer Method Sending in Batch records via a Data Transfer method: All insurance companies need to send in their policy records to the RMV database via a Batch Data Transfer method. In order to do this, complete the following steps:

1. Contact Advantis (877) 326-6426 and have a mailbox account set up with Expedite software. All costs associated with this mailbox account is the responsibility of the insurance company.

2. Once the Advantis mailbox account is set up, email Patricia Bennett at

[email protected] with your account number, user ID, and three digit insurance code.

3. Work with Patricia Bennett to send in some TEST data into our TEST region to be

sure that your record layout of the policy record is correct.

4. Once approved for production, contact Ellen Armata @ (617) 660-4548 or email [email protected] to discuss sending a TEST Processing Request Form (Control Sheet) via email to the [email protected] email group address with the company contact information.

All other UMS questions need to be addressed to the UMS department at 857-368-9770. .



UMS Processing Request Form The Production Control Department requires that you supply a UMS Processing Request Form with each data file you submit via email. In addition, you must supply a UMS Processing Request Form for each insurer on the data file. Refer to Appendix A, "Processing Request Form", for the UMS Control Log format.

Response Records For each UMS transaction the Registry receives, one or more corresponding response records are returned to the submitting insurance company. Records are returned to the insurance company using the medium by which they submitted the original transactions to UMS via file data transfer. Each response record contains UMS validation and error information appended to a copy of the original submission. UMS also provides relevant policyholder, vehicle, and registration information as maintained at the Registry. You should use this information to correct and synchronize your database with that of the Registry. For an example of a response record, refer to Appendix E. For detailed UMS record descriptions and definitions, refer to Chapter 10.UMS Insurance Company Summary Report



Edit Categories

Note: Italic and reverse typeface denotes required elements that identify an insurance policy on the UMS System. Policy Information 02 Insurance Company CodePolicy Number 03 Policy Number 04 Policy Binder Reference Number 05 Policy Binder First Digit 06 Policy Binder Subsequent Digits 07 Policy Binder Surrogate 08 Policy Binder Insurance Company 09 Policy Binder Date 10 Policy Type 11 Policy Effective Date 12 Policy Expiration Date 13 Number of Transactions Submitted 14 Transaction Type 15 Transaction Effective Date Policyholder Information 16 Policyholder License Number 17 NOWN Policyholder FID Number 18 NOWN Policyholder Zip Code 19 Policyholder License State 20 Policyholder Surname 21 Policyholder First Name 22 Policyholder Date of Birth 23 Policyholder NOWN Name



Vehicle/Registration Information 27 Vehicle Action Code 28 Vehicle Identification Number 29 Vehicle Year 30 Vehicle Make 31 Vehicle Premium Town 32 Registration Plate Type 33 Registration Number 34 Registration Plate Color 35 Vehicle Owner Type Vehicle Owner Information 36 Vehicle Owner License Number (pers) 37 Vehicle Owner License State (pers) 38 Vehicle Owner Surname (pers) 39 Vehicle Owner First Name (pers) 40 Vehicle Owner Date of Birth (pers) 41 Vehicle Owner NOWN FID (corp) 42 Vehicle Owner NOWN Zip (corp) 43 Vehicle Owner NOWN Name (corp)


Registry of Motor Vehicles – UMS Batch Manual Cancel/Reinstatement Detail 46 Cancellation/Reinstatement Reason Code 47 Unpaid Dollar Amount Bind Verification Detail 49 Binder Reference Number



New Business Transaction

Transaction Type 1

Use the New Business transaction to add new policy records to the UMS database.

A New Business transaction is sent to the Registry of Motor Vehicles for policy information that has not previously been reported to UMS. Note: (1). If a registration status is ACTV/PINS or ACTV/INSC, a New Business transaction

stops the revocation process. (2). If a registration status is REVO/INSC, a New Business transaction reinstates the plate to active or expired as long as the policy effective date is prior or equal to the effective date of revocation.

Input

A New Business transaction may contain one or more New Business records. One New Business record must be submitted for each vehicle insured by a unique policy. Refer to Chapter 10, “UMS Record Descriptions,” for the record layout format.

Chapter Two –New Business Transaction 2-1


Edits

A New Business transaction is applied if all New Business records for a unique policy pass the required edits. The acceptance of a New Business transaction therefore relies on an all or nothing matching algorithm.* The editing criteria for each New Business record requires the record to pass edits from the following categories:

Policy Information The submitting and carrying insurance company codes are checked for validity. UMS policy identification consists of the following:

• Insurer’s insurance company code • Unique and previously unknown policy number

Policy type (P=private passenger, C=commercial) • Policy effective date

The policy identification must be previously undefined to the RMV database. UMS rejects the transaction if the policy identification already exists on the database.

The transaction effective date must be identical to the policy effective date. The policy expiration date must be within two years of the policy effective date.

The insurance company must submit one transaction for each vehicle insured on a given policy. For this reason, the Number of Transactions Submitted field in the header portion of the record must contain the number of New Business transactions UMS can expect to receive for a unique policy. When multiple records are submitted for a given policy, all information in the header portion of each record must be identical in order for the record to be accepted.

* An exception will occur when the transaction has over 200 records and one or more, but not all, of the records fail the edits. This will result in the creation of the policy with only some of the vehicles. The response records will identify which records were accepted or rejected. Rejected records may only be resubmitted as Add Vehicle transactions.



Policyholder Information

UMS must receive information from one of the following sources to complete policyholder edits: • Massachusetts license information • Out of state license information • Code designation for policyholders that do not hold a license • NOWN (a non-individual owner, e.g. a company) information

Massachusetts License Number

When the policyholder’s license state is MA, UMS compares the submitted license number to the license information on our license file. The transaction is rejected if there is no matching record for an RMV licensed driver.

Out-of-State License Number

When the policyholder’s license state is a valid state code other than MA, the license number is compared to out-of-state license information residing on ALARS. Out-of-state license information unknown to ALARS is recorded through the use of a unique 9-character number (an alphanumeric character followed by eight digits). This process enables UMS to accept and record policyholder information for licensed drivers not yet known to ALARS.

No License Number

Unlicensed policyholders are reported to UMS by entering NOLICENSE in the license number field, and XX as the License State. (This alternative should only be employed for truly unlicensed drivers.) In these cases, the RMV will not record any unique policyholder information and will not allow the recording of unpaid premium.



Policyholder Surname and Date of Birth

For policyholders licensed in Massachusetts, the surname and date of birth recorded on our license file are compared to that supplied by the insurance companies in the New Business transaction. The current MRB operator edits are used to allow flexibility and continuity between systems.

At least three of the first five characters must match the last name associated with the license number on ALARS, and at least two of the three component data elements comprising the date of birth (MM/DD/YYYY) are required for acceptance. UMS returns the appropriate error message indicating the field in error for records which fail the policyholder edits (that is, 1302, POLICYHOLDER SURNAME DOES NOT MATCH).

Transactions that pass the UMS policyholder edits return relevant license information maintained on the RMV database. This data proves useful for policyholders that pass the required edits, but do not match the RMV’s information exactly.

NOWN Policyholders

For NOWN policyholders (non-individual owners, e.g. a company) the FID number (Federal Identification number), the company/NOWN name, and zip code must be entered. A "ZZ" must be entered in the License State field.

Vehicle/Registration Information

Each New Business or Policy Renewal transaction record requires a unique vehicle identification number (VIN). The VIN must already exist on the RMV database.

VIN Edit

The VIN supplied is verified against the information on the RMV registration file. UMS requires that all vehicles reported on a New Business, Renewal, or Vehicle Amend Policy transaction must be previously known to the ALARS system. If the VIN does not exist on ALARS, the transaction is rejected. However, UMS uses a check digit algorithm to perform VIN editing for post 1980 vehicles that are not on ALARS. A specific error code will be returned for vehicles reported with an invalid VIN (2101). If UMS finds more than one occurrence of that VIN on ALARS, it uses the vehicle make and year supplied on the transaction to identify the correct vehicle/registration record.

Registration/Owner Edit

Once a VIN is determined to be valid, UMS compares the plate type and registration and/or the vehicle owner information stored on ALARS to the information supplied by the insurance company. UMS requires that either the supplied registration or vehicle owner information matches the information recorded on ALARS for the vehicle.



Registration Edit

UMS checks the plate type and registration number supplied by the insurance company and compares it to the current plate type and registration recorded on ALARS for that vehicle. If the plate type and registration number match, the record is accepted. When the plate type and registration number do not match, the vehicle owner information is verified against the information residing on the UMS system.

Vehicle Owner Information

The vehicle owner information is only edited if the vehicle registration information is missing or invalid.

The supplied vehicle owner type (individual or non-individual) is examined and the appropriate vehicle owner edits are applied.

Individual Vehicle Owners

The vehicle owner's license number supplied is compared to the vehicle owner license number stored on the registration record. A match on license number results in the acceptance of the record. Mismatches on license number initiate the owner surname and date of birth edits. These edits are identical to those used for verifying policyholder information. The surname and date of birth supplied are compared to the information stored for all owners recorded on ALARS. Matches result in acceptance of the record.

NOWN Vehicle Owners

Transactions received with a non-individual owner type are edited in the following manner:

The vehicle owner supplied and vehicle owner recorded on ALARS are left justified. Special characters, duplicate spaces, and numbers are removed. The first eight characters of the owner name supplied are compared to the first eight characters of the corporation name recorded on ALARS. A match on at least five of the first eight characters results in the acceptance of the new business record. Mismatches result in the rejection of the record. In addition, the vehicle owner FID and zip code must be supplied and verified against current system information. Refer to Appendix C for information relating to input record edits.

Output

For each New Business record received, there is one corresponding response record sent to the submitting insurance company. Each response record contains a mirror image of the New Business record submitted by the insurance company appended to UMS validation (information as contained on the Registry's system) and error information.

Refer to Appendix E for a sample response record format. Refer to Appendix D for a list of UMS error codes.



Timing Issues

New Business transactions must be submitted within twenty-three days from the policy effective date. Failure to comply with this UMS requirement may result in erroneous registration revocations (REVO/INSC). New Business transactions can also be submitted up to 90 days in advance.

Example 1

A New Business transaction for a policy insuring three vehicles would be reported to UMS in the following manner:

Three new business records are sent to the RMV no later than 23 days from the policy effective date. Each New Business record contains identical header information and unique vehicle information. When UMS accepts two New Business records and rejects one, the entire transaction is rejected and all three records must be resubmitted as soon as possible to avoid any erroneous registration revocation activity.

Example 2 (For Large Number of Records)

A New Business transaction for insuring 550 vehicles would be reported in the following manner:

Five hundred and fifty New Business records are sent to the RMV no later than 23 days from the policy effective date. Each New Business record contains identical header information and unique vehicle information.

The records are processed 200 at a time. If the first 200 records pass the edits, then the policy is created and the 200 vehicles are added to it. If one of the second hundred records fails to pass the edits, then the second set of the 200 records are rejected. If the last 150 records pass the edits, they are also added to the policy.

Two hundred rejected records should be resubmitted as Add Vehicle transactions as soon as possible to avoid any erroneous registration revocation activity.



Bind Verification Transaction

Transaction Type 2

When an agent/producer binds a new insurance policy and updates the UMS database via an on-line bind transaction, the system generates a binder transaction reference number for the policy. The Bind Verification transaction replaces the binder transaction number with the actual policy number.

For a list of edit categories associated with this transaction, refer to Edit Categories in Chapter 1.

Input

The insurance company submits one Bind Verification record per policy. The record is comprised of the UMS record header and the bind verification detail. The Bind Verification record includes complete policy information comprised of the header and the RMV bind transaction number. The bind transaction number must include a pound sign (#).

Chapter Three –Bind Verification Transaction 3-1


Edits

UMS receives a Bind Verification transaction and edits the record for validity. The editing criteria for each transaction requires the record to pass edits from the category:

" Policy Information

" Policyholder Information

" Bind Verification Detail

Policy Information

The insurance company code, policy type, bind verification transaction reference number, and policy effective date are compared to information resident on the UMS database. A match is required for the verification record to be accepted. The related policy record on the UMS database must exist in a “bind” status.


Refer to Chapter 2, "New Business Transaction", for complete Policyholder Information.

Bind Verification Detail

The bind transaction reference number is required and must match the number generated by UMS at the time of on-line binding.

The Bind Verification transaction acts as an amend to the policy number. The bind transaction number on UMS is replaced with the insurance company assigned policy number in the record header. When information in the bind verification header (such as policy expiration date and coverage code) is different than that stored on UMS at the time of the bind, the UMS database is updated with the information supplied on the Bind Verification transaction. Policy type, policy effective date, policyholder, and vehicle data cannot be changed with the Bind Verification transaction.

Refer to Appendix C for UMS detailed field edits.



Output

One response record is returned to the submitting insurance company for each vehicle on the policy. Each response record contains UMS validation and error information appended to a copy of the bind verification record submitted. UMS also provides relevant policyholder, vehicle, and registration information, as maintained at the RMV. This information may be used by the insurance company to correct and synchronize their database.

Refer to Appendix E for response record format. Refer to Appendix D for a list of UMS error codes.

Timing Issues

The Bind Verification transaction must be accepted at the Registry within ninety days of the effective date recorded at the time of on-line bind.

Example

An insurance agent binds a new insurance policy via the UMS on-line transaction “change of carrier” screen (UPIC). UMS generates a bind transaction reference number, which is returned to the insurance agent. A Bind Verification transaction is received at the Registry twenty days from the policy effective date recorded at the time of the bind. The insurance company code, policy type, bind verification transaction reference number, and policy effective date is compared to the UMS database. A match initiates the transaction and the policy number, supplied in the header portion of the record, replaces the previous bind number.

Note: Insurance agents can only gain access to the UMS system through their insurance company. The Registry of Motor Vehicles does not allow direct access to UMS screens for processing transactions.



Policy Renewal Transaction

Transaction Type 3

Insurance companies submit Policy Renewal transactions to UMS for those policies scheduled to expire within a short period from the current date. The policy number in a Policy Renewal transaction may be new or exist on the database; however, the policy effective date must be unique to UMS.

Note: Policy Renewal transactions will stop the revocation process ACTV/INSC or ACTV/PINS. It will also take plates out of revocation REVO/INSC as long as the effective date of the renewal is prior or equal to the revocation date of the registration.


Input

A Policy Renewal transaction may contain one or more records. A Renewal record is submitted for each vehicle insured by a unique policy. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Chapter Four – New Business Transaction 4-1


Edits

As is the case with New Business transactions, a Policy Renewal transaction is applied if all renewal records for a unique policy pass the required edits. The acceptance of a Policy Renewal transaction therefore relies on an all or nothing matching algorithm. *

All renewal records for a unique policy must pass edits from the following categories:



" Vehicle/Registration Information

" Vehicle Owner Information

Editing criteria for each Renewal record is identical to the New Business record edits. Refer to Chapter 2, “New Business Transaction,” for further details.


Output

For each Policy Renewal record received, there is one corresponding response record sent to the submitting insurance company. Each response record contains UMS validation and error information appended to a copy of the renewal record submitted. The response record contains all relevant policyholder, vehicle, and registration information, as maintained at the RMV. This information may be used by the insurance company to correct and synchronize their database.

Refer to Chapter 10, “UMS Record Descriptions,” for response record format. Refer to Appendix D for a list of UMS error codes.

• An exception will occur when the transaction has over 200 records and one or more, but not all, of the records fail the edits. This will result in the creation of the policy with only some of the vehicles. The response records will identify which records were accepted or rejected. Rejected records may only be resubmitted as Add Vehicle transactions.



Timing Issues

Renewal records are rejected if received earlier than ninety days prior to the policy effective date and must be submitted within 23 days from the policy effective date. Failure to comply with this UMS requirement may result in erroneous registration revocation (REVO/INSC).

Example 1

A Policy Renewal transaction for a policy insuring two vehicles would be reported to UMS in the following manner:

Two Policy Renewal records are sent to the RMV 30 days prior to the effective date. Each Renewal record contains identical header information and unique vehicle information. UMS policy, policyholder, and vehicle edits are performed. If two Renewal records are accepted (that is, pass all edits), UMS adds the new policy information to the database.

Example 2 (For Large Number of Records)

A Renewal transaction for insuring 550 vehicles would be reported in the following manner:

Five hundred and fifty Renewal records are sent to the RMV no later than 23 days from the policy effective date. Each Renewal record contains identical header information and unique vehicle information.

The records are processed 200 at a time. If the first 200 records pass the edits, then the policy is created and the 200 vehicles are added to it. If one of the second hundred records fails to pass the edits, then the second set of the 200 records are rejected. If the last 150 records pass the edits, they are also added to the policy.

Two hundred rejected records should be resubmitted as Add Vehicle transactions as soon as possible to avoid any erroneous registration revocation activity.



Policy Amend Transaction

Transaction Type 4

The Policy Amend transaction changes information on an insurance policy that has been previously established on the UMS policy database. Changes made to a policy that are required to be reported to the RMV include vehicle additions, vehicle deletions, and changes of policyholder.

The Policy Amend transaction does not allow changes to:

" policy number " insurance company code " policy effective date " policy expiration date " policy type " cancellation reason " unpaid premium amount.

Previously recorded unpaid premium amounts may only be cleared via the Clear and Amend Unpaid Premiums transaction (transaction type 7).

Amend transactions can be either vehicle related or policyholder related.


Chapter Five – Policy Amend Transaction 5-1


Vehicle-Related Amend Transactions

Each amend record is treated as a separate transaction. One amend record is submitted for each vehicle to be amended, added, or removed. The amend record consists of the UMS record header and UMS vehicle detail. Refer to Chapter 10, “UMS Record Descriptions,” for record format. If more than one amend record is submitted for the same policy (that is, removing some vehicles and adding other vehicles), and one record fails the edits, the other records will be accepted.

Edits

The Number of Transactions Submitted field on a Policy Amend record shows the total Amend records sent to UMS for a unique policy. Such an example is a policy that previously covered two vehicles has a new vehicle added and one vehicle deleted. The insurance company submits two Amend records. The Number of Transactions Submitted field in the header portion of that record contains 02, which indicates that UMS can expect two Amend records for that policy. When multiple Amend records are submitted for a policy, the policy portion (header) of each record must match exactly.

The vehicle action code indicates the type of amendment: The following list shows vehicle action codes and their meanings.

Code Meaning

0 A change to header information (policyholder amend)

1 A vehicle addition

2 A vehicle removal

3 A change to the vehicle premium town

Each amend record is validated under the following sets of edit criteria:



" Vehicle/Registration Information

" Vehicle Owner Information



Policy Information

The policy identification submitted must exactly match a valid policy record on the UMS database.


Refer to Chapter 2, "New Business Transaction", for details on policyholder information edits.

Vehicle/Registration Information (Add/Delete/Amend)

The vehicle delete, add, and change of premium town Amend transactions require vehicle information to be submitted and match the vehicle information recorded on the UMS policy database.

The vehicle-related Policy Amend transaction uses the same vehicle information edits as the New Business and Policy Renewal transactions.

Refer to Appendix C for UMS field edits.


Refer to Chapter 2, "New Business Transaction", for details on vehicle owner edits.

Policyholder Related Amend Transactions

For Policy Amend transactions that update policy information only (that is, policyholder amend), the insurance company submits one Amend record, consisting of the UMS record header and the UMS Policy Amend information detail. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Edits UMS compares policy information resident on the UMS database to that submitted on the Amend record. UMS compares policy identification (which consists of insurance company code, policy number, policy type, and effective date). A match is required for UMS to accept the transaction. Policyholder information is also verified.

UMS validates each Amend record using the following sets of edit criteria:



" Policy Amend Transaction Detail (filler)



Policy Information

The policy identification submitted must match a valid policy record on the UMS database exactly.


Refer to Chapter 2, "New Business Transaction", for details on policyholder information.

Policy Amend Transaction Detail For non-vehicle related Policy Amends, the Policy Amend detail must contain spaces.

Output

For each Amend record received, UMS sends a corresponding response record to the submitting insurance company. Each response record contains UMS validation and error information appended to a copy of the Amend record submitted. UMS also provides relevant policyholder, vehicle, and registration information as maintained at the RMV. The insurance company may use this information to correct and synchronize their database.

Refer to Chapter 10, “UMS Record Descriptions,” for the UMS response record format. Refer to Appendix D for a list of UMS error codes.

Timing Issues UMS accepts Policy Amend transactions for policies previously reported through New Business or Policy Renewal activity. UMS also accepts Policy Amend transactions for policies residing on UMS that are not yet effective (that is, a renewal done in advance of the policy effective date).

Policy Amend transactions are permitted for expired policies residing on UMS, if the policy is not in a cancelled status. For expired policies, the transaction effective date submitted must fall on or between the policy effective and expiration dates.

Vehicle additions must be reported to the RMV no later than 23 days from the effective date of coverage for that vehicle. Failure to comply with this UMS requirement results in erroneous registration revocation (REVO/INSC).



Examples:

Two Policy Amend transactions are submitted to UMS for an existing policy in an active status.

Vehicle-Related Amend Transactions

Vehicle Add: A vehicle action code of 1 signifies that the Policy Amend is a vehicle add activity. The Vehicle Add Amend transaction consists of the UMS record header and the vehicle detail for that record. The policy information in the header is compared to the header resident on the UMS database. The vehicle data submitted (in the detail portion of the record) is edited and compared to the vehicle data resident on ALARS. A match initiates the Add Vehicle Amend transaction, and UMS adds the vehicle and current registration information to the policy information on the database.

Non-Vehicle-Related Amend Transactions

The submitting insurance company changes the policyholder for a policy. The Policy Amend transaction consists of the UMS record header and a 0 in the vehicle action code field. The header contains the new policyholder license number, surname, and date of birth. This information is edited and compared to existing information on ALARS for validity. If the new policyholder submitted for the policy is determined to be valid, the current and future policy history records for the policy on UMS are associated with this new individual.



Policy Cancellation Transaction

Transaction Type 5

Use the Policy Cancellation transaction to inform the Uninsured Motorist System of insurance policy cancellations. This UMS transaction is considered the legal notification of policy cancellation and replaces paper forms formerly submitted to the RMV. A valid Policy Cancellation transaction initiates the registration revocation process for all “uninsured” vehicles/registrations on a cancelled policy.


Input

An insurance company sends one Policy Cancellation transaction per policy to be cancelled. Each Policy Cancellation transaction is comprised of one record containing the UMS record header and the cancellation information detail. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Chapter Six – Policy Cancellation Transaction 6-1


Edits

UMS receives the Policy Cancellation transaction and edits it for validity. Editing criteria for each Policy Cancellation transaction requires the record to contain the following information:

? Policy Information

? Policyholder Information

? Cancellation/Reinstatement Detail Information

Policy Information

UMS compares the policy information resident on the UMS database to that submitted on the cancellation record. The policy identification information includes the insurance company code, policy number, policy type, and effective date. A match is required for the transaction to be accepted.


Refer to Chapter 2, "New Business Transaction", for details on Policyholder Information.

Cancellation/Reinstatement Detail Information

UMS requires a valid cancellation reason code to cancel a policy. If the code dictates the recording of earned but unpaid premium, UMS records that information on the policyholder’s cancellation history record.

Note: The Unpaid Premium field should contain 0 if no earned but unpaid premium exists. If the field does not contain 0, the system rejects the cancellation.


Output

One response record is returned to the submitting insurance company for each vehicle insured. The response record contains error information appended to a copy of the cancellation record and all relevant policyholder, vehicle, and registration information as maintained at the RMV. The insurance company should use this information to verify that the correct vehicles and registrations associated with a cancelled policy have been identified.



Refer to Chapter 10, “UMS Record Descriptions,” for response record format. Refer to Appendix D for UMS error codes.

Timing Issues

UMS edits allow the acceptance of Policy Cancellation transactions both before and after the actual date of cancellation. You should remember, however, that Chapter 175, §113A of the Massachusetts General Laws indicates:

"… said cancellation shall not become effective unless the company or an insurance premium finance agency....has, immediately upon the intended effective date of the cancellation of the policy... forwarded to the Registrar of Motor Vehicles, a notice, in such form as he may prescribe, containing such information - to apprise the registrar of the particular motor vehicle registration which the insurance is intended to be cancelled."

Two examples are listed below.

Active and Expired Policies You can submit a cancellation against an active or expired policy at any time if the cancellation effective date is a valid date and within the policy period.

Active Examples

Policy Effective Date: 05/15/96 - 05/15/97

System Date: 06/01/96

Cancellation Date: 05/30/96

Cancellation: Accepted



Cancellation Date: 06/15/96 (expiration date of policy)




Cancellation Date: 06/16/96 (one day after expiration date of policy)

Cancellation: Rejected



Expired Examples







Cancellation Date: 01/02/96 (one day after expiration date of policy)


Advance Policies

You can send a cancellation in advance of the policy becoming active if the cancellation date is also the policy effective date.

Examples







Cancellation Date: 5/30/96 (policy effective date is one day later)




7 Policy Reinstatement Transaction

Transaction Type 6

The Policy Reinstatement transaction re-establishes insurance coverage for a previously cancelled insurance policy on the UMS database. A Policy Reinstatement transaction rescinds any pending registration revocations for vehicles considered uninsured due to a cancellation of the same policy. The UMS policy database is updated to reflect that the policy has a status of active/expired again, and the unpaid premium recorded for a policyholder (at the time of cancellation) is reversed on the system.

Note: If a registration status is ACTV/INSC or ACTV/PINS, a Policy Reinstatement transaction stops the revocation process. If a registration status is REVO/INSC, a Policy Reinstatement transaction reinstates the plate to active or expired.


Input

The insurance company submits one record for each policy to be reinstated. Each Policy Reinstatement transaction consists of a record containing the UMS record header and the reinstatement information detail. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Chapter Seven – Policy Re-instatement Transaction 7-1


Edits

UMS receives the Policy Reinstatement transaction and edits it for validity. The editing criteria for each Policy Reinstatement transaction requires the record to contain the following information:



" Cancellation/Reinstatement Detail Information

Policy Information

UMS compares policy information residing in UMS to the information submitted on the Reinstatement record. UMS compares the policy identification (insurance company code, policy number, policy type, and effective date) and requires a match in order to accept the transaction. The policy status on the UMS database must be cancelled, and the insurance company reinstating the policy must be the company that initiated the cancellation.

The transaction effective date must be identical to the cancellation effective date of the policy for the reinstatement to be accepted. The policy effective date and the policy expiration date must be the same as the policy dates originally recorded on the policy.


Refer to Chapter 2, "New Business Transaction", for details on Policyholder Information.

Cancellation/Reinstatement Detail Information

UMS requires a valid reinstatement reason code. A reinstatement reason code of 21 is considered a reversal of the original cancellation reason code. A reinstatement reason code of 22 is used to identify cancellations done in error.




Output One response record is returned to the submitting insurance company for each vehicle insured. The response record contains error information appended to a copy of the reinstatement record. In addition, all relevant policyholder, vehicle, and registration information, as maintained by the RMV is included. Refer to Chapter 10, “UMS Record Descriptions,” for response record format. Refer to Appendix D for a list of UMS error codes.

Example A reinstatement record is accepted by UMS ten days after the initial cancellation effective date for a unique policy. The registration status will be ACTV/PINS. Record editing is performed on the policy identification and reinstatement detail. Insurance coverage is determined to be continuous. The system matches the policy identification supplied with a previously cancelled policy for the same insurance company. The reinstatement reason code of 21 reverses the original cancellation reason code of 01 (nonpayment of premium) and the unpaid premium is reversed on the policyholder’s cancellation history record. All subsequent registration revocation processing for vehicles covered on the policy is discontinued.



Clear and Amend Unpaid

Premium Transaction

Transaction Type 7

The Clear and Amend Unpaid Premium transaction permits removal or the adjustment of unpaid premium amounts from a policyholder’s cancellation history record on UMS. For a list of edit categories associated with this transaction, refer to Edit Categories in Chapter 1.

Input

The insurance company submits one Clear Unpaid Premium record per transaction. The record is comprised of the UMS record header and the Cancellation/Reinstatement Detail. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Chapter Eight – Policy Re-instatement Transaction 8-1


Edits

UMS receives a Clear Unpaid Premium transaction and edits the record for validity. The editing criteria for each Clear transaction requires the record to contain the following information: " Policy Information " Policyholder Information " Cancellation/Reinstatement Detail Information

Policy Information

UMS compares the policy information resident on the RMV database to that submitted on the Clear Unpaid Premium record. UMS compares the policy identification (insurance company code, policy type, policy number, and effective date) and requires a match for the record to be accepted.


Refer to Chapter 2, "New Business Transaction", for details on policyholder information.

Clear and Amend Unpaid Premium

UMS edits the unpaid premium amount and compares it to the amount recorded at the time of policy cancellation. UMS allows clearing of unpaid premiums in partial payments when using reason code #43. The dollar amount submitted, if decreasing, should be the dollar amount still owed to the insurance company. UMS will show a reason code of EAMT on the UPTH screen, as well as the subtraction of dollar amounts paid. If a customer pays in full, put a 0 in the dollar amount field and use the reason code #41. The reason code will display paid on the UPTH screen as well as show the total dollar amount subtracted from the customer policy. The Clear Unpaid Premium record must contain a valid reason code. Note that the maximum dollar amount is $99,999.

Refer to Appendix C for UMS detailed field edits, and to Chapter 10 for acceptable transaction reason codes.

Output For each Clear or Amend Unpaid Premium record received, a corresponding response record is sent to the submitting insurance company for each vehicle insured. Each response record contains UMS validation and error information appended to a copy of the record submitted. Refer to Chapter 10, “UMS Record Descriptions,” for the UMS response record format. Refer to Appendix D for a list of UMS error codes.



Timing Issues

UMS must receive a Clear and Amend Unpaid Premium transaction within three years of the policy cancellation date.

Example

UMS receives a Clear and Amend Unpaid Premium transaction six months after the policy cancellation effective date. The customer owes the company $350 dollars and sends in $125 toward the unpaid dollar amount. The company sends UMS an Amend Premium transaction. It performs record editing on the policy identification and record detail. The system matches the policy identification supplied with a previously cancelled policy for the same insurance company and the company sends the RMV an unpaid dollar amount of $225 (money still owed to the company). The record is accepted and now shows a balance of $225 dollars owed to the company. The UPTH screen will show a minus $125(-).

Note: Clearing or adjusting an unpaid premium is NOT reinstating a policy. The policy remains cancelled and only the dollar amount is amended.



Policy Inquiry Transaction

Transaction Type 8

An insurance company submits a Policy Inquiry transaction to request RMV response information for a specific policy. The policy is identified by insurance company code, policy type, policy number, and policy effective date.


Input

The insurance company submits one Policy Inquiry transaction per policy. Refer to Chapter 10, “UMS Record Descriptions,” for record format.

Chapter Nine – Policy Inquiry Transaction 9-1


Edits

UMS receives a Policy Inquiry transaction and edits the record for validity. The editing criteria for each transaction requires the record to contain the following information:

Policy Information

Policy Information

UMS compares the insurance company code, policy type, policy number, and policy effective date to information residing on the UMS database. UMS requires a match to accept the Policy Inquiry record.

An 8 identifies Policy Inquiry transaction records in the Transaction Type field. The Policy Inquiry record includes only the insurance company code, policy number, policy type, and policy effective date; other fields are optional.


Output

A response record for each vehicle on the policy is sent to the submitting insurance company. Each response record contains UMS validation and error information appended to a copy of the Policy Inquiry record submitted. UMS also provides relevant policyholder, vehicle, and registration information, as maintained at the RMV. The insurance company can use this information to correct and synchronize their database.

Refer to Chapter 10, “UMS Record Descriptions,” for response record format. Refer to Appendix D for a list of UMS error codes.

Timing Issues

You can submit a Policy Inquiry record any time after the UMS policy record has been added to the database. UMS rejects an inquiry submitted more than one year after the policy expiration date.

Example

An insurance company submits a Policy Inquiry transaction to gain information regarding a particular company-owned policy that will be/is/was held by that same company. A record is sent to the Registry on the UMS transaction file. UMS performs policy identification edits and returns one response record per vehicle.

Chapter Nine – Policy Inquiry Transaction 9-2


10 UMS Record Descriptions

This chapter contains descriptions and definitions for the UMS Transaction Input Record and Response Record. The record description provides a translation of the COBOL version of the input and response records found in Appendix B. The record definition field numbers correspond with the record descriptions, which provide additional detail about element meaning.

UMS Transaction Input Record - Descriptions

Field # Name/Description Picture Position

01

Record Header (for all transactions)

TXIN-SUB-INCP-NUMB Submitting Insurance Company’s Code

X(003) 000-002

Chapter Ten – UMS Records 10-1


UMS Transaction Input Record - Descriptions (continued)

Policy Information


02 TXIN-INCP-NUMB Insurance Company Code

9(003) 003-005

03 TXIN-PLCY-CODE-ID Policy Number

X(016) 006-021

04 TXIN-PLCY-CODE-BIND Policy Binder Reference Number

X(016) 006-021

05 TXIN-PLCY-CODE-FIR-DIGIT Policy Binder First Digit

X(001) 006-006

06 TXIN-PLCY-CODE-NUMB-X Policy Binder Subsequent Digits

X(015) 007-021

07 TXIN-PLCY-CODE-BIND-SURR Policy Binder Surrogate

9(008) 007-014

08 TXIN-PLCY-CODE-BIND-INCP Policy Binder Insurance Company

9(003) 015-017

09 TXIN-PLCY-CODE-BIND-DATE-YDDD Policy Binder Date

9(004) 018-021

10 TXIN-PLCY-TYPE Policy Type

X(001) 022-022

11 TXIN- PLCY-DATE-EFFECTIVE Policy Effective Date

X(008) 023-030

12 TXIN-PLCY-DATE-EXPIRE Policy Expiration Date

X(008) 031-038

13 TXIN-NUMB-REC-SUBMITTED Number of Transactions Submitted

9(004) 039-042

14 TXIN-TXN-TYPE Transaction Type

X(001) 043-043

15 TXIN-DATE-EFFECTIVE Transaction Effective Date

X(008) 044-051






16 TXIN-PLCY-LICENSE-NUMB Policyholder License Number (pers)

X(025) 052-076

17 TXIN-PLCYHLDR-FID NOWN Policyholder FID Number (corp)

X(009) 052-060

18 TXIN-PLCY-FID-ZIP NOWN Policyholder Zip Code (corp)

X(009) 061-069

19 TXIN-PLCY-LICENSE-STATE Policyholder License State (pers)

X(002) 077-078

20 TXIN-PLCY-PERS-NAME-LAST Policyholder Surname (pers)

X(016) 079-094

21 TXIN-PLCY-PERS-NAME-FIRST Policyholder First Name (pers)

X(012) 095-106

22 TXIN-PLCY-PERS-DOB Policyholder Date of Birth (pers)

X(008) 107-114

23 TXIN-PLCY-NOWN-NAME Policyholder NOWN Name (corp)

X(036) 079-114

24 RESERVED-FOR-INCP For insurance company use

X(040) 115-154

25 FILLER For future use

X(014) 155-168

26 RESERVED-FOR-RMV For RMV use

X(001) 169-169






27 TXIN-TXN-VEHC-ACTION-CODE Vehicle Action Code

X(001) 170-170

28 TXIN-VIN Vehicle Identification Number

X(017) 171-187

29 TXIN-VMAK-NUMB-YEAR Vehicle Year

9(004) 188-191

30 TXIN-VMAK-NAME Vehicle Make

X(005) 192-196

31 TXIN-VEHR-TOWN-NUMB Vehicle Premium Town

9(003) 197-199

32 TXIN-VEHR-CODE-PLATE-TYPE Registration Plate Type

X(003) 200-202

33 TXIN-VEHR-CODE-REGISTRATION Registration Number

X(007) 203-209

34 TXIN-VEHR-CODE-COLOR Registration Plate Color

X(001) 210-210

35 TXIN-OWNR-CODE-TYPE-PHYS Registration Owner Type

X(001) 211-211




Vehicle Owner Information Field # Name/Description Picture Position

36 TXIN-VEHC-LICENSE-NUMB Vehicle Owner License Number (pers)

X(025) 212-236

37 TXIN-VEHC-LICENSE-STATE Vehicle Owner License State (pers)

X(002) 237-238

38 TXIN-VEHC-NAME-LAST Vehicle Owner Surname (pers)

X(016) 239-254

39 TXIN-VEHC-PERS-NAME-FIRST Vehicle Owner First Name (pers)

X(012) 255-266

40 TXIN-VEHC-PERS-DOB Vehicle Owner Date of Birth (pers)

X(008) 267-274

41 TXIN-VEHC-NOWN-FID Vehicle Owner NOWN FID (corp)

X(009) 212-220

42 TXIN-VEHC-NOWN-ZIP Vehicle Owner NOWN Zip (corp)

X(009) 221-229

43 TXIN-VEHC-NOWN-NAME Vehicle Owner NOWN Name (corp)

X(020) 230-249

44 FILLER For corp

X(025) 250-274

45 FILLER For future use

X(020) 275-294

Cancellation/Reinstatement Detail


46

47

48

TXIN-TXN-CANC-REIN-CODE Cancellation/Rein Reason Code

TXIN-UNPAID-DOLLAR-AMT Unpaid Dollar Amount

FILLER For future use

X(002)

9(005)

X(118)

170-171

172-176

177-294




Bind Verification Detail


49

50

TXIN-BINDER-TXN-NUMB Binder Reference Number

FILLER

X(016)

X(109)

170-185

186-294

Amend Policy Information Detail


51 FILLER X(125) 170-294



UMS Transaction Input Record - Definitions

Record Header (all UMS batch records)

Field Definition

01 Submitting Insurance Company Code: 3-character alphanumeric code. Assigned to the insurance / processing company by the Commonwealth Automobile Reinsurers (CAR). Insurance Service Bureaus receive their code from the Registry

.



UMS Transaction Input Record - Definitions (continued) Policy Information

Field Definition

02 Insurance Company Code: 3-digit numeric code. Assigned to the insurance company by CAR.

03 Policy Number: 16 character alphanumeric. Number by which this policy may be referenced in the insurance company files. Use only significant alpha or numeric digits, left justified, with no blanks between significant digits. Special characters are not permitted

04 Policy Binder Reference Number: 16 character alphanumeric. System generated binder reference number. The first digit is always a pound sign (#).

05 Policy Binder First Digit: 1-character alphanumeric. First digit of the binder reference number

06 Policy Binder Subsequent Digits: 15-character alphanumeric. Next fifteen digits of the binder number

07 Policy Binder Surrogate: 8-digit numeric. Part of system generated binder number

08 Policy Binder Insurance Company: 3-digit numeric. Part of system generated binder number.

09 Policy Binder Date: 4-digit numeric. Part of system generated binder number.

10 Policy Type: 1-character alphanumeric. Specify P for Private Passenger policy or C for Commercial policy.

11 Policy Effective Date: 8-digit numeric. Effective month, day, century and year for the policy (MMDDCCYY).

12 Policy Expiration Date: 8-digit numeric. Effective month, day, century, and year for the policy (MMDDCCYY).

13 Number of Transactions Submitted: 4-digit numeric value (zero filled, right justified). For New Business and Renewal transactions, this field represents the number of vehicles to be insured by this unique policy (1 - 9,999 available vehicle entries). For Amend transactions, it is the number of Amend transactions for a given policy.

14 Transaction Type: 1-digit numeric. Specifies type of UMS transaction to be processed:

1 New Business transaction 2 Bind Verification transaction 3 Policy Renewal transaction 4 Policy Amend transaction 5 Policy Cancellation transaction 6 Policy Reinstatement transaction 7 Clear and Amend Unpaid Premium transaction 8 Policy Inquiry transaction

15 Transaction Effective Date: 8-digit numeric. The effective month, day, century and year of the specified transaction (MMDDCCYY).



UMS Transaction Input Record - Definitions (continued)


Field Definition

16 Policyholder License Number: 25-character alphanumeric. An individual policyholder’s driver license number exactly as it appears on the policyholder’s driver license. Left justified, blank filled, imbedded spaces removed. This field should contain NOLICENSE if the policyholder is not licensed in any state

17 NOWN Policyholder FID Number: 9-character numeric. A NOWN (corp) policyholder’s Federal Identification number or EIN.

18 NOWN Policyholder Zip Code: 9-character numeric. A NOWN (corp) policyholder’s zip code. The first five digits are required.

19 Policyholder License State: 2-character alphabetic. U.S. Postal Service code of the state that issued the policyholder’s driver license. For NOLICENSE, this field should contain XX. For a NOWN policyholder, this field should contain ZZ.

20 Policyholder Surname: 16-character alphabetic. The first 16 characters of the policyholder’s surname, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes and commas should be omitted. One hyphen is permitted in those cases where two last names are combined. If the policyholder’s surname has fewer than 16 characters, enter only the surname. Do not enter the policyholder’s first name in this field. Policyholder name suffixes such as Jr. and Sr. should be omitted.

21 Policyholder First Name: 12-character alphabetic. The first 12 characters of the policyholder’s first name, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes and commas should be omitted.

22 Policyholder Date of Birth: 8-digit numeric. Date of birth of the policyholder exactly as it appears on the driver license. If the policyholder has no driver license, enter the date of birth exactly as it appears on the policyholder's birth certificate (MMDDCCYY).

23 Policyholder NOWN Name: 36-character alphabetic. A NOWN policyholder's corporation name. Do not include any special characters such as periods, hyphens, commas or quotations. Imbedded spaces are allowed and numbers must be spelled out. For example, if the company name is Acme 10, enter Acme Ten.

24 Filler: 40 characters reserved for company use.

25 Filler: 14 characters reserved for future use.

26. Filler: 1 character reserved for RMV use.





Field Definition

27 Vehicle Action Code: 1-digit numeric. Identifies the action to be taken for a specified record. 0 Change to Header Information (Policyholder) 1 Add Vehicle to Policy (or for New Business/Policy Renewal transactions) 2 Delete Vehicle from Policy (Amend transaction only) 3 Change to Vehicle Detail (Premium Town Code)

28 Vehicle Identification Number: 17-character alphanumeric. Left justified. Identifies the vehicle(s) being insured. Validity of post-1980 VIN’s is determined through a check-digit routine.

29 Vehicle Year: 4-digit numeric. Year in which the vehicle was built (YYYY).

30 Vehicle Make: 5-character alphabetic. Make of the vehicle, as it appears on the registration.

31 Vehicle Premium Town: 3-digit numeric. Town code taken from the table of accident towns and premium towns as published in the Massachusetts Private Passenger Statistical Plan.

32 Registration Plate Type: 3-character alphabetic. Represents the registration number plate type

33 Registration Number: 7-character alphanumeric. The RMV registration number currently assigned to the vehicle; keyed exactly as it appears on the RMV database. Left justified, blank filled.

34 Registration Plate Color: 1-character alphabetic. The registration plate color code for the current registration plate

35 Registration Owner Type: 1-digit numeric. Identifies the owner of the vehicle as an individual or a corporation (i.e. a leasing company). 1. Signifies an individual. 2. Signifies a corporation.





Field Definition

35 Vehicle Owner License Number (pers): 25-character alphanumeric. Entered exactly as it appears on the driver license number. Left justified, blank filled.

37 Vehicle Owner License State (pers): 2-character alphabetic. U.S. Postal Service code of the state that issued the vehicle owner’s driver license. Refer to Appendix G for a list of state codes.

38 Vehicle Owner Surname (pers): 16-character alphabetic. The first 16 characters of the vehicle owner’s surname, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes and commas should be omitted. If the vehicle owner’s surname has fewer than 16 characters, enter only the surname. Do not enter the vehicle owner’s first name in this field.

39 Vehicle Owner First Name (pers): 12-character alphabetic. The first 12 characters of the vehicle owner’s first name, exactly as it appears on the owner’s registration. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes and commas should be omitted.

40 Vehicle Owner Date of Birth (pers): 8-digit numeric. Date of birth of the vehicle owner, exactly as it appears on the owner’s driver’s license. If the owner has no driver license, enter the date of birth exactly as it appears on the birth certificate (MMDDCCYY).

41 Vehicle Owner NOWN FID (corp): 9-character numeric. A NOWN vehicle owner’s corporation Federal Identification number or EIN.

42 Vehicle Owner NOWN Zip Code (corp): 9-character numeric. A NOWN vehicle owner’s corporation zip code

43 Owner NOWN Name (corp): 20-character alphabetic. A NOWN vehicle owner’s corporation name. Do not include any special characters such as periods, hyphens, commas or quotations. Imbedded spaces are allowed and numbers must be spelled out. For example, if the company name is Acme 10, enter Acme Ten.

44 Filler (corp): 25-character alphanumeric. For insurance company use.

45 Filler: 20-character alphanumeric. For future use

.



UMS Transaction Input Record - Definitions (continued) Cancellation/Reinstatement Detail

Field Definition

47 Cancellation / Reinstatement Reason Code: 2-character numeric. Identifies the reason for the specified action.

Cancellation Reason Codes 01 Non-Payment 02 Underwriting Reasons 03 Competition / Voluntary 04 Fraud by Insured 05 Failure to Pay Surcharge 06 License or Registration Revoked 07 Void Cancellation 08 Dissatisfaction 09 Vehicle Sold 10 Transfer 11 Financed Account 12 Cancel / Rewrite 13 All Other

Reinstatement Reason Codes 21 Reversal of Cancellation Reason Code 22 Cancellation Done in Error

Clear Unpaid Premium Reason Codes 41 Unpaid Premium Paid

Recording of Unpaid Premium Done in Error Change Dollar Amount

47 Unpaid Dollar Amount: 5-character numeric. The whole dollar amount of money being recorded/removed for a Cancellation, Reinstatement, or Clear of Unpaid Premium.

48 Filler: 118-character alphanumeric. For future use.

Bind Verification Detail Field Definition

49 Bind Transaction Reference Number: 16-characters alphanumeric. The 15- character number must be preceded by a pound sign (#). The bind number is returned to the Insurance Agent at the time of On-line Bind. UMS uses this bind number to allow the new policy number to relate to the bind number under which the policy information was originally recorded.

50 Filler: 109 alphanumeric spaces. For future use.

Amend Policy Information Detail Field Definition

51 Filler: 125 alphanumeric characters



UMS Transaction Response Record - Descriptions


01

02

03

04

Copy of Input Record

TXRS-PROCESS-DATE UMS Process Date

TXRS-ERROR-CODE-TABLE UMS Error Codes (occurs 8 times)

TXRS-NUMB-VEHC UMS Vehicles Submitted

X(295)

9(008)

9(004)

9(004)

000-294

295-302

303-334

335-338



05 TXRS-PLCY-LICENSE-NUMB RMV Policyholder License Number (pers)

X(025) 339-363

06 TXRS-PLCY-FID-NUMB NOWN RMV Policyholder FID (corp)

X(009) 339-347

07 FILLER X(016) 348-363

08 TXRS-PLCY-LICENSE-STATE RMV Policyholder License State (pers)

X(002) 364-365

09 TXRS-PLCYHLDR-NAME-LAST RMV Policyholder Last Name (pers)

X(016) 366-381

10 TXRS-PLCYHLDR-NAME-FIRST RMV Policyholder First Name (pers)

X(012) 382-393

11 TXRS-PLCYHLDR-NAME-MIDDLE RMV Policyholder Middle Name (pers)

X(008) 394-401

12 TXRS-PLCYHLDR-DOB RMV Policyholder Date of Birth (pers)

X(008) 402-409

13 TXRS-PLCYHLDR-NOWN-NAME RMV Policyholder NOWN Name (corp)

X(044) 366-409

14 TXRS-PLCYHLDR-MAIL-STREET1 RMV Policyholder Mail Address 1

X(020) 410-429

15 TXRS-PLCYHLDR-MAIL-STREET2 RMV Policyholder Mail Address 2

X(020) 430-449

16 TXRS-PLCYHLDR-MAIL-CITY RMV Policyholder City/Town

X(015) 450-464

17 TXRS-PLCYHLDR-MAIL-STATE RMV Policyholder Mail State

X(002) 465-466

18 TXRS-PLCYHLDR-MAIL-ZIP NOWN RMV Policyholder Zip Code

9(009) 467-475



UMS Transaction Response Record - Descriptions (continued)



19 TXRS-VIN RMV VIN

X(017) 476-492

20 TXRS-VMAK-NUMB-YEAR RMV Vehicle Year

9(004) 493-496

21 TXRS-VMAK-NAME RMV Vehicle Make

X(005) 497-501

22 TXRS-VEHR-TOWN-NUMB RMV Vehicle Garage Town Code

9(003) 502-504

23 TXRS-VEHR-CODE-PLATE-TYPE RMV Registration Plate Type

X(003) 505-507

24 TXRS-VEHR-CODE-REGISTRATION RMV Registration Number

X(007) 508-514

25 TXRS-VEHR-CODE-COLOR RMV Registration Plate Color

X(001) 515-515

26 TXRS-VEHR-STATUS RMV Registration Status

X(009) 516-524

27 TXRS-VEHR-DATE-EXPIRE RMV Registration Expire Date

9(006) 525-530

28 TXRS-OWNR-CODE-TYPE-PHYS RMV Registration Owner Type

X(001) 531-531



UMS Transaction Response Record - Descriptions (continued)



29 TXRS-PERS-LICENSE-NUMB RMV Owner License Number (pers)

X(025) 532-556

30 TXRS-PERS-LICENSE-STATE RMV Owner License State (pers)

X(002) 557-558

31 TXRS-PERS-NAME-LAST RMV Vehicle Owner Surname (pers)

X(016) 559-574

32 TXRS-PERS-NAME-FIRST RMV Vehicle Owner First Name (pers)

X(012) 575-586

33 TXRS-PERS-DOB RMV Owner Date of Birth (pers)

X(008) 587-594

34 FILLER X(001) 595-595

35 TXRS-NOWN-FID RMV NOWN Vehicle Owner FID (corp)

X(009) 532-540

36 TXRS-NOWN-NAME RMV NOWN Vehicle Owner Name (corp)

X(055) 541-595

37 TXRS-OWNR-MAIL-STREET1 Registration Owner Mail Address 1

X(020) 596-615

38 TXRS-OWNR-MAIL-STREET2 Registration Owner Mail Address 2

X(020) 616-635

39 TXRS-OWNR-MAIL-CITY Registration Owner Mail City

X(015) 636-650

40 TXRS-OWNR-MAIL-STATE Registration Owner Mail State

X(002) 651-652

41 TXRS-OWNR-MAIL-ZIP Registration Owner Mail Zip

9(009) 653-661

42 TXRS-INDC-ACCEPTED-REJECTED Transaction Accept/Reject Indicator

X(001) 662-662

43 FILLER X(018) 663-680



UMS Transaction Response Record - Definitions

Field Definition

01 Copy of Input Record: 295-character alphanumeric.

Policy Information

Field Definition

02 UMS Process Date: 8-digit numeric. Month, day, century, and year (MMDDCCYY).

03 UMS Error Codes: 4-digit numeric. Up to eight error codes per record can be returned by the RMV.

04 UMS Vehicles Submitted: 4-digit numeric value (zero filled, right justified). For New Business and Renewal transactions, this field represents the number of vehicles to be insured by this unique policy (1 - 9,999 available vehicle entries). For Amend transactions, it is the number of Amend transactions for a given policy.



UMS Transaction Response Record - Definitions (continued)


Field Definition

05 RMV Policyholder License Number: 25-character alphanumeric. An individual policyholder’s driver license number exactly as it appears on the policyholder’s driver license. Left justified, blank filled, imbedded spaces removed

06 NOWN RMV Policyholder FID: 9-character numeric. A NOWN policyholder’s Federal Identification number or EIN.

07 Policy Binder Surrogate: 8-digit numeric. Part of system generated binder Filler: 16-character alphanumeric.

08 RMV Policyholder License State: 2-character alphabetic. U.S. Postal Service code of the state that issued the policyholder’s driver license. Refer to Appendix G for a list of state codes.

09 RMV Policyholder Last Name: 16-character alphabetic. The first 16 characters of the policyholder’s surname, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes, and commas omitted.

10 RMV Policyholder First Name: 12-character alphabetic. The first 12 characters of the policyholder’s first name, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes, and commas should be omitted.

11 RMV Policyholder Middle Name: 8-character alphabetic. The first 8 characters of the policyholder's middle name, exactly as it appears on the driver license. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes, and commas omitted.

12 RMV Policyholder Date of Birth: 8-digit numeric. Date of birth of the policyholder exactly as it appears on the driver license.

13 RMV Policyholder NOWN Name: 44-character alphabetic.

14 RMV Policyholder Mail Address 1: 20-character alphanumeric.

15 RMV Policyholder Mail Address 2: 20-character alphanumeric.

16 RMV Policyholder City/Town: 15-character alphanumeric.

17 RMV Policyholder Mail State: 2-character alphabetic.

18 NOWN RMV Policyholder Zip Code: 9-character numeric.





Field Definition

19 RMV VIN: 17-character alphanumeric. Left justified.

20 RMV Vehicle Year: 4-digit numeric. Year in which the vehicle was built (YYYY).

21 RMV Vehicle Make: 5-character alphabetic. Make of the vehicle as it appears on the registration.

22 RMV Vehicle Garage Town Code: 3-digit numeric.

23 RMV Registration Plate Type: 3-character alphabetic.

24 RMV Registration Number: 7-character alphanumeric. The RMV registration number currently assigned to the vehicle as it appears on the RMV database. Left justified, blank filled.

25 RMV Registration Plate Color: 1-character alphabetic. The registration plate color code for the current registration plate.

26 RMV Registration Status: 9-character alphabetic. Not currently provided by the RMV.

27 RMV Registration Expire Date: 6-digit numeric. End effective date for registration, month, century, and year (MMCCYY).

28 RMV Registration Owner Type: 1-digit numeric. Identifies the owner of the vehicle as an individual or a corporation (i.e. a leasing company). 1. Signifies an individual. 2. Signifies a corporation.





Field Definition

29 RMV Owner License Number: 25-character alphanumeric. Left justified, blank filled.

30 RMV Owner License State: 2-character alphabetic.

31 RMV Vehicle Owner Surname: 16-character alphabetic. The first 16 characters of the vehicle owner’s surname. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes, and commas omitted.

32 RMV Vehicle Owner First Name: 12-character alphabetic. The first 12 characters of the vehicle owner’s first name, exactly as it appears on the owner’s registration. Left justified, blank filled, imbedded spaces and punctuation such as periods, apostrophes and commas omitted.

33 RMV Owner Date of Birth: 8-digit numeric. Date of birth of the vehicle owner (MMDDCCYY).

34 Filler: 1 character.

35 RMV NOWN Vehicle Owner FID: 9-character numeric. A NOWN vehicle owner’s corporation Federal Identification number or EIN.

36 RMV NOWN Vehicle Owner Name: 55-character alphabetic.

37 Registration Owner Mail Address 1: 20-character alphanumeric.

38 Registration Owner Mail Address 2: 20-character alphanumeric.

39 Registration Owner Mail City: 15-character alphanumeric.

40 Registration Owner Mail State: 2-character alphabetic.

41 Registration Owner Zip Code: 9-character numeric.

42 Transaction Accept/Reject Indicator: 1-character alphabetic. System response to transaction: “Y” means accepted, “N” means rejected.

43 Filler: 18 characters reserved for future use.


Registry of Motor Vehicles - UMS Batch Manual

11 Batch-Related FAQ’s

This chapter lists frequently asked questions concerning UMS Batch Processing.

Chapter 11 - Batch-Related FAQ’s 11-1


FAQ’S

1. What does error code 0602 mean?

When editing each record, the UMS "count verification" checks if the "header" portion of the records submitted are the same. If not, you receive a 0602 error code. Another reason you may receive this error code is if one of the records submitted is rejected. In this instance, your count would be off in the header and therefore, the header record would not be the same. When you find and correct the error on the policy, retransmit the record and the error code 0602 will not reappear as long as all hard edits are correct.

2. When submitting a commercial policy and the vehicle we are insuring is a leased vehicle, how do we submit the Policyholder information and the vehicle information?

Example information: Policyholder = Boston Florist Inc. Fid/Ein#= 123456789 Vehicle registered to GMAC Fid/EIN# = 987654321 Lessee name = Boston Florist Inc. Fid/EIN# = 123456789

The policyholder name should be submitted as Boston Florist Inc using their Fid/EIN # 123456789. The vehicle is NOT registered to them so your company would need to submit the registered owner GMAC and their FID/EIN# 987654321 for the vehicle portion of the record along with GMAC's ZIP code.

3. Can we make a change to the policy expiration date once we submitted it to the Registry/UMS system and it was accepted?

No, there is no way to "amend" the policy expiration date. You would have to cancel the original policy and submit another policy record with the proper and or extended expiration date.

4. My company does not capture FID/EIN information. Is there any way the Registry can supply this information to my company?

If the company in which you are interested has VEHICLES registered in Massachusetts, then yes, we can supply your company with a listing of all vehicles that are registered and insured by your company. See Appendix I which describes the "Registration Data File request form". The information returned by the RMV provides your company with Registration, VIN#, Vehicle information, and owner information which also supplies either a license # or a FID/EIN #.

5. We don't capture VIN #'s or Registration numbers. Do we need to submit these vehicles to UMS?

Yes, the Registry's position on this is that your agents prepare RMV 1 's in order for your customers to register their vehicles. In which case, you or your agent knows the specific vehicles that are on "composite" rated policies. You should address this issue with your agents, so that the information can be forwarded to your company and then passed along to UMS. The most important thing to remember is that in order to cancel a policy with the Registry of Motor Vehicles; you need to report it electronically.



6. We don't capture VIN numbers or Registration plate information, do we have to submit this information to UMS?

Yes, see FAQ # 4, above, pertaining to Appendix I of this manual for the "Registration Data File" request form.

7. Do we have to send in our Renewal policies to UMS every year?

Yes, you have to send a policy to UMS every year when it renews along with ALL of the vehicles that are on the policy.

8. What happens if we don't give you information about a vehicle on a new policy that we took over from another company?

By not giving us a particular vehicle, you will cause that person's/company's registration to go into revocation. Our system checks if there is coverage for a vehicle every night if we receive a cancellation notice that was previously covering a vehicle. If no coverage is present after 23 days, the RMV sends out an Intent to Revoke letter explaining that the registered owner has 10 days in which to prove to the RMV that he or she has insurance. (Proof means, have the parent company electronically report the policy information to the Registry/UMS system). If on the 10-th day, no coverage is present for a particular registration, the Registry revokes that vehicle’s plate(s).

9. Is there a "TEST" area in which we can submit documents prior to going LIVE in production?

Yes. We want your company to submit a "test" file to us prior to moving to production. Our test region is a copy of our production region and is updated at least once a month. This testing needs to be coordinated with our operations area at ITD, where your cartridges are submitted. Please refer to page 1-3 of this manual for the Data Set Identifier name to use for testing purposes.

10. How often can we submit our records to the Uninsured System?

As often as necessary for your company, keeping in mind that every record is time sensitive and that records need to be submitted within 23 days of their policy effective date.

11. How do we know if a record was accepted by the Registry's UMS system?

The last character in the response record is a one byte, alpha character that is either a "Y" or a "N". "Y" meaning: Yes, your policy was accepted, or "N", NO your policy record failed the edits for any number of reasons and we did not accept your policy record.

12. How long do we have to correct any records found in error and rejected out of a batch?

You must correct these records as soon as possible. Some companies use the on-line system to resubmit their policy information. Again, there is a 23-day timing issue to contend with.



13. What if we get a "Y" back on the policy saying it was accepted but there are error codes on the response record? Was this record accepted or not, and what should we do about the error codes?

Any time you get a "Y" back on a record, that record has been accepted by UMS. The error codes are informational error codes and are NOT hard errors. An example of an informational error code would be if you got a 2401 (vehc prem twn not valid twn code in mass ppsp). The premium town code is an "optional" field. Therefore, your policy would not reject if you received this error code only. If you passed us all of the correct vehicle/owner information but did not pass us the correct vehicle owner ZIP code, we would have ACCEPTED your policy record, but we would have given you back error code 3302 (vehc owner zip code is invalid. Veh own info is stored in the response section). Some insurance companies use the information that we pass back to them on the response record, to update their database with the information to be in sync with the Registry's database.

14. What if we cancel a policy for nonpayment, and the customer pays us but decides to go with another insurance carrier. What should we do with this customer's policy on UMS?

Your company should process a Clear and Amend Unpaid Premium Transaction (code 7). If a customer pays in full, put a zero in the dollar amount field and use the reason code of 41. Or, if your company wants to decrease the dollar amount in partial payments, use the reason code of 43. The dollar amount submitted, if decreasing, should be the dollar amount STILL OWED to the insurance company.

15. How can we send you policyholder information such as license information, if the customer does not have a license to drive?

If a person has an out of state driver's license, you can submit that in the policyholder license number field along with that state's two alpha character field (e.g., NY). However, if a person does not have an out of state license or a Massachusetts license, then you should submit "NOLICENSE" in the license field and XX in the state field.

16. In any of the batch fields can we pass special characters such as comma's, periods, dashes, etc.?

No, special characters are not to be used throughout the batch record.

17. What is a Bind Verification transaction?

A binder number is generated on a policy when an insurance company builds a New Business or Renewal transaction on-line, but leaves out the policy number from the policy number field. The Registry/UMS generates the "binder" number for that specific policy, until the Parent company finds out what the actual policy number is going to be. Once the company determines the policy number, they can submit a "bind verification" transaction that will overlay the binder number that the Registry/UMS built for the policy.



18. Is there a specific order in which batch transactions get processed?

Yes, the order in which we process transactions is as follows: 1. New Business 2. Bind Verification 3. Policy Renewals 4. Policy Amendments 5. Policy Cancellations 6. Policy Reinstatements 7. Amend Unpaid Premiums 8. Policy Inquiry

19. Does the RMV allow batch transactions to be sent via FTP?

Yes, we prefer that companies send in their batch records via FTP. Please see information about this subject in Chapter 1 (page 1-2) of this manual.


Section 2

Reference Information


Appendix A Processing Request Form

This appendix shows a copy of the UMS Processing Request Form.

Use this form when submitting a UMS processing request to the RMV

Appendix A – Processing Request Form A-1


Appendix A – Processing Request Form A-2


Appendix B COBOL Transaction Record

Layouts

This appendix contains the COBOL record layouts of the UMS input record and the UMS response record.

B-1 Appendix B – COBOL Transaction Record Layouts


UMS COBOL Transaction Input Record



UMS COBOL Transaction Input Record (continued)



UMS COBOL Transaction Response Record



UMS COBOL Transaction Response Record (continued)



Appendix C Input Record Edits

This appendix shows Input Record Edits for the UMS Transaction Codes.

You can use this information to check of Mandatory and Optional codes that must be included in your data records when you submit them in a batch for UMS Transactions

Appendix C – Input Record Edits C-1


New Business and Policy Renewal Transactions- Codes 1 and 3

Field Content Status

01 Submitting Insurance Company Code

Mandatory

02 Insurance Company Code Mandatory

03,04 Policy Number or Policy Binder Reference Number

Mandatory

05-09 The RMV system uses these element names to redefine different parts of the Policy Binder Reference Number.

Not Applicable

10 Policy Type Mandatory

11 Policy Effective Date Mandatory

12 Policy Expiration Date Mandatory

13 Number of Transactions Submitted

Mandatory

14 Transaction Type Mandatory

15 Transaction Effective Date Mandatory

16,17 Policyholder License Number, NOLICENSE, or NOWN Policyholder FID Number

Mandatory

18 NOWN Policyholder Zip Code Mandatory (First 5 digits for NOWN only)

19 Policyholder License State Mandatory (MA or valid state code for individual. ZZ when submitting a NOWN, XX for No License)

20 Policyholder Surname Mandatory (Individual only)

21 Policyholder First Name Optional (Individual only)

22 Policyholder Date of Birth Mandatory (Individual only)

23 Policyholder NOWN Name Mandatory (NOWN only)

24 Filler Optional (For company use)

25 Filler Optional (For future use)

26 Filler Reserved For RMV use

27 Vehicle Action Code Mandatory

28 Vehicle Identification Number Mandatory

29 Vehicle Year Optional

30 Vehicle Make Optional

31 Vehicle Premium Town Mandatory



New Business and Policy Renewal Transactions- Codes 1 and 3 (continued)


32 Registration Plate Type Mandatory unless alternative vehicle owner information is given. See alternative individual owner fields (marked A1) and alternative NOWN owner fields (marked A2) below.

33 Registration Number Owner information is given. See alternative individual owner fields (marked A1) and alternative NOWN owner fields (marked A2).

34 Registration Color Optional

35 Registration Owner Type Mandatory

36 Vehicle Owner License Number (A1)

Mandatory for individual vehicle owner if 32 and 33 not provided.

37 Vehicle Owner License State (A1)


38 Vehicle Owner Surname (A1) Mandatory for individual vehicle owner if 32 and 33 not provided.

39 Vehicle Owner First Name Optional

40 Vehicle Owner Date of Birth (A1)


41 Vehicle Owner NOWN FID (A2)

Mandatory for NOWN vehicle owner if 32 and 33 not provided.

42 Vehicle Owner NOWN Zip Code (A2)


43 Vehicle Owner NOWN Name (A2)


44-51 These element names are not used in the transaction.

Not Applicable



Bind Verification Transaction Code 2



Mandatory


03 Policy Number Mandatory

04 Policy Binder Reference Number

Not Applicable

05- 09 The RMV system uses these element to redefine different parts of the Policy Binder Reference Number.

Not Applicable





Mandatory



16, 17 Policyholder License Number, NOLICENSE, or NOWN Policyholder FID Number

Mandatory









26 Filler Reserved for RMV use


Not Applicable

49 Policy Binder Reference Number

Mandatory


51 This element name is not used in the transaction.

Not Applicable



Policy Amend Transaction - Code 4



Mandatory


03-04 Policy Number or Policy Binder Reference Number

Mandatory

05-09 The RMV system uses these element names to redefine different parts of the Policy Binder Reference Number.

Not Applicable





Mandatory



16-17 Policyholder License Number, NOLICENSE, or NOWN Policyholder FID Number

Mandatory

18 NOWN Policyholder Zip Code Mandatory (NOWN only)









27 Vehicle Action Code Note: If Policyholder Amend (0) then use only element 51. For other Amends (1 - 3), use the following elements except 51.

Mandatory

28 Vehicle Identification Number Mandatory

29 Vehicle Year Optional

30 Vehicle Make Optional



Policy Amend Transaction - Code 4 (continued)


31 Vehicle Premium Town Mandatory

32 Registration Plate Type Mandatory unless alternative vehicle owner information is given. See alternative individual owner fields (marked A1) and alternative NOWN owner fields (marked A2)

33 Registration Number Mandatory unless alternative vehicle owner information is given. See alternative individual owner fields (marked A1) and alternative NOWN owner fields (marked A2).

34 Registration Color Optional

35 Registration Owner Type Mandatory

36 Vehicle Owner License Number (A1)


37 Vehicle Owner License State (A1)


38 Vehicle Owner Surname (A1) Mandatory for individual vehicle owner if 32 and 33 not provided.

39 Vehicle Owner First Name Optional

40 Vehicle Owner Date of Birth (A1)


41 Vehicle Owner NOWN FID (A2)


42 Vehicle Owner NOWN Zip Code (A2)


43 Owner NOWN Name (A2) Mandatory for NOWN vehicle owner if 32 and 33 not provided.


Not Applicable

51 Filler Optional



Policy Cancellation Transaction - Code 5



Mandatory



Mandatory

05-09 These element names are used by the RMV system to re-define different parts of the Policy Binder Reference Number.

Not Applicable





Mandatory




Mandatory










27-45 These element names are not used by the transaction.

Not Applicable

46 Cancellation / Reinstatement Reason Code

Mandatory

47 Unpaid Dollar Amount Mandatory

48 Filler Optional


Not Applicable



Policy Reinstatement Transaction - Code 6 Field Content Status


Mandatory



Mandatory

05-09 These element names are used by the RMV system to redefine different parts of the Policy Binder Reference Number.

Not Applicable





Mandatory




Mandatory











Not Applicable

46 Reinstatement Code or Error Cancel

Mandatory


48 Filler Optional


Not Applicable



Clear and Amend Unpaid Premium Transaction - Code 7 Field Content Status


Mandatory



Mandatory


Not Applicable





Mandatory




Mandatory


19 Policyholder License State Mandatory (MA or valid state code for individual. ZZ when submitting a NOWN)









Not Applicable

46 Cancellation / Reinstatement Reason Code

Mandatory


48 Filler Optional


Not Applicable



Policy Inquiry Transaction - Code 8 Field Content Status


Mandatory



Mandatory


Not Applicable





Mandatory



16-51 These element names are not used in the transaction

Not Applicable



Appendix D Error Codes

This appendix lists error codes for the UMS Error Code fields on the UMS Transaction Response Records.

This information can be used to correct input files when they are re-submitted for UMS Transactions.

Appendix D – Error Codes D-1


Table of UMS Batch Error Codes

Error Code Meaning

0101 Submitting Insurance Company Code blank or invalid (not on table)

0201 Carrying Insurance Company Code blank or invalid (not on table)

0202 Submitting Insurance Company not equal to Issuing Insurance Company.

0301 Policy Number blank or not alphanumeric.

0302 Policy Identification (Carrying Insurance Company Code, Policy Number, and Policy Effective Date) already used on a policy stored on the RMV database (for New Business, Policy Renewal, and Bind Verification transactions).

0303 Policy Identification not found on RMV database (for all transactions except New Business, Policy Renewal, and Bind Verification).

0304 Policy Type must be P (Private Passenger) or C (Commercial).

0401 Policy Effective Date not a valid date.

0404 Transaction Effective Date not equal to policy effective date.

0501 Policy Expiration Date not a valid date.

0502 Policy Expiration Date on or before Policy Effective Date.

0503 Policy Expiration Date greater than two years after the Policy Effective Date.

0601 Number of Records Submitted not numeric.

0602 Incorrect Transaction Count/Headers not equal.

0901 Transaction Type not 1, 2, 3, 4, 5, 6, 7, or 8.

0902 Invalid transaction for cancelled policy.

0903 Invalid transaction for active policy.

0904 Unpaid Amount equals zero - not needed to clear.

0905 Invalid Bind Verification transaction. Policy Status already ACTV.

1001 Transaction Effective Date not a valid date.

1002 Invalid time lapse.

1003 Transaction Effective Date not between policy effective and expiration dates (All transactions except New Business and Policy Renewal).

1004 Advanced cancel to a policy not yet in effect.

1005 Policy already in Advance Cancel status.

1006 Policy History For Advanced Cancel not found.

1007 TXN Effective Date must equal ADV Cancel Date.

1101 Policyholder License Number blank or invalid.

1102 Policyholder License Number not found on RMV database for MA Policyholder License State.



1103 Commercial policies may not be entered before 8/15/97 and must have an effective date of 10/01/97 or later.

1104 Corporate policies must be entered in the new record format.

1105 Corporate FID number must follow federal guidelines.

1106 FID number not found on RMV database.

1107 FID numbers 777777777 and 999999999 may not be used. Must specify a valid FID.

1201 Policyholder License State blank or invalid.

1301 Policyholder Surname blank or invalid.

1302 Policyholder Surname does not match surname on RMV database on at least three of the first five characters for MA Policyholder License State.

1303 FID found on RMV database but name does not match.

1304 Corporate Name is invalid.

1401 Policyholder First Name blank or invalid.

1501 Policyholder Date of Birth not a valid date.

1502 Zip Code is missing or invalid.

1503 Policyholder Date of Birth does not match the date of birth on the RMV database on at least two of the three elements (month, day, year) for MA Policyholder License State.

2003 Vehicle Action Code invalid.

2101 VIN blank or invalid.

2102 VIN not found on RMV database (for New Business, Policy Renewal, and Add Vehicle transactions).

2103 Vehicle not connected to policy on RMV database (for Delete Vehicle transaction).

2104 Vehicle already added to policy on RMV database.

2105 No match for Registration or Owner information on RMV database.

2106 Vehicle already deleted from policy on RMV database.

2302 Vehicle Year not a valid year.

2304 Vehicle Make/Name blank or invalid.

2401 Vehicle Premium Town not a valid town code as published in the Massachusetts Private Passenger Statistical Plan in the Table of Accident Towns and Premium Towns.

2601 Current Registration Number required for vehicle.

2801 Vehicle Owner Type blank or invalid.

2901 Vehicle Owner License Number blank or invalid.

2902 Vehicle Owner FID is invalid. Vehicle owner information is stored in the response section.

3001 Vehicle Owner License State not a valid state code.

3101 Vehicle Owner Surname blank or invalid.

3102 Vehicle Owner Name is invalid. Vehicle owner information is stored in the response section.

3201 Vehicle Owner First Name blank or invalid.

3301 Vehicle Owner Date of Birth not a valid date.



3302 Vehicle Owner Zip Code is invalid. Vehicle owner information is stored in the response section.

3401 Vehicle Owner Name (corp) blank or invalid.

4001 Cancellation/Reinstatement Code blank or invalid (for Policy Cancellation, Policy Reinstatement, or Clear Unpaid Premium transaction).

4101 Unpaid Dollar Amount blank or not numeric.

5001 Binder Transaction Reference Number blank or invalid.

5002 Binder Transaction Reference Number not found on RMV database.

9901 Related Transaction in error.

9902 Maximum Errors exceeded.

9903 Duplicate Records submitted.

9999 Unknown Error Codes.



Appendix E UMS Response Record & UMS Insurance Company

Summary Report

This appendix contains an example of a UMS Response record. It also contains a sample UMS Insurance Company Summary Report.

Appendix E – Example of UMS Response Record & UMS Insurance Company E-1 Summary Report


UMS Response Record Field Description

Information From Input Record

Field # Sample Record Info. Field Description

1 ISI Submitting Insurance Company Code

2 419 Insurance Company Code

3 ARM0000000000010 Policy Number

10 P Policy Type

11 06201997 Policy Effective Date

12 06201998 Policy Expiration Date

13 0001 Number of Transactions Submitted

14 2 Transaction Type

15 06201997 Transaction Effective Date

16 022523593 Policyholder License Number

19 MA Policyholder License State

20 Comerford Policyholder Surname

21 Mark Policyholder First Name

22 01141959 Policyholder Date of Birth

26 0 Reserved for RMV Use

49 #000001974197174 Binder Reference Number



UMS Response Record Field Description (continued)

Information From RMV Response Record

Field # Sample Record Info. Field Description

2 06241997 UMS Process Date

4 0001 UMS Vehicles Submitted

5 022523593 RMV Policyholder License Number

8 MA RMV Policyholder License State

9 Comerford RMV Policyholder Last Name

10 Mark RMV Policyholder First Name

11 RMV RMV Policyholder Middle Name

12 01141959 RMV Policyholder Date of Birth

14 72 Jewett St RMV Policyholder Mail Address 1

16 Newton Corner RMV Policyholder City/Town

17 MA RMV Policyholder Mail State

18 021580000 NOWN RMV Policyholder Zip Code

19 4382001374 RMV VIN

20 0000 RMV Vehicle Year

22 014 RMV Vehicle Garage Town Code

23 PAN RMV Registration Plate Type

24 379263 RMV Registration Number

25 G RMV Registration Plate Color

27 031999 RMV Registration Expire Date

28 1 RMV Registration Owner Type

29 022523593 RMV Vehicle License Number

30 MA RMV Vehicle License State

31 Comerford RMV Vehicle Owner Surname

32 Mark RMV Vehicle Owner First Name

33 01141959 RMV Owner Date of Birth

34 (1 blank) Filler

37 72 Jewett St Registration Owner Mail Address 1

39 Newton Corner Registration Owner Mail City

40 MA Registration Owner Mail State

41 021580000 Registration Owner Mail Zip

42 Y Transaction Accept/Reject Indicator



UMS Insurance Company Summary Report

UMS INPUT PAGE VSN: X02757 UNINSURED MOTORIST SYSTEM UMS RESPONSE TAPE VSN: X03859 UMS RESPONSE TAPE INSURANCE COMPANY REPORT 575 MASSWEST INSURANCE COMPANY

UMS TRANSACTION INPUT RESPONSE RESPONSE RESPONSE TRANSACTIONS INPUT RECORDS RECORDS RECORDS

GENERATED ACCEPTED REJECTED NEW BUSINESS 10 10 10 0 BIND VERIFICATION 0 0 0 0 POLICY RENEWAL 149 149 148 1 POLICY AMEND 43 43 17 24 POLICY CANCELLATION 13 13 13 0 POLICY REINSTATEMENT 2 2 2 0 CLEAR UNPAID PREMIUM 0 0 0 0 POLICY INQUIRY 0 0 0 0 UNKNOWN TRANSACTION 0 0 0 0

_____ _____ _____ _____ TOTAL TRANSACTIONS 217 217 190 27 -----------------------------------------------------------------------------------------------------------------------------------------------------

RESPONSE ERROR STATISTICS ------------------------------------------------------------------------------------------------------------------------------------------------------

ERROR DESCRIPTION COUNT 0101 SUBMITTING INSURANCE COMPANY BLANK OR INVALID 0 0201 CARRYING INSURANCE COMPANY CODE BLANK OR INVALID 0 0202 SUBMITTING INS CODE NOT EQUAL TO ISSUING INS CODE 0 0301 POLICY NUMBER BLANK OR NOT ALPHANUMERIC 0 0302 POLICY ID USED ON A POLICY STORED ON RMV DATABASE 0 0303 POLICY ID NOT FOUND ON RMV DATA BASE 3 0304 POLICY TYPE MUST BE P (PRIVATE PASSENGER) OR C (COMMERCIAL) 0 0401 POLICY EFFECTIVE DATE NOT A VALID DATE 0 0404 TRANS EFFEC DATE NOT = TO POLICY EFFEC DATE 0 0501 POLICY EXPIRATION DATE NOT A VALID DATE 0 0502 POLICY EXPIRE DATE ON OR BEFORE POLICY EFFEC DATE 0 0503 POLICY EXPIR DATE > 2 YRS AFTER POLICY EFFEC DATE 0 0601 NUMBER OF RECORDS SUBMITTED NOT NUMERIC 0 0602 INCORRECT TRANSACTION COUNT/HEADERS NOT EQUAL 0 0901 TRANS TYPE NOT "1", "2", "3", "4", "5", "6", "7", "8" 0 0903 POLICY STATUS IS NOT CANCELED 0 0904 UNPAID AMOUNT EQUALS ZERO - NO NEED TO CLEAR 0 0905 INVALID BIND TXN - POLICY STATUS ALREADY ACTIVE 0 1001 TRANSACTION EFFECTIVE DATE NOT A VALID DATE 0 1002 INVALID TIME LAPSE 0 1003 CANC EFF DATE NOT EQUAL TO PLCY EFF DATE FOR ADV CANCEL 0 1004 CANC EFF DTE MUST BE BTWN PLCY EFF AND EXP DATES 0 1005 PLCY ALREADY IN ADVANCE CANCEL STATUS 0 1006 PLCY HIST FOR ADVANCE CANCEL NOT FOUND 0 1007 TXN EFFECTIVE DATE MUST EQUAL ADV CANCEL DATE 0



ERROR DESCRIPTION COUNT 1101 POLICYHOLDER LICENSE NUMBER BLANK OR INVALID 0 1102 POLICYHOLDER LIC NUMB NOT FOUND ON RMV DATA BASE 0 1103 COMMERCIAL POLCY MAY NOT BE ENTRED BEF 8/15/97/EFF DATE OF 10/01/97 OR LATER 0 1104 COMMERCIAL POLICIES MUST BE ENTERED IN THE NEW RECORD FORMAT 0 1105 FID NUMBER MUST FOLLOW FEDERAL GUIDELINES 0 1106 FID NUMBER NOT FOUND ON RMV DATABASE 0 1107 FID NOS.777777777 AND 999999999 MAY NOT BE USED. MUST SPECIFY A VALID FID 0 1201 POLICYHOLDER LICENSE STATE BLANK OR INVALID 0 1301 POLICYHOLDER SURNAME BLANK OR INVALID 0 1302 PLICYHOLDER SURNAME DOESN'T MATCH SURNAME ON RMV DB 0 1303 FID FOUND ON RMV DATABASE BUT NAME DOES NOT MATCH 0 1304 CORPORATE NAME IS INVALID 0 1401 POLICYHOLDER FIRST NAME BLANK OR INVALID 0 1501 POLICYHOLDER DATE OF BIRTH NOT A VALID DATE 0 1502 ZIP CODE IS MISSING OR INVALID 0 1503 POLICYHOLDER D.O.B. DOES NOT MATCH D.O.B. ON RMV DATABASE 0 2003 INVALID VEHICLE ACTION CODE 0 2101 VIN BLANK OR INVALID 0 2102 VEHICLE NOT FOUND ON RMV DATA BASE 0 2103 VEHICLE NOT CONNECTED TO POLICY ON RMV DATABASE 0 2104 VEHICLE ALREADY ADDED TO POLICY ON RMV DATABASE 0 2105 NO MATCH FOR REGISTRATION OR OWNER INFO ON RMV DATABASE 0 2106 VEHICLE ALREADY DELETED FROM POLICY ON RMV DATABASE 0 2202 VEHICLE YEAR NOT A VALID YEAR 0 2204 VEHICLE MAKE IS BLANK OR INVALID 0 2401 VEHICLE PREM TOWN CODE NOT VALID 0 2601 CURRENT REGISTRATION NUMBER REQUIRED FOR VEHICLE 0 2801 VEHICLE OWNER TYPE BLANK OR INVALID 0 2901 VEHICLE OWNER LICENSE NUMBER BLANK OR INVALID 0 2902 VEHICLE OWNER FID IS INVALID. VEHICLE OWNER INFO IS STORED IN RESPONSE RECORD 0 3001 VEHICLE OWNER LIC STATE NOT A VALID STATE CODE 0 3101 VEHICLE OWNER SURNAME BLANK OR INVALID 0 3102 VEHICLE OWNER NAME IS INVALID. VEHICLE OWNER INFO IS STORED IN RESPONSE RECORD 0 3201 VEHICLE OWNER FIRST NAME BLANK OR INVALID 0 3301 VEHICLE OWNER DATE OF BIRTH NOT A VALID DATE 0 3302 VEHICLE OWNER ZIP COD IS INVALID. VEH OWN INFO IS STORED IN RESPONSE RECORD 0 3401 NOWN NAME BLANK OR INVALID 0 4001 CANCEL/REINSTATE/CLEAR REASON CODE IS BLANK OR INVALID 0 4101 UNPAID DOLLAR AMOUNT IS BLANK OR NOT NUMERIC 0 5001 BINDER TRANSACTION REFERENCE NUMBER IS BLANK OR INVALID 0 5002 BINDER TRANSACTION REFERENCE NUMBER IS NOT ON RMV DATABASE 0 9901 RELATED TRANSACTION IN ERROR 0 9902 MAXIMUM ERRORS EXCEEDED 0 9903 DUPLICATE RECORDS SUBMITTED 0 9999 UNKNOWN ERROR CODES 0



Appendix F UMS Batch Date Codes

This appendix contains a list of Date Edits by transaction type for UMS. Each transaction type is accompanied by examples that clarify the transaction.

Appendix F - UMS Batch Date Edits F-1


New Business Transaction: Transaction Code 1

Maximum number of days allowed after transaction effective date before commencement of revocation action: 23 days

Maximum number of days in advance that one can submit a transaction: 90 days

RMV system date: 05/01/97

Policy effective dates: 06/20/97 - 06/20/98

Insurance company transaction effective dates: 06/20/97

Expected results: Accepted




Expected results: Rejected

Bind Verification Transaction: Transaction Code 2

Maximum number of days allowed after bind effective date: 90 days

Maximum number of days in advance that one can submit a transaction: 90 days











Policy Renewal Transaction: Transaction Code 3 Transaction should be submitted within 23 days or revocation action will commence (only if a cancelled policy is on file at the RMV).

Maximum number of days in advance that you can submit a transaction: 90


The policy effective dates: 05/20/97 - 05/20/98

The insurance company transaction effective date: 05/20/97






Policy Amend Transaction: Transaction Code 4 (adding or deleting a vehicle)

Vehicle Action code: 1 (Add) or 2 (Delete)

Maximum number of days that you can submit a transaction after the transaction effective date: Any valid dates within a valid policy’s effective period.

Maximum number of days in advance that you can submit a transaction: NA







Policy Cancellation Transaction: Transaction Code 5 Transaction should be submitted on the date that the cancellation took effect.

Maximum number of days in advance that you can submit a transaction: Any valid dates between a valid policy’s effective date and expiration date. However, the advance cancellation of a future insured policy must be the same date as the policy effective date.



The insurance company cancellation effective date: 06/01/97
















Policy Reinstatement Transaction: Transaction Code 6

Maximum number of days that you can submit a transaction after the transaction effective date: 23 After 23rd day registration status is ACTV/INSC.

Maximum number of days in advance that you can submit a transaction: You must make the reinstatement date the same date as the cancellation date.


The cancellation date: 04/30/97

The insurance company reinstatement effective date:04/30/97


Clear and Amend Unpaid Premiums Transaction: Transaction Code 7

Maximum number of days that you can submit a transaction after the transaction effective date: You can submit a request to clear an unpaid premium up to 3 years after the policy cancellation date.

Maximum number of days in advance that you can submit a transaction: N/A


The cancellation date: 05/01/97



Policy Inquiry Transaction: Transaction Code 8

Maximum number of days that you can submit a transaction after the transaction effective date: At any time while the policy exists on the system.

Maximum number of days in advance that you can submit a transaction: N/A

You can submit a policy inquiry transaction at any time as long as the policy exists on UMS.







Appendix G U.S. State, Canadian Province &

Mexican County Codes

This appendix contains a list of U. S. Postal Service codes (abbreviations) for states, Canadian provinces, and Mexican counties.

Appendix G - STATES, PROVINCES & MEXICAN COUNTIES G-1

&


U. S. STATE CODES

STATE CODE STATE CODE STATE CODE

ALABAMA AL KENTUCKY KY NORTH DAKOTA ND

ALASKA AK LOUISIANA LA OHIO OH

ARIZONA AZ MAINE ME OKLAHOMA OK

ARKANSAS AR MARYLAND MD OREGON OR

CALIFORNIA CA MASSACHUSETTS MA PENNSYLVANIA PA

COLORADO CO MICHIGAN MI RHODE ISLAND RI

CONNECTICUT CT MINNESOTA MN SOUTH CAROLINA SC

DELEWARE DE MISSISSIPPI MS SOUTH DAKOTA SD

DITRICT OF COLUMBIA DC MISSOURI MO TENNESSEE TN

FLORIDA FL MONTANA MO TEXAS TX

GEORGIA GA NEBRASKA NE UTAH UT

HAWAII HI NEVADA NV VERMONT VT

IDAHO ID NEW HAMPSHIRE NH VIRGINIA VA

ILLONOIS IL NEW JERSEY NJ WASHINGTON WA

INDIANA IN NEW MEXICO NM WEST VIRGINIA WV

IOWA IA NEW YORK NY WISCONSIN WI

KANSAS KS NORTH CAROLINA NC WYOMING WY

CANADIAN PROVINCE CODES

PROVINCE CODE PROVINCE CODE PROVINCE CODE

ALBERTA AB NEW BRUNSWICK NBK PRINCE EDWARD IS. PE

BRITISH COLUMBIA BC NOVA SCOTIA NS QUEBEC PQ

NEWFOUNDLAND NORTHWEST SASKATCHEWAN SK LABRADOR NFLD TERRITORIES NT YUKON TERR. YT MANITOBA MB ONTARIO ON



MEXICAN COUNTIES

COUNTY CODE

AGUASCALIENTES AG BAJA CALIFORNIA BA BAJA CALIFORNIA SUR BJCAMPECHE CM CHIAPAS CL CHIHUAHUA CH COAHUILA DE ZARAGOZA CU COLIMA CL DISTRITO FEDERAL DF DURANGO DO GUANAJUATO GT GUERRERO GR HIDALGO HL JALISCO JL MEXICO MX MICHOACAN DE OCAMPO MC MORELOS MR NAYARIT NA NUEVO LEON NL OAXACA OA PUEBLA PB QUERETERO DE ARTEAGA QU QUINTANA ROO QR SAN LUIS POTOSI SLI SINALOA SL SONORA SO TABASCO TB TAMAULIPAS TA TLAXCALA TL VERACRUZ-LLAVA VC YUCATAN YU ZACATECAS ZA OTHER JURISDICTIONS OT



Appendix H Registration Data File Record

Layout

This appendix describes the format of the Registration Data File Record Layout sent back to insurance companies.

Appendix H – Registration Data File Record Layout H-1

Field

PICTURE

relevant info


REGISTRATION DATA FILE RECORD LAYOUT

Position

null value

1-3 lNS-CO-CODE PIC 9(03) none

4-19 POLICY-ID PIC X(16) spaces

20-27 POLICY DATE-EFFECTIVE PIC X(08) MMDDYYYY low-val

28-35 POLICYDATE-EXPIRE PIC X(08) MMDDYYYY low-val

36-44 PLCY-OWNR-LICENSE PIC X(09) spaces

45-47 REG-PLATE-TYPE PIC X(03) none

48-54 PLATE-NUMBER PIC X(07) none

55 OWNER-TYPE-IND PIC X(01) 1=PERSON 2=CORP.

none

56-64 REG-OWNR-LICENSE PIC X(09) spaces

65-76 REG-OWNR-FIRST-NAME PIC X(12) spaces

77-92 REG-OWNR-LAST-NAME PIC X(16) spaces

93 REG-OWNR-MIDDLE-INIT PIC X(01) spaces

94-101 REG-OWNR-birth-date PIC X(08) spaces

102-121 OWNER-NAME PIC X(20) FILLED information spaces

OWNER- TYPE -IND = 2

l22-130 FEDERAL-ID PIC X(09) spaces

l31-147 VIN PIC X(17) spaces

148-151 YR-OF-MANUFACTURE PIC 9(04) 0000

152-156 MAKE PIC X(05) spaces

157-162 MODEL PIC X(06) spaces

163-171 REG-OWNR-ZIP-CODE PIC 9(09) spaces

172-172 POLICY TYPE PIC X(01) P or C spaces

173-173 POLICY HOLDER TYPE PIC 9(01) 1=PERSON 2=CORP.

spaces

Appendix H – Registration Data File Record Layout H-2


Appendix I Registration File Submittal

Form

This form shown on the following page should be used by an insurance company when submitting a file data transfer to the RMV for processing.

Appendix I - Form for File Submittal by Insurance Company I-1

ums batch manual - mass.gov manual.pdf · 3. work with patricia bennett to send in some test data...

Documents