Loading
The Oregon Administrative Rules contain OARs filed through August 15, 2014
 
QUESTIONS ABOUT THE CONTENT OR MEANING OF THIS AGENCY'S RULES?
CLICK HERE TO ACCESS RULES COORDINATOR CONTACT INFORMATION

 

DEPARTMENT OF CONSUMER AND BUSINESS SERVICES,
WORKERS' COMPENSATION DIVISION

 

DIVISION 162

ELECTRONIC DATA INTERCHANGE; PROOF OF COVERAGE

436-162-0001

Authority for Rules

These rules are promulgated under the director's authority contained in ORS 656.726(4).

Stat. Auth: ORS 656.264, 656.726(4)
Stats. Implemented: ORS 656.017, 656.407, 656.419, 656.423, 656.427
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0002

Purpose

The director’s purpose is to require workers’ compensation proof of coverage reporting via electronic data interchange.

Stat. Auth: ORS 656.264, 656.726(4)
Stats. Implemented: ORS 656.017, 656.407, 656.419, 656.423, 656.427
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0003

Applicability of Rules

(1) These rules apply to workers’ compensation related transactions filed with the director via electronic data interchange on or after the effective date of these rules.

(2) The director may waive procedural rules as justice requires, unless otherwise obligated by statute.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.726(4)
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0004

Adoption of Standards

The director adopts, by reference, IAIABC EDI Implementation Guide for Proof of Coverage, Release 2.1, dated July 1, 2010, including the definition of standards and procedures, unless otherwise provided in these rules. Copies of the guide are available from the IAIABC website: http://www.iaiabc.org/i4a/pages/index.cfm?pageid=3339.

Stat. Auth: ORS 656.264
Stats. Implemented: ORS 656.017, 656.407, 656.419, 656.423, and 656.427
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0005

General Definitions

For the purpose of these rules, unless it conflicts with statute or rule:

(1) “ANSI” means the American National Standards Institute.

(2) "Conditional data element" means an element that becomes mandatory under certain conditions. Once mandatory, a conditional data element will cause a rejection of the transaction if the data element is omitted or submitted in a format not capable of being processed by the division’s information processing system.

(3) "Director" means the Director of the Department of Consumer and Business Services or the director's designee for the matter.

(4) "Division" means the Workers' Compensation Division of the Department of Consumer and Business Services.

(5) "Electronic Data Interchange" or "EDI" means a computer to computer exchange of information in a standardized electronic format.

(6) "Electronic Record" means information created, generated, sent, communicated, received, or stored by electronic means.

(7) “Establishing document” means an EDI transaction that reports coverage for one or more entities. Establishing document types may include binders, new policies, rewrite/reissue transactions, renewals, reinstatements, add jurisdiction endorsements, or add employer/location endorsements.

(8) "FEIN" means the federal employer identification number or other federal reporting number used by the insurer, insured, or employer for federal tax reporting purposes.

(9) "Header record" means the record that precedes each transmission for the purpose of identifying a sender, the date and time of the transmission, and the transaction set within the transmission.

(10) "IAIABC" means the International Association of Industrial Accident Boards and Commissions, a professional trade association comprised of state workers' compensation regulators and insurance representatives (www.iaiabc.org).

(11) "Information" means data, text, images, sounds, codes, computer programs, software, databases, or the like.

(12) "Industry code" means the code which indicates the nature of the employer's business, which is contained in the Standard Industrial Classification (SIC) manual published by the Federal Office of Management and Budget, or in the North American Industrial Classification System (NAICS) published by the U.S. Census Bureau.

(13) "Insurer" means the State Accident Insurance Fund Corporation; an insurer authorized under ORS chapter 731 to transact workers' compensation insurance in Oregon; or a self-insured employer.

(14) "Mandatory data element" means an element that will cause a rejection of a transaction if the data element is omitted or submitted in a format not capable of being processed by the division's information processing system.

(15) "Optional data element" means an element that an insurer should report to the director if the information is available to the insurer. Optional data elements will not cause a rejection if missing or invalid.

(16) "Proof of coverage" means an electronic record or set of records identifying an insurer as providing workers' compensation coverage for a specific employer.

(17) "Record" means electronic record.

(18) “Reprocessed transaction” means a rejected transaction that, at the discretion of the director, has been reprocessed and accepted by the division.

(19) "Sender" means the person or entity reporting electronic data interchange transactions to the division. Sender may include vendors or insurers.

