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.