Library / Management Accounting Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:16:56 UTC

Part of a long section. Showing characters 1–59887 of 136207. Continue below for the remaining text.

Preface

MA.Preface:1 - The working problem

A controller is asked whether another order is worthwhile. The report supplies a cost per unit, but the order needs a setup, qualified staff and perhaps an extra machine block. The unit cost does not explain those dependencies. Elsewhere, a manager sees profit rise while cash falls, or receives a demand forecast that has been negotiated to match a spending ceiling.

Management Accounting serves these internal accounts and their uses. Its central work is to construct and interpret the relationships between work, resources, money, expectations and measured performance. The resulting account can support a decision, explanation or inquiry. The decision itself retains the criteria and authority of the responsible operating, financial or management practice.

An account’s purpose matters. A required external statement, a resource-consumption model and a timed cash account can all be correct while carrying different amounts. The aim is to supply the account the receiving use needs and preserve its relationship to the other valid views.

MA.Preface:2 - How the methods connect

Start from the account or decision that must become possible, then work back to its missing inputs. A funding question needs receipts and payments at their dates. Obtaining those dates may require the workload, its resource demand and the actual supply or settlement arrangement. Keep an adequate supplied result; use its owning method when the result is missing or its assumptions no longer fit. This backward reading selects the necessary work, while the resulting inputs are then combined into the receiving account.

MA.1 constructs the resource-consumption and cost model when it is missing. It begins with work outputs and consequential resource dependencies, then relates quantities to supply, money and payment time. It also chooses detail: an interval can suffice when its variation cannot change the relevant threshold or comparison.

MA.2 and MA.3 are independent entries when capacity or shared assignment is the unresolved problem. Their results can improve MA.1’s model, but neither is a mandatory stage in every model construction. MA.4 reconciles operating, reporting and cash accounts by carrying their opening balances through the relevant events to closing balances under each view’s rules.

MA.5 constructs compatible demand inputs and carries them through resource relationships and balance movements to forecast the relevant outlook. MA.6 preserves its distinction from targets and resource decisions. MA.7 constructs intermediate accounts to explain a difference, including changed product mix, without treating arithmetic decomposition as causal evidence. MA.8 constructs cohort and product accounts across calendar periods and separates the whole history from a future choice, and MA.9 examines what an account’s actual use encourages people to do.

Before joining results, align their population, period, quantities and account meanings. Units ordered, units produced and units delivered can differ. A cohort’s second month is an age, not necessarily the calendar month used by another cohort. A resource-consumption value, a shared assignment and a payment can all describe the same work without being interchangeable amounts.

For a shared resource, add the demands that compete in the same calendar window before applying its usable-capacity, reserve or supply-block condition. Use the resulting supply arrangement to obtain payment once in the whole account. Two separately feasible demands can exceed shared capacity together; two allocated costs can also represent one unchanged payment. Preserve separate setups unless the operating model supports a replacement by shared work.

Carry the connected result into the receiving use. A population forecast supplies work quantities; those quantities supply resource demand; an obtainable supply action supplies its payment terms. A shortage returns to the operating decision about scope, schedule or provision. It does not create another resource block by calculation. MA.4 connects the resulting events and balances across valid account views. For an alternative comparison, isolate the changing future flows; for liquidity, restore all relevant flows and unchanged obligations in the whole cash position.

These methods can be used in different combinations. An established model can feed a forecast directly. A surprising variance can lead to a revised dependency or reveal a changed allocation. A harmful unit-cost target can require changing its use while keeping the report needed for another purpose. Enter the unresolved question and stop when the receiving use has an adequate result.

The accountant also performs work at several scopes at once. While calculating rig occupation, they can be deriving the order’s resource demand and thereby constructing its resource account. The account’s purpose determines what the calculation must include. Use B.1.5.EW — Recover How Constituent Actions Enact Encompassing Work when you cannot yet explain such a connection or locate the capability needed to perform it. MA.1:5.3 shows how an error between those scopes survives correct arithmetic. Reuse a connection you already understand.

The same relation appears in a joint customer account. Deriving one cohort’s hours is already part of constructing the whole operating account, whose calendar window and shared-capacity condition constrain that derivation. The horizontal dependencies between results and this vertical contribution to the whole both matter: correct cohort calculations can still feed an incorrect combined account. The MA-E4 application follows both and reopens only the consequences of a changed effort bound.

MA.Preface:3 - A model that changes the next decision

In MA.1’s constructed test-order case, 100 accepted units require 26–29 rig-hours. The supplied arrangement has 20 usable hours and one additional ten-hour block costing 240. Materials and supplier use add 300. The model therefore supplies 540 of additional payments, rather than the report’s 1,500 assigned cost.

OPS.14 uses those quantities and the stated absence of displacement to compare the 1,200 receipt with 540, giving 660. Its funding question uses the whole timed cash position. Under the example’s explicit baseline-cash premise, 440 is paid now, 100 is due on day 7 and the receipt arrives on day 28; a 40 day-7 funding gap remains. The favorable comparison and the unresolved funding are both useful results.

Other entries change different actions. MA.4 explains how inventory and receivables connect profit to cash. MA.6 preserves an expectation of 100, ambition of 120, request for provision covering 130 and authorization covering 110. MA.8 distinguishes the recovery of past acquisition or development payments from a new continuation choice. MA-E4 joins two cohorts before testing the common capacity and payment dates. A reader does not have to reconstruct the order model to use these methods.

MA.Preface:4 - Correct use, evidence and effort

Begin by stating what the account must explain. For a connected use of the language, establish that the chosen methods answer that question, that their resource and monetary meanings agree where they connect, and that material time, uncertainty and supply conditions survive the connection. Use each pattern’s substantive questions for the result it supplies; reopen the conditions changed by the current use.

