What a completed review should leave you with
A processing approval record linking the reviewed preview to one submission and its resulting invoice and notification states.
Evidence to collect
- Prepared run identifier, preview version, scope, and approver.
- Approval time and eligible versus deferred or blocked outcome.
- Created invoice, notification, or recovery record for the result.
What to do when the review finds a problem
More than one prepared run or preview is available.
Select the prepared run whose scope and preview are the ones the team reviewed.
The preview contains deferred or blocked entries.
Resolve or explicitly record deferred work before approval so it is not mistaken for eligible work.
The reviewed run is ready for processing.
Approve and submit once, then follow the operation state rather than starting a second run.
The run finishes with anything other than the expected complete state.
Open the resulting invoice or delivery record when processing reports a partial or failed outcome.
A common mistake to avoid
Approving a different or older preview because its totals look similar to the run under review.
How should an organization process an invoice run?
Start from a prepared preview, review eligible and deferred work, approve the run once, and follow the resulting invoice and notification states. Processing preserves the run context so teams can investigate a failed or incomplete outcome.
Manage the work in Granite
Granite's billing processing workspace connects a reviewed preview to one approval and its resulting states.
Open dashboard ↗