User Support Forum

Problem:
We use PowerChurch payroll to track employee payroll data in addition to using Heartland Payroll processing for processing payments. (I know this is redundant--we use the payroll module to create/post the payroll journal entries.) Our last payroll cycle pay release was 12/01/17. We set check date in payroll module to match Heartland pay stub pay date.

With this payroll provider, funds are drafted in advance (ie., 11/28/17), and appeared on bank account statement (11/30/17). Our monthly bank statement included this transaction, so we can't reconcile the account without adjusting the payroll posting date from 12/01/17 to 11/30/17. Seems to be one of those serendipitous moments that unfortunately occur.

Question:
I know I can void payroll transactions in PowerChurch and reenter all data again, with check date of 11/30/17 instead of 12/01/17.

Would this be the best practice?

bmrouse wrote:Problem:
We use PowerChurch payroll to track employee payroll data in addition to using Heartland Payroll processing for processing payments. (I know this is redundant--we use the payroll module to create/post the payroll journal entries.) Our last payroll cycle pay release was 12/01/17. We set check date in payroll module to match Heartland pay stub pay date.

With this payroll provider, funds are drafted in advance (ie., 11/28/17), and appeared on bank account statement (11/30/17). Our monthly bank statement included this transaction, so we can't reconcile the account without adjusting the payroll posting date from 12/01/17 to 11/30/17. Seems to be one of those serendipitous moments that unfortunately occur.

Question:
I know I can void payroll transactions in PowerChurch and reenter all data again, with check date of 11/30/17 instead of 12/01/17.

Would this be the best practice?

Actually, you CAN reconcile this by UNCHECKING the box on the Reconciliation screen that says Only show items dated before the statement date.

I do use this for such issues as this.