Log in

View Full Version : GL Export sending invalid data ahead of Employee Code



CLC Peoria
02-08-2011, 10:22 PM
Using build 9.0.24, the GL export file has several lines of illogical data before the first employee code. This prevents Shepherd's Staff from importing the file because the vendor/employee codes don't match. NOTHING HAS CHANGED OR BEEN UPDATED IN SHEPHERD'S STAFF, and the export process worked as it always has as of build 9.0.19 (our last payroll). I can see from your update notes that 9.0.20 addressed some issues with the GL Export. Strangely, if I look at the file with Excel or Notepad before it arrives in Shepherd's Staff, I do not see any data ahead of the first employee code.
In the GL Export setup, we use CSV as we always have.
Thank you for your help.
Julie

Paul Mayer
02-08-2011, 11:13 PM
We notified Shepherd's Staff of the addition of a new data field at the end of each employee record in the exported data. The export file schema can be seen in this page of the help file here:

http://zpay.com/pw-online-help/module_13_8.htm?MenuState=AcOXw5VVXcOVV8OdXXVVw5d1 dcO1w5XvtIrvtIRVBcOnAAFLBA==

I'm guessing that they should have an update ready by now as it was a few weeks ago that this was added and I contacted them.

CLC Peoria
02-09-2011, 12:33 AM
Thanks Paul. There isn't a service pack listed on their website yet. Any chance I could get a copy of an earlier build, say 9.0.19, to run my payroll until I can get the update from Concordia? Thanks again for your help.

Paul Mayer
02-09-2011, 01:06 AM
You might want to wait for the update to import as the FICA will be no good if you use an older version. :-(

You might want to contact them to see how soon the update will be available, I just sent them another email and am guessing the more requests, the faster it may happen.

CLC Peoria
02-10-2011, 08:16 PM
Follow-up to this discussion, in case anyone else needs to know.....
Shepherd's Staff said that a fix for this should be available "in a couple weeks" via their website. They suggested we can temporarily work around the problem by deleting the last column of data from the file before importing it. Sounds like a bit of a mess in my general ledger, but at least we can get the checks entered so we can pay our staff.

CLC Peoria
02-11-2011, 05:48 PM
Paul,
I have reviewed the info you provided for the export file schema and also the data in the export file itself. I can see that you are adding a field for the employer's Social Security obligation, which is obviously no longer the same as the employees' share. However, I see a little problem in our situation. 5 of our 35 employees are exempt from FICA withholding, so there is also no employer's FICA due. However, all 5 of these employees have a value in new field #30, which I believe should be zero.
Thanks again.
Julie

Paul Mayer
02-11-2011, 06:51 PM
Thanks, I have the developer checking into that. We are also adding an option to export the pre-2011 format as some of our partners have not released an update yet and the customers can't import.

Markenrenuk
02-13-2011, 10:55 PM
I also use the GLImport feature for shepherds staff - I found that all you need to do is match up the vendors again - obviously this is awkward due to the employee code being incorrect but if you only have 5 employees like me then it doesnt take too long - alternatively just delete the extra field before you import in SS as was suggested earlier.