Start from the account’s current billing overview
Cloudways groups its billing pages into Overview, Settings, Billing History and Credits & Discounts. The Overview includes current estimated usage, overdue amounts and funds paid in advance. Its interface guide says the month-to-date view is updated daily. Save the period and export used for your comparison, rather than treating today’s screen as a permanent copy of last month’s invoice.
The payment-system guide describes Estimated Due as an approximation, not a confirmed charge. Total Charges is also different from the amount left after credits, taxes and prepayments. Label these figures in an internal report. Comparing a gross service subtotal with a net card payment can create an apparent discrepancy even when the invoice is correctly settled.
Identify the product and resources that generated the bill
Cloudways’ billing guide separates Flexible server use from Autonomous application use and autoscaling. It also lists separately billed products and add-ons, plus possible bandwidth or storage overages. Record the server or application, active period and enabled extras alongside each service category. A list of websites alone is not a reliable record of all billable resources.
The payment guide cautions that stopping a Flexible server does not pause billing for DigitalOcean, Linode or Vultr because allocated resources remain. Stopped AWS/GCE servers can still incur storage costs. Before changing infrastructure, identify the provider and the data that must be retained; do not use a stop button as proof that every charge has ended. Ask the administrator to explain the remaining resources instead of repeatedly changing the payment card.
Trace carry-forward items to the usage period
Cloudways explains that some AWS and GCE resource data from the last two or three days of a month arrives too late for the new monthly invoice. It describes those bandwidth, disk or snapshot amounts as carry-forward charges in the following cycle. An item appearing later can therefore relate to earlier resource use; check both its description and its period before labelling it a duplicate.
For an invented reconciliation, USD 90 of current-period services plus USD 7 of earlier carry-forward usage equals USD 97 before other adjustments. These are not Cloudways rates. Keep the earlier amount on a separate line with the relevant resource and period. That also prevents an agency from charging one client for another client’s resource simply because the items appear on the same account invoice.
Sources & further reading: [1]
Separate promotional credits, prepayments and the card remainder
Cloudways’ payment-management guide says promotional credits are used before prepaid account funds; any remaining balance is then charged to the primary payment method. Backup methods can be used if the primary fails. New transactions are processed in USD, while historical invoices in another currency can retain their original settlement currency. Read the currency on the actual invoice being reconciled.
As a budgeting example, a USD 100 invoice with USD 10 of applicable promotional credit and USD 30 of available prepayments leaves USD 60 for the payment method, assuming no other adjustments. Do not report the USD 100 invoice and USD 60 card entry as separate purchases. Preserve the credit application and prepaid-fund deduction so the arithmetic is visible to the next person reviewing the account.
Sources & further reading: [4]
Close the record with the invoice and its applied payment
Billing History brings invoices, payments and prepayments together and supports downloadable records. Cloudways distinguishes a temporary USD 1 card-authorisation hold from the USD 5 PayPal setup transaction that becomes a prepayment. Those entries do not have the same meaning as a monthly service invoice. Match the invoice and applied payment in the history before deciding whether a balance remains outstanding.
Approval Plus funding is another separate ledger. Its minimum is USD 10, with a 1% platform top-up fee below USD 300 and 0% at USD 300 or above; network fees remain separate. A USD 100 request credits USD 99 after the platform fee. Keep that funding record, the Cloudways prepayment if one was made, and the settled hosting invoice distinct. None should be counted twice merely because funds passed through more than one step.
Your questions, answered
Is Cloudways Estimated Due already a completed card charge?
No. Cloudways describes it as an estimate based on the current billing cycle. Compare the final invoice and payment history before reconciling it as money already collected.
Does stopping a Cloudways server prove its charges have ended?
No. The official payment guide distinguishes providers and continuing allocated resources. DigitalOcean, Linode and Vultr Flexible servers continue billing when stopped; stopped AWS/GCE servers may still have storage charges.
Why might a Cloudways card payment be lower than the invoice?
Promotional credits and prepayments can be applied before the remaining amount reaches the payment method. Match those applications to the invoice instead of comparing only its gross total.
Sources & further reading
- Cloudways: billing navigation, estimates and carry-forward items ↗Checked Nov 16, 2026
- Cloudways: payment system, estimates and stopped-server billing ↗Checked Nov 16, 2026
- Cloudways: products, usage and authorisation entries ↗Checked Nov 16, 2026
- Cloudways: payment management, credits and prepaid funds ↗Checked Nov 16, 2026
- Approval Plus: account funding minimum and platform fees ↗Checked Nov 16, 2026