For best user experience with Actual versus Budget/Forecast, how should the Suffix be configured?

For best user experience with Actual versus Budget/Forecast, how should the Suffix be configured?

• A. Set ACT to Actual Set BUD to Budget Set FCST to Forecast
• B. Set ACT to Actual Set BUDFCST to Budget Set BUDFCST to Forecast
• C. Set ACT to Actual Set ACT to Budget Set ACT to Forecast
• D. Set BUDFCST to Actual Set BUDFCST to Budget Set BUDFCST to Forecast

Answer: (B)

The key idea is to label data types so users can compare actual results to planned figures smoothly. In OneStream, the suffix identifies what kind of data you’re looking at. For the best actual versus budget/forecast experience, you map actual values to the ACT suffix, and have the budget and forecast share a single BUDFCST suffix. This setup keeps Budget and Forecast in one combined category for easy comparison against Actual, reducing clutter and confusion. Using separate suffixes for Budget and Forecast would create two distinct planned-series tracks, making the comparison less intuitive. Using the same suffix for all three would blur the distinction between actual and plan, and labeling actual data with a Budget suffix would misrepresent the data.

The key idea is to label data types so users can compare actual results to planned figures smoothly. In OneStream, the suffix identifies what kind of data you’re looking at. For the best actual versus budget/forecast experience, you map actual values to the ACT suffix, and have the budget and forecast share a single BUDFCST suffix. This setup keeps Budget and Forecast in one combined category for easy comparison against Actual, reducing clutter and confusion.

Using separate suffixes for Budget and Forecast would create two distinct planned-series tracks, making the comparison less intuitive. Using the same suffix for all three would blur the distinction between actual and plan, and labeling actual data with a Budget suffix would misrepresent the data.