Choose the symptom you can observe
Open the matching case. Check the existing state before changing a record or repeating an action.
A warning points to a value that looks correct in the source file.
Check first
- Compare the source cell, unit, and period with the value named in the warning.
- Check whether the system interpreted a text number, blank, sign, or decimal differently.
- Confirm whether the warning is about the value itself or its mapping to a report category.
Next action
Record the comparison, then correct the source representation or route the warning for reviewer acceptance. Keep a value that was checked but accepted distinct from a value that was changed and recalculated.
Confirm the result
The warning includes a source-context disposition and the report result reflects either the corrected value or the recorded acceptance.
The calculated total does not agree with the reported components.
Check first
- Add the visible components using the same rounding and sign rules as the source.
- Check for omitted, duplicated, or out-of-period rows in the calculation inputs.
- Compare the calculation version with the source file version that was reviewed.
Next action
Do not overwrite the total to make it match. Identify the missing or duplicated input, correct the source or mapping, and request a new calculation with the issue log attached.
Confirm the result
The recalculated total can be reproduced from the visible components and the calculation state no longer relies on the superseded source version.
The warning has no usable row, field, or source context.
Check first
- Capture the complete warning text and the report identifier before refreshing.
- Check whether the warning appears on one report or across several periods and franchises.
- Confirm that the report version and calculation timestamp are visible.
Next action
Record the warning as unresolved and attach the report context to the owner of the calculation or source mapping. Avoid marking it accepted when the reviewer cannot tell what was checked.
Confirm the result
The follow-up names the affected report and version, includes the exact message, and records a decision or a reproducible support case.
A corrected source value still produces the old warning.
Check first
- Confirm the corrected file or value is the version used by the latest calculation.
- Check the calculation timestamp and whether the report is still using an older draft.
- Compare the current warning with the original to see whether the affected field changed.
Next action
Keep the old warning in the issue history, submit or recalculate the corrected version through the normal review path, and do not treat a page refresh as a new calculation.
Confirm the result
The report shows a later calculation time, the corrected source version, and either a cleared warning or a new message tied to the current input.
Prepare a useful escalation
- Attach the report identifier, franchise, period, source version, calculation timestamp, and full warning text.
- Separate a source-value discrepancy from a mapping or calculation problem before routing it.
- Ask the reviewer with authority over the reported result to disposition an ambiguous warning.
Reference the relevant record instead of copying credentials or unrelated personal information into the handoff.