Proof of Coverage Data

Note: CAOM is currently not onboarding new POC carries until further notice. Please contact poc@caom.com with any questions.

ELECTRONIC PROOF OF COVERAGE OVERVIEW

In Michigan, carriers must file all:

  • Policy data with the Compensation Advisory Organization of Michigan (CAOM); and
  • Proof of Coverage (POC) data with the Michigan Workers Disability Compensation Agency (WDCA).  

Carriers must file with WDCA the following POC forms: WC-400 Insurer’s Notice of Issuance of Policy; WC-401 Notice of Termination of Liability; and WC-403 Insurer’s Notice of Name or Address Change. 

Carriers must file with CAOM all carrier policy data electronically in the Workers Compensation Policy Reporting Specifications (WCPOLS) format. 

For ease of doing business, carriers may seek CAOM’s assistance in electronically reporting a carrier’s POC data to WDCA. Once a carrier is approved for electronic POC reporting using CAOM’s free service, forms 400, 401 and 403 will be generated from the WCPOLS data submitted to CAOM, thus eliminating the need for the carrier to send these forms to WDCA. CAOM converts the WCPOLS data to the required IAIABC format and forwards it to WDCA. Transaction 06 (policy replacement due to a key field change) and Transaction 15 (policy replacement due to add/deleted state change), however, are not sent. The carrier is still required to file forms directly to WDCA for those transactions.

Because CAOM and WDCA are two different entities, each has separate reporting requirements that must be satisfied in order for CAOM to successfully report a carrier’s POC data to WDCA. 

Please refer to:

Contact WDCA to determine when they can work with you to get approved for electronic POC. When you are ready, CAOM can begin performing test POC edits on your WCPOLS data.

Communication among the carrier, CAOM and WDCA is essential and is detailed in the following sections.

CAOM – POC TEST PROCESS

Testing with CAOM for Electronic POC Reporting

Electronic POC reporting includes the following WCPOLS transactions:

  • Transaction Type Code 01 – New Policy
  • Transaction Type Code 02 – Renewal Policy
  • Transaction Type Code 05 – Cancellation / Reinstatement
  • Transaction Type Code 08 – Rating Change
  • Transaction Type Code 10 – Non-Rating Change
  • Transaction Type Code 14 – Miscellaneous Change/Non-Key Field Change

Carriers that want CAOM to electronically report their carrier POC data to the WDCA must follow specific steps:

1.  Policy Data Reconciliation between Carrier and WDCA (“Reconciliation”).

You must participate in a database cleanup effort with the WDCA in order to ensure all policy data filings are up-to-date, the correct Federal Employer Identification Number is being used, and the WDCA records are updated with the most current policy number. 

This step can occur any time during the testing process, however, it must be completed before approval is received.  Email LEO-WC-EDI-POC@michigan.gov to schedule reconciliation.  You are responsible for notifying CAOM when reconciliation is complete.

For details on the specific steps in the test plan with the WDCA, click here.

2. Carrier Compliance with WCPOLS Filing Guidelines.

Certain WCPOLS fields allow for more than one way to report data.  In order for CAOM to convert the WCPOLS data to the IAIABC format required by the WDCA, specific reporting requirements must be met.  See the Proof of Coverage-EDI Guide (michigan.gov) for details.

Certain valid WCPOLS data cannot be mapped to an acceptable record for the WDCA.  In these cases, the data will be rejected and sent back to you for correction and resubmission.  All corrections must be electronically resubmitted to CAOM.  Data that cannot be electronically corrected will require a paper filing to the WDCA.

3.  Carrier Testing with CAOM (“Test Phase”).

The purpose of this phase is to verify your WCPOLS data can be cleanly converted.  In Test, CAOM will provide you with a report of POC edits for every WCPOLS production file you submit.  The reports will show the errors that would not pass edits if you were in production (once in production, transactions that error would need to be corrected and resubmitted).  The reports will be stored on CAOM’s FTP server and will not be transferred to the WDCA.  This allows you to address certain issues before you begin testing with the WDCA.   

During testing, you will continue to submit regular production files for CAOM purposes.  Rejection for POC purposes does not equate to rejection for CAOM purposes or vice versa.

Issues that require significant WCPOLS programming changes must be tested with CAOM prior to implementing in production.  Failure to provide test submissions prior to moving upgrades into production can severely impact both you and CAOM.  You must make necessary entry and or system changes to meet POC requirements.  CAOM requires no more than a 5% error ratio in this phase before moving you to the next phase.  See the MI-POC-R30 Edit Matrix for more information. 

We highly recommend you include CAOM testing of WCPOLS data in your test plans.  Contact 734-462-9600 ext. 265 or poc@caom.com to arrange for WCPOLS testing.

