Mercurie
/DOCSSUBSCRIPTIONSCLOUD_BILLING_SPEND
SUBSCRIPTIONS

Understand Cloud Billing Spend

Explain Google Cloud and AWS invoice changes, VAT, spend spikes, idle resources, and project or service cost breakdowns.

Understand cloud billing spend

Mercurie can help customers review Google Cloud or AWS billing questions after cloud billing is moved into a Mercurie-managed Naira invoicing workflow.

What Mercurie can help explain

Support can help you interpret provider billing data you share, including:

  • Which project, account, or service caused a charge, when exports or reports are available.
  • Why an invoice increased compared with a previous month.
  • Whether VAT, FX, or payment terms affected the final Naira invoice.
  • Whether deleted resources may still have generated charges before deletion.
  • What information is needed to estimate future spend.

Cloud providers calculate the underlying usage. Mercurie helps translate the billing output into your local invoicing workflow.

Spend spikes

If your invoice increased unexpectedly, first check Google Cloud Billing reports or AWS Cost Explorer for the billing period, project/account, and changed services. If the reason is still unclear, send support:

  • The billing period.
  • The invoice or statement you are reviewing.
  • The project, account, or workload you suspect caused the increase.
  • Any recent changes, launches, tests, backups, data transfers, or new services.

For Google Cloud, project-level and service-level billing exports can make investigation much easier. For AWS, Cost Explorer or billing reports can help show which services changed.

Charges after deleting a service

You may still see cloud charges after deleting a resource if:

  • Usage happened before deletion but was billed later.
  • Attached storage, snapshots, IP addresses, logs, backups, or data transfer remained active.
  • A related service kept running in another project, region, or account.
  • The invoice covers a billing period before the resource was deleted.

Support can help review the billing period and point you to the provider data needed to confirm the source.

Idle resources before the next bill

Mercurie can help you review billing reports for signs of idle or forgotten resources, but the cloud provider remains the source of truth for what is running. For Google Cloud, check Billing reports, cost tables, recommender insights, and project-level usage. For AWS, check Cost Explorer, budgets, Trusted Advisor where available, and service-level usage.

When asking support to help review idle spend, include:

  • The provider: Google Cloud or AWS.
  • The billing period you want reviewed.
  • The project, account, region, or workload you are concerned about.
  • Any services you recently deleted, resized, paused, or migrated.

Mercurie can help explain what the reports show and what to verify next. We do not delete or resize customer cloud resources without explicit approval from your authorized admin.

VAT and invoice lines

VAT may appear separately from cloud usage because taxes are calculated as a separate line from the underlying provider usage. The final Naira invoice can also reflect FX and agreed commercial terms.

Estimate next month's bill

Mercurie can help estimate future cloud spend when you provide current usage, recent invoices, expected growth, and any planned changes. Estimates are not guarantees because cloud usage, FX, taxes, credits, committed-use terms, marketplace charges, data transfer, provider reporting delays, and services added by your team can change the final invoice.

Need help?

Open a support ticket with the provider, billing period, invoice amount, and what changed. Avoid sending secrets, API keys, or credentials.

Login to your Mercurie Account