What a completed review should leave you with
A simulation signoff that records scope, period, eligible and deferred work, blocked items, projected totals, and rerun decisions.
Evidence to collect
- Simulation identifier, scope, reporting context, and timestamp.
- Counts or records for eligible, deferred, and blocked work.
- Projected totals, corrections, rerun result, and signoff owner.
What to do when the review finds a problem
The preview scope does not match the intended run.
Stop and correct the selection when the simulated organization, franchise set, or reporting context is wrong.
The simulation returns multiple outcome groups.
Review eligible, deferred, and blocked items separately so unresolved work is not hidden in the total.
The preview exposes a blocker or unexplained total.
Correct setup or data issues and rerun the simulation when projected output is incomplete or unexpected.
The eligible output and remaining deferrals are understood.
Sign off the exact simulation scope and time before handing it to processing.
A common mistake to avoid
Assuming a simulation created invoices or charges when it only previewed what a run could do.
What is billing simulation used for?
Simulation previews eligible entries, deferred or blocked work, and projected totals before invoice creation. Teams can inspect the authorized scope, correct setup or data issues, and rerun the preview before approving processing.
Manage the work in Granite
Granite's billing simulation previews eligible, deferred, blocked, and projected results before processing.
Open dashboard ↗