Canadian Payroll issues and fixes

/, Troubleshooting/Canadian Payroll issues and fixes

Canadian Payroll issues and fixes

Third time’s the charm… 🙂  Gotta love computers, I’ve written this twice already and lost it completely, the draft didn’t even save.  Argh!

Today I have 2 issues to write about relating specifically to Canadian Payroll in Dynamics GP; things that a couple of my clients have recently run into that are fairly common and easy fixes.

Issue #1 is regarding stuck batches and the message “The batch is currently in use – Please wait until the other user is finished”.

Issue #2 is regarding permissions during the Generate Cheques routine and the message “There is an error in the Transmission Header – Incorrect Length”.

Issue 1: Stuck Batches

This first issue is incredibly easy to resolve yet one of those things that consultants are not looking for something this simple; the solution is different than for nearly every other module which requires a SQL script to be run.

The issue is trying to do something to a batch in Canadian Payroll and receiving the following message: “The batch is currently in use – Please wait until the other user is finished”.

Pic_CanPaystuckbatch

The solution is to open the Payroll Batch Setup window, select your batch and click the Reset Button.  This resets the batch’s status from In Process to Available, freeing it up for the user to proceed with it.  When you click Reset, you will get a message to confirm that says something like “are you sure you want to perform a general cleanup of the batch file?” and the answer is Yes.

Pic_CanPaybatch

 

Issue 2: Permissions

This second error, which occurs during the Generate Cheques process, is permissions related.  Of course you wouldn’t know that by the error message though!  We really should help those developers with improving the text on error messages some day!

The error is: “There is an error in the Transmission Header – Incorrect Length”.  Meaningful isn’t it?  Well, when this first happened, it was with a client who had just upgraded from GP9 to GP2010 and this was on processing their first payroll.  They didn’t get the error during their test upgrade so it was a little surprising.

Pic_CanPaypermissionerror

The solution ended up being that the user – now that GP2010 was installed on her own workstation with her normal permissions – didn’t have “write” permissions on the application directory (C:\Program Files\Microsoft Dynamics\GP2010).  During the Generate Cheques routine, for most Canadian Payroll users, there are two files being generated – a direct deposit file which you sent to the bank, and a Canada Savings Bond file which you send to the bank or manually transmit in other ways.

Years ago, both files defaulted to the application directory without giving the user the option where to save it; nor was there an option to configure a default location like most other file-based things in other modules.  After many complaints and suggestions, Microsoft finally fixed the issue on the Direct Deposit file, which now prompts the user for a location to save the output file.  Unfortunately they didn’t do the same for the CSB file and it continues to default to the application directory.

At this client, they switched to Windows 7 with the upgrade so the workstations were using default User Account Control settings.  A simple switch to give the users permission to create a file in that directory solved the problem.

Hopefully this helps someone out there when they get one or more of these error messages!

By | 2017-08-13T11:46:31+00:00 November 19th, 2011|Canadian Payroll, Troubleshooting|8 Comments

8 Comments

  1. Jerry February 1, 2012 at 3:10 am - Reply

    Hi,

    Quick Question around Canadian Payroll – sorry if this is not the place to asking questions, but the resources around CPY are dwindling each year, it seems!
    Microsoft states that Bank Rec will not be updated when the employee is paid by Direct Deposit. 
    Have you seen any non-Integration Manager or SmartConnect workaround for this?

    Thanks

    Jerry

  2. Jen Kuntz February 1, 2012 at 9:05 am - Reply

    Hi Jerry,

    Most customers simply do a bank transaction to reflect the direct deposit.  It’s a minor annoyance but it’s one entry because it’s a lump sum that comes out of the bank account.

    I’ve seen customers map the “bank” account in CanPay to a clearing account then they do a Bank Trx Entry from the same clearing account to offset it.

  3. Wendy November 9, 2012 at 12:45 pm - Reply

    Found this article very helpful and was able to get things up and running very quickly.  Thanks

  4. Patty Barnas July 3, 2013 at 5:10 am - Reply

    Using Encore Bank Rec instead of the GP bank rec will resolve this issue.

    • Jen Kuntz June 16, 2014 at 5:36 pm - Reply

      Patty,

      I ran into an interesting issue at a client recently. They have some payroll with cheques and some with direct deposit. Encore doesn’t work for them because they post payroll in summary, so the cheque detail isn’t in the GL. So… if a customer only uses DD, then Encore is a good solution, otherwise, there are pros and cons.

      Jen

  5. Jen Kuntz July 25, 2013 at 5:04 am - Reply

    Thanks Patty… very true.

    For the issue Jerry is describing I didn’t even think about the ISV solutions. Encore Bank Rec reads the GL directly, so this issue would disappear.

  6. nicole June 6, 2014 at 6:17 pm - Reply

    hello, you suggest that when dealing with payroll batches that get “stuck” you do a reset then when it asks you if you want to do a general clean up of this batch, to say yes. But what does this clean up actually do? something in the background? in the tables? I cannot find any information on the MS partnersource page nor in web searches. some of my colleagues say yes, and some say no, but no one knows what it does. can you shed any light on this subject? thanks!!!

    • Jen Kuntz June 16, 2014 at 5:34 pm - Reply

      Hi Nicole,

      I haven’t actually run SQL profiler or any tools like that to see exactly what it does, sorry!

      Jen

Leave A Comment