Batch Job Submission
This screen is used to submit a batch job run request. The batch job requested will be queued for execution immediately. Once the desired batch job has been executed, details can be seen via Batch Run History.
Three options exist: -
- which performs depreciation calculations up to the batch run date
- Lease charge
- which performs operating lease charge calculations up to the batch run date
- Year-end Rollover
- which rolls the year-end dates over to the new accounting period. This would be used if a user had deleted the rollover batch job run the previous evening and now needs to roll forward immediately. If the user does not run the batch job, it will happen automatically overnight anyway.
Note To Close a Year End or Revalue/Impair a fixed asset use the links shown in blue.
Select whether the batch job is for depreciation, lease charge or year end rollover and enter the date up to which the system is to prepare the calculations and confirm the job by clicking on SUBMIT.
As At Date
You can specify an As At Date for the transaction. The date can either be entered manually or selected from the pop-up calendar by clicking the icon. The As At Date must be entered in the format DD/MM/YYYY, for example, 01/01/2000.
Clicking the "Last Year End" button is a short cut for populating the AS AT Date field with last year end date.
When entering dates manually, a date guessing routine speeds up the input by taking the user input and assuming the missing month and or year based on the current date as the user leaves the field i.e.
the date today is 30th October 2009
- User enters 15 or 15/ and tabs - field displays 15/10/2009
- User enters 15/9 or 15/9/ and tabs - field displays 15/9/2009
The impact of running a batch job
If the batch job request is at a date prior to batch job that has already run (either automatically or user batch job) then the system will block this run until the later dated job is deleted. This prevents an extra expense being recorded.
Example: Automatic batch job was run on 30th Sept; a request is submitted for a batch job on the 15th Sept. this will be prevented until the 30th Sept run is deleted.
If the batch job requested is dated the same date as previous batch job, there will be no impact unless the relevant ledger (fixed asset or operating lease) has been updated in some way, in which case revised expenses will be entered. However it is preferable to delete the previous batch job first and then run a user batch job with the same date.
If the user batch job requested is dated between the last automatic batch job and the next automatic batch job (either monthly or annually), then entries will be created up to the date of the user batch job. The next automatic batch job will simply create entries for the period from the user batch job to the automatic batch job date.
Example: Automatic batch job 31/08/2019 User batch job 15/09/2019 - creates entries for the period 1/09-15/09; Automatic batch job 30/09/2019 - creates entries for the period 16/09-30/09
Where a monthly charge schedule has been selected for an entity and a user batch job has been requested for a date later than the next automatic batch job run, then the system will create entries up to the user batch job date. These will not however be automatically reversed when the automatic batch job is run resulting in an excess expenses charge in the accounts. To be correct the user batch job needs to be reversed before the next automatic batch job run. This facility is really only to allow an assessment as to what future lease or depreciation expense could be.
Example: Automatic batch job 31/08/2019 User batch job 31/12/2019 - creates entries for the period 1/09-31/12 Automatic batch job 30/09/2019 - creates entries for the period 1/09-30/09 In effect an extra charge for the period 1/09-30/09 has been created; deleting the user batch job corrects the situation.