A recognizable discrepancy is a reason to investigate. It is not proof that a proposed order should be accepted, that an allocated cost is avoidable or that a measure caused behavior. The worked examples establish reasoning under supplied facts. An actual conclusion needs adequate support for its resource relationships, terms, observations and causal claims.

The gain is a smaller and better explained next decision. The cost is obtaining and maintaining the facts the account needs. Reuse adequate models and observations. Increase detail where a plausible difference could change the answer or its required assurance.

A commercial example supplies no universal monetary objective. An internal or public service can use these accounting methods while obtaining its intended result and choice criteria from the responsible practice. Forecast and performance arrangements must also be examined from the affected participants’ positions, rather than assuming a single account expresses every interest.

MA.Preface:5 - Why this organization of methods

The language separates quantity construction, monetary interpretation, comparison and evidence because a failure in one cannot be repaired by precision in another. Multiplying a reported rate more accurately cannot recover a missing setup. A reconciled variance cannot establish its cause. A forecast cannot authorize a resource request.

OPS.14 already supplies the operating comparison, including changed flows, displacement, timing and funding. OPS.15 supplies account definitions and source events. MA therefore supplies the missing accounting construction and interpretation instead of introducing another comparison or observation method under a new name.

A stable simple report is adequate when it preserves the distinctions its use needs. A detailed activity model, forecast system or broader Beyond Budgeting arrangement becomes useful when its additional contribution warrants the effort. The alternative to an inadequate report can be a small supported model; the alternative to a misunderstood forecast can be a clarified use rather than a replacement management system.

MA.Preface:6 - Sources, qualifications and changed conditions

Internal and externally required accounts serve different uses. An account must retain capacity thresholds and the acquisition or scale assumptions that change its resource and monetary consequences. Changing an expectation is distinct from deciding about resources. Cost models remain useful when their meaning fits the receiving decision. Revenue uncertainty calls for warranted scenarios; unit economics, ROI and ROMI need their actual definitions and cannot be treated as interchangeable labels.

IMA’s managerial-cost-model guidance contributes resource dependencies and a use-driven choice of model detail. Bragg and Caspari supply historical constraint-accounting cases that expose the difference between assigned cost, capacity and changed payments. The relevant TameFlow capacity distinctions are used with adequate OPS operating results; elapsed flow time alone does not identify the constraint.

Bogsnes and the continuing Beyond Budgeting principles shape MA.5–6’s separation of expectation, ambition and resource allocation. The wider organizational proposal is an alternative whose value depends on the actual problem. Forecasting: Principles and Practice supplies the construction and qualification of missing forecast inputs in MA.5. ACCA’s intermediate-account and life-cycle explanations support the changed-composition and product-time constructions in MA.7–8. The customer-model sources used in MA.8 qualify population, horizon and continuation assumptions. Their contribution is to avoid an unwarranted universal formula, not to require every account to adopt one predictive model.

Use the source qualifications in the relevant pattern when adapting its method. Reopen an affected account when actual resource behavior, contract terms, reporting rules, population or decision use changes.

MA.Preface:End

MA.1 - Build the Resource-Consumption and Cost Model

Type: Architectural

Status: Stable

MA.1:0 - Use this when

Use this pattern when a cost report cannot explain what a proposed order, changed method or different workload would require. A quote below reported average cost, a claimed labor saving or a sudden rise in unit cost can expose this difficulty. Start by identifying the resource dependency that the existing account leaves unanswered.

The pattern governs a model relating work outputs to resource consumption and monetary amounts for a stated use. Its useful result is enough of that model to explain the relevant quantities, capacity conditions and money. The operating decision can then use OPS.14 to compare options.

If an existing model already supplies adequate quantities and conditions, use it. Rebuilding the whole cost system adds no value to a question that an adequate account can already answer.

MA.1:1 - Problem frame

A service can use a machine, qualified staff, consumables and a supplier’s processing service to deliver one accepted result. Each resource has a different relationship to the work. The machine is occupied during setup and processing; staff may supervise only part of that time; consumables may be used on unsuccessful attempts as well as accepted units. A supplier may charge for an attempt, a completed batch or a reserved block.

The money follows further relationships. Stock consumed today may have been paid for last month. Salaried capacity may be available within unchanged pay. Another machine block may require a payment before the customer pays. An internal unit-cost report may also assign a share of the building and management costs. These amounts can all be meaningful while answering different questions.

Management accounting needs an explanation connecting those facts. The relevant boundary follows the work, resource behavior and receiving use; it need not coincide with the chart of accounts or an organizational department.

MA.1:2 - Problem

A monetary total compresses the relations needed to explain a change. Multiplying average cost by a proposed quantity can miss available capacity, a setup, failed attempts or a supply threshold. It can also turn an allocation into an apparent payment consequence.

A model that contains every observable detail has the opposite defect: it costs too much to construct and maintain, while its precision may exceed what the underlying observations support. The working problem is to recover the dependencies that can change this answer and stop at a justified level of detail.

MA.1:3 - Forces

Consumption, available capability and payment are connected but need different evidence. The person who supplies a credible processing-time estimate may not know the supplier’s charging terms or the actual payment date. Bringing these facts together is useful even when each is already recorded elsewhere.

Grouping resources makes an account usable. It loses value when the group hides a capability requirement, a different response to demand or a payment threshold. More detailed observation can reduce a consequential uncertainty, but detailed tracking itself consumes resources and can encourage people to optimize what is easiest to count.

MA.1:4 - Solution

MA.1:4.1 - Begin with the missing explanation

