How to verify forecast results and report issues
If the query is “I need to verify forecast results before export,” this is the practical flow. You should validate first, then export.
1) Validate in browser before export
Use the following sequence:
- Confirm opening BS values and forecast start period.
- Review period settings (monthly vs annual) and check lag settings.
- Open the Checks view and confirm no obvious sign, mapping, or period anomalies.
- Run one minimal scenario and compare against expected direction (not exact match).
2) Common causes of mismatched signs
- Different sign convention inside opening BS input.
- Transaction month entered outside expected forecast window.
- Collection/payment lag set too large for first periods.
- Journal type selected with unintended flow direction.
3) How to report a calculation issue
The tool includes a Report a journal issue action. Include:
- Issue type: journal mapping, account mapping, or calculation.
- Sample month, account code or account name.
- Observed value and expected value.
- Short reproducible steps.
The report is stored as a compact record with no full scenario payload. This keeps support review fast and reduces data footprint.
4) Why export is not required for issue triage
A common misconception is that export is needed to confirm correctness. In this workflow, all core checks and calculations can be reviewed in the web tables.