Automating Payroll processing?

Hello,

Anyone automated your payroll processing? We have a multi page document that outlines the steps and can build from that but I'm just wondering if anyone has done this yet and might want to share their flow? We are on 10.0.7 apps.

Thanks,

-Lance

VISUAL Roadmap - July 2020-Seminar Series.pdf

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Hi Lance, we use mainly multistep jobs to automate our payroll, because we run payroll by process level and we have many of them - so, we have many jobs. We do use a flow to help us update the parameters in the programs that are in the multistep jobs, that change every payroll, for example dates. We use an inhouse scheduler to kick off the multistep jobs, but Lawson itself does have a basic scheduling tool in lid. Alternatively, any job, including a multistep, can be submitted from a flow - then you could use the rich client's scheduler.

lrjurgen

Thanks - That is very similar to what we do, except we have not used IPA to update the dates etc. That might help in that piece. If I end up doing anything I'll update this post.

unknown

We are looking at several Robotic Process Automation production to automate payroll cycle processing. Pacific Life has 2 products in-house but I'm also looking at an offering from Intellias that was developed specifically for Lawson.

unknown

We are using Intellias for payroll automation for 3 months. We've worked most of the kinks out but it has been rough.

unknown

What challenges did you encounter with Intellias?

unknown

It mainly has to do with figuring out what their product can and cannot do (vs expectation)

This is the gist of it:

the intellias automation product is a set of javascript programs that runs on the internet explorer browser(only). It is basically a wrapper on the portal, it runs queries via ags/dme calls(not sure which) and submits jobs. You define job parameters, their order of execution and javascript functions to do some data queries and job parameter population. you can setup breakpoints in the automaiton for manual tasks, verification, etc.

They have tables in lsf to keep track of what step the automation is currently at.

Things we learned:

- scheduling is not part of the product. automation has to be started manually.

- User starts the automation and need to leave the browser open. It runs using the logged-on user's account.

- Make sure that the computer running the automation does not go to sleep or the automation will pause. it will continue when the machine wakes up.

- There is a potential for users to run the same automation on different machines and the jobs will be submitted twice.

- Avoid using the account that is running the automation while it is running especially if you jump from one data area to another.

- the automation can run IPA via WFWK.1 but it is a fire and forget process.

- part of our payroll involves running sql stored procedures. We wrote javascript functions to have the automation wait until the sprocs are done.

- intellias helped us with the above 2 problems with examples.

- there are advanced features like arrays and customized input fields(?) but the provided documentation does not mention how to use these (for advanced users only)

MSP8 introduced an extra parameter in PR160. if this parameter is not supplied, PR160 will go into recovery. We didn't know about this so we didn't change the automation to supply that parameter. it was a big issue trying to figure out the cause.

Copyright © 2025 Infor. All rights reserved.