How Long Do Cloud SLA Credits Take to Arrive? The Provider Processing Timelines

October 23, 2026

You filed the claim, the case closed with an approval, and then nothing happened. That silence is normal: cloud SLA credits move on billing-cycle clocks, not support clocks. AWS issues the credit within one billing cycle of confirming your claim, Azure says processing typically takes 45 days from receipt, Google commits to applying the credit within 60 days of the request, and DigitalOcean issues within one billing cycle of verification. Translated into calendar time, the money usually shows up on the second invoice after you file, not the first. This post lays out the exact wording each provider signs up to, what the wait looks like with real numbers, and when stopping-waiting-and-chasing becomes the right move.

The promises, in the providers' own words

The four contracts phrase the wait differently, and the difference matters because two of them start their clock only after they have decided in your favor. The Amazon Compute SLA (May 2022) says: "If a claim under the Region-Level or Instance-Level SLA is confirmed by us as valid, we will issue you a Service Credit within one billing cycle following the month in which your request is confirmed by us." Confirmation, not filing. DigitalOcean's CPU Droplet SLA goes the same way: "Upon verification, DigitalOcean will issue applicable Service Credits within one billing cycle."

Microsoft and Google instead commit to fixed days from a fixed event. The consolidated Online Services SLA (October 2026 edition) promises to "process claims promptly following an investigation, typically within forty-five (45) days of receipt of the claim," then apply the credit to your Applicable Service Fees. Google's Compute Engine SLA (last modified October 14, 2026) states that financial credits "will be applied within 60 days after the Financial Credit was requested."

Plan for two invoices, not one. AWS and DigitalOcean count in billing cycles and only start counting at confirmation, Azure runs a 45-day processing window, and Google applies within 60 days of the request. If the credit is not on your bill two full billing cycles after you filed, that is the day to start chasing.

The worked timeline: $200 on a $2,000 bill

Say a service that bills $2,000 a month dips below its commitment and earns the 10% tier. That is $200. You file on November 3. Here is what each provider's contract implies, assuming no back-and-forth:

The spread between providers is roughly a month, and it is fully explained by contract language. AWS is the slowest when you file early in a month, because the confirmation month still has weeks left to run, and the credit waits for the billing cycle after that one. Google is the slowest in worst case by design: 60 days is a hard ceiling, but it is a ceiling, so expect the January statement. Azure sits between them.

One credit never makes you wait: AWS already forgives any clock hour where a single EC2 instance is unavailable for more than six minutes. That discount is applied automatically to the month's bill, no claim, no case, no 45 days. It is also the smallest money in the system, which is exactly why the provider is comfortable automating it. Everything above the six-minute threshold follows the table.

Why claims sit in limbo (it is usually not the provider being slow)

The contract promises above assume a complete claim that lands in the right queue. Real claims lose weeks in four places:

• Wrong filing channel. The Amazon Compute SLA demands the exact subject line "Amazon Compute SLA Credit Request - Region-Level Claim" (or the Instance-Level variant). A generic subject routes the case to the wrong queue for days. Azure SLA credits are billing tickets, not technical tickets; technical queues run on different clocks.
• Evidence gaps restart the conversation. AWS states that failing to provide the required information disqualifies the request, and Google will not evaluate a claim without log files showing the downtime periods. Every round of "please send your request logs" is a week the 45-day Azure clock is not really ticking. The evidence checklist that keeps claims moving is covered in our guide to what providers accept.
• Month boundaries stretch the math. File on the 2nd and AWS counts your confirmation month as nearly full, pushing the credit to the cycle after next. The same claim filed on the 28th lands a full month sooner. Billing-cycle reasoning means the filing date inside the month matters as much as the deadline.
• Sometimes there is nothing to apply. AWS ignores credits under $1, free-tier usage bills nothing and Google and Microsoft exclude it from eligibility, and every credit is a percentage of the affected service's fees only. A $200 claim processed in 45 days is normal. A $0.80 claim is not processed at all.

One real-world anchor: in a 2021 r/AZURE thread about an erroneous charge, the user logged a billing ticket on August 22, got verbal approval on September 22 after an escalation, and saw the card refund on October 8. That was a refund of a mistaken charge, not an SLA credit, but it went through the same billing team. Expect approvals in weeks and money in days after approval, on every provider.

Two invoices, then chase

Check the right artifact before you chase anything. On AWS the credit shows as a line item on a future invoice (and AWS may, at its discretion, refund the card used in the incident month instead). On Azure it lands as a credit against Applicable Service Fees on the invoice. On Google it appears as a credit on the billing statement for the covered service. On DigitalOcean it sits in the credit balance under Billing, applied to future invoices.

Know what a billing cycle is on each side when you read the promises: AWS billing cycles run per account over the calendar month, DigitalOcean documents that its billing cycles are monthly, Azure invoices follow your billing period (monthly for most agreements), and Google bills on calendar-month statements. The practical rule is the same everywhere: the credit can only appear on a statement after the processing promise has run, so mid-month filing nearly always means waiting past the next month end.

If two full billing cycles have passed and nothing shows:

1. Reopen the original case or ticket, not a new one. Quote the case ID, the credit amount, and the SLA clause from the table above, and ask for a date.
2. If it was denied somewhere in that silence, the appeal lives in the same ticket. The denial reasons and the escalation path are in our appeal walkthrough.
3. Do not take matters into your own billing hands. Microsoft's SLA is explicit that you may not unilaterally offset your Applicable Service Fees, and DigitalOcean credits are non-refundable. Self-applied offsets are how clean claims turn into disputes.

The concrete move, today: the moment your claim gets its approval, add a calendar entry two billing cycles out, named with the case ID and the dollar amount. On that day, open the invoice, search for the credit line, and if it is missing, reply to the approval message with the case ID and the exact promise from the table. The credit is yours. The provider just keeps its own calendar, and now you know what that calendar says.