State the work being considered, the relevant result and the period over which the model must answer. Inspect the existing account with its user. Ask what it cannot presently explain: the resources required for another order, the effect of a changed batch size, the cost of unused provision or some other concrete dependency.

Use that question to choose the first observations. For a proposed order, obtain the actual processing route and the conditions under which it works. For a reusable product-cost account, obtain representative routes and the variation the account must retain. Ask the people who perform or arrange the work, and compare their explanation with available operating records. A ledger category locates recorded money; it does not by itself explain how the work consumes a resource.

MA.1:4.2 - Recover outputs and resource dependencies

Identify the accepted outputs and the intermediate results that materially consume resources. Recover setups, attempts, rework, inspection and handling where their resource demands differ. Distinguish quantities of accepted results from quantities of attempts: a charge on every processing attempt will not generally equal a charge on every accepted output.

For each relevant resource, express the dependency in meaningful units. A simple relationship may be:

Required rig-hours = setup hours + processing attempts × rig-hours per attempt.

Other resources can require a table, interval, threshold or conditional rule. A one-time setup, a resource shared by simultaneous tasks and a failure-dependent repeat are not all linear per-unit demands. Preserve the conditions under which each relationship holds, including product type, qualification, batch size or equipment state when these matter.

Establish the reason for the relationship. Engineering knowledge, applicable terms and observations of the process can support different parts of it. Mark an estimate as an estimate and retain the assumption that makes it usable. An observed association between order value and staff expense may help prediction; it does not establish that an extra currency unit of sales consumes a particular staff quantity. When that distinction changes the decision, investigate the mechanism or return the missing dependency.

If the calculation is familiar but you cannot relate its quantities to the account being constructed, use B.1.5.EW to locate the missing modeling operation. Obtain that contribution or learn to perform it before relying on the calculation. Greater arithmetic precision does not recover an omitted resource dependency.

MA.1:4.3 - Keep resource quantities and supplied capacity distinct

A rig-hour, a qualified staff-hour and an elapsed hour measure different things. Recover what each resource must actually provide. Check that an estimate of machine occupation has not silently become an estimate of staff attendance.

Group resources only while the grouping preserves relevant capability, consumption and money. Two machines can share a pool if their interchangeable capability and behavior suffice for this use. A specialist machine that alone performs a required test needs its own boundary. Likewise, splitting identical consumables by invoice number may add detail without improving the answer.

Compare demand with the supplied capacity conditions for the required time window. Retain commitments to other work, unavailable time and protected reserve. Keep thresholds such as an additional shift, license tier, supplier block or specialist booking visible. Obtain an adequate operating result when feasibility, the constraint or the schedule is unresolved; the cost model uses that result rather than establishing a feasible schedule from a total number of hours. MA.2 deepens the account when the meaning or cost of capacity itself needs explanation.

MA.1:4.4 - Attach the relevant monetary meanings

Connect resource quantities to money through the relationship that actually applies. For each amount that could be misread, make clear whether it is:

  • consumption valued for the account, such as materials issued from stock;
  • the payment required to supply or obtain a resource, such as a whole additional shift;
  • a payment at a particular time; or
  • an assigned share under an allocation convention.

The distinction can be carried in ordinary columns or explanatory prose.

A supplied resource can be consumed without another payment in the period. Record the capability used and the account’s warranted value without inventing a cash saving or expenditure. Conversely, obtaining a resource block may require paying for more capacity than the proposed work consumes. Use the charging rule for that block. An average rate multiplied by consumed hours does not reproduce every supply arrangement.

Preserve the horizon. A salaried hour whose payment is unchanged this week can still matter to a later staffing decision or to displaced work now. Stock consumption can trigger a replacement payment, use scarce inventory or have another relevant consequence even though the original purchase is sunk. Obtain those facts for the receiving comparison instead of classifying a cost as permanently fixed or variable.

When a shared assignment is the unresolved issue, use MA.3. When management, reporting and cash amounts appear inconsistent, use MA.4. These are separate questions that can also be answered from adequate existing accounts.

MA.1:4.5 - Choose the detail that can change the answer

Ask which plausible differences could change feasibility, a payment threshold, the comparison or the assurance needed for this use. Split a resource group or obtain another observation when such a difference is concealed. Preserve a justified range when all values in it support the same relevant conclusion.

For example, a setup estimate of six to nine hours may be sufficient if every value requires exactly one additional ten-hour block and fits the supplied arrangement. Measuring setup to the minute adds little to that choice. If the estimate straddles the available capacity, its uncertainty matters: obtain a better bound, change the option or report unresolved feasibility.

This stopping rule applies to the stated use. A model sufficient for one order can be inadequate for a pricing policy, capital decision or assurance claim with a longer horizon. Reuse the established relations, then deepen only the part the new use needs. C.11.DUA supplies the broader inquiry decision when the value of further information is itself disputed.

MA.1:4.6 - Return a model someone can use

Return the quantities and dependencies together with the conditions needed to interpret them. A short table can be enough. Make an unresolved premise visible at the point where it changes the result: required qualification, available block, rework rate, supplier terms or another specific issue.

For an operating option, supply the resource and monetary consequences to OPS.14. That method compares options, considers displacement and tests timing and funding. A favorable difference is a result of the comparison under its premises; building the model does not authorize the work or supply missing capacity.

Retain the observations worth reusing and the conditions that would reopen the account. Actual use of a different process, changed terms or a new demand range can require a revision.

MA.1:5 - Archetypal Grounding

MA.1:5.1 - A test order below reported average cost

A test service considers an order for 100 accepted units at 12 currency units each. Its standard report assigns an average cost of 15 per unit. The manager first needs the resource model; the comparison follows from it. The following is a constructed case with supplied operating and contractual facts.