4.  CAOM Testing with WDCA (“Certify Phase”).

When the WDCA is ready, it will request CAOM provide the IAIABC file on a test basis.  The WDCA will provide error and acknowledgement reports to CAOM and CAOM will forward those reports to you.  The reports will be stored on CAOM’s FTP server. 

You must successfully complete three consecutive submissions from CAOM to WDCA.

You will continue to file all required forms on paper with the WDCA during this phase.

5.  WDCA Approves Carrier for Production (“Production Phase”).

The WDCA will advise you and CAOM when you are approved for electronic POC.  All parties sign a Trading Partner (EDI) agreement.  The agreement specifies CAOM will electronically report a list of triplicate codes for POC to the WDCA on behalf of the insurance company(ies) named in the agreement.  Once production begins, you will discontinue separate paper filings to the WDCA for the approved transactions that pass the edits. 

All reports are deployed to CAOM’s FTP server which you will need to retrieve.  Let us know when you are ready so we can produce the reports.  A FEIN will be required for each carrier in the group that will be involved.


Retrieving of POC Error Reports

As part of the Proof of Coverage process, CAOM creates a report for each file CAOM receives.  These reports are stored on CAOM’s FTP server.  

Contact POC@caom.com for your user name and password.

The report files will be PDFs with the names of CAOMERROR and SOMACK with a timestamp on them.  You have only read access to those files.

We keep approximately 15 days of files on our web server in your primary folder.  

We suggest you use WS_FTP from Ipswitch.  CAOM uses WS_FTP Server from Ipswitch.  You can download and purchase the software at http://www.ipswitch.com/products/ws_ftp/index.asp.

If you want to just test the FTP Interface to our site you could use COREFTP, a shareware program that we have found works.

Other FTP programs may also work but CAOM will only support the above products.

Our FTP server requires SSH protocol.

WS_FTP supports synchronized folders.  By running on any server or workstation, it will regularly go out to our server and synchronize a folder on your network with the folder on our server.  When we add a file to the list, then only that file will be added onto your network folder.  When we delete a file from the list, then the sync program will delete the file from your network.  This is a very easy setup.

The file names have a timestamp on it in the format of mmddyyyyhhmmsstt with the guarantee that the timestamp is always 16 characters long.

If there are any technical questions, please contact POC team at poc@caom.com.

ACK Report Retrieval Schedule

Due to the increased volume of transactions, the current POC 3.0 ACK reports availability schedule is as follows:

  • CAOM sends POC to WDCA: 3:30 PM
  • CAOM receives ACK from WDCA: 1:00 AM – 3:00 AM next day
  • CAOM processes ACK: 6:00 AM
  • CAOM generates ACK Reports via report queue: 6:00 AM – 1:00 PM

The above schedule is subject to change. We will notify you of any change.

CAOM copies ACK Reports to the FTP server for Carrier access weekdays at 4:00 AM, 6:00 AM, 7:45 AM, 10:00 AM, 12:00 PM, 2:00PM and 4:00 PM.


