Steps for sales report issue review
- 01
Open the report from the list of reports needing review or from the franchise.
- 02
Read the calculation status and each warning, with the rows it refers to.
- 03
Correct the report data, or pass the issue to the person who can decide it.
- 04
Check the report status again before billing uses it.
What the finished work leaves you with
An issue log that ties each report warning to its source row, the decision made, the reviewer, and the resulting status.
What to do when the review finds a problem
The reviewer has checked the warning and it does not change the result
Note it as accepted and continue the review.
The warning points to data that would change the result
Correct the source data and recalculate the report.
The warning is unclear or needs a decision the reviewer cannot make
Escalate it with a link to the report.
The source data or decision has changed
Close the issue only when the new calculation or decision shows on the report.
A common mistake to avoid
Clearing a warning without noting why it was accepted or which source value fixed it.
Franchise sales report issue review checklist
Use this checklist when a submitted sales report has a warning, a calculation problem, or an unclear review status. It keeps the original warning, ties the issue to the source figures, records the reviewer’s decision, and shows the final status before the report is used for billing.
Before you start
- Open the report with its franchise, reporting period, calculation status, and warning details.
- Have the source figures or supporting record ready to compare with the flagged value.
- Decide who can correct figures, ask for a recalculation, or make the call on an unclear issue.
When a sales report warning will not clear
A warning is only useful if the reviewer can find the value behind it and decide whether it changes the result. Keep the original message, find where the problem comes from, and keep accepted warnings separate from numbers that still cannot be trusted.
A warning points to a value that looks right in the source file.
Check first
- Compare the source cell, unit, and period with the value named in the warning.
- Check whether a number stored as text, a blank, a minus sign, or a decimal was read differently.
- Confirm whether the warning is about the value itself or the column it was mapped to.
Next action
Note what you compared, then fix how the value is written in the file or send the warning to the reviewer to accept. Keep a value that was checked and accepted separate from one that was changed and recalculated.
Confirm the result
The warning has a recorded decision, and the report reflects either the corrected value or the acceptance.
The calculated total does not match the reported line amounts.
Check first
- Add the visible amounts using the same rounding and signs as the source.
- Check for missing, duplicated, or out-of-period rows.
- Confirm the calculation used the same file version that was reviewed.
Next action
Do not overwrite the total to make it match. Find the missing or duplicated row, fix the file or column mapping, and recalculate with a note on what changed.
Confirm the result
The new total can be rebuilt from the visible amounts and comes from the current file, not the one it replaced.
The warning does not say which row or field is affected.
Check first
- Copy the full warning text and note which report it is on before refreshing.
- Check whether the warning appears on one report or across several periods and franchises.
- Note the file version and calculation time.
Next action
Mark the warning as unresolved and send it, with the report details, to whoever owns the calculation or column mapping. Do not accept it when nobody can tell what was checked.
Confirm the result
The follow-up names the report and file version, includes the exact message, and records either a decision or a support request someone can reproduce.
A corrected value still shows the old warning.
Check first
- Confirm the latest calculation used the corrected file or value.
- Check the calculation time and whether the report still uses 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 report history, then recalculate or resubmit the corrected version through normal review. A page refresh is not a new calculation.
Confirm the result
The report shows a later calculation time, the corrected file, and either no warning or a new one tied to the current numbers.
When you need to hand it on
- Include the report, franchise, period, file version, calculation time, and full warning text.
- Decide whether the problem is the source value or the mapping and calculation before sending it on.
- Ask the reviewer responsible for the result to decide an unclear warning.
Link to the record instead of copying passwords or unrelated personal details into your note.
A situation to work through
A submitted report has a warning on one row. The reviewer opens that row, checks the source value, and records whether it needs a correction or a decision from someone who can approve it.
Tie each warning to its source row and the decision made, then check the report’s resulting status.
This is a planning example, not a customer result.
What happens when a sales report needs review?
Open the report’s warnings and calculation details, check the rows they point to, and fix the problem before billing uses the report. Granite shows whether a report has warnings, needs review or is fully calculated.
Put the workflow into practice
In Granite, a sales report keeps its warnings and calculation status with it, so reviewers can fix problems before billing.
Set it up in Granite with your own franchises, reporting periods and billing rules.