Fictional worked example

Open-order snapshot

A static review of 10 fictional open order lines on 6 October 2026: 5 overdue, 3 missing confirmations, and 7 unique lines needing follow-up.

Static demonstration · No client outcomes or live-system changes

Fictional demonstration. All data is invented.

A static review of 10 fictional open order lines on 6 October 2026: 5 overdue, 3 missing confirmations, and 7 unique lines needing follow-up.

Ten fictional order lines with a 29 September prior observation and a 6 October current observation. The same ten lines remain open at both dates.

Before and after

Measure29 Sep 20266 Oct 2026
Open lines1010
Overdue15
Missing confirmation53
Unique exception lines67

Example exceptions

Order lineOpen qtyDue dateFinding
DEMO-OO-0013002026-09-30Overdue
DEMO-OO-0021202026-10-02Overdue; Missing confirmation
DEMO-OO-005402026-09-25Overdue
DEMO-OO-006242026-10-12Missing confirmation

1. What changed

  • Open quantity = ordered quantity - received quantity. Include lines with open quantity above zero.
  • Use the confirmed due date when supplied. Otherwise use the requested date and label it provisional.
  • An open line is overdue only when its effective due date is earlier than the snapshot date. A line due on the snapshot date is not overdue.
  • A blank confirmed due date counts as a missing confirmation, even if a requested date exists.
  • When both dates are blank, overdue is unknown. Count the line as a missing-date exception rather than not overdue.
  • Exception report includes the union of overdue, missing-confirmation and missing-date lines. Count each line once. Due today alone is not an exception.
  • Compare the same fields and order-line IDs between the two supplied observations. Source changes exclude snapshot-date rollover.

2. Calculations and checks

  • Current: 5 overdue + 3 missing confirmations - 1 overlapping line = 7 unique exception lines.
  • DEMO-OO-009 has no due date. Its overdue state is unknown and it already belongs to the missing-confirmation group.
  • Current date categories: 5 overdue + 1 due today + 3 future due + 1 unknown = 10 lines.
  • Prior: 1 overdue, 5 missing confirmations, 6 unique exception lines.
  • Change: overdue +4; missing confirmations -2; unique exception lines +1.
  • Seven source records changed, three were unchanged. Receipts increased by 260 units across three order lines.
  • All 10 IDs are unique and all open quantities are positive at both observations.
  • Confirmed/requested-date precedence, strict date boundary and unknown due date were checked independently.
  • One line is both overdue and missing confirmation, preventing double-counting.
  • Every changed source value is inspectable in the source and change downloads.

3. Decisions still needed

  • Request confirmations for DEMO-OO-002, DEMO-OO-006 and DEMO-OO-009.
  • Ask for a due date for DEMO-OO-009.
  • Ask for updated delivery information on the five overdue lines.

Limits of this example

  • The snapshot is fictional and fixed at 6 October 2026. It is not a live order feed.
  • Source statuses describe the fictional observations and do not confirm physical delivery.
  • Date rules must be agreed for real work. This example uses calendar dates with no holiday adjustment.

Four scheduled updates per monthly billing period. This does not guarantee an update in every calendar week. This demonstration is static and sends no updates.

Bring the problem. We’ll define the project.

A few lines about what you have and what you need are enough to begin.

Tell me what you need