Skip to main content

A register of contested figures

The Enterprise Discrepancy.

Issue 002 · week of September 21, 2026 · a new issue every Monday at 1:00 PM UTC

One contested figure at a time. Three systems, three answers, none of them wrong about their own records, and the economic consequence worked through in plain arithmetic. Figures below are synthetic and labeled; the point is the pattern, and the pattern is in your estate right now.

SIMULATEDCURATED QUEUEIssue 002 · week of September 21, 2026

The invoice price moved; the purchase order did not

A contract amendment raised the unit price on August 1. Procurement recorded it; the ERP purchase order still carries the old price, so every invoice now fails the three-way match.

  • ERP purchase order · $12.40 a unit
  • Contract system · $12.90 a unit, effective August 1
  • Invoice · 4,000 units at $12.90
  • Receipt · 4,000 units, matched

Value at stake: $2,000 on this invoice; $48,000 across the quarter's releases · Decision owner: Category manager, procurement

Accept the amended price and correct the order, or dispute it with the supplier. Either way the price that stands is decided once, by name, not re-argued at every invoice.

Next issue, September 28, 2026, 1:00 PM UTC: One supplier, three names. A new issue every Monday at 1:00 PM UTC from a curated synthetic queue; a real finding appears only with written customer consent.

Issue 001 · Supplier inventory Week of August 17, 2026 · the first issue, in full

Supplier X's units, on hand, right now. Who is right?

SAP · ERP1,842as recorded
WMS1,517as recorded
Procurement1,932as recorded
Widest gap: 415 units. Each system is true to its own record. The disagreement lives above all three, where nobody is looking.
Simulated figures, labeled as such
$581,000

of inventory nobody can locate, at an illustrative $1,400 landed cost per unit. And the gap is only the visible cost. Planning trusts the ERP, so safety stock is sized against 1,842. The floor can only ship 1,517, so the difference surfaces as an expedite or a stockout at the worst possible moment. Procurement pays against 1,932 received, so 90 units of the gap are already cash out the door. Three departments, three correct reports, one six-figure hole.

How this resolves, in order

  • TraceEach figure back to its dated records: goods receipts in the ERP, bin counts in the WMS, three-way-match lines in procurement. No figure survives here without its receipt.
  • PreserveAll three values stay on the record. Nothing is overwritten, averaged, or silently chosen, because the disagreement itself is the finding.
  • ExplainUsual causes: receipts posted before putaway confirms, a WMS count adjustment that never flowed upstream, an over-receipt paid against the PO. Each carries the records to prove it.
  • DecideRouted to the one person with authority over the figure, who decides with the evidence attached, on the record, with a timestamp.
  • MeasureThe correction is worth a specific number of dollars and days. That number is recorded against the decision, not absorbed into the noise.

Why this is a category and not a data-quality chore. Nothing above involves a wrong system. MDM will not fix it, because there is no bad master record. ETL will not fix it, because every pipeline faithfully carried what its source said. The missing capability is an authoritative answer to whether the systems agree, with evidence, and a named decision when they do not. That is the entire product.

Every figure in this series is synthetic and says so. The first non-synthetic issue will be a real finding from a signed pilot, published with the customer's permission, and it will say that too.

Bring us your disagreement Run a discrepancy session The fifty-six second film

New issues publish here and on LinkedIn. No newsletter and no sequence, by standing policy; follow Shadow Key or check this page.