If I'm not mistaken, you can add two scheduled dates. You set each date to run monthly but make sure it runs after the payroll as processed. Or, you can run it On Demand. That means someone has to manually get the task to run twice a month.

The condition on the task is what matters for the dates. Mine is conditioned to run for any PE date greater than the current date minus 7. Since mine runs on Friday, it will print for the prior Sunday PE date. If you do biweekly, you can set it to run for any PE date greater than current date minus 14 or 16 or any number that makes sure it only picks up the last PE date.

Hope that makes sense!

Thanks, that's an interesting way to look at it and what I was looking for with my question.  It would be handy if there was a way to set it to run Current Date Plus two after payroll has been posted but did not remember that ability.  But the thought process of two dates will be something I will explore..  Just trying to avoid it running before the money gets put into peoples accounts so some procedural thoughts will be needed on our end. 

Thanks, that's an interesting way to look at it and what I was looking for with my question.  It would be handy if there was a way to set it to run Current Date Plus two after payroll has been posted but did not remember that ability.  But the thought process of two dates will be something I will explore..  Just trying to avoid it running before the money gets put into peoples accounts so some procedural thoughts will be needed on our end. 

We run ours as soon as everything is posted, the dates make clear what the pay period is and what the paycheck date is. That may be a cultural thing here, though. We just this year made it mandatory that direct deposit includes email delivery of paystubs, that only took us 7 years!

Thanks Brian.  The manual process is certainly one of our options.  We only have the application install on two machines so that requires one of two people to do it but like you suggested we would need to condition people to understand the stub does not always mean when the money is in the bank.  

We have a specially designated and configured Windows Server instance that a few staff has access to. This has our MA Designer seat installed on it as well. This makes is easier for the few people that have the necessary permissions to cover for each other for vacations and such. It also simplifies support calls and occasional consultant access. Something to consider. And a LOT easier to get going that changing people's expectations about paystubs!

Edit to add: After a .NET problem with installing My Assistant on a fresh Sage 14.1 install, we moved My Assistant to a dedicated server instance as well. That has drastically simplified managing the MA hiccups!

I have thought of that but have not done it yet.  But its a good idea.