Hi Jennifer Leugers,

EIN field is not mandatory. You can leave it blank. So system will consider default one internally. As per template customization in our WT system, the thing is column must be present with header in the correction import file.

In your provided correction file, you have created the correction file without column header, so in such case when you save the file as csv it will not take consider last column placeholder if it is blank. Please refer this for more details.

Please note that we have removed EIN field in template customization (for city of chico only) and accordingly correction file is corrected in your provided file & imported yesterday.

In our template specification,we have column headers for 1095 C part-2 like below
1. Employee Social Security No
2. Month Index
3. Tax Year
4. Line 14 Code
5. Line 15 Cost
6. Line 16 Code
7. Plan Start Month
8. EIN

So accordingly we have template customization in WT system with " File Contain Header Information=Yes & File Format=.csv " in template setting and our correction file should be created as per these settings.

Please note - If on template setting, "File contain header information=Yes" and if there is no header row in correction file, first row will be skipped from importing.

Thanks,
Revan

CC- Nandkumar Prabhakar Karlekar,Smita Pawar, Ramya Tantry, Kumar Chhajed,Sachin Hingole, Gaurav Sodani

Hi all - what blank value do we need to put in the file if they do not need to specify the EIN since there is only one?

Hi Jennifer Leugers,

CONCERN:
When try to import the correction , the bad files are saying the # of fields do not match.
CAUSE:
In template (WT system) customization, there was a EIN field column present which you need to provide either blank value or valid value against EIN column in import file and as per customization, import file should have header which was not in your file.
CORRECTION:
To resolve a concern we followed as per below points.
1. In import file has been added header row.
2. From template customization has been removed EIN field.
3. Data transformation has been done for member type in Part 3 template.

After expected changes done in template customization, we occurred below issues while importing

1. In the file was provided a wrong SSN for the employee, we set the correct SSN for the employee by taking the reference of Member SSN & corrected in the file
from wrong SSN-5481173571 to correct SSN-548173571
2. While Importing part-2 correction, we get a bad record file for the employees 6049X2X63, 5559X9X38 for the error of Invalid code for 1H,2G and for 569XX93X7-invalid code-1A/2A .
Hence we changed in the file for those employees as 1H,(Blank) and 1A,(Blank) respectively.

Please find the below run details which we run after correction import on Main Production Company..
Report run time-1/2/2018 3:42:18 AM

We have corrected the files & imported using this Corrected Files.zip file.

Password will be sent in mail.

Thanks,
Revan

CC- Ramya Tantry, Kumar Chhajed, Nandkumar Prabhakar Karlekar, Smita Pawar, Sachin Hingole,Gaurav Sodani

Hi all - I have the correction files for this group and the formatting looks correct but when I try to upload, the bad files are saying the # of fields do not match. I'll send the password on the file via email.

Hi Jennifer Leugers,

Instead of using existing report, this group has been run by creating separate Report for 2017 named- "2017 1095C for Chico" with dates of 01/01/2017 to 12/31/2017.

Please refer to download the run dated "12/5/2017 1:37:11 AM" for verification.

Thanks,
Revan

CC- Ramya Tantry, Kumar Chhajed, Nandkumar Prabhakar Karlekar

Please change dates to the 2017 calendar year (1.1.17 - 12.31.17) and group is ready to run. Thanks!