(20) "Trading partner agreement" means the agreement entered into under OAR 436-162-0020 between the director and an insurer to conduct transactions via EDI.

(21) "Trailer record" means the record that designates the end of a transmission and provides a count of transactions contained within the transmission, not including the header and trailer records.

(22) "Transaction" means a set of EDI records, defined according to standards in OAR 436-162-0004.

(23) "Transmission" means a defined set of transactions, including both header and trailer records to be sent to the division or sender via EDI.

(24) "Vendor" means an agent identified by the insurer to submit transmissions to the division on behalf of an insurer. Vendors may include service companies, third party administrators, and managing general agents.

Stat. Auth: ORS 656.264 and 656.726(4)
Stats. Implemented: ORS 84.004, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0006

Administration of Rules

Orders issued by the division in carrying out the director's authority to enforce ORS chapter 656 are considered orders of the director.

Stat. Auth: ORS 656.704, 656.726(4)
Stats. Implemented: ORS 656.704, 656.726(4)
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0010

Security

(1) The sender must verify that an electronic signature, record, or performance is that of a specific person.

(2) The sender must utilize anti-virus software to eliminate any viruses on all electronic transmissions. The sender must maintain the anti-virus software with the most recent anti-virus update files from the software provider. The sender must notify the director immediately if a virus is detected.

Stat. Auth: ORS 656.264, 656.726(4)
Stats. Implemented: ORS 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0020

Trading Partner Agreement

(1) If the director so requires, an insurer must enter into a trading partner agreement with the director before the division will begin testing with or accept production electronic transmissions from the insurer or from a vendor on behalf of that insurer.

(2) The trading partner agreement will include:

(a) A statement that the insurer will remain responsible and liable for all electronic records transmitted to the director;

(b) Transmission protocol between sender and director;

(c) A specific description of the form, format, and delivery of electronic transmissions under OAR 436-162-0004 and 436-162-0050;

(d) Specific identifying information for insurer, third party administrator, if any, and vendor, if any;

(e) Cost allocation of transactions, if any;

(f) The time frame for the director to submit acknowledgements of transmissions; and

(g) Any other necessary statements, conditions, or requirements to facilitate EDI.

Stat. Auth: ORS 656.264, 656.726(4)
Stats. Implemented: ORS 84.013, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0030

Retention of Electronic Records

Insurers and self-insured employers must retain workers' compensation records under OAR 436-050-0120 and OAR 436-050-0220. Records may be retained in electronic format if the records can be reproduced.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.455, 731.475
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0040

Recognized Filing Date

(1) Unless otherwise stated in the trading partner agreement, an electronic record is sent when it:

(a) Is addressed or directed properly to an information processing system designated or used by the division to receive electronic records or information;

(b) Is in a form and format capable of being processed by that system; and

(c) Enters an information processing system outside the control of the sender or enters a region of the information processing system designated or used by the division and that is under control of the division.

(2) Unless otherwise stated in the trading partner agreement an electronic record is received when it:

(a) Enters an information processing system designated or used by the division to receive electronic records or information of the type sent and from which the division is able to retrieve the electronic record; and

(b) Is in a form and format capable of being processed by the division's information processing system.

(3) For the purpose of these rules, an electronic transaction is capable of being processed by the division's information processing system when all the required data elements are in the form and format specified in these rules, in the proper sequence, and in accordance with the terms of the trading partner agreement.

(4) A reprocessed transaction retains the filing date of the original transaction.

Stat. Auth: ORS 656.264, 656.726(4)
Stats. Implemented: ORS 84.043, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0050

Form, Format, and Delivery for Electronic Data Reporting

The form, format, and delivery of data elements and definitions will conform to the standards specified in OAR 436-162-0004, or as otherwise identified in the trading partner agreement.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 84.013, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0060

Testing Procedures and Requirements

Proof of coverage testing:

(1) The director adopts the Oregon EDI Implementation Guide for Proof of Coverage as the standard for EDI testing procedures and requirements, available from the division’s website: http://www.cbs.state.or.us/wcd/operations/edi/ediindex.html#bill.

(2) Senders conducting EDI transactions as of Jan. 1, 2009, do not have to complete EDI testing. Insurers using an approved EDI vendor to submit proof of coverage data to the department do not have to complete testing as provided by this rule.

