ARPIn practice

Eight chains, each traced to the entry it leaves

One domain at a time, from the event that starts the chain to the posting that ends it, with the resource classes each chain crosses named and the steps a person holds marked as theirs.

Eight domains81 steps tracedReviewed September 2026

Each chain runs to the posting

A chain is traced to the consequence it records, because that is where the difference between advising and acting becomes checkable. A description that stops at the recommendation is true of a system that files a suggestion and true of a system that changes the position, and the reader cannot tell which one is being described. A chain traced to the entry can be held against a system: ask which step it reaches, and who does the rest.

Every chain also names the resource classes it crosses, and the naming is a discipline, not a label. A chain confined to one class is a point tool. Point tools are worth buying and they are not this. The eight chains here touch all 7 classes the definition enumerates, and not one of them stays inside a single class from trigger to posting.

The steps are marked by who holds them. A filled node and the word Human mean a person decided; an open node and the word System mean the system did. 9 of the 81 steps below are a person’s, and they are not distributed evenly. They sit where authority to commit something, or judgement about something outside the record, actually belongs.

DomainClasses crossedStepsWhere a person appears
Period closeMoney, Information, Time, Agents10Steps 6 and 9
ProcurementMaterials, Time, Money, Information11Step 9
InventoryMaterials, Time, Capacity, Money10Step 9
ManufacturingCapacity, Materials, People, Time10Step 8
Supply chainMaterials, Time, Money, Capacity10Step 6
TreasuryMoney, Time, Agents, Information10Step 8
RevenueMoney, Information, Time, Materials10Step 9
WorkforcePeople, Capacity, Money, Time10Step 9

The eight, traced

The detail is the point. A chain drawn at the altitude of a diagram can be agreed to in a meeting without anything being checked. These are traced step by step, and to the entry.

Chain 01

Period close

Classes crossed

The close is the chain most often produced as evidence that a system acts, and it is the narrowest one here: it moves money and information and very little else. It is first so the other seven can be read against it.

Trigger

The last subledger for the period stops accepting postings and the close calendar opens on day one, with the prior day's bank statements and the final goods receipts already in.

The chain, step by step

  1. 01System

    Reconciles every bank account to the cash ledger at statement line level, clearing what matches and listing what does not by age, value and account, never as a single difference.

  2. 02System

    Accrues for goods received and not yet invoiced by pairing open goods receipts against purchase order prices, and reverses the prior period's accrual first so the same cost cannot be carried twice.

  3. 03System

    Runs depreciation and amortisation across the fixed asset register, including assets capitalised mid period, which are depreciated from their in service date, not from the period start.

  4. 04System

    Revalues foreign currency monetary balances at the period end rate and posts the unrealised movement to the revaluation account, leaving non monetary balances at historic rate.

  5. 05System

    Matches intercompany balances pair by pair, eliminates what agrees on both sides and lists what does not with the counterparty entity, the amount and the age of the difference.

  6. 06Human

    The controller dispositions one accrual the system cannot settle, on a contract in dispute where the amount owed turns on whether a delivery obligation was met. The reading of the obligation is the input the ledger does not hold.

  7. 07System

    Runs the variance review at account level against prior period and budget, holding every account whose movement exceeds the stated threshold until the movement is attributed to transactions it can name.

  8. 08System

    Posts the entries that fall inside its grant, each carrying the evidence it was built from, the version of the policy in force and the accounts it was read from.

  9. 09Human

    The controller signs the close, which is the point at which responsibility for the reported position passes to a person who can answer for it.

  10. 10System

    Files the close package, locks the period against further posting, and records the trial balance, the entry list and the open reconciling items as the record of what the period was closed on.

Escalates when

An entry above the value ceiling in the grant, an intercompany difference that survives matching, a bank item unreconciled beyond the stated age, or an account whose variance the system cannot attribute to transactions it can name.

Recorded consequence

A closed period: journals posted to the ledger, the period locked, and a trial balance signed by a named person, with every entry reconstructable to the evidence and the policy version that produced it.

Chain 02

Procurement

Classes crossed

This is the chain the category was named for, and it is worth following past the point most descriptions stop. The order is placed a third of the way down it. Everything after that is the part a recommendation leaves for somebody else.

Trigger

A customer order is amended upward inside the frozen horizon, which changes the demand for a finished item the plan had already covered.

