Day-end stories

The Stories panel shows how configured customer stories behaved during simulation. You find it on Day-end enquiry, if you have permission to view story outcomes. Counts cover all recorded instances, regardless of the enquiry’s date range.

Read the outcomes

Outcome Meaning
Expected The instance completed every action and check.
Not expected An action failed or a check found a different outcome. That instance stopped.
In flight The instance still waits for a later date or event.
graph LR
    Started["Story starts"] --> Waiting["In flight"]
    Waiting --> Passed["Expected"]
    Waiting --> Failed["Not expected"]
    style Started fill:#059669,color:#ffffff
    style Waiting fill:#374151,color:#ffffff
    style Passed fill:#166534,color:#ffffff
    style Failed fill:#b45309,color:#ffffff

Stories act before that day’s close. A check sees the previous night’s completed work. If a check needs a statement, it waits until the configured date after statement close.

Inspect a failure

  1. Find the story in Stories.
  2. Select View failures.
  3. Read the date, beat, action, and reason.
  4. For a missed check, compare Wanted with Found.

If an action failed, keep its Request reference when asking for help. A failure stops that instance. Other stories and day-end continue. An In flight instance needs more time; it does not count as a failure.

Choose the stories

Your organisation configures the available stories, their cast, start dates, and checks. Stories run only when simulation and story playback are enabled. They use each cast member’s permissions and follow normal approval rules.

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.