The resource owner supplies an adequate schedule, qualification and reserve account. There are 20 uncommitted usable rig-hours in the required window. Exactly one additional contiguous ten-hour block can be obtained for 240, subject to booking. Setup requires six to nine rig-hours, followed by 0.2 rig-hours per processed unit. One successful attempt per accepted unit is assumed.

The work requires 14 qualified staff-hours; 16 usable hours are already available and pay is unchanged. Materials for this order must be bought now at 2 per unit. A supplier charges 1 per processed unit.

Recovered dependencyQuantity or amountWhat the receiving comparison can use
Setup plus processing occupies the rig.6–9 + 100 × 0.2 = 26–29 rig-hours.The supplied 20 hours are insufficient; one extra ten-hour block makes the supplied arrangement adequate.
Qualified staff support the work.14 staff-hours within the supplied 16.The option uses capability, with no additional wage payment under these terms.
Materials are consumed and purchased for the order.100 × 2 = 200.A payment of 200 now.
The supplier charges per processing attempt.100 × 1 = 100.A payment of 100 under the one-attempt premise.
Extra rig capacity is sold as one block.240 for the ten-hour block.A payment of 240, although the extra occupation is only six to nine hours.
The existing report assigns average cost.100 × 15 = 1,500.A reported amount whose assignment basis remains available for its own use.

The model supplies 540 in additional payments. OPS.14 compares the 1,200 receipt with those payments: the difference is 660, over a horizon that includes both, with all other flows unchanged and no displaced contribution. The reported 1,500 does not establish this incremental amount.

Payment time changes what is feasible. Without the order, unrestricted cash available for these payments would remain 500 through day 28 after all other receipts and obligations. Materials and the block require 440 now, leaving 60. The supplier’s 100 is due on day 7; the customer pays on day 28. There is therefore a 40 funding gap on day 7. The operating or finance decision must resolve that gap before treating the option as funded.

If an additional receipt of 50, unchanged between accepting and declining the order, instead arrives before day 7, cash after both payments is 10. The order’s incremental difference remains 660. The unchanged receipt cancels from that difference but changes the whole cash position used to establish payment feasibility.

The setup interval is sufficient for the one-block question: 26–29 hours always lies within the supplied 30. A new product requiring an eleven-hour setup would require 31 hours. That case reopens feasibility and the resource model; the earlier result cannot be extended by merely changing the sales quantity. Failed attempts, different staff qualifications or changed supplier terms likewise require attention where they affect the dependencies.

MA.1:5.2 - A faster method with unchanged wages

A repair method reduces salaried technician attendance from six hours to four for one job. The two released hours become usable capability if the schedule and qualification allow their use. Pay this week remains unchanged.

The model returns the two-hour reduction and the unchanged payment. If another valuable job can use the released time, OPS.14 can compare the resulting options. If no work is displaced and no payment changes, the model provides no current cash saving. For a later staffing question, construct the relevant demand and supply relationship over that later horizon.

MA.1:5.3 - Correct arithmetic in an incomplete resource account

Return to the test order with a nine-hour setup. Suppose obtaining 100 accepted units now requires 20 additional unsuccessful attempts. Each of the 120 attempts occupies the rig for 0.2 hours, and there is no extra setup. Counting only accepted units gives 9 + 100 × 0.2 = 29 hours; retaining every attempt gives 9 + 120 × 0.2 = 33 hours. The supplied 30 hours are insufficient. The supplier’s charge also rises from 100 to 120 under its per-attempt rule. A revised payment comparison must retain this change as well as the unresolved capacity.

While doing that multiplication, the accountant is deriving rig demand and constructing the order’s resource account. The accepted-output requirement governs which attempts must enter the calculation. A colleague may supply the process relationship when the accountant cannot establish it; the accountant still needs to understand how that contribution affects the model. Repeating multiplication exercises would not supply the missing relationship.

The observed production attempts belong to the work being modeled. They are not constituent acts of the accountant’s model construction. Likewise, using one calculation to construct an account does not create additional rig occupation or additional hours of accounting work for each description of it.

Return the changed demand to the operating comparison. OPS.11.1 can recover the routing, shared-resource and completion conditions when a different operating arrangement is needed. Recalculating existing assignments or changing an authorized allocation is an operating question. OCE becomes relevant if the proposed repair changes who may commit resources or other organizational arrangements.

MA.1:6 - Bias-Annotation

An accountant may favor categories already present in the ledger; an operator may favor the resource easiest to observe. Both can miss the relation that changes the answer. Compare their accounts around the actual work and keep different units explicit.

The order example concerns a commercial service and a short horizon. Its arithmetic does not establish that profit is every organization’s purpose or that all long-run choices can be made from short-run payments. Public and internal services can use the same construction to explain required resources while obtaining their objectives and decision criteria from the responsible practice.

MA.1:7 - Conformance Checklist

For the model’s stated use, examine whether:

  1. The work, output and horizon are clear enough to choose the relevant dependencies.
  2. Attempts, setups, resource units and capability boundaries are retained wherever they can change the answer.
  3. The relationships have adequate support, with material estimates and unresolved assumptions identifiable.
  4. Capacity conclusions use an adequate supplied operating account, including commitments, reserve and relevant thresholds.
  5. Consumption values, supply payments, timing and allocations can be distinguished where their meanings affect use.
  6. The chosen detail preserves the consequential variation, and the returned result names any premise still needed by its recipient.

A plausible entry cue establishes a reason to inspect the account. These questions assess the model and its warranted use; observing actual consumption, obtaining a resource and achieving the business result require their own evidence.

MA.1:8 - Common Anti-Patterns and How to Avoid Them

Rejecting an order from the average-cost multiplication alone. Recover what changes when the order is undertaken, including the capacity and payment conditions. Keep the original report’s meaning available.

