How to set aside and restore expected cloud-cost findings in WHMCS
Set aside an unmatched row when you have reviewed it and confirmed why it is expected. This changes the local review queue; it does not stop provider billing or attribute the cost to a customer.
Mark the reviewed row
- Open PD Modules → Cost & Margin → Paying for nothing.
- Select the intended month and find the resource under Things to look at.
- Confirm the provider, resource and reason it is expected.
- Choose Expected, then check the resulting list.
Examples can include a shared resource or a deliberately retained backup. Make the decision from the actual resource context, not simply because a large cost makes the queue inconvenient.
Revisit it later
Choose Ones you have set aside for the same period. This view can show ignored rows regardless of their age or cost threshold. Select Look at it again when the row should return to normal review.
Returning a row to review does not guarantee that it appears immediately in the default queue: age, cost and candidate limits still apply. Check the period and thresholds before assuming the restore failed.
Understand the scope of the decision
The flag belongs to the stored provider-resource-month row. A later import of that same row retains its existing flag, but the same resource in a different month is a different row. A changed cost does not necessarily reset the earlier expected decision.
Review set-aside items deliberately as your infrastructure changes. Marking a row expected does not remove it from every provider total, recall earlier alert emails or change the service margin calculation. If a row behaves unexpectedly, check its period, expected flag and queue thresholds before changing it.
See the PD Cloud Cost & Margin WHMCS guide for related tasks, or explore PD Cloud Cost & Margin.