(3) Senders must obtain director approval to submit proof of coverage data via EDI transactions. Each sender must successfully complete the Secure File Transfer Protocol (SFTP) test and the format and structure test(s) detailed in the Oregon EDI Implementation Guide for Proof of Coverage to demonstrate ability to successfully transmit coverage data in the format specified in OAR 436-162-0004. The director will notify senders once they have successfully completed testing. Insurers must either use an approved sender or be approved as a sender to report proof of coverage via EDI. If an insurer is not an approved sender, it must report through an approved sender until approved by the director for direct reporting of proof of coverage via EDI.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 84.013, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0070

Electronic Signature

The sender’s federal employer identification number (FEIN) plus its postal code as reported in the header record and stated in the trading partner agreement, if such an agreement is required, is the unique identifier that is the electronic signature for electronic data interchange.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 84.001-84.061, 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0090

Address Reporting

The sender will follow the standard United States Postal Service guidelines in reporting all addresses.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264
Hist.: WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0300

Establishing Document Transaction

For policies effective before July 1, 2009, the establishing document transaction types listed in OAR 436-162-0350(3)(c) can be used to file a guaranty contract under that rule. For policies effective on or after July 1, 2009, the establishing document transaction types listed in OAR 436-162-0355(2)(b) can be used to file proof of coverage. In Oregon, a reinstatement, an add location, and an add employer transaction type can also be an establishing document. A change policy number transaction type is not an establishing document.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.419, 656.423 and 656.427
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0300, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0310

Electronic Filing Requirements

(1) The chart in Appendix "A" shows all proof of coverage data elements accepted via EDI in Oregon, and whether the data element is mandatory (M), conditional (C), or optional (O) for each transaction type.

(2) Unless otherwise provided in these rules, the data elements shall have the meaning provided in the data dictionary of the IAIABC EDI Implementation Guide for Proof of Coverage, Release 2.1, dated July 1, 2010, referenced in OAR 436-162-0004.

(3) Transactions will be rejected if mandatory or required conditional data elements are omitted or submitted in a format that is not capable of being processed by the division's information processing system designated for proof of coverage transactions.

(4) Optional data element(s) in a transaction will be ignored if the optional data element is either omitted, or submitted in a format that is not capable of being processed by the division's information processing system designated for proof of coverage transactions.

(5) Unless otherwise provided in these rules, an insurer must transmit proof of coverage via EDI. Insurers may not submit paper documents to the director without the director’s express permission or as provided in OAR 436-162-0350(7).

(6) Changes or corrections to proof of coverage transactions must be filed within 30 days of insurer knowledge of the change to a required data field.

(7) Professional employee organization (PEO) policies will be accepted via EDI, subject to the same data and transaction editing standards as other policies. A policy filing for a PEO does not eliminate the PEO’s requirement to file worker leasing notices under OAR 436-050-0410.

(8) Wrap-up policies will be accepted via EDI, subject to the same data and transaction editing standards as other policies.

[ED. NOTE: Appendix referenced is not included in rule text. Click here for PDF of appendix.]

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; WCD 3-2009, f. 12-1-09, cert. ef. 1-1-10; Renumbered from 436-160-0310, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0320

Acknowledgement

(1) The division will respond to submitted transmissions with either a transaction accepted or a transaction rejected acknowledgement. The division may, at its discretion, reprocess transactions.

(2) A transaction rejected acknowledgement will be sent for all transactions incapable of being processed by the division’s information processing system, including, but not limited to:

(a) An omitted mandatory data element;

(b) An improperly populated data element field, e.g., numeric data element field is populated with alpha or alphanumeric data, or is not a valid value;

(c) Transactions or electronic records within the transaction which require matching and cannot be matched to the division's database;

(d) Illogical data in mandatory or required conditional field, e.g., termination date is before coverage effective date;

(e) Duplicate transmission or duplicate transaction within the transmission;

(f) Invalid triplicate code; or

(g) Illogical event sequence relationship between transactions, e.g., endorsement transaction submitted before a policy transaction is submitted.

(3) The insurer must correct and resubmit any transactions rejected for which law or rule require filing, reporting, or notice to the director.

(4) Insurers are not required to resubmit reprocessed transactions.

(5) A transaction accepted acknowledgement will be sent for all transactions that are in a format capable of being processed by the division's information processing system and are not rejected pursuant to section (2) of this rule.

(6) An insurer’s obligation to file proof of coverage for the purposes of this rule is not satisfied unless the director acknowledges acceptance of the transaction.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0320, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0330

Effective Dates

(1) For policies with effective dates before July 1, 2009:

