This is exactly the reason I gave up pushing clients to use the Link back in 2007 or so.
Here is the list of issues back then. Can anyone verify if any of them have been resolved. At the time, Abra and Sage were deaf and dumb to the client's dilemma. Since then I only used the link to transfer data from Sage PR for the initial data load of Abra. @ShawnSlavin ????
Abra Issues with MAS PR.
1.The necessity of an additional field in Abra Suite in order for the user to select which state's unemployment tax will be used for the employee, as some employees need a different state's UI tax applied from their primary state. This particular request has previously been documented and is currently under review by the Product Management and Design teams. (4047) The current lack of this functionality can cause problems for customers as if the UI tax applied to the employee is not the primary state then an additional transfer of the employee from Abra to MAS 90 can cause the removal of the previously applied amounts to the UI tax. This issue can be avoided by the placement of a patch file into the Abra System (6335). The patch file does not add a SUI filed into Abra but does stop the removal of any UI that is not a match.
2. Benefits add in Abra will transfer to MAS 90 regardless of the start date for employee benefit. This issue is also documented and under review for possible enhancement(6394), but currently the Link will continue to transfer the
benefit to MAS 90 deductions as long as the benefit is applied to the employee's Abra details. (There is no patch file for this issue currently)
3. Accruals do not start automatically in MAS PR Solution from Abra - To get the accruals to start operating when using the MAS 90 Interface, after all mapping has been completed, a maintenance routine must be run in MAS 90. To find this utility, launch MAS 90 and select Modules, Payroll, Setup, Benefit Schedule Maintenance, put in Benefit Code, click Apply button, put in new hire employee number that was just transferred from Abra HR into MAS 90 Payroll. This has been submitted to Engineering. Notification will be included in the Release Bulletin accompanying the version with the change. We apologize for the delay in responding to your issue but it was received after hours and we are closed on the weekends.
4. No mapping cross link for UDF's in both systems.
5. Issues with employees having more than two state tax codes for withholding Abra Limit was two states.
6. Tracking changes to MAS PR change audit log is not updated if change comes through Abra.
7. Terminated employees THIS year in Abra. When she tries to run the link to MAS 90, if she selects terminated employees, ALL terminated employees are sent over (meaning last year employee's that were purged from MAS 90 during the YE closing process).
Suggested Solutions
A) Regarding the date fields, hold the dates last entered as a default date. That way user could enter the current period (year) and it would serve as a reminder.
B) If you click on the include terminated employee field, FORCE the user to enter a date range.
C) If you click on the include terminated employee field, open a warning box advising user to enter a date range.
in either 2 or 3, user could not go forward without entering a date range.
D) For terminations, only allow the changes made in the same year as the MAS 90 Payroll Setup ""Current Processing Year"" field are transferred. See the box below.