Export comparison downloads the budget view for the selected saved plan and version. Confirm the scope, period, currency and basis before using the output in a review. Those details are needed to interpret Planned, Posted actual and the difference.
Wait for posted actuals to load successfully before treating the comparison as complete. An unavailable actual comparison is not the same as zero actual activity. Resolve the book-setup or evidence issue shown by the workspace before drawing conclusions from the missing values.
For project and department plans, retain the allocation coverage with the review. Their actuals come from confirmed whole-journal allocations, while other operational values may be tracked separately. The export should not be described as a complete company statement when its scope is narrower.
Keep earlier plan versions when explaining how expectations changed. A new export using the latest revision can differ from one made against the original plan without any error. Label the version and reporting period so another reviewer can reproduce the comparison and trace significant variances to the supporting ledger entries.
Was this article helpful?
Tell us whether this answered the question you came with.