Valuing every released hour as an avoided wage payment. State the released capability and the action, if any, that changes payment or displaced work. An unchanged salary cannot be saved merely by assigning it fewer hours.

Refining a harmless decimal while concealing a threshold. Preserve the supply block or qualification boundary first. Add measurement detail only where its plausible variation can change the use.

Using paid capacity as proof of timely availability. Obtain the actual usable and committed capacity for the required window. Payment for a resource does not establish the schedule.

MA.1:9 - Consequences

The user can explain why a proposed workload consumes particular resources and why its monetary consequences differ from a report. The result supports a small first decision and can be extended when another use needs more detail.

The model also exposes missing operational or contractual facts that accounting categories previously concealed. Recovering those facts has a cost. Keeping only consequential detail reduces maintenance, while explicit conditions make later reuse more demanding than copying a single unit-cost number.

MA.1:10 - Architectural Rationale

The construction begins with work and quantitative dependencies because a money total cannot recover a lost capability requirement or setup. Monetary interpretation follows the relevant resource relation. This order also lets an existing operating account supply a sufficient quantity directly.

A report based on a stable average can be adequate for the question it was designed to answer. Replacing it is justified when its aggregation conceals an answer-changing relation. A comprehensive activity model can support repeated heterogeneous decisions, but its collection and maintenance burden is unnecessary for a small case whose decisive relations are already known.

Keeping the model separate from the option comparison makes both usable independently. The same model can support a forecast or variance explanation; the same comparison method can use an already adequate model. A longer horizon or different decision changes the needed relationships rather than making one cost label universally correct.

MA.1:11 - SoTA-Echoing

The practical question is how much resource and monetary structure an internal account needs to support its use. The selected line combines causal management-cost modeling with the constraint-accounting distinction between consumed capability and payments. It adapts IMA’s Developing an Effective Managerial Costing Model: model resources and their quantitative dependencies, distinguish their monetary treatment, and choose sophistication for the decision. Here those contributions change the construction and detail decision in §§4.2–4.5.

At the effort of recovering a few consequential relationships, this line can distinguish the extra capacity block from a reported average that obscures it. A detailed activity or time-driven model becomes preferable when repeated decisions need the distinctions it supplies and their maintenance is worthwhile. Its use still needs adequate capacity and monetary premises.

Bragg’s Throughput Accounting (2007), printed pp.44–47 and 84–86, supplies historical examples and assumptions behind short-run comparisons. The pattern retains their attention to changed payments and capacity, while including supplier charges, setup supply and other changed flows when actual terms require them. Caspari and Caspari’s Management Dynamics (2004), printed pp.1–11, supplies the counterexample in which local time reduction need not improve the constrained system or reduce wages. These sources inform the returned quantities and the faster-method case.

Reconsider the model when observed work, relevant terms or the receiving use defeats its dependency, capacity or detail assumptions. A newer cost-model label alone is not evidence that a more elaborate account would answer the question better.

MA.1:12 - Relations

OPS.14 consumes adequate resource quantities, monetary consequences and conditions for its incremental comparison. The relevant OPS capacity and scheduling methods supply an unresolved operating result. OPS.15 supplies operating-account definitions and source events where those are missing.

MA.2 explains capacity use and its cost; MA.3 resolves shared assignment; MA.4 reconciles differing accounts. MA.5 can reuse the dependencies in a forecast, MA.7 in a variance explanation and MA.8 in a cohort or product account. Each is entered for its own unresolved question.

C.16 supplies measurement discipline when a quantity’s meaning or evidence is disputed. C.11.DUA supplies the inquiry decision when further information could change the action.

MA.1:End

MA.2 - Explain the Cost and Use of Capacity

Type: Architectural

Status: Stable

MA.2:0 - Use this when

Use this pattern when paid capacity, used capacity and apparently idle capacity have been treated as the same thing. A proposed efficiency saving, staff reduction or extra workload often exposes the difference.

The pattern governs an account of resource supply, usable capability, its use and its monetary consequences. It returns an explanation of what is available, what is used or reserved, and what action could change supply or payments.

Use an adequate capacity account directly. The operating choice about the constraint, reserve or feasible schedule belongs to the relevant OPS method.

MA.2:1 - Problem frame

A team pays for a resource arrangement that supplies capability over time. Some provision can be unavailable for the relevant service; some usable capacity can support actual work; some can protect the service against variation. A remaining unused portion may offer another use or a possible supply change.

These quantities do not have one monetary meaning. Released time can increase available capability without changing the current payment. A supply reduction can save money while also removing capacity needed in another time window.

MA.2:2 - Problem

An account that prices every unused hour as waste invites a reduction that may damage service. An account that treats every paid hour as available can promise work the resource cannot perform.

The working difficulty is to explain both use and monetary consequence without making an accounting classification decide the operational question.

MA.2:3 - Forces

A simple utilization ratio is easy to communicate. Its denominator can hide unavailability, capability differences and reserve. A very detailed capacity account can become expensive while still failing to establish a feasible schedule.

A reserve consumes an opportunity to use capacity elsewhere. Its reason and size require an operating judgement; calling it protective cannot by itself justify keeping it indefinitely.

MA.2:4 - Solution

MA.2:4.1 - Define the resource and relevant capacity quantity

Name the resource arrangement, capability, time window and receiving question. Recover the supplied quantity, the unit and the conditions under which it can serve the relevant work. Distinguish staff attendance, machine occupation and elapsed time.

Use the current operating account for availability, commitments and reserve. If those results are disputed, obtain the missing OPS result before attaching a monetary conclusion to them.

MA.2:4.2 - Explain the supplied, used and unused portions