WCA Carrier Test Plan

  1. Kickoff meeting with the carrier and CAOM to discuss overview of EDI. 
    • Carrier will supply the WDCA with the names, phone numbers and e-mail addresses of contact persons that will participate in the testing process.
    • WDCA will provide all supporting documentation to the carrier, including: 
    • Record layout for Policy Number Reconciliation (LW02592)
    • Record layout for Carrier Reconciliation (LW02601)
    • Record layout for Carrier Active Policies  (LW02401)
    • Sample of new report that will be generated if the provided policy number on a cancellation is found on the WDCA database but not all employers could be terminated.
    • Sample of Acknowledgment Report that the WDCA sends to CAOM.
    • WDCA will provide a spreadsheet outlining valid Triplicate Codes and their WCPOLS equivalents for carriers to indicate which transactions they want to file electronically.
    • Depending upon the Triplicate Codes the carriers intend to file, the carrier must be prepared to submit examples of the following scenarios correctly in WCPOLS to CAOM so they can be mapped to the IAIABC format:
      • Single FEIN policies
        • With multiple address records
        • With multiple name records 
      • Multiple FEIN policies
        • With multiple address records
        • With multiple name records for each FEIN
  2. Carrier clean-up.
    • Carrier sends Policy Number Reconciliation file (LW02592) to WDCA so database can be updated prior to reconciliation process.  
    • Carrier will submit Carrier Reconciliation file (LW02601) to WDCA.  
      • Inconsistent FEINs will be reconciled with the carrier.
      • If the report indicates an incorrect FEIN for an employer (based on the Department of Treasury records), the WDCA will generate e-mails to the carrier contact person to supply them with the correct FEINs. The carrier does not have to make corrected filings. They just have to make the corrections internally. If the carrier can supply proof that their FEIN is correct, the WDCA will accept their number.
      • If the FEIN cannot be confirmed (based on the Department of Treasury records), the WDCA will update their database with the FEIN supplied by the Carrier.
      • WDCA will generate e-mails to the carrier contact person indicating the process to reconcile all other errors. This might entail new or corrected filings or verification of information that must be completed timely.
      • The WDCA will identify the carrier’s common errors to the contact person. 
      • The carrier’s procedures may need to be adjusted to avoid these errors on future electronic filings.
      • The carrier must also resolve any outstanding correspondence issues with the WDCA. All letters from the WDCA should be resolved in a timely manner.
      • The above steps are repeated until the WDCA is satisfied that records are in sync and common errors have been resolved in both electronic and paper filings.
    • The WDCA will run Carrier Active Policies (LW02401) and send to carrier. 
      • Carrier will file terminations for any employer on the Carrier Active Policies report that they no longer insure. If the policy information is old and has been purged from the Carrier’s system, a termination should be submitted to flat cancel their issuance using the information on the Carrier Active Policies report.  
      • Carrier will file issuances for any employer they insure that was not found on the Carrier Active Policies report.
      • Carrier will file Form 403 to add or delete locations and/or divisions as needed so the WDCA database accurately reflects the carrier’s policies. 
      • Carrier will supply FEINs for all employers with a TP or JV number on the Carrier Active Policies report that they currently insure. The Carrier should e-mail the TP number, name of employer, policy number and FEIN to the contact person at the WDCA. The WDCA contact person will verify each FEIN with the Department of Treasury. Discrepancies will be reconciled between the carrier and WDCA.
      • Some employers are not required to obtain a FEIN. They are allowed to use their Social Security Number (SSN). If one of these employer’s SSN matches another employer’s FEIN on the WDCA’s database, the first 2 digits in the SSN will be replaced with WC.  
    • Carrier will supply the complete name and corresponding FEIN of each member in their group. 
      • WDCA will verify the FEINs and resolve any discrepancies with the contact person. 
  3. WDCA requests another Policy Number Reconciliation file (LW02592), if needed, from the carrier in order to update policy numbers on the WDCA database prior to testing with CAOM.
  4. The final test before a carrier receives permission to go to production will consist of successful completion of the following:
    • The carrier must submit to CAOM at least 20 of each transaction type (issuances, cancellations, etc.), including single and multiple entity policies that will be submitted electronically.  
    • The WDCA must receive a minimum of 3 consecutive transmission days of files from CAOM on behalf of the carrier with 100% accuracy of mandatory data elements and structuring of records.  
    • Ensure that the carrier receives the Acknowledgment Report from CAOM immediately upon receipt from the WDCA.
    • Ensure that carriers are able to resolve errors on a timely basis (both electronically and on paper, depending on the type of error).
  5. The WDCA requests a final Policy Number Reconciliation file (LW02592), if needed, from the carrier.
  6. All parties sign Trading Partner agreement.
  7. All parties agree upon a scheduled implementation date.

Once Carrier is Approved for POC Production

If CAOM receives your WCPOLS file through CDX and rejects the entire file, CDX will notify you. 

If CAOM accepts your WCPOLS file, two things happen:

  1. The WCPOLS file is loaded into CAOM’s processing area.

If there are reporting issues with the file or a specific transaction CAOM cannot process, CAOM will notify you via email or crit via Michigan’s Manage Policy System (MPS).  MPS allows a carrier to view CAOM’s processing status of each transaction as well as view any CAOM crit messages. 

  1. The WCPOLS file data is converted to the IAIABC format required by the WDCA for POC reporting and a series of “pre-edits” is performed on the data as required by the WDCA.
  1. If a transaction does not pass the edits, CAOM generates a CAOM/POC Audit Trail report to communicate which transactions were not sent to the WDCA and the reason.  These transactions will need to be corrected and resubmitted.
     
  2. If a transaction passes the edits, CAOM sends it to the WDCA for POC purposes. The WDCA generates a WDCA/POC Audit Trail report to communicate which transactions were not accepted by the WDCA and the reason.  These transactions will need to be corrected and resubmitted.

​You will need to establish an individual or team to manage POC responses and correct ACK errors on a consistent, daily basis.

Keep in mind, CAOM’s POC process is separate and independent of POC reports generated for the WDCA and by the WDCA.

If a carrier changes or updates their system, CAOM will require a WCPOLS test file.


faq

How do I comply with the Legal Nature of Entity requirements for Record Type Code 02?

The WDCA requires the Legal Nature of Entity for every name record reported.  In order to comply with the requirement Record Type Code 02, field 11 must be filled with the appropriate code.

Which Cancellation/Reinstatement Reason Codes are accepted?

