Carrier Feed Project Status
OVERVIEW
This article will help you track the status of your Carrier Feed Project, and provides guidance on what needs to be done to advance the project from each status noted.
If you have any questions about your carrier feed project, reach out to your EDI Consultant, or the assigned engineer. You should expect to receive separate emails related to each individual carrier feed you have with Namely, as different carriers operate on different timeframes, and it's easier to isolate specific issues with different email chains.
BEST PRACTICES
-
Continue to make manual contributions and enrollments with your carrier until the project is completed and your feed goes live.
-
CC editesting@namely.com on all emails sent during the build process.
CARRIER FEED PROJECT STATUSES
The following table contains the different statuses that a carrier feed project can be in, what each status means, and who must take action to move the project forward.
TIP:
Using a Control+F (for PC) or Command+F (for Mac) to search for your status in the chart below.
Status |
Communication |
Action Owner |
Additional Services Agreement |
We are currently preparing the Additional Services Agreement that will serve as an invoice to this feed. |
Namely |
Approved |
Great news! Your carrier has approved your file for a 'Go-Live' date. We need to obtain the date that works for you to turn this connection on. |
Client |
Brokerage Triage |
Your Namely broker is reviewing your data before we send it to your carrier. |
Broker |
Carrier Corrections |
We are reviewing feedback from your carrier and will either need to make changes to our build, or request data updates from you in order to send another test file. |
Namely |
Carrier Feedback Received |
We received feedback and are about to make changes in order to send another test file to your carrier for approval. |
Namely |
Client in Manual Enrollment |
The client has confirmed that they will make manual enrollments for this feed. |
Client |
Data Corrections Needed |
Changes to your Namely benefits data need to be made in order to pass information correctly to your carrier. |
Namely |
Data Validation |
Data corrections need to be made in Namely before we can send accurate information to the carrier. |
Namely + Client |
DV: Data Fix |
Data corrections need to be made in Namely before we can send accurate information to the carrier. |
Namely + Client |
DV: Waiting on Broker |
Data corrections need to be made in Namely before we can send accurate information to the carrier. |
Broker |
DV: Waiting on Carrier |
Data corrections need to be made in Namely before we can send accurate information to the carrier. |
Carrier |
DV: Waiting on Client |
Data corrections need to be made in Namely before we can send accurate information to the carrier. |
Client |
Escalated |
We have marked this project with the most urgent priority. |
Namely |
In Progress |
We are currently updating or building your file, will test it for quality, and then send a test file to your Carrier for approval. |
Namely |
In Triage |
We have validated your contract for this EDI feed. We are in the process of verifying your data for any discrepancies, and we may need to contact you to resolve them. You may run the 'Namely Data Audit Report' in Namely Payroll to obtain a preview of this process at any time. |
Namely + Client |
Info Needed |
We require more information before we can continue this project. |
Client |
Namely Corrections Needed |
We are reviewing our internal build for quality issues to prevent errors before testing with your carrier |
Namely |
OE Approved |
Great news! Your carrier has approved the Open Enrollment updates we made to your file. |
N/A |
OE Elections Sent |
We have sent your Open Enrollment data to your carrier and are waiting to hear back on the results. |
Carrier |
OE Elections Sent w/o Confirmations |
We have sent your Open Enrollment data to your carrier and are waiting to hear back on the results. |
Carrier |
OE Elections Sent w/o Structure |
We have sent your Open Enrollment data to your carrier and are waiting to hear back on the results. |
Carrier |
OE Questionnaire |
We sent a recent communication to your carrier to obtain the information we need to update for feed for Open Enrollment changes. |
Carrier |
On Hold |
We have currently placed this project on hold. |
Anyone |
Pending Development |
Your carrier's technical requirements are being developed by our Engineering department. Once complete, we may continue this project. |
Namely |
Pending OE Confirmations |
We are waiting until the client finishes confirming enrollments before sending the OE File. |
Client |
QA |
We are reviewing our internal build for quality issues to prevent errors before testing with your carrier. |
Namely |
QA Approved |
We have reviewed our internal build for quality to prevent errors while testing with your carrier. We are preparing to send a test file to your carrier for approval. |
Namely |
QA Rejected |
After an internal quality audit, we've identified some changes that need to be made before attempting to re-send this file. |
Namely |
Ready for Assignment |
Your Namely data has recently been audited and is clean. We will be assigning this project to an Engineer shortly. |
Namely |
Ready for QA |
We are preparing to review our internal build for quality issues to prevent errors before testing with your carrier. |
Namely |
Sent to Carrier |
We have sent a test file to your carrier and are waiting to hear back on the results. |
Carrier |
Structure Received |
We have recently obtained the 'Plan Structure', which is a mapping of our plans to your carrier's plans. We will be assigning your project to an Engineer shortly. |
Namely |
Structure Requested |
Before we can build this feed, we need an up to date 'Plan Structure', which is a mapping of our plans to your carrier's plans. We have reached out to your carrier to obtain this information. If you have any specific contacts at your carrier that you would prefer that we work with, please let us know! |
Carrier + Client (if applicable) |
Test Scenarios |
Your carrier requires detailed testing scenarios with your data. We are preparing mock data in order to satisfy these requirements. This requires additional time for this build. Your carrier may be able to waive these testing requirements at your request. |
Namely |
Waiting on Broker |
We require more information from your broker before we can continue this project. |
Broker |
Waiting on Carrier |
We have sent a test file to your carrier and are waiting to hear back on the results. |
Carrier |
Waiting on Carrier + Client |
We require additional information from your carrier before we send a test file. If you have any specific contacts at your carrier that you would prefer that we work with, please let us know! |
Client + Carrier |
Waiting on Client |
We require more information from you before we can continue this project. |
Client |