Reconcile the supplied quantity with its relevant uses and restrictions. Identify unavailable or differently committed provision, actual or expected consumption, protected reserve and any remaining unused usable capacity. Keep the categories mutually interpretable for this account; reserve can be part of available capacity while being unavailable for ordinary commitment.

Investigate the reason for an apparently idle portion. It may reflect demand variation, a necessary skill mix, downtime, a minimum supplier block or inadequate demand. Preserve a disputed explanation as disputed. A utilization label is an entry cue, not a causal diagnosis.

MA.2:4.3 - Connect a capacity change to a supply action

Ask what action would change resource supply and on what terms. Recover notice periods, minimum blocks, alternative uses and consequential payments for the stated horizon.

A saved hour can be used elsewhere if capability and scheduling permit it. A payment saving requires an avoided or reduced payment within the stated horizon. A smaller assigned share of unchanged payroll establishes neither.

Retain the threshold. Removing five hours of work may leave the same supplied shift; adding five can require another whole block. MA.1 supplies a missing demand model.

MA.2:4.4 - Return the capacity and monetary account

Return the quantities, reasons and relevant supply options with their limits. If a unit cost is useful, state its denominator and purpose. Dividing the same payment by supplied, used or productive hours gives different rates.

Supply the supported quantities and payment conditions to OPS for the capacity or incremental decision. Keep uncertainty about the operating reserve separate from uncertainty about a supplier’s terms.

MA.2:5 - Archetypal Grounding

A service purchases 100 scheduled qualified staff-hours for 2,400 in a period. An adequate supplied operating account identifies 20 hours unavailable for the service, 50 used on service work, 10 held as justified reserve and 20 otherwise unused usable hours. The account reconciles 20 + 50 + 10 + 20 = 100.

Dividing 2,400 by all 100 supplied hours gives 24 per supplied hour. Dividing it by the 50 service hours gives 48 per used service hour. Neither division establishes the payment avoided by releasing another hour.

A changed method releases two service hours. Pay remains 2,400 under the arrangement. The result is two hours of released capability, subject to their actual usefulness in the schedule. Multiplying two by 24 or 48 does not establish a cash saving.

Consider an extra request under the original arrangement, before the method change. It needs 25 hours in the same window. The supplied operating account permits ordinary commitment of only the 20 unused hours while retaining the reserve. A feasible additional block of 20 hours costs 500 under the supplied terms. The model returns the five-hour gap and the block’s payment, or the question whether OPS should change the reserve or option. It does not silently consume the reserve to make the request fit.

MA.2:6 - Bias-Annotation

A high-utilization target can conceal the value of protective capacity; the label “reserve” can conceal unnecessary provision. Examine the actual operating reason and consequence.

The period account does not establish a long-run staffing result. A later horizon can change demand, terms and the feasible supply action.

MA.2:7 - Conformance Checklist

Examine whether the account identifies the resource, capability, unit and window; reconciles supply with relevant uses and restrictions; retains the operating basis of reserve; distinguishes released capability from changed payment; and names the action and conditions needed for a supply change.

These checks assess the explanation. The existence of paid capacity does not establish a feasible schedule or the adequacy of a reserve.

MA.2:8 - Common Anti-Patterns and How to Avoid Them

Booking every released hour as a saving. Find the payment or opportunity that actually changes.

Removing reserve because it appears unused. Obtain the operational consequence of removing it, including the variation it was intended to absorb.

Comparing utilization rates with different denominators. Recover what each denominator includes before judging a difference.

MA.2:9 - Consequences

The user can distinguish an efficiency improvement, unused provision and an avoidable payment. This improves the information supplied to a capacity decision.

The account may leave the operating choice unresolved. That is useful when its remaining question is explicit, such as the needed reserve or the feasibility of a replacement block.

MA.2:10 - Architectural Rationale

Supply, capability and consumption are separated because each responds differently to action. A single hourly rate can support a defined account, but cannot carry all three meanings.

The accounting method explains quantities and money while OPS decides the operating arrangement. Combining them without preserving that boundary would let a chosen denominator decide what the service can safely promise.

MA.2:11 - SoTA-Echoing

The selected line combines resource-based managerial costing with the distinction between productive, protective and excess capacity discussed in Tendon and Doiron’s Tame your Work Flow (2020), chapter 7. It adapts the distinction to the actual operating account: the reason for reserve must be established, and elapsed flow time alone does not identify a constrained resource.

In the historical fixture example in Caspari and Caspari’s Management Dynamics (2004), a fixture transfers work between stations: it saves five minutes per unit at one station but adds two at the station that limits production. Total processing time falls from 55 to 52 minutes, while wages remain unchanged. When demand uses the limiting station’s capacity, increasing its work from 25 to 27 minutes per unit reduces possible output. These contributions inform §§4.2–4.3 and the released-hours example.

At the effort of reconciling one resource pool, this account exposes distinctions a utilization percentage hides. More detailed tracking is worthwhile when a capability or time boundary changes the decision. Reopen the account when those conditions or the supply terms change.

MA.2:12 - Relations

MA.1 supplies resource demand. MA.3 uses adequate pool meanings for shared assignment; MA.4 reconciles monetary views. OPS supplies constraint, reserve, schedule and capacity decisions and consumes this account’s supported quantities.

MA.2:End

MA.3 - Assign Shared Costs for the Stated Use

Type: Architectural

Status: Stable

MA.3:0 - Use this when

Use this pattern when a shared cost must be assigned to products, customers or units, or when an assigned amount is being interpreted as something its recipient caused or can avoid.

The pattern governs a purpose-qualified shared-cost assignment. It returns assigned amounts reconciled to the source total, with the consumption evidence and any allocation convention needed to interpret them.