(a) For all binder or new policy establishing document transactions submitted under OAR 436-162-0350, the coverage effective date will also be the guaranty contract effective date.

(b) For all other establishing document transactions that meet the guaranty contract filing requirements of OAR 436-162-0350, the transaction set type effective date will also be the guaranty contract effective date.

(c) The policy expiration date submitted on a transaction does not terminate liability under a guaranty contract. Liability under a guaranty contract filed by an insurer continues until it is terminated under OAR 436-162-0360 and ORS 656.423 or 656.427.

(2) For policies with effective dates on or after July 1, 2009:

(a) For binder or new policy establishing document transactions, the policy effective date will also be the effective date of the proof of coverage for the reported entity.

(b) For all other establishing document transactions, the transaction set type effective date will also be the effective date of the proof of coverage for the reported entity.

(3) For reinstatement transactions the transaction set type date will determine whether the transaction reinstates the guaranty contract or reinstates proof of coverage shown by the reinstated policy. Transaction effective dates before July 1, 2009, will reinstate the guaranty contract, which will remain in effect until renewed, replaced by new coverage, or terminated by the insurer. Transaction effective dates on or after July 1, 2009, will reinstate the director’s required proof of coverage through the reinstated policy, which will remain in effect until the policy expiration date or the date of cancellation, whichever is earlier.

(4) For all other transactions, the effective date will be the transaction set type effective date.

(5) For reissue, renewal, reinstatement, or endorsement transactions, the transaction effective date will be the transaction set type effective date submitted by the insurer.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264, 656.419, 656.423 and 656.427
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0330, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0340

Changes or Corrections

(1) Changes or corrections to proof of coverage information must be submitted pursuant to the standards referenced in OAR 436-162-0004.

(2) To report changes or corrections of an insured employer's name or address, or other data elements, the insurer must transmit the appropriate transaction to specify what data is being changed or corrected.

(3) The insurer's policy number is used to assist in matching each transaction to the appropriate employer. When an insurer changes a policy number, the insurer must report that change with or prior to the next transaction submitted for that policy. Failure to report a change in the policy number will render future filings incapable of being processed by the division's information processing system and the insurer will receive a transaction rejected acknowledgement.

(4) If changing a partner name of an insured or employer does not change the entity, a new guaranty contract or policy proof of coverage does not need to be filed.

(5) To add or delete coverage for corporate officers, members of a limited liability company, partners, sole proprietors, or other non-subject workers, the insurer must file the appropriate “include” or “exclude” endorsement transaction to the associated policy filing.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264 and 656.419
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 1-2008, f. 6-13-08, cert. ef. 7-1-08; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; WCD 3-2009, f. 12-1-09, cert. ef. 1-1-10; Renumbered from 436-160-0340, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0350

Guaranty Contract Filing Requirements

(1) This rule applies to coverage effective before July 1, 2009.

(2) For the purpose of these rules, an electronic guaranty contract consists of an executed trading partner agreement containing the guaranty described in subsection (3)(a) of this rule, and an accepted proof of coverage insured and employer electronic record.

(3) An insurer may file a guaranty contract via EDI by:

(a) Entering into a trading partner agreement with the director under OAR 436-162-0020 that contains a statement of assumption of liability and guaranty of payment under ORS 656.419(1);

(b) Transmitting an electronic record of the proof of coverage data elements identified as mandatory or required conditional under OAR 436-162-0310, including a unique FEIN for each legally distinct employer included in the establishing document transaction; and

(c) Transmitting an establishing document transaction: binder, new policy, renew policy, rewrite/reissue policy, reinstatement, add location, add employer, or add jurisdiction. A renew policy, add location, or add employer transaction will only establish a guaranty contract if the data elements have not previously been transmitted, the employer FEIN is not a duplicate per section (4) below, and coverage for that unique employer FEIN has not been previously established by the reporting carrier. A reinstatement transaction will only establish a new guaranty contract if there is a lapse in coverage and the requirements of ORS 656.419 and OAR 436-162-0350 are otherwise met.

(4) A duplicate FEIN or a FEIN previously reported under the same policy will be recorded as an additional employer location or an assumed business name, but will not establish an additional guaranty contract for effective dates of coverage before July 1, 2009.

(5) Reinstatement, rewrite, and reissue transaction types must follow a cancellation transaction.

(6) If an employer elects to include any non-subject worker(s) under coverage, or subsequently to exclude such workers from coverage, the insurer must submit a transaction with a reason code for including or excluding a corporate officer, partner, member, sole proprietor, or any other person.

