When using the "batch transfer for subledger journals" functionality, a batch job is created. But for the actual execution of the batch transfer, it creates a new batch job for the actual subledger transfer. This is not good design, since we don’t have the actual execution times in the original batch jobs then. Also, these “new” batch jobs are removed, so that no detail remains available.

Also, we can enter filters when creating the batch, but it is not good design that these filters are not available when looking up the batch job filters afterwards. Also if the job does not recurrent we want to keep this parameters for review afterwards.

We found out that we were able to execute the batch transfer filtered by period by entering both fiscal year and period name. Only entering fiscal year will cause the batch transfer being executed for ALL periods. This is not clear and should not happen! Either the month should be required when entering a fiscal year or the filter should work when only a fiscal year.

The status once the process has started is not clear. The records are removed from the “Subledger journal entries not yet transferred” listpage almost immediately, while in reality they are still in process.