If the current assignment is adequate for its use, retain it. An incremental choice can often use actual changed flows without allocating every shared cost.

MA.3:1 - Problem frame

A shared resource supports several recipients. Some consumption can be traced to a recipient; some sustains the group or cannot be separated at warranted effort. A reporting, pricing, charging or responsibility question can still require a distributed total.

The need to assign money does not establish that one assignment rule answers all those purposes. A contractual charging convention can be valid for billing while being inadequate as evidence of avoidable cost.

MA.3:2 - Problem

An allocation makes an account add up, which can give the assigned number an unwarranted causal meaning. Closing a segment can then appear to avoid a payment even when the payment for the shared resource stays unchanged and only its allocation among the remaining segments changes.

Refusing every assignment is also unhelpful when the receiving use legitimately requires one. The task is to supply that assignment while preserving what it actually means.

MA.3:3 - Forces

Tracing can improve the account but has a measurement cost. Convenient drivers are cheap and can be misleading. More precise allocation does not establish a payment consequence when the shared supply remains unchanged.

Recipients can influence both the rule and recorded use. An apparently technical choice can therefore change incentives or who bears a charge.

MA.3:4 - Solution

MA.3:4.1 - Establish the receiving purpose and source total

State what the assignment must support: a management account, agreed charge, pricing analysis, reporting requirement or another particular use. Recover the source pool, period, included costs and relevant resource meaning.

Separate pools whose capability or monetary behavior would change the interpretation. Reconcile the source total before distributing it; an unexplained residual must not be hidden in a recipient’s rate.

MA.3:4.2 - Trace what the evidence supports

Recover the resource consumption attributable to each recipient at warranted detail. Use MA.1 for missing dependencies and MA.2 for a disputed supply or capacity meaning.

Retain joint or sustaining costs at the level their explanation supports when the receiving purpose allows it. A sales-value percentage can be an allocation convention; it does not establish resource consumption merely because it correlates with a recipient’s size.

MA.3:4.3 - Make a necessary convention explicit

When the receiving purpose requires distribution beyond supported tracing, select or obtain the rule appropriate to that purpose. State the basis and why it is usable here. An applicable agreement or reporting rule may determine it.

Apply the rule consistently to the defined source total and recipients. Retain rounding, excluded items or residuals where they affect reconciliation. Distinguish a change in the total from a change in its assignment.

Where plausible rules could change a consequential interpretation, show that sensitivity or return the disputed rule.

MA.3:4.4 - Return the assignment with its warranted interpretation

Supply the assigned amounts, their source total and the tracing or convention needed to interpret them. State whether the assignment describes resource consumption, an agreed charge or another specific account.

If someone proposes an avoidance or closure conclusion, obtain the actual payment and opportunity changes through MA.1–2 and OPS.14. MA.9 examines the assignment’s behavioral consequences when they are the unresolved question.

MA.3:5 - Archetypal Grounding

A shared support arrangement costs 1,200 per period. Its supplied terms keep the payment unchanged if either segment closes during this horizon. A required internal charge uses observed support-hours: six for A and four for B. The agreed assignment is therefore 720 to A and 480 to B.

A has revenue 900 and other avoidable payments of 300. B has revenue 700 and other avoidable payments of 200. After the shared assignment, A shows −120 and B 20; together they show −100.

If A closes and all other conditions remain unchanged, the group loses its 600 contribution while the shared payment remains 1,200. B’s remaining account is 700 − 200 − 1,200 = −700. The assigned loss of 120 did not identify a 720 payment saving.

If an actual permitted supply change instead avoids 300 of the shared payment in the relevant horizon, include that changed amount. The comparison now differs by −600 + 300 = −300, under the stated remaining premises. OPS.14 performs the choice with any further displacement, timing and feasibility consequences. Reallocating the same 1,200 does not supply this change.

MA.3:6 - Bias-Annotation

A recipient can prefer a driver that lowers its charge. An analyst can prefer measurable activity even when it poorly explains the resource pool. Make the source purpose and evidence inspectable.

The example uses an agreed internal convention. Its validity for that charge does not establish a universally fair or causal allocation rule.

MA.3:7 - Conformance Checklist

Examine whether the assignment has a stated use; its source pool and period are adequate; supported tracing is distinguishable from convention; assigned amounts reconcile with explicit residuals; and the recipient can tell what the amounts support.

An avoidance claim additionally needs evidence of the actual change. Reconciliation alone cannot supply it.

MA.3:8 - Common Anti-Patterns and How to Avoid Them

Saving an allocated share by deleting its recipient. Inspect which payments and opportunities disappear.

Calling a convenient driver causal. Establish the consumption relationship or label the warranted convention.

Forcing every sustaining cost onto a unit. Retain its supported level when the receiving purpose permits; allocate further only for a use that needs it.

MA.3:9 - Consequences

The user obtains an assignment that can be reconciled and interpreted. Different accounts can serve their stated purposes. An assigned share alone does not show which payments or opportunities would change.

The rule can distribute burden and affect behavior. Its maintenance and measurement cost must be justified by the use it serves.

MA.3:10 - Architectural Rationale

Purpose precedes the assignment rule because tracing, internal charging and a required reporting allocation have different standards of adequacy. Reconciliation preserves the total; the explanation preserves the assigned amounts’ meaning.

A single stable driver is adequate when it serves the agreed purpose. A more detailed model becomes useful when heterogeneity changes that use. Neither removes the need to establish actual changed flows for a closure decision.

MA.3:11 - SoTA-Echoing

The selected line uses managerial costing’s separation of supported consumption from attribution and the throughput-accounting warning about average or allocated amounts in an incremental choice. Bragg’s Throughput Accounting (2007), printed pp.44–47, supplies historical pricing and allocation examples; MA.1 supplies the quantitative resource construction used here.

