What is the difference between Budget, LE, commitments, and actuals?
Four views of the business that are often compared but should never be treated as interchangeable.
Short answer
Budget is the approved annual plan. Latest Estimate, or LE, is the current forecast of where the business will land. Commitments are customer-level commercial expectations created by approved awards or agreements. Actuals are recorded purchases or recognized results. Connecting them explains not only the size of a variance, but which customer and product decisions created it.
Each view answers a different question
Budget asks what the organization approved before the year began. LE asks what the organization currently expects. Commitments ask what specific customer business has been awarded or activated. Actuals ask what customers have purchased or what the business has recorded.
- Budget: What did we plan?
- Latest Estimate: What do we now expect?
- Commitments: What customer business supports that expectation?
- Actuals: What has happened so far?
Connect at customer and product level
A total-company variance can be numerically correct but operationally useless. When the four views share customer, product, period, and scenario dimensions, the team can identify whether a variance comes from price, volume, timing, product mix, award changes, or customer performance.
The commercial record should also preserve the version of the assumptions that was current when a decision was approved. Otherwise historical explanations change every time the forecast is refreshed.
Use a bridge, not four isolated reports
A useful review starts with the approved Budget, incorporates awarded and activated commitments, shows the latest forecast adjustments, and then compares actual performance. The bridge should let a reviewer move from an aggregate variance into the customer and product records that explain it.
Frequently asked questions
Should commitments automatically become the forecast?
Not always. A commitment is an important input, but timing, supply, customer behavior, and probability may require an explicit forecast adjustment. The relationship and the adjustment reason should both remain visible.
Why keep old forecast assumptions?
They show what the team knew when it made a decision. That history supports learning, governance, and fair evaluation of the decision rather than judging it only with later information.