(7) Insurers not approved to file guaranty contract information via EDI by Dec. 31, 2008, must continue to file changes to existing guaranty contracts via paper on or after July 1, 2009.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264, 656.419, 656.423, 656.427
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 1-2008, f. 6-13-08, cert. ef. 7-1-08; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; ; Renumbered from 436-160-0350, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0355

Proof of Coverage Filing Requirements

(1) This rule applies to coverage effective on or after July 1, 2009.

(2) An insurer may file proof of coverage via EDI by:

(a) Transmitting an electronic record of the proof of coverage data elements identified as mandatory or required conditional under OAR 436-162-0310, including a unique FEIN for each legally distinct employer included in the establishing document transaction; and

(b) Transmitting an establishing document transaction: binder, new policy, renew policy, rewrite/reissue policy, reinstatement, add location, add employer, or add jurisdiction.

(3) Reinstatement, rewrite, and reissue transaction types must follow a cancellation transaction.

(4) If an employer elects to include any non-subject worker(s) for coverage, or subsequently to exclude such workers from coverage, the insurer must submit a transaction with a reason code for including or excluding a corporate officer, partner, member, sole proprietor, or any other person.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264, 656.419, 656.423, 656.427
Hist.: WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0355, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0360

Guaranty Contract Terminations

(1) For the purposes of EDI, to terminate a guaranty contract when an insurer receives written notice of cancellation of coverage from an employer pursuant to ORS 656.423, the insurer must:

(a) Provide notice to the director no more than ten calendar days after the effective date of termination by transmitting the transaction type for cancellation by insured or nonrenewal by insured. The “transaction effective date” will be used to report the effective date of termination under ORS 656.423 or ORS 656.427;

(b) Retain the employer's written notice for inspection by the division; and

(c) Provide written notice to the employer under ORS 656.423 or ORS 656.427(1) and (3), if required.

(2) For the purposes of EDI, to terminate a guaranty contract for any other reason, the insurer must:

(a) Provide notice to the director no more than ten calendar days after the effective date of termination by transmitting the transaction type for cancellation, nonrenewal, or delete jurisdiction; and

(b) Provide written notice to the employer under ORS 656.423 or ORS 656.427(1) and (3), if required.

(3) The date of termination must be included in the written notice to the employer to terminate a guaranty contract. For the purposes of notice to the director, the transaction effective date is the termination effective date.

(4) A delete location transaction can be used to notify the director that one or more locations for an employer are no longer workplaces of the employer. This transaction does not meet the requirements of ORS 656.423 or ORS 656.427 for notice of termination.

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264, 656.419, 656.423 and 656.427
Hist.: WCD 3-2003, f. 3-18-03, cert. ef. 4-1-03; WCD 12-2003, f. 12-4-03, cert. ef. 1-1-04; WCD 1-2008, f. 6-13-08, cert. ef. 7-1-08; WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0360, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

436-162-0370

Proof of Coverage Terminations

For policies effective on or after July 1, 2009, to report a cancellation of a policy before the expiration of the policy term, the insurer must:

(1) Provide notice to the director no more than ten calendar days after the effective date of cancellation by transmitting the transaction type for cancellation, delete jurisdiction, or delete location(s). The “transaction set type effective date” will be used to report the effective date of cancellation under ORS 656.423 or 656.427;

(2) Retain a record of the written notice sent to the employer under ORS 656.427 for inspection by the division; and

(3) Provide written notice to the employer under ORS 656.427(1) and (3).

Stat. Auth: ORS 656.726(4)
Stats. Implemented: ORS 656.264, 656.419, 656.423, 656.427
Hist.: WCD 4-2008, f. 9-17-08, cert. ef. 7-1-09; Renumbered from 436-160-0370, WCD 7-2010, f. 10-1-10, cert. ef. 1-1-11

The official copy of an Oregon Administrative Rule is contained in the Administrative Order filed at the Archives Division, 800 Summer St. NE, Salem, Oregon 97310. Any discrepancies with the published version are satisfied in favor of the Administrative Order. The Oregon Administrative Rules and the Oregon Bulletin are copyrighted by the Oregon Secretary of State. Terms and Conditions of Use

Oregon Secretary of State • 136 State Capitol • Salem, OR 97310-0722
Phone: (503) 986-1523 • Fax: (503) 986-1616 • oregon.sos@state.or.us

© 2013 State of Oregon All Rights Reserved​