Day-end enquiry
Day end runs every night. The day-end enquiry tells you how long it took, whether it is getting slower, and which step is responsible.
Open it from the System hub, under Day end, or go to Day-end enquiry directly. It opens on the last 90 trading dates, already summarised.
Start with the nights, not the steps
The enquiry has three views, in the order you ask the questions.
| View | Answers |
|---|---|
| By day | Is day end getting slower? |
| By step | Which step is responsible? |
| Steps | What exactly happened on a given night? |
Start with By day. Suspecting a step before you know the nights are getting longer sends you looking for a problem that may not be there.
Reading a night
Each row is one trading date, and it reports two different times.
- Total elapsed is the time from the first step starting to the last step finishing. It is what you wait for.
- In steps is the time the steps themselves took, added up.
- Between steps is the difference.
A large Between steps means the night is being spent somewhere other than the work. That is worth investigating even when every step looks fast.
For example, a night that reports 13.0s total and 6.0s in steps spent 7.0s between its steps — more than half the night outside the work.
A night still being processed reports its total as partial. A night whose last step was skipped still reports a full total: a skipped step takes no time, so it does not shorten the night.
Finding the step that is slowing down
Switch to By step. Each row is one step across the range you chose.
| Column | What it tells you |
|---|---|
| Days run | The nights this step actually ran. A step switched off for part of the range shows fewer days. |
| Average | Its typical duration on the nights it ran. |
| p95 | Its slow nights. Close to the average means it is steady. |
| Records | How much work it did, on average. |
| Rate | Records a second. |
| Growth | How much slower it has become across the range. |
Growth is the number to sort by. Above 1 means the step is taking longer at the end of the range than at the start. About 1 means it is steady.
Read Average next to Records. A step taking 3.6s over 86 accounts is 42 milliseconds an account, which is healthy. The same 3.6s over 8,600 accounts would be remarkable. Without the rate, a slow step and a busy step look the same.
Select Steps on a row to see every night that step ran.
When a column shows a dash
A dash means the number would mislead, so it is withheld rather than guessed.
| Column | Shows a dash when |
|---|---|
| Growth | The range is under twelve trading dates, or the step did not run at one end of it. |
| Rate | The step processed no records. |
A step switched off for the second half of a range has not become infinitely fast — it has stopped running. Growth is withheld rather than reporting that.
Looking at one night in detail
The Steps view lists every step of every night in the range: trading date, step, phase, status, records and duration. Filter it to one step from the By step view, or search it.
Where a night was run twice — a run failed part-way and a later run finished it — the summaries report the later attempt only, so a retried night does not read as a slow one. Both attempts stay in the Steps view, so nothing is lost.
When a step waited for the books
Three steps read the general ledger: the operating-entity balance snapshot, and the two accounting export files. Each one waits until every transaction posted on the day being closed has reached the ledger, so the figures they report and the files they deliver are complete rather than whatever had arrived in time.
On the System hub, a step that read the ledger says what it found.
| What the step says | What it means |
|---|---|
| Books were settled; nothing was waited for. | Everything had already reached the ledger. This is the ordinary night. |
| Waited 2.0s for the books: 1 transaction outstanding. | One transaction was still on its way. Day end waited, then ran the step. |
A wait of a few seconds is normal on a busy night and needs no action. The line is there so that months later you can show the file was complete, rather than assume it.
When the books never catch up
If a transaction never reaches the ledger, day end stops rather than delivering a file that is short of real money. The run fails, and it names the transactions it was waiting for.
Two things are true when that happens, and both matter.
- The trading date has not moved, and nothing was delivered. The night can be run again once the backlog clears.
- A failed close is visible. A short file would not have been.
Take the transactions the failure names to whoever supports your system. They can be retried; the day can then be closed again.
When a step completes with failures
Many steps work through a list: every standing order due, every direct credit waiting for approval, every card clearing item. Each item on the list is handled on its own. If one item fails, the others still go through.
A step like this waits until every item has finished, not just until the work was handed out. Then it reports one of two results.
| The step says | What it means |
|---|---|
| Completed | Every item went through. |
| With failures | At least one item failed. The rest went through. |
A step With failures does not stop the night. The next step still runs, and the run itself reports With failures.
Open the step’s batch from the System hub to see which items failed and why. A failed item is picked up again at the next end of day, once its cause is fixed.
Some steps add a note that says what a failure means for the books. For example, if an exchange rate could not be restated, the note says that the day’s official rates stay provisional. See where today’s exchange rates come from.
Taking the numbers away
Select Export to download what is on screen as a spreadsheet file. The export carries the same range and the same filters as the view you are looking at.
Choosing a range
Set From and To to any period up to one year. A wider range is refused, and the enquiry tells you the widest it accepts. For a longer period, run several enquiries.
Nothing is ever pruned, so any night the system has run remains available.
Nights recorded before this screen existed
A run recorded before the enquiry was introduced keeps its summary line in the day-end run list, but contributes nothing to either view here — its step detail was not kept in the form these views read. The enquiry says so for a range that contains one.
Story outcomes
If your tenant plays stories, read day-end stories for their outcomes and failure details.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.