New York Codes, Rules and Regulations › Title 15 - Department of Motor Vehicles › Chapter I - REGULATIONS OF THE COMMISSIONER › Subchapter C - INSURANCE › Part 34 - Motor Vehicle Liability Insurance Reporting › Section 34.2 - Definitions and general requirements

Current through Register Vol. 46, No. 28, July 10, 2024
(a) Batch processing. A daily
				  DMV operation that includes the attempted matching to department registration
				  records of notices received by the department from insurance companies or servicing
				  agents. A notice matched to an individual registration record results in the posting
				  of information (data elements) from such notice to DMV's insurance information
				  database.
(b) DBA (doing business as). A
				  DBA most commonly involves an individual conducting business or trading under an
				  assumed name. For purposes of this Part a DBA name is treated as an organization
				  name. DBA may also apply to a corporate entity doing business under an assumed
				  name.
(c) DMV initiated verification
				  transaction report. A weekly and periodic report prepared by the department for an
				  insurance company. An insurance company shall obtain the report from a department
				  web site during the time period that the report is published. Except for manual
				  submissions for dealer and transporter registrations, such report shall contain the
				  following information: date of report; begin and end date of report; total number of
				  days in reporting period; insurance company and servicing agent codes and names;
				  total number of verification transactions (mandatory and negative); and total number
				  of and percentage of insurer responses. Upon receipt of notification from the
				  department that DMV initiated mandatory verification (MVF) transactions are not
				  being responded to or are not being responded to in a timely manner as required by
				  this Part, an insurance company or servicing agent shall take immediate steps to
				  determine the reasons for such performance, formulate a remediation plan to correct
				  the deficiencies and fully implement such remediation plan to eliminate
				  non-responses to MVF transactions and non-timely responses to MVF transactions
				  submitted to the department.
(d) EDI.
				  Electronic data interchange. The electronic transfer of business documents from one
				  computer application to another computer application in a prescribed format using
				  translation software. Insurance companies and servicing agents shall utilize
				  commercial translator/mapping software to send transactions to and receive
				  transactions from DMV.
(e) Edit error
				  (EDI translator). A notice submitted by an insurance company or servicing agent
				  unacceptable for filing purposes because the EDI file format or segments (group of
				  data elements) within the EDI file are not compliant with DMV's EDI specifications.
				  DMV translator error scenarios:
(1) required
				  segments are missing;
(2) required data
				  elements are missing; and
(3) data
				  elements are invalid, e.g., incorrect number of characters, incorrect value
				  according to specifications, etc.
Such notice is not matched to a department registration record,
					 is not posted to DMV's insurance information database and is not a filing. Upon
					 receipt of notice from the department of edit errors, an insurance company or
					 servicing agent shall take immediate steps to determine the reason(s) for edit
					 errors, formulate a remediation plan to correct deficiencies and fully implement
					 such remediation plan to eliminate edit errors from its submissions to the
					 department. An insurance company or servicing agent shall resubmit a corrected
					 notice to the department, as prescribed by this Part, unless its submission is not
					 required by law, this Part or DMV MVLIR specifications.