Close Runs
The month-end job set (Platform > Batch Sets, CLOSE-MONTH) run by the server, step by step: recurring entries, revaluation, depreciation, intercompany, consolidation, the readiness check and the soft close. It stops at the first step that fails and says why; Resume carries on from that step.
Where to find it
- Module: Accounting
- Group: Close & Compliance
- Section: Finance Automation
- Screen: Close Runs
Address in the console: /accounting/close-job-runs
Read-only list · 9 columns · 3 actions
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Run | Code | run_no |
| Period | Code | period_code |
| Rehearsal | Yes or no | dry_run |
| Steps done | Number | steps_done |
| Of | Number | steps_total |
| Stopped because | Text | stop_reason |
| Resumed | Number | resume_count |
| Started | Date and time | started_at |
| Status | Status | status |
What you can do here
Run the close primary
Run the month-end close on the server
Asks for: Period (YYYY-MM)* Rehearse only (change nothing)
Steps
Each step and what it did
Resume primary
Asks for confirmation: Carry on from the step that stopped this run? The steps already done are not run again.
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.