Configure Close of Business
How to configure and authorize COB controls.
COB Configuration controls whether Close of Business is enabled, how it starts, how pending Transaction approvals are handled, and which safety conditions block a run.
Access required
Use Create COB Configuration for a company without one and Update COB Configuration for changes. The record uses maker-checker and Amendments when approval is configured.
Create or change the Configuration
- Open Processing & Monitoring → Close of Business → Configuration.
- Select the Company when shown.
- On General, turn COB on, choose Manual or Automatic, and choose the Pending Transaction Approval Policy.
- For Automatic mode, set Auto Start Time and the 0–120 minute pre-start notification interval.
- On Safety, choose Strict Mode or configure each blocker separately.
- Save a Draft or Save & Submit.
General controls
| Control | What it does |
|---|---|
| Enabled | Allows an Authorized Configuration to be used for COB. |
| Mode: Manual | A permitted user starts each run from the Runs page. |
| Mode: Automatic | remoteEaze queues COB at the configured start time. |
| Notify Minutes Before | Sends the pre-start notice this many minutes before an Automatic run. |
| Rollover pending approvals | Moves the Transactions that were awaiting approval when COB began to the next working day. |
| Block COB until transactions are resolved | Pauses closing until the frozen set of pending approvals has been resolved. |
The pending approval policy is copied into each run. Changing the Configuration later does not rewrite a run that has already started.
Safety controls
Strict Mode turns on every blocking safety policy for new runs. Use it when COB must stop instead of continuing after any configured financial processing failure. When Strict Mode is off, each blocker can be selected separately.
| Control | Effect during prechecks and processing |
|---|---|
| Block on Due FDT Failure | Stops COB if a due Forward-Dated Transaction fails. |
| Block on Pending Retro-Accrual | Stops COB while retro-accrual work is running or after it fails. |
| Block on Interest Accrual Failure | Stops COB when account interest accrual fails. |
| Block on Interest Posting Failure | Stops COB when accrued interest cannot be posted. |
| Block on Failed Schedule Generation | Stops COB when an unresolved loan schedule-generation job has failed. |
| Warn on Pending Schedule Generation | Records a warning when a loan schedule has remained pending for more than ten minutes. |
| Warn on Pending Uncleared Effects | Records a warning when pending uncleared effects are detected. The configuration control is available now; the operational Uncleared Effects workspace will be documented when it is surfaced. |
A warning is evidence for the operator to review. It does not stop the run. A blocker prevents progression until the underlying condition is resolved.
Submit and complete the required L3 → L2 → L1 authorization. Only an active Authorized Configuration can be used to start COB. Updating an Authorized Configuration creates an Amendment when approval is required.