Who's On?

	Membership:
	Latest: HireIQ
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5264

	People Online:
	Visitors: 519
	Members: 0
	Total: 519

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

PR560 Payroll History Import

4 Replies

0 Subscribed to this topic

68 Subscribed to this forum

Sort:

Author

Messages

val

Basic Member Send Private Message

Posts: 8

5/22/2008 4:19 PM

Hi All. We are in the middle of implementing Lawson. I am wondering, how many times can I run the PR560 conversion?

I am having problems getting payroll history out of our current legacy system all in one big report. So I am wondering, if I could maybe do the import in 3 different sections, one for check history, one for earn code history and amounts, and a 3rd time for deductions history and amounts.

Any input would be greatly appreciated, thanks!

Phil Simon

Veteran Member Send Private Message

Posts: 135

5/22/2008 4:21 PM

The 560 has an internal balancing mechanism that enforces this basic calculation:

gross - deductions - taxes = net

As a result, you can't upload only deduction records; they'll all be out of balance.

You'd have to run all records associated with a particular payment concurrently.

val

Basic Member Send Private Message

Posts: 8

5/22/2008 8:53 PM

Thanks Phil. So how about this. If I ran three different reports, one for check amounts, one for earn code amounts, and another for deduction amounts, could I just run grand totals for each one and import one row with each amount for each employee? I.e.

emp1 earncodeamounts deductionamounts
emp2 earncodeamounts deductionamounts

Or would it be more like t his:
row1: emp1 recordtype1 earncodeamounts
row2: emp1 recordtype2 deductionamounts
row3: emp2 recordtype1 earncodeamounts
row4: emp2 recordtype2 deductionamounts

Thanks again!

Phil Simon

Veteran Member Send Private Message

Posts: 135

5/22/2008 10:59 PM

You probably want the per-pay code and per-deduction detail, not just the summaries.

John Henley

Posts: 3351

5/23/2008 12:56 AM

One thing I've done for clients is to stage all of their legacy data from the various reports, etc. into a common database and then prepare the Lawson PR560 CSV from that data. PR560 is a very tricky program, and things definitely have to be loaded in the correct order in the CSV file, or you will have a mess. While it's best if you can load payment detail, quarter totals will also work.