The WDCA does not accept Reason for Cancellation code 99 (other). The WDCA requires a Reason for Cancellation code for non-renewals (Cancellation / Reinstatement ID Code 3) 

If CANCELLATION/REINSTATEMENT ID CODE (Position 48) is 2 (Reinstatement), report the REASON FOR REINSTATEMENT CODE.

See the Proof of Coverage-EDI Guide (michigan.gov) for details.

How do I report a FEIN change?

According to the Michigan Worker’s Disability Compensation Agency (WDCA), carriers should not submit FEIN changes with change transactions (Transaction code 08, 10 or 14).

Carriers should first issue a policy cancellation (Transaction code 05) followed by a new policy (Transaction code 01) with the corrected FEIN(s).

How soon must ACK errors be resolved?

Correcting ACK errors on a daily and consistent basis is critical. Each carrier must establish a plan to address and resolve error messages. An individual or team must be responsible for managing POC responses and understand the timeline for doing so.

Can I send multiple transactions for a policy in one transmission?

Carriers should avoid filing multiple transactions for a policy in one transmission.  Transactions should always be sent in chronological order.

If the carrier sends a paper transaction to WDCA to fix an acknowledgement (ACK) error, does the carrier have to send a WCPOLS transaction to CAOM replicating what was sent?

Yes. This practice ensures both CAOM and WDCA have the same data and will avoid future errors.


Important Links

To read how CAOM currently processes Proof of Coverage, click here
To read how CAOM currently processes Policy Data, click here
To read general data reporting rules, click here
To access State of Michigan Workers Compensation EDI section, click here.

Contact

* While contacting CAOM, please provide the Insurance carrier code(s). Also confirm if you  are the POC contact for your company. If you have already done this, thank you.

Email POC@caom.com
Phone 734-462-9600 ext. 265 

 

POC Updates
  • 5/21/2023 - POC 3.0 goes live.
  • 5/3/2023 - Important POC Technical information
  • 3/24/2023 - CAOM Tentative Priority Plan for Deploying Proof of Coverage (POC) 3.0 - CAOM’s tentative priority plan for deploying POC 3.0, which is subject to confirmation by the Michigan Workers’ Disability Compensation Agency (WDCA), is as follows. Please be advised of this priority plan based on the category that best describes your carrier situation below. Should you have any questions, please reply to POC@caom.com.
    1. Member carriers currently in production phase to use CAOM to report POC to the WDCA, and ready from a carrier systems perspective to comply with all POC 3.0 requirements.
    2. Member carriers currently in production phase to use CAOM to report POC to the WDCA, but not yet ready from a carrier systems perspective to comply with all POC 3.0 requirements. These carriers should contact the WDCA for further instructions on POC submissions.
    3. Member carriers currently in test phase to use CAOM to report POC to the WDCA, and working with the WDCA to certify for production POC 2.0. These carrier systems must comply with the POC 3.0 requirements.
    4. Member carriers currently in test phase to use CAOM to report POC to the WDCA, but not in contact with the WDCA to reconcile database cleanup.
    5. Member carriers currently submitting paper POC to the WDCA. When POC 3.0 goes live, these carriers may contact CAOM to start the testing/certification process in order for CAOM to report their POC to the WDCA.
  • 02/17/2023 - Proof of coverage change notification circular released. See CAOM Circular Letter #336
  • 02/09/2023 - Updates to Proof of Coverage 3.0 requirement changes by WDCA
  • 02/08/2023 - Proof of Coverage 3.0 requirement changes by WDCA.
  • 12/16/2022 - As MI Workers' Disability Compensation Agency (WDCA) is currently performing Proof of coverage (POC) version 3.0 testing, they are not authorizing new carriers for POC version 2.0. CAOM is also suspending its POC 2.0 testing activities. Contact us if you have any questions.
  • 03/29/2022 - No new information on CAOM POC 3.0 project testing - waiting for update from WDCA on implementation date
  • 10/14/2021 - CAOM POC 3.0 project testing delayed - waiting for update from WDCA on implementation date
  • 5/26/2021 - CAOM POC 3.0 project testing re-scheduled to Fall 2021 in alignment with WDCA's implementation date
  • 4/8/2021 - WDCA delays POC effective date until Jan 2022
  • 3/22/2021 - WDCA DELAYS POC 3.0 EFFECTIVE DATE UNTIL FALL 2021.  See CAOM Circular Letter #325
  • 2/9/2021 - CAOM POC Test Data Submission requirements REVISED
  • 1/5/2021 - CAOM POC 3.0 Carrier Testing Readiness
  • 12/30/2020 - CAOM POC Test Data Submission requirements (Please see updates on 2/9/2021)
  • 11/13/2020 - Additional Updates
  • 9/10/2020 - WCPOLS Changes