After converting to Financial Edge Payroll 7 we are experiencing extremely slow processing of the time batch entries and the payroll calculation. We are currently entering the third payroll since conversion and we are encountering different problems with each payroll. Anyone else having similar problems or even better, solutions that have worked for you?

We are having the exact same issues. After our conversion the Financial Edge has come to a crawl. We have created over 20 cases that have yet to be resolved dealing with many aspects of the Payroll Module. All I can say so far is that Blackbaud closed a few cases stating the performace issues would be resolved in Quarter 2 of 2006..... talk about a wait time for a solution. My advice right now if you're thinking of upgrading, don't.....until all the kinks, quirks, and performace issues have been resolved.

We were looking to make the jump after W-2's had been produced. Now I am having second thoughts. Is anyone having a good experience with Payroll 7? We run in house payroll for about 140 employees. We enter the batches as bi-weekly hours from time clock cards, not as daily time in time out. I am very interested to hear how others are doing on the new platform.

We just switched over in the middle of November to payroll 7. Big mistake. There are alot of issues that are still being worked out.

I would also suggest waiting. It seems everytime we process a payroll more and more issues crop up. When we try to work with technical support they tell us it works fine on their end, close the case and then when it happens again we have to start all over again. We probably have uploaded our database to them at least 5-6 times in the six weeks we have been on this version for various issues.

Have you updated to the year end version yet? We just processed our first payroll since updating to 7.52.232.0000 and the calcuations were created much quicker.

Yes we have. Now we are having some different problems. We have sent our database to them a couple of time. They say it works fine for them, but it doesn't for us. Maybe a couple of uploads away. Are your YTD figures printing correctly? They look fine in the computer, but don't print out what is there.

I delayed our scheduled December conversions due to some staff vacations and illnesses. Now that seems like a fortuitous delay. I have been contemplating an early February payroll conversion, but these stories are causing me some concern. If the first 1/4 06 patch takes anywhere as long as the original release estimates, we may not convert until this time next year. I am going to wait and see. Please keep us informed of the progress. Why borrow trouble?

On about a third of our employees it seems to be doubling the YTD taxable wages when printing their checks/EFTs. That is one they say is fine on their end and I have had to re-open today. Have you posted any payroll to a project? I did for the first first time last payroll and although the payroll register shows the correct distribution when it posted to the GL, only a few actually posted to the project.

We are having similar problems. The YTD is about the same as yours. We post to projects, but I haven't checked that yet. We did find our local taxes calculated correctly, but did not print on the GL report when we printed it. Only 1/4 of the withholdings printed, but the total at the bottom was correct. Right now we are having trouble printing our EFT forms for our employees. We voided a check run, hoping to recalculate and have things correct after the download, but now we can't get rid of the voided checks even after purging. They keep showing up on our payroll-prepayment report.

We discovered during this final payroll of the year that any salaried employee who had received an increase during the year calculated incorrectly. The software used the annual salary amount from the employee file and calculated the final ck of the year so that the total pay for the year equaled that figure regardless of the effective date of the increase. The solution from BB is pending

We had the same problem today. I couldn't figure out why there were a few salaried people who were fine but they must have been ones without an increase. I didn't have time to call Blackbaud since I have a 4:30pm deadline at the bank for EFT. FYI for anyone else that may have this problem: In order to get it to work, I had to go into each affected employee, open up their salary pay type, click on pay only in specific pay periods and then back to every pay period and it recalculated the amount correctly.

Thanks so much for your comments. We have updated to 7.52.32.0000 and we too have found the calculations to be quicker. We have been fairly pleased with the responses from support but have had to find ways to work around some issues due to the time constraints associated with payroll processing. There are still issues to be resolved with a piece rate payroll that is imported, but I expect those issues to be resolved within the week. We'll see.

We converted to payroll 7 in early January. We wish that we stayed on payroll 6. Payroll 7 operates and feels like it is still in beta testing. The biggest improvement in the new system is the third party software that generates tax forms. The W2 wizard is easy to use and errors in W2 reporting are easy to correct. We were able to get the 4 up W2s printed using the Align function within Atrix. However, we have many issues (most still unresolved) when processing payroll. We are working with customer support, but it is a slow process. Our biggest issue is with posting. Any accounts coded to project are not distributed by what is in the calculation, but by what is on an employee's default distribution. Furthermore, when an account is coded to project, it allocates a small amount to the project and then dumps the remainder into the same account without project. Upon conversion, everyone in our database with a residency required local tax had their settings changed to "non resident". Since a non-resident tax does not exist in our locality, payroll 7 did not calculate local tax. When we changed the employees back to residents, it calculated the local tax. However, it still regards everyone in the system as a non resident (reflected on reports) and puts the withheld amount into the cash account instead of the correct liability account. We are also experiencing issues with entering piece rates with the "enter time worked" function. If you choose to enter piece rates this way, you have to leave all employee defaults blank (as we were told by customer support). Additionally, converting to payroll 7 has significantly slowed the entire Financial Edge system. If you have yet to convert, I would wait until all of the kinks get worked out. It isn't worth the trouble. [i]--- Edited at 2/2/2006 2:49:28 PM by Liz Bloomfield[/i]