How do you support Budget to Report when the control position looks wrong?
Restore a trustworthy control position by tracing where budget authority, consumption, or management evidence became incorrect. A report is the end of the control chain; investigate the underlying authority and source evidence before changing a setting.
B2R CONTROL SPINE
Trace from management symptom to the control evidence
Budget authority, commitment, actual cost, available amount, and reporting are different records. Keep them separate while locating the first point where the position differs from expectation.
- 01PlanNeed
- 02Authorize and releaseAuthority
- 03CommitObligation
- 04Post actualConsumption
- 05Availability controlDecision
- 06Report and actAction
SUPPORT OPERATING LOOP
Establish the position before changing the control
Establish impact
Identify the budget object, cost domain, period, scope, and whether authority, release, commitment, actual, available amount, or reporting is wrong.
Find the failed transition
Trace budget baseline → release → commitment → actual → available amount → exception or change → report, and record the last known-good position.
Choose the owning layer
Separate authority, consumption, object structure, configuration, change governance, integration, CO-close evidence, and reporting interpretation.
Correct the evidence owner
Correct the source transaction, control object, approved budget record, configuration, integration, or report—never increase budget merely to bypass a block.
Reconcile the full spine
Validate authority, consumption, and performance separately: approved and released budget, commitments and actuals, remaining amount, variance, owner, and required action.
Make exceptions visible
Turn repeated incidents into release controls, stale-commitment review, availability alerts, controlled change workflow, close monitoring, or regression tests.
FIRST B2R DECISION
Separate authority, consumption, and performance
Ask whether the user is looking at a planning issue, a budget-authority issue, a commitment or actual-cost issue, or a reporting interpretation issue.
An approved budget is not necessarily available. Release determines what may currently be consumed.
Both can reduce availability, but commitment is a future obligation and actual is booked consumption.
A tolerance block, incomplete approval, period control, or exhausted available amount may be the intended result.
CHOOSE THE SUPPORT RAIL
Use the same control spine against the object that owns the evidence
Authority, consumption, remaining capacity, and action remain the common B2R question. The technical object and close evidence change by rail.
Cost Center and Internal Order
Trace: source transaction → FI/CO assignment → cost center or internal order → allocation or settlement → plan/actual report. Diagnose wrong cost center, stale commitment, allocation result, or unexpected internal-order settlement. A cost-center plan is not automatically a formal budget-availability control.
WBS and Network
Trace: approved and released project authority → commitment or actual → WBS/network → availability result → settlement or capitalization → project report. Diagnose scope, release, assignment, change, and project-close evidence.
Production Order
Trace: material or activity event → production order → actual cost → WIP or variance → settlement → cost report. Diagnose order assignment, goods movement, confirmation, close sequence, variance, and settlement before interpreting the final position.
RAIL-SPECIFIC DIAGNOSTIC PLAYBOOKS
Diagnose the failure in the object that owns it
Start with the named business object and follow the evidence trail before changing a control, rate, allocation, or settlement rule.
Operating · Actual or commitment hit the wrong Cost Center
Trace: PO, invoice, payroll, journal, or other source → account assignment → cost center → commitment or actual → plan/actual report. Check the source account assignment, defaulting, substitution, validity date, responsible cost center, and reversal history. Correct the source or controlled reposting path; do not hide the error with a report reclassification.
Operating · Cost Center allocation is missing or wrong
Trace: sender cost center → allocation cycle → tracing factor or activity quantity → receiver → cycle run log → sender and receiver balances. Check cycle version, period, sender/receiver selection, statistical key figure or activity basis, rate, exclusions, execution log, rerun, and reversal. Prove both sender reduction and receiver receipt.
Operating · Internal Order settlement is missing or wrong
Trace: internal order actuals → order status → settlement rule → receiver cost center, WBS, asset, or profitability segment → settlement run → balance and report. Check settlement profile, valid receiver, percentage or amount, period, order status, run log, and prior settlement or reversal. An internal order is temporary collection evidence; its residual balance must be explainable.
Project / Capital · PO is assigned to the wrong WBS, Network, or Cost Center
Trace: requisition or PO → account assignment category → WBS/network/cost center → commitment → goods receipt or invoice → project or cost report. Check the account-assignment object, status, validity, budget-control scope, responsible owner, and whether the PO was changed after approval. Correct the controlled source assignment and prove the old and new object positions reconcile.
Production · Activity rate is missing or wrong
Trace: production order operation → work center → activity type → confirmation quantity → activity price or rate → CO posting → order actual cost. Check work-center assignment, control key, activity type, price validity, cost center, period, unit of measure, confirmation quantity, and rate calculation. A missing rate can create an absent or unexpected activity-cost result even when the order confirmed successfully.
Production · Production Order settlement is wrong
Trace: order actuals and goods movements → WIP or variance calculation → settlement rule → receiver → settlement run → inventory, P&L, or margin report. Check settlement variant and order range, settlement rule and receiver, run log, and whether settlement ran before month-end cost and confirmation were complete. Check relevant configuration changes. Reverse and repost only as the controlled last option.
B2R DIAGNOSTIC PLAYBOOKS
Follow the path that matches the control symptom
01 · Budget is not available
Trace: Budget object → approved baseline → release → period and scope → available amount. Approved budget does not necessarily mean released authority.
02 · Available budget is lower than expected
Trace: Released budget − commitments − actuals ± approved changes = available position. Check requisitions, POs, contracts, actuals, reversals, transfers, supplements, and returns.
03 · Commitment is wrong
Trace: Source transaction → account assignment → B2R object → commitment → available amount. Check value, currency, status, responsible object, deletion, closure, and reversal.
04 · Actual cost hit the wrong object
Trace: Source event → FI posting → CO assignment → cost object → B2R consumption. Determine whether the source event or the assignment and determination is wrong.
05 · Availability control blocked a transaction
Trace: Released authority → existing consumption → new commitment or actual → available amount → tolerance → control action. Confirm the checked object and threshold before removing a block.
06 · Availability control did not block
Trace: Authority → consumption → tolerance → control result. Check object and transaction coverage, activation, timing, exception rules, and budget profile.
07 · Budget change is not reflected
Trace: Change request → approval → transfer, supplement, return, or rephase → effective period → updated authority → available amount.
08 · Cost position changed after close
Trace: Source cost → allocation → settlement → WIP or variance → reconciliation → final cost position. Do not confuse movement of cost with movement of budget authority.
09 · Budget report is wrong
Trace: Budget → release → commitment → actual → available amount → forecast or variance → report. Check object, period, hierarchy, currency, changes, close evidence, and filters.
B2R SUPPORT MOMENT
Budget appears available, but the purchase order is blocked
Do not start by changing availability-control settings. Establish the baseline, released amount, commitments, actuals, available amount, and tolerance result. A block can be correct control evidence rather than a defect.
- Record the known-good position and observed control difference.
- Preserve authority, consumption, object, tolerance, source-document, and report evidence before changing anything.
- Correct the layer that owns the first incorrect position.
Use 101 for lifecycle language, 202 for control capabilities, 303 for operation, 404 for design, and 505 for implementation context.