Part 1: Understanding Batch Processing

Problem
Users need to run multiple reports or processes automatically — such as end-of-month resets, account status reports, and direct debit postings — without manually launching each one. Batch Processing allows these tasks to be grouped, sequenced, and run together.

Key concept: Most batch tasks require a saved public Preset before they can be added to a batch. The preset stores all the parameters the task needs (dates, output file path, format, etc.). Without a valid preset, the batch will fail to initiate.

Exceptions — tasks that do NOT require a preset:

• End of Month resets

Part 2: Setting Up Presets

Before building a batch, create a public preset for each report or process task you intend to include.

Access: Open the relevant report or process dialog from its module menu (e.g. Fixed Loan | Account Status Report).

1. Enter all required field values — date ranges, output format, file path, filename, etc.
2. For any date fields, press [F2] to open the Date Builder and set a dynamic date (e.g. "today minus 1 day", or "Fixed Loan Month End date"). This ensures the preset stays accurate each time it runs without manual edits.
3. For report output, set the following fields:
   • Output Format — select PDF, Excel, CSV, or other as required
   • File Folder — [F2] to browse and select the destination folder
   • Filename Prefix — enter a short descriptive prefix (e.g. AccStatusRpt)
   • Filename Date — [F2] to use the Date Builder; this appends the date to the filename so files are never overwritten
   • Date Format — select DDMMYY for daily reports, MMYY for monthly reports
   • The Resulting Filename field will preview the full file path and name
4. Click [Preset] and select Save As.
5. Enter a meaningful preset name (e.g. EOM Account Status Report).
6. Set the preset to Public — this is mandatory for batch use. Private presets cannot be selected in Batch Processing.
7. Deselect Startup Preset unless you want this to load automatically for all users on this dialog.
8. Save the preset.

Note: File locations specified in report output presets must be valid network paths. The system will verify the path when the preset is saved. If the path is invalid, the batch will fail to start — not just fail a task.

Note: If more than one user needs the same report output to a different location, set up separate presets with each user's file path, and add them as separate tasks in the batch.

Part 3: Creating a Batch Process

Access: Batch Processing | Edit/View Batch Processes | [Add]

1. Enter a Code for the batch (e.g. EOM1).
2. Enter a Description (e.g. End of Month Process).
3. Click [Add Task] to add the first task to the batch.
   • Select the Module (e.g. Fixed Loan, Accounts, Lease).
   • Select the Task from the list of available tasks for that module.
4. On the Batch Task Details dialog, complete:
   

5. Click [OK] to add the task.
6. Repeat steps 3–5 for each additional task.
7. Use the [Up] and [Down] buttons to set the correct sequence order.
8. Save the batch process.

Tip: Use [Duplicate] on the Batch Process Browse to copy an existing batch (including its presets) as a starting point for a new one.

Part 4: Available Batch Processing Tasks

For a full list of reports and processes available for batch processing, grouped by module, refer to the Batch Processing Tasks article:

Batch Processing Tasks

Part 5: Running a Batch Process Manually

Access: Batch Processing | Edit/View Batch Processes

1. Highlight the required batch in the browse list.
2. Click [Run] to initiate.
3. If the Argos Server is online, a prompt will appear asking whether to run on the server or on your local computer. Select as appropriate.
4. A progress bar will display while the tasks execute.
5. On completion, review the results dialog and click [OK] to confirm all tasks completed as expected.
6. If the results dialog is closed accidentally, the log can be accessed via: Control | View Batch Log File, or navigate to C:\Users\{your windows login}\AppData\Local\Temp and open the XML file named {BatchName}_xxxxxxxx.xxxx.xml.

Batch Log — what to look for:

• Header Status: Shows overall result — Completed or Failed.
• Individual task status: Any failed task will show as Failed with an error message. Use this to identify which step broke and why.

Part 6: Scheduling a Batch via the Argos Server

Access: Batch Processing | Edit/View Batch Processes — highlight the batch and click [Run]

1. On the Create Job dialog, select the required frequency from the dropdown.
2. Enter the Start Date and Start Hour (0–23) as required for the selected frequency.
3. Click [OK].

