101
B2R ยท FOUNDATIONUnderstand the governed budget lifecycle

What is Budget to Report?

Budget to Report turns planned demand into an approved spending boundary, monitors consumption, governs changes, and presents the position so leaders can act.

Budget to Report flow

From intended spend to accountable action

A budget is a controlled commitment, not just a forecast

The budget establishes an authorized baseline and, where policy requires it, an availability boundary. SAP Controlling (CO) explains cost and accountable objects inside the B2R path. FP&A refreshes the outlook and scenarios. R2R confirms the accounting record. B2R controls authorization and availability without replacing native cost collection, allocation, settlement, or status logic.

READ THE LIFECYCLE

From budget authority to accountable reporting

Read B2R as a control loop: convert a plan into object-appropriate authority, monitor commitments and actuals, close cost evidence, then act on the reported position.

  1. 01

    Plan the cost and funding need

    Define the scope, cost drivers, phasing, accountable object, expected cost, and funding need before requesting authority. Validate the planning version, assumptions, owner, period, and evidence trail; a cost plan explains expected demand but does not itself authorize spending.

  2. 02

    Authorize the budget

    Approval establishes the governed budget baseline. Where the selected project/WBS model supports release, it makes an authorized portion available for consumption. Confirm the approved amount, release profile, validity, tolerance, approver, and controlled-change route; released budget is authority, not an accounting posting or forecast.

  3. 03

    Consume budget and control availability

    Operational documents create commitments and accounting events create actual cost against the responsible budget and cost objects. Compare the object-specific allowed budget with that consumption before an irreversible commitment or posting proceeds; record the warning, block, or override and resolve exceptions through the approved route.

  4. 04

    Close, allocate, settle, and reconcile cost

    At period end, run the applicable CO processing to allocate shared cost, calculate WIP or variance, settle temporary objects, and reconcile the result. Check run status, sender and receiver totals, drivers, settlement rules, reversals, and exceptions before using the result for management reporting.

  5. 05

    Report the position and take action

    Report budget, commitment, actual, available amount, forecast implication, variance, accountable owner, and required decision together; include project release only where relevant. Tie material variance to its source evidence and action date, making clear whether management must intervene, revise a forecast, or initiate a separately governed budget change.

SAP Controlling (CO), within B2R

Owns cost objects, allocations, activity and product cost, close evidence, and profitability analysis.

B2R

Budget authority, object-specific availability control, change governance, and budget-position reporting.

FP&A

Forecast, scenario, performance outlook, and decision support beyond the spending boundary.

BUDGET EVIDENCE

Connect authority to accountable action

This lens answers a different question from the lifecycle above: what evidence proves the result at each ownership boundary?

AUTHORITYWhich approved budget and release permits the commitment?
CONSUMPTIONWhich commitment or actual posting uses the authority?
POSITIONDo budget, commitment, actual, forecast, and available balance agree?
ACTIONWho approves, corrects, transfers, releases, or explains the exception?
CONTINUE TO B2R 202Explore the control capabilities

Build the policy, planning, approval, monitoring, change, and reporting components.

Open capabilities