FAQ: Large Batch Processing

A feature that moves payroll processing from the application to the cloud to accommodate a significantly larger number of transactions [exceeding 500 transactions].

This will automatically queue batches so that when processing a large number of transactions, the user can continue to utilize the application for other activities.

 

CHAPTERS

How do you get access to the Large Payroll Batch Processing Feature?
What are the benefits of the Large Payroll Batch Processing Feature?
I would see the impact of the Large Payroll Batch Processing Feature after how many transactions?
How will it look different with the Large Payroll Batch Processing Feature?
What if I hit Process again while my process is already in progress?
What happens if I hit Process again for a payroll batch that was already processed?
I have transactions that have encountered errors, what happens now?
Do I have to clear out all the errors before I print the checks of the transactions with no errors?
How do I get the feature turned on?

 

 

How do you get access to the Large Payroll Batch Processing Feature?

This functionality would need to be requested to be available in your environment as the logic is behind a feature flag and is not available for all users, this would have to be requested.

 

 

What are the benefits of the Large Payroll Batch Processing Feature?

Some of the benefits of the Large Payroll Batch Processing Feature would include:

  • Asynchronous processing allows the user to continue to utilize the application for other activities.
  • Error batches split when errors are encountered, allowing the transactions with no errors to continue processing.
  • Eliminates the cap on the maximum number of transactions.
  • Email notifications for completed processing.
  • Introduction of pagination on the Transactions and Paychecks, so that when viewing, it eliminates the need to continuously scroll down to find the lower items you can move to the next page.

 

 

I would see the impact of the Large Payroll Batch Processing Feature after how many transactions?

500 transactions will initiate the Large Payroll Batch Processing. Anything less will process as it currently processes.

 

 

How will it look different with the Large Payroll Batch Processing Feature?

The Payment Batch Summary will now display a field called Percent Complete.

 

 

What if I hit Process again while my process is already in progress?

The user will be notified This batch has already been sent to the queue for processing. Please wait until processing is complete or discard the batch.

 

 

What happens if I hit Process again for a payroll batch that was already processed?

If you are reprocessing because there were errors that needed to be addressed, the system will reprocess without notification.

If you are reprocessing and there were no prior errors, the user will get the notification of This batch has already processed by the queue. Are you sure you want to re-process the batch? with a Yes or No option.

 

 

I have transactions that have encountered errors, what happens now?

With the Large Payroll Batch Processing all transactions that error [hit a DRM flag], will split off into its own sub-batch, tagged with the Description of Error Batch: #

If the error batch exceeds 500 transactions, it goes to the queue, otherwise is processed as it normally does.

 

 

Do I have to clear out all the errors before I print the checks of the transactions with no errors?

No, you are able to print the checks that processed successfully prior to correcting the transactions that have errored.

 

 

How do I get the feature turned on?

Client needs to request to turn on the feature via a support ticket.

At Avionte, a user with administrator access to the AWS console/CLI would need to turn the feature on.

 

 

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share