Frequency Options:

The Argos Server will execute the batch at the nominated frequency. Monitor job status from the server application — the Job Status grid shows job ID, created time, status (Ready to Start / Started / Completed / Cancelled), and any error messages.

Note: Only one Argos Server can be online at a time. If the server goes offline mid-job, the job will not be reassigned to another server — it will need to be re-run manually.

Result
Batch tasks run in sequence and produce output to the specified file locations. The batch log confirms which tasks succeeded and flags any failures with error messages for follow-up.

Tidy Up

• Confirm output files have been created in the correct folders after the first run.
• Verify preset file paths are accessible by all relevant users.
• Check that any posting tasks in the batch (e.g. Post Direct Debits, End of Month Reset) are sequenced after any reports that depend on pre-posted data.
• For recurring batches, confirm the Argos Server is set to start automatically with Windows — your IT department may need to assist with this.

Related articles to cross-reference:

• Presets
  
• Date Builder
  
• Batch Processing Tasks
• Using the Argos Server to Run a Batch Process
  
• End of Month Reset
  
• Batch Process Browse
  
• Batch Task Details
  

Examples

Example 1 — End of Month Batch: Fixed and Variable Loans

A typical end of month batch sequence covering Fixed Loan, Variable Loan, Insurer, Dealer, GL reporting, and Cashbook posting.

Notes on this sequence:

• All EOM resets are placed before the GL Trial Balance — this ensures the report reflects the newly rolled month end figures.
• The General Ledger EOM Reset is placed last — the GL should only be rolled after all module resets and reports are complete.
• Database Backup is sequenced before Cashbook Posting so a restore point exists prior to the final posting run.
• For tasks 5–7, ensure public presets are created and saved before running this batch. The batch will not initiate if any required preset is missing or has an invalid file path.
• Set Continue if Batch Task Fails to OFF for all posting and reset tasks — a failure in any of these steps should halt the batch rather than allow subsequent processes to run against incorrect data.

Example 2 — Daily Processing Batch: Fixed and Variable Loans

A typical daily processing batch sequence for Fixed and Variable Loan modules.

Notes on this sequence:

• Cashbook Posting to Other Systems runs first to ensure all cashbook transactions are posted to modules before instalment and interest processes run.
• Fixed Loan Instalments and Variable Loan interest and instalments are sequenced before the GL posting so all transactions are available to post to the General Ledger in a single step.
• All tasks in this batch require a preset. Ensure public presets with valid file paths are in place before running.
• Set Continue if Batch Task Fails to OFF for all tasks — a failure in any posting step should halt the batch to prevent incomplete or out-of-sequence postings.

Example 3 — Month End Reporting Batch: Fixed and Variable Loans

A typical month end reporting batch covering account status, closed accounts, top exposure, transaction summaries, interest, fees, arrears, and reconciliation reporting across Fixed and Variable Loan modules.

Notes on this sequence:

• All tasks in this batch require a preset. Ensure public presets with valid output file paths and dynamic dates (using Date Builder) are configured before running.
• Use the Date Builder set to the Fixed Loan or Variable Loan month end date for all date fields in presets — this ensures reports always cover the correct period without manual updates each month.
• Reports and exports are paired in sequence (e.g. Unearned Interest Report followed immediately by Unearned Interest Export) so outputs are generated together and easy to reconcile.
• The Cashbook Reconciliation Report is positioned after all loan reporting to capture the full picture of transactions for the period.
• This batch is reporting only — no posting or reset tasks are included. It should be run after the EOM reset batch (Example 1) has completed successfully.
• Set Continue if Batch Task Fails to ON for reporting tasks — a single report failure should not prevent the remaining reports from running.

Example 4 — Statement Creation Batch

A typical batch for bulk generation of account statements across Fixed and Variable Loan modules.

Notes on this sequence:

• All tasks require a preset. Ensure public presets are configured with the correct date range, output format, and file path before running.
• Use the Date Builder in presets to set dynamic statement period dates so the batch can be run each month without manual updates.
• Set Continue if Batch Task Fails to ON — a failure generating one statement type should not prevent the remaining statement tasks from running.