Start with the reported source and coverage when AWS costs are missing. No new costs read is not proof that the AWS account spent nothing.

Review the provider state

1. Open PD Modules → Cost & Margin → Providers and choose the intended month.
2. Read How we read it, the stored resource counts and matched count.
3. Review the latest Report or Activity result before repeating a refresh.
4. Distinguish no configured source, unavailable runtime support, permission refusal, resource-detail opt-in, delayed data and request validation errors.

The published implementation uses the AWS SDK when available and the configured PD AWS module credentials. Provisioning permissions do not themselves prove Cost Explorer access; review the exact reported error with the account administrator rather than granting broad permissions.

Check data scope

AWS documents that daily resource detail is an opt-in feature with a recent history window. Its API reference also specifies request constraints. An enabled setting does not guarantee that the released request satisfies every constraint.

Do not assume a service-level fallback total can be attributed to individual resources. Partial windows, pagination and overlapping accounts can limit the stored view, and a later refresh can overwrite the stored amount for the same month rather than adding a separate daily history. Check the covered dates independently.

Retry deliberately

Refresh can make chargeable provider API requests; review AWS’s current API pricing before repeated attempts. An error can follow a partial update, so compare existing stored data before retrying. Use the reported error and covered dates to distinguish request validation from incomplete data; do not repeatedly loosen permissions or treat a partial bill as a complete month.

See the PD Cloud Cost & Margin WHMCS guide for related tasks, or explore PD Cloud Cost & Margin.