Regenerating Finance Integration Batches

Finance Integration batches can be regenerated if the Finance Integration maintenance settings that were configured at the time of processing the batch were not configured appropriately. For example, if you discover that transactions in the export files that are generated by processing a batch do not have the required GL account segment mapping the GL account segment mapping configuration can be modified. The batch can then be regenerated, which will result in new export files being created. The new export files will be created based on the updated GL account segment configuration.

The following occurs when a batch is regenerated:

the system applies the Finance Integration maintenance settings that are valid at the time of regeneration rather than those that were valid on the original export date
new export files are generated based on the maintenance settings that apply on the date of regeneration
the batch status is set to Regenerated
an action is recorded in the audit history of the batch to indicate the date and time the batch was regenerated and the user who triggered the regeneration
if a notification email address is configured in the Finance Integration General Maintenance settings, a notification is sent to that email address to advise that the batch has been regenerated.

A regenerated batch will only include the transactions that were included in the original batch. Any new transactions that have been generated since the batch was originally processed will not be included in the regenerated batch. There is no limit to the number of times that a batch can be regenerated.

GL account segment mapping and wage transaction grouping maintenance configuration is based on validity periods and therefore any changes to this configuration will only apply from the day after the last successful export or later. Therefore, any changes to this configuration will not be reflected in a regenerated batch if either of the following conditions apply:

the batch is regenerated on the same date that it was originally exported
the batch is regenerated on a date prior to the start date of the new configuration settings validity period.

If you need to update the configuration and regenerate a batch on the same day that the batch was originally created, you can delete the original batch instead. This will release all transactions that were included in the batch and will unlock the validity period for the GL account segment mapping and wage transaction grouping configuration, if no other batches have been processed since. Once you have updated the configuration as required you can create and process a new batch that includes all of the transactions in the original batch.

General maintenance settings are not based on validity periods and therefore any changes made to those settings will be reflected in a regenerated batch regardless of the date on which a batch is regenerated.