LensReading which lens this session carries.
Back to the single queue

Q-0054 · Arbitration

Who owns the wait between the payables platform and treasury

Decide which of the two functions owns the boundary, or rule that neither does and name a third.

Medium materialityDirectionProcurement & Source-to-PayBoard or committee dateOpen
Consequence
53
of a possible 100, from four factors
Rank in this queue
10th
of 15 open items held by Morgan Idris
Records covered
1
One record, one call.
Work held behind it
296
items that cannot move until this is decided
Waiting
7.7 wk
raised 2026-06-24 by Anneke de Vries · Group treasurer

Why it is ranked where it is

Four factors, scored out of 40, 30, 20 and 10, added to 53.

The commitment it breaches
Is there a window on this, and did it close?
14 / 40
Inside the window, which closes on 2026-09-11.
Measured from: Point scale out of 40: a window already closed scores 40, less than a quarter of the window left scores 28, inside the window scores 14, no window at all scores 0.
The work it holds
How much is stopped behind it?
24 / 30
296 outcome chains cross this boundary and carry whatever it costs.
Measured from: Point scale out of 30, on the count held behind the item: 1,000 or more scores 30, 100 or more scores 24, 25 or more scores 18, 5 or more scores 12, 1 or more scores 6, nothing held scores 0.
The money at stake
What band does the record itself carry?
9 / 20
$214,000 is claimed on one side of this dispute. The two sides do not agree on the figure, which is part of what is being arbitrated.
Measured from: Point scale out of 20, on the materiality band: critical 20, high 15, medium 9, low 4.
Whose clock it is
Is the deadline ours, a regulator’s or a court’s?
6 / 10
The date the question is tabled at a governing body. Missing it does not breach anything; it moves the answer by one cycle.
Measured from: Point scale out of 10, on whose deadline it is: statutory 10, retention 8, board or committee 6, audit 5, expiry 4, service level 3, no clock 0.
The score is carried mainly by work held behind it, which contributes 24 of the 53 points on this item. All four factors score above zero on this item.
The ranking is a scheme, not a measurement. Four factors are scored out of 40, 30, 20 and 10, and the four scores are added. The ceilings were chosen by us and no one has yet agreed them. What is measured is each factor underneath: the window and whether it closed, the count held behind the item, the band on the record and whose deadline applies.
Directly above · 59
Fleet & Assets: AD7C-1005 held at flag
Directly below · 48
The certification stage sits outside the close

The whole context, here

Everything the decision needs, so the queue is not a routing table.

What is being asked
Decide which of the two functions owns the boundary, or rule that neither does and name a third.
Why it is waiting
Invoices approved for payment sit until the next scheduled run. Payables counts the invoice as done at approval; treasury counts it as arriving at the run. The days in between belong to neither. Procurement says: The invoice is approved and matched. Payables has discharged its obligation and the clock should stop at approval. Finance says: Payment runs are scheduled to protect liquidity. Treasury cannot be accountable for a wait created by a calendar the group set deliberately.
Kind
Arbitration
Two functions disagree and neither can settle it.
Money on the record
$214k
This is the figure the source record carries, not an estimate made here.

The clock on it

Board or committee date

Deadline
2026-09-11
3.5 wk left.
Whose clock
The date the question is tabled at a governing body. Missing it does not breach anything; it moves the answer by one cycle.
Measurable against a recorded date.
Measured. The date is stored on the executive decision as the date it is due by.
Commitment: Arbitration due 2026-09-11

Where it came from

The queue holds no work of its own.

Boundary Disputes
/disputes · BD-0001
That page counts 7 waiting and places 7 items here. One record, one item, so the two counts agree.
How items are formed from that page: One item per dispute. Each has a named arbiter and two written positions.
The action that page names is: Arbitrate a boundary two functions each disown. Clearing this item is that same decision.

What the queue will enforce

Checked at submission, not at display.

Authority to sign
Within the cap
The register carries a grant that covers this item at this value. No grant reference is recorded against the item.
Separation of duties
No rule engaged
No separation rule is engaged on this item.
One separation rule blocks and five report. Concentrating decisions on one surface makes that difference load bearing: the queue refuses a self-raised item at the point of submission under SOD-01, and records but does not stop the other five.

Who holds it, and who covers

Morgan Idris · VP Business Services

Addressed to
Morgan Idris
[email protected]
Routing is by remit alone. Nothing about the value of an item changes who receives it, only whether the person who receives it can sign it.
Cover
Anika Kaplan
Director, Security Engineering
Names security engineering as cover. Security engineering names this post back. Both are away on the same two days, so the delegation resolves to a loop and neither queue has anybody in it.
The cover board

Decide it here

The outcome, the reason and the note go in one submission, and the evidence record is written on the way through.

Take the decision as asked. The item closes.
Note written onto the record

What has already been decided on this item

0 decisions on the record

Nothing has been decided on this item yet. The first submission made here will appear in this list with its evidence sequence.
Decisions already on the record were reconstructed from the source rows at assembly and carry no spine sequence. A decision taken here writes one, and the sequence is shown against it.

What this item page is, and what it is not

This page carries the whole of one decision: what is being asked, the four scores that put it where it sits, the clock that applies, the page the row still lives on, and the two rules the queue will check when the submission is made. Deciding it here is the same act as deciding it there. There is no second copy of the work.

The consequence score is ours. The four things underneath it are measured, but the ceilings that turn them into a single number out of 100 were chosen by us and have not been agreed with anyone. Read the factors, not the total, if the two ever disagree.

The authority and separation checks shown above are statements of what will happen at submission. They are enforced by the server when the form is sent, not by hiding controls on this page, so a refusal always names the rule that produced it.