Sage 100

Heads up regarding upgrades and the new ACA info. It appears the ACA codes get wiped out during an upgrade. I've done 2 separate upgrades now - one to 2014 and one to 2015 where the codes were wiped out. Reinstalling seems to be how you have to get them back. I haven't had issues when just installing PUs that include the ACA info - just upgrades - so I'm assuming something happens during the migration. The first time it happened I logged it to Sage and was told they would look into it to see if they have a problem or not. Of course I haven't heard back from them.

At least they didn't ask you to send data. I now recommend unless it is super critical that customers not send data or rely on ""waiting for Sage to research"". Both have been stall tactics that wasted my time.

@MaryJoKrueger - Can you clarify? You set up the ACA in V2014 (PU5), then migrated to v2015 and this data did not migrate??

In one instance I installed version 2014 with PU5 and migrated in data from version 4.5. All of the ACA menus and screens were there, but when I tried to lookup the codes in the Offer of Coverage column and in the Applicable Section 4980H Safe Harbor section, nothing was there. In the other instance I installed Sage 2015 with PU1 and migrated data from version 4.5. I had the same results where none of the codes showed up. In both cases I ended up having to reinstall Sage 100 and the appropriate PU to get the codes to show up.

Interesting - I just looked at a client that went live in v2015 from v2014 PU3. Those tables are not available when I click on ACA employee maintenance. They ARE in my company version of v2015 though. Are you in the VIP program? I think we are still supposed to get priority assistance if participating in the program.

I wonder if rebuilding the ALE will bring the information back.

I AM in the VIP program but didn't go that route to log the issue as I figured we were past that stage. I always rebuild ALE files as part of my upgrades - right after the conversion step - so I know that won't fix it. I'm guessing there's either something in the migration or in the conversion that gets rid of those codes somehow.

I just asked Deborah Nelson if the priority support was still available. You had to register the client ahead of time. Never hurts to ask.