OHM · Workflows · Daily close
Daily close
The close stops being an event because nothing is deferred to it.
A monthly close exists to catch up on a month of decisions nobody had time to make properly. When entries arrive clean and reconciliations run daily, there is nothing to catch up on.
The same step, two ways
How it runs today
- Entries accumulate through the month, correct enough to post and wrong enough to fix later.
- Reconciliations run at the close, so a break from week one is found in week five.
- The first reliable number appears well after the period it describes.
- Everyone knows the first version of the close is not the final one.
With the team on it
- Entries are checked at the moment they arrive, so nothing accumulates.
- The sub-ledger agrees to the control account every day.
- Breaks are found on the day they appear, when the cause is still obvious.
- The period-end number is a confirmation, not a first draft.
Who runs, and what they enforce
All of them, on the same daily position, at the same time. Not a queue.
| Agent | What it enforces |
|---|---|
| Journal Agent | Entry balanced, support attached |
| Reconciliation Agent | Sub-ledger agrees to the control account |
| Period Agent | Posted in the open period |
| Audit Agent | Immutable trail written |
| Report Agent | Books ready to report, no cleanup pass |
Agents without a link yet are part of the team but do not have a page written up.
What lands in your ERP
A position that is current every day rather than accurate once a month, with anything unresolved named and owned instead of absorbed into the close.
Current
The stamp on a daily position that cleared this step. It means every check ran and passed — not that a sample did, and not that it will be reviewed later.
See this step run on your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→