The adaptation retains an allocation when the receiving purpose needs it, while withholding an unsupported avoidance interpretation. At the effort of identifying one pool and its rule, the segment example reveals a closure loss that its allocated result conceals. Reopen the assignment when its purpose, source pool, consumption evidence or applicable rule changes.

MA.3:12 - Relations

MA.1–2 supply consumption and capacity meanings. MA.4 reconciles different accounts; MA.7 explains a changed assignment or cost; MA.9 examines resulting incentives. OPS.14 uses actual incremental consequences for the operating comparison.

MA.3:End

MA.4 - Reconcile Operating, Reporting and Cash Accounts

Type: Architectural

Status: Stable

MA.4:0 - Use this when

Use this pattern when the same work seems to produce incompatible profit, inventory or cash results in different accounts. Begin with the difference that changes a decision or interpretation.

The pattern governs an explanation connecting the relevant accounts while retaining each account’s purpose and rules. Its result is a reconciled difference, or a located discrepancy requiring correction or specialist interpretation.

Use an adequate existing reconciliation directly. The method does not replace the applicable financial, tax or other reporting rules.

MA.4:1 - Problem frame

Production, sale, recognition of an expense and payment can occur at different times. One management account can expense a supplied resource in the period; another account can include an eligible share in inventory until sale. An unpaid credit sale can increase reported revenue and create a customer receivable before cash arrives.

These accounts can disagree numerically without contradicting one another. They can also contain an error. The model must establish which explanation applies.

MA.4:2 - Problem

A profit figure is often treated as cash generated, or a management restatement as a correction to an external report. That loses recognition, valuation or settlement conditions.

A reconciliation that merely inserts an unexplained balancing amount has the opposite defect: it makes totals agree while hiding the unresolved question. The practitioner needs an explicit explanation of the difference.

MA.4:3 - Forces

Each account simplifies work for a purpose. Comparing them requires enough common subject and period information to retain their different rules. A detailed event reconstruction is costly when a small inventory or receivable bridge is sufficient.

A correct mathematical reconciliation can still use an inapplicable policy. Reporting adequacy and arithmetic therefore need different evidence.

MA.4:4 - Solution

MA.4:4.1 - Recover what each account measures

Identify the entities, work, period, currency and intended use of each account. Recover the recognition and valuation rules relevant to the disputed amount. State whether the account concerns revenue, expense, inventory, resource consumption, payments or another quantity.

Use OPS.15 for an unresolved event or observation definition. Use the responsible reporting practice when the applicable policy is missing or disputed.

MA.4:4.2 - Build the movement account

Recover the opening balances and the events that change them during the period. Match the entities, goods or services, dates and currency to each view. The closing balance of the previous period normally supplies the next opening balance on that same basis. If a policy, boundary or opening amount changed, explain that change before comparing period results.

A sufficient source account can supply aggregate movements. Reconstruct individual events where aggregation hides the disputed term. For an ordinary purchase, production and credit-sale account, begin with these relationships:

BalanceMovement through the period
InventoryOpening inventory + eligible purchases or production cost − cost consumed or sold = closing inventory
ReceivablesOpening receivables + recognized credit sales − customer settlements = closing receivables
PayablesOpening payables + purchases or resource supply on credit − supplier settlements = closing payables

Use each account’s actual recognition and valuation rules to fill the terms. Physical production can be the same in two views while the cost admitted to inventory differs. Carry opening inventory on the corresponding view’s basis and apply its rule for identifying the cost released when goods are sold. Purchases, consumption and payment are separate events; equating them would erase the difference being explained.

Extend the movement account when other events occur. A write-down changes inventory without buying or selling units. A customer advance may create a liability before revenue is earned. An equipment purchase, depreciation or financing transaction needs its own balance and flow treatment. Obtain that treatment from the responsible reporting or financial practice. Locate an unexplained residual in the missing event, valuation, period or scope; an invented balancing entry cannot explain it.

MA.4:4.3 - Derive the connection between the views

Construct the result under each view from the common events and that view’s rules. Then explain how its opening and closing balances connect the recognized flows to settlements.

In a bounded account containing only the ordinary inventory, credit-sale and supplier-payment events above, collections equal revenue less the increase in receivables. Resource costs acquired during the period equal costs recognized in the result plus the increase in inventory. Payments for those acquisitions equal their amount less the increase in payables. Combining these relationships gives:

Cash movement = period result − increase in inventory − increase in receivables + increase in payables.

Here an increase means closing balance minus opening balance within the same view. A decrease therefore has the opposite effect. Use a full-cost result with full-cost inventory, and an internal result with that internal account’s inventory values. Mixing the result of one policy with the balance of another creates a spurious cash difference.

The formula’s scope matters. If the result includes a noncash charge, explain its effect without inventing a payment; if equipment is purchased, include its dated payment separately. For an advance received before revenue, carry the corresponding liability movement. Reconstruct the material additional terms from their events rather than assuming the inventory/receivable/payable bridge covers them. A direct receipt-and-payment account can supply an independent arithmetic comparison.

When one policy retains a production-resource cost in inventory and another expenses it, compare the amount retained at both ends of the period. The difference between the period results is the increase in that retained amount, under otherwise matching recognition. Releasing earlier stock can reverse the result difference even while the policies themselves stay unchanged. State whether the explanation concerns recognition, valuation or settlement; those changes need not occur together.

Show enough intermediate amounts to expose an omitted term and reconcile to the same cash movement where both views describe the same events. The movement is not the closing cash balance. Funding uses opening available cash and the other receipts and obligations at the dates when they occur.

MA.4:4.4 - Return the reconciled views and any discrepancy