The chain, step by step

  1. 01System

    Reads the amended demand and recalculates the dependent requirement for every component through the bill of materials, each dated to the operation that consumes it, not to the order.

  2. 02System

    Compares the new requirement against projected on hand by date and finds one purchased component short in week three, once safety stock is held back instead of counted as cover.

  3. 03System

    Evaluates the cover that already exists before creating anything: stock on hand, stock allocated to other orders, open purchase orders at their confirmed dates, and quantities sitting in inspection.

  4. 04System

    Reads the approved supplier list for the component, with each supplier's quoted lead time, minimum order quantity, price break and measured delivery performance on that part.

  5. 05System

    Costs the options against each other: expedite an open order with the incumbent, split the requirement across two approved suppliers, or place a single order at the next price break.

  6. 06System

    Places the purchase order with the supplier whose lead time closes the shortage, inside the value ceiling and the supplier scope of its grant, at the contracted price and terms.

  7. 07System

    Monitors fulfilment against the confirmed date, reading the supplier acknowledgement and the despatch advice, and reschedules the dependent operations when the acknowledgement differs from the request.

  8. 08System

    Matches receipt, purchase order and supplier invoice on quantity, price and tax, and posts the goods receipt and the payable when the three agree inside tolerance.

  9. 09Human

    A buyer settles the one price difference outside tolerance, where the invoice carries a surcharge the contract does not name. The question is contractual, not arithmetic, and it is answered with the supplier.

  10. 10System

    Updates the cash requirement at the payment date from the new payable and passes it to the cash forecast, so the order is visible as a claim on cash before it is due.

  11. 11System

    Posts the consequence and records the chain that produced it: the demand change that started it, the shortage it answered, the alternatives weighed and the order that settled it.

Escalates when

Only outside policy: a value above the ceiling, a supplier not on the approved list, a lead time that cannot close the shortage without breaking a customer commitment, or a price variance beyond tolerance.

Recorded consequence

A purchase order placed and acknowledged, a goods receipt and a payable posted against it, the component covered on the date the operation needs it, and the cash forecast carrying the payment.

Chain 03

Inventory

Classes crossed

The reorder point and the safety stock are corrected as well as the position. That is the difference between answering the shortage and answering what produced it, and only one of the two stops the shortage happening again next quarter.

Trigger

A cycle count records a variance on a fast moving item at one distribution centre, and the corrected quantity on hand falls below its reorder point.

The chain, step by step

  1. 01System

    Posts the count variance to the inventory adjustment account and keeps the count sheet as evidence, so the corrected quantity is the position every later step reads.

  2. 02System

    Recalculates the reorder point from measured demand variability and supplier lead time variability against the item's stated service level. The figure set when the item was created is not reused.

  3. 03System

    Projects the position forward by date across the network, netting open replenishment orders, stock reserved against customer orders and forecast demand at each site.

  4. 04System

    Finds cover at a second distribution centre that sits above its own reorder point and outside its demand season, and compares a transfer against a new supplier order on landed cost and arrival date.

  5. 05System

    Confirms the receiving site has the putaway capacity and the storage conditions the item requires, since a transfer that arrives with nowhere to go is not cover.

  6. 06System

    Raises the transfer order inside its grant and reserves the stock at the sending site, so the same units cannot be promised to a customer order while they are in transit.

  7. 07System

    Resets safety stock at both sites for the lead time profile it just measured, which is the durable correction; the movement itself was only the symptom.

  8. 08System

    Reviews the item's ageing while it holds the position, measures the slow moving and obsolete quantities against the reserve policy and recalculates the provision.

  9. 09Human

    A planner rules on the obsolete quantity: a write down, a return under the buyback clause in the supplier agreement, or a clearance sale that touches the pricing of the live range. The choice commits value and sits with a person.

  10. 10System

    Posts the movement, the revised provision and the carrying cost effect, and records the variance against the site's inventory accuracy measure.

Escalates when

A count variance above the value threshold, a transfer that would take the sending site below its own service level, a provision change beyond the ceiling in the grant, or a second variance on the same item inside the quarter, which is a process fault, not a stock fault.

Recorded consequence

Stock corrected in the ledger, a transfer order raised and the units reserved against it, reorder point and safety stock reset from measured variability, and the obsolescence provision posted at its new figure.

Chain 04

Manufacturing

Classes crossed

A scrap report arrives as a production event and settles as a variance, a held tool and a moved customer date. No one function owns that set, which is why a shop floor system that ends at the rescheduled order has finished a task and not a result.

Trigger

Scrap is reported at the second operation of a released work order, which leaves the order unable to complete its released quantity from the material issued to it.

The chain, step by step

  1. 01System

    Records the scrap quantity against the operation with its reason code, and recalculates the yield through the rest of the routing from the quantity that survives it.

  2. 02System

    Confirms the shortfall against the order, not against the schedule: the released quantity can no longer be built from the material already issued.

  3. 03System

    Checks material availability for a replacement lot, including stock already allocated to other work orders, and finds part of the quantity free and the balance committed.

  4. 04System

    Checks the work centre calendar for the capacity to run the balance, against the shifts the finite schedule has already committed to other orders.

  5. 05System

    Compares a supplementary work order on the same line against resequencing the order behind it, on the customer dates each option touches and the changeover each one costs.

  6. 06System

    Raises the supplementary work order, issues the replacement material to it and reserves the work centre time on the shift that closes the gap.

  7. 07System

    Measures the scrap rate for the operation against its control limit and finds the limit breached across the last three orders run on the same tool.

  8. 08Human

    A quality engineer dispositions the scrap: rework or reject, whether the lot is contained, and whether the tool comes off the line. Containment is a judgement about the risk to parts already shipped.

  9. 09System

    Posts the scrap and the material usage variance to the manufacturing variance accounts, and carries the lost hours into the absorption of the work centre.

  10. 10System

    Recalculates the promise date on the sales order the work order serves and republishes the available to promise position for the item.

Escalates when

A scrap rate above the control limit, a rework disposition that departs from the specification, a resequence that breaks a committed customer date, or a supplementary order that takes the work centre past its planned hours.

Recorded consequence

A supplementary work order released and scheduled, material issued and reserved against it, scrap and usage variances posted, the tool held pending quality, and the promise date on the customer order restated.

Chain 05

Supply chain

Classes crossed

The system does everything here except decide who goes short. That is the shape of a well drawn grant: it can spend freight money up to a ceiling and it cannot spend a customer relationship at all.

Trigger

A carrier milestone moves the arrival of an inbound container out by nine days, on a lane that feeds two distribution centres.

The chain, step by step

  1. 01System

    Updates the shipment's estimated arrival from the carrier message and revises every date downstream that had been calculated from the old one.

  2. 02System

    Recomputes cover by item and by site across the delay window, and identifies the three items that run out before the container now lands.

  3. 03System

    Lists the customer orders that lose cover, with their promised dates, the service levels their contracts carry and the penalty terms attached to them.

  4. 04System

    Evaluates the alternatives side by side: airfreight for a partial quantity, a transfer from the site holding surplus, a substitution the engineering record already permits, and doing nothing.

  5. 05System

    Costs each alternative against the exposure it avoids, counting freight, handling, penalty terms and the carrying cost of the stock it would move.

  6. 06Human

    A supply planner decides the allocation, because cover cannot serve every order: which customers go short and by how much. That is a commercial judgement about relationships, and not an optimisation.

  7. 07System

    Books the partial airfreight inside its freight authority, raises the transfer order for the balance, and reserves the inbound slots at the receiving sites so the stock can be put away on arrival.

  8. 08System

    Restates the promise dates on the affected orders and records the reason against each one, so the customer facing record says why the date moved and on whose decision.

  9. 09System

    Accrues the freight and updates landed cost for the units moved, which changes the margin on the orders they serve and the valuation of what remains.

  10. 10System

    Records the carrier's performance on the lane and the supplier's delivered in full position, which is the evidence the next sourcing decision reads.

Escalates when

Freight above the expedite ceiling, an allocation that breaches a contractual service level, a substitution the engineering record has not approved, or a second delay on the same lane inside the quarter.

Recorded consequence

Airfreight booked and accrued, a transfer order raised and slotted, promise dates restated with their reasons, landed cost and margin updated, and the lane's carrier record adjusted for the next sourcing decision.

Chain 06

Treasury

Classes crossed

Every step sits inside a limit somebody set: a sweep mandate, a counterparty limit, a hedge policy band, a notional ceiling. Treasury is the domain where bounded authority was ordinary practice long before software asked to hold any.

Trigger

Prior day statements arrive across the group's bank accounts and the day's position is built before the payment cut off.

The chain, step by step

  1. 01System

    Imports the statements, reconciles them to the cash ledger and clears the matched items, so the opening figure is a reconciled position, not a bank balance.

  2. 02System

    Builds the intraday position by account and by currency from the flows it knows: collections received, the payment run, payroll, tax payments and the deposits maturing today.

  3. 03System

    Identifies a projected overdraft on one entity's operating account and a surplus on another, in the same currency and on the same value date.

  4. 04System

    Tests the intercompany funding option against the constraints that govern it: the lending limits in the group policy, the interest terms required for the arrangement to stand at arm's length, and the withholding treatment between the two jurisdictions.

  5. 05System

    Executes the zero balance sweep into the header account inside the sweep mandate, leaving each participating account at its agreed target balance.

  6. 06System

    Places the residual surplus inside the limits that apply to it: the counterparty limit, the concentration limit across the portfolio, and a tenor the forecast will support without an early break.

  7. 07System

    Recalculates net exposure by currency pair after the day's flows and compares it against the hedge policy band, separating contracted exposure from forecast exposure instead of netting the two.

  8. 08Human

    The treasurer confirms the forward above the notional threshold, and the intercompany loan with it. Both commit the group to a counterparty beyond the day, and that is where the grant stops.

  9. 09System

    Executes the forward inside the notional ceiling of the grant, and records the trade, its confirmation and the hedge designation against the exposure it was taken for.

  10. 10System

    Posts the sweep, the investment, the loan and the deal entries to the ledger, and reconciles each settlement when the following day's statements arrive.

Escalates when

A counterparty or concentration limit that cannot be met without breach, an exposure outside the policy band that cannot be closed inside the grant, a funding need that requires uncommitted borrowing, or a sweep that would take an account below a local minimum balance requirement.

Recorded consequence

Accounts swept to target, the surplus placed inside counterparty and concentration limits, the overdraft funded intercompany at arm's length terms, the forward executed and designated against its exposure, and every deal and cash entry posted to the ledger it was decided from.

Chain 07

Revenue

Classes crossed

The chain begins in metered usage and ends by releasing stock that had been reserved for an order. A revenue system that never reaches the warehouse has not finished the collection decision it started.

Trigger

Metered usage closes for a billing period on an account that has crossed its committed tier, under a contract carrying a ramp and an annual minimum commitment.

The chain, step by step

  1. 01System

    Rates the usage against the contract's price book: the committed tier, the overage rate above it, and the drawdown against the minimum commitment already consumed this year.

  2. 02System

    Applies the credits and the ramp in force for the current contract year, and reconciles the rated quantity back to the metered records it was built from.

  3. 03System

    Determines tax by jurisdiction from the place of supply rules for the service and the customer's registration status, never from the address on the account.

  4. 04System

    Issues the invoice on the date the contract names, through the channel the contract names, carrying the usage detail the customer's terms require for it to be payable.

  5. 05System

    Recognises revenue against the performance obligations in the contract, releasing deferred revenue for the period served and holding back what the overage has not yet satisfied.

  6. 06System

    Monitors the receivable against terms, applies received cash to open items at invoice level, and opens the dunning sequence at the days past due the collections policy states.

  7. 07System

    Recalculates credit exposure for the account from the ageing, the unbilled usage and the open orders, and finds the credit limit breached.

  8. 08System

    Places the account on credit hold, which stops a pending order and releases the stock that had been reserved for it back to available inventory.

  9. 09Human

    A credit controller settles the hold: a payment plan, shortened terms, a partial release against a deposit, or a stop. What the account is worth and what the relationship will bear are inputs the ledger does not carry.

  10. 10System

    Posts the provision on the aged balance under the expected credit loss policy, and records the dispute, its reason and its resolution against the invoice it belongs to.

Escalates when

A disputed invoice, a contract modification that changes the allocation of the transaction price, a credit hold on an account above the exposure ceiling, or a write off beyond the value in the grant.

Recorded consequence

An invoice issued and posted, revenue recognised against its performance obligations with deferred revenue released, the receivable in the collections sequence, the credit hold recorded with the order it stopped and the stock it freed, and the loss provision at its new figure.

Chain 08

Workforce

Classes crossed

An absence is answered as a capacity question and a cost question at the same time. The system ranks the options against both and a supervisor spends the budget, which is the division the final posting records.

Trigger

An absence is recorded before the shift starts and leaves the day shift one certified operator short on a line already committed to the day's production schedule.

The chain, step by step

  1. 01System

    Compares the roster against the staffing the schedule requires, by skill and by certification, and establishes which line and which hours are uncovered.

  2. 02System

    Rebuilds the day's labour demand from the production schedule, not the roster, so the shortfall is measured against the work and not against a plan already overtaken.

  3. 03System

    Builds the qualified pool: current certification for the operation, contracted hours still unused this week, rest period since the last shift, and the working time limits that apply to each person.

  4. 04System

    Ranks the pool by cost: contracted hours not yet used before overtime, overtime before agency cover, with the premium each option carries stated against it.

  5. 05System

    Checks overtime spend for the period against the site's labour cost plan and finds the remaining budget covers part of the uncovered hours.

  6. 06System

    Offers the shift to the ranked pool through the scheduling channel, with the hours, the premium and the time the offer closes stated in the offer.

  7. 07System

    Takes the acceptance, updates the roster, and passes the hours and the premium to payroll for the period they fall in.

  8. 08System

    Finds part of the shift still uncovered when the offer window closes, and models what remains: run the line at a reduced rate, resequence to a product the available skills cover, or bring in agency cover above the budget.

  9. 09Human

    The shift supervisor chooses between the reduced line rate and agency cover above budget. The trade is the day's output against the labour cost plan, and the authority to spend that budget belongs to a person.

  10. 10System

    Posts the labour variance for the shift against standard, and records the vacancy against the skill so the pattern reaches the establishment plan instead of being absorbed shift by shift.

Escalates when

A shift still uncovered at the offer deadline, an assignment that would breach working time or rest rules, a certification that has lapsed or expires inside the shift, or agency cover beyond the overtime authority.

Recorded consequence

The shift covered to the hours the schedule required, roster and payroll updated with the premium, the line rate and the sequence restated where cover fell short, the labour variance posted, and the recurring vacancy recorded against the skill it belongs to.

What the eight have in common

The domains were chosen to be as far apart as enterprise work gets. A controller, a buyer, a production planner, a treasurer and a shift supervisor would not recognise each other’s daily work. Three properties survive the distance anyway.

Every chain ends in a posting

Not a recommendation, a queue or a notification. A journal, a purchase order, a transfer, a work order, a booked shipment, a deal, an invoice, a roster and the payroll behind it. Each of those is a change to the record the system read from, and each is the point at which the system has spent something on the company’s behalf instead of proposing that somebody else spend it.

This is also what makes the chains testable from outside. The last line of each one names an artefact somebody can ask to see, and a system that cannot produce it has not run the chain, whatever the demonstration showed of the steps before. Reconciliation is what closes the distance between the instruction and the artefact, which is why several of the chains keep running after the action lands.

Every chain crosses classes

Not one of the eight stays inside a single resource class, and the crossings are not incidental to the work: they are the work. Scrap is a materials event that becomes a capacity problem and settles as a variance and a moved commitment. A credit hold is a money decision that releases reserved stock. An absence is a people event answered against a production schedule and a labour budget at the same time.

A system that plans one class well handles the first step of each of these chains and hands the rest across a boundary, where the trade between the two classes is made by whoever happens to be holding both. That trade is the thing worth recording, and the cross-functional principle asks for it as a document, not as an outcome somebody can reconstruct afterwards.

The person appears where authority or judgement belongs

9 steps of 81 are held by a person, and every one of them is one of two things. Either a commitment beyond the grant: a forward above the notional threshold, agency cover above the budget, a write down of stock. Or a judgement about something the record does not contain: whether a delivery obligation was met, whether a lot is contained, which customer goes short.

The shape matters more than the count. A system that routes every step to a person has automated nothing and calls the queue oversight. A system that routes none of them has taken authority nobody granted it. What the chains show is the third arrangement: the person is rare, the person is late in the chain, and the person is at the step where being wrong is expensive in a way the system has no standing to settle.

That arrangement is also what makes the chains readable as a grade instead of as stories. Take any one of them against a system you run, find the step it reaches, and the answer is a position on the maturity model for that class, not an impression of the whole system.

A chain is graded per class, because no system is at one level across all of them.

The maturity model