PR14 start/stop dates with Benefits in secondary system

unknown

For those of you that may be using a secondary system for benefits but using Lawson for Payroll, when you load deductions, how does PR14 behave?  We are not loading anything to BN32, just straight to PR14.  I know in the past, when we had benefits in BN32, the corresponding deduction in PR14 would start/stop and the dates would stay in sync with BN32.  We've not been able to figure out how we can make the PR14 act accordingly when we are loading deductions via PR514 or manually keying changes.  This means all history attached to a deduction is wiped out with each change.  If this is functioning as designed, how do you manage tracking the history for payroll purposes, especially if you are audited for some reason?  Any thoughts are welcome!

0911060553270289.pdf

unknown

Hi Yvonne, we also use an external system for employee benefit elections and port them over to Lawson. We have used both BN531 and a custom flow that populates BN31 & 32 to do this. Bottom line is, if you enter the benefit deductions directly on PR14 (or load with PR514), you cannot keep any history under the same deduction code. The only deductions that can be stopped and started are those that come from the Lawson benefits system. If you try to stop and re-add a straight deduction on PR14, it will tell you that the deduction already exists. The only way I know to keep history for a straight deduction is to keep creating new deduction codes.