Run and monitor Close of Business
How to start, monitor, retry, and complete COB.
COB runs a controlled 27-step sequence for one company's current working date. It cannot be cancelled once queued.
Access required
Create COB Run triggers and retries a run. Read COB Run opens run status, steps, snapshots, blockers, and exceptions. Export COB Run enables the run export.
Trigger a run
- Complete Before running the first COB.
- Open Processing & Monitoring → Close of Business → Runs.
- Select Trigger COB. An L0 user selects the Company.
- Review the warning and confirm.
The server rejects a trigger when another run is active, the current working date already has a canonical run, the COB Configuration is missing or not Authorized/enabled, or a blocking precheck fails.
Monitor the run
The header shows the business date, overall status, progress, elapsed and active processing time, time spent waiting, the pending-approval policy, the effective safety policy, and the number of frozen pending approvals.
Use the four tabs as follows:
| Tab | What to review |
|---|---|
| Steps | Each of the 27 ordered steps, its status, start and completion times, duration, processed count, and summary. Start here when a run pauses or fails. |
| Account Snapshots | Per-Account opening and closing balances, forward values, interest values, and the balance evidence captured by COB. Use this for account-level reconciliation. |
| Product Snapshots | Aggregated daily, month-to-date, and year-to-date Product balances. Use this for financial control and Product-level reconciliation. |
| Posting Exceptions | Financial postings that failed, including their source and error. Resolve the cause before retrying failed postings. |
When the policy is Block COB until transactions are resolved, use Review pending approvals to inspect the exact Transactions frozen at the start of the run. This set does not grow as new Transactions are submitted later.
The sequence processes due Forward-Dated Transactions, account and loan state, interest, commissions, penalties, provisioning, pending approvals, ordinary postings, balance snapshots, period rollovers, workday advancement, and notifications before finalization.
Retry a failed run
First identify the failed step or Posting Exception and correct its underlying configuration, Account, Transaction, schedule, or infrastructure cause. Then select Retry failed postings for posting exceptions, or use the run retry action with Create COB Run for an eligible failed run.
Retry is allowed only for the failed canonical run on the current business date. It continues the same controlled run and does not create a parallel COB for that date.