I tried to use up the $100 in Claude Pro promotional credit, so I set the monthly spending cap to $1.02. The result: $1.08 used (106%), balance -$0.01.

A negative balance isn't a bill. But the assumption that "it stops at the cap" turns out to be wrong. I checked what actually stops things and what doesn't, using the official documentation and a support inquiry.

Premise — Don't mix up the four numbers

What makes this confusing is that there are four numbers with similar names. Mix them up and you'll misidentify the cause.

Name What it measures Reset
Plan-included usage allowance What comes with Pro from the start. The free-to-use range Every 5 hours
Usage credits (balance) The prepaid wallet used once the allowance runs out. API-equivalent pay-as-you-go Only decreases. Increases with top-ups
Monthly spending cap The limit on how much can be drawn from the wallet per month. Set by yourself Monthly
Promotional credit Distributed credit. Goes into the same wallet Has an expiration

The cap and the balance are different numbers. The cap is "how much may be drawn," the balance is "how much is in there." This time both happened to be around $1 and close in value, which made them easy to confuse.

What happened

  • By the end of last month, $98.97 of the $100 in promotional credit had been consumed. Balance: $1.03
  • Intending to use up the rest, I set the monthly spending cap to $1.02 (one cent below the balance)
  • The usage screen showed $1.08 used / 106% used, and it stopped after exceeding the cap
  • The balance display showed -$0.01

The screen showed this:

$1.08 used          ████████████████ 106% used
Resets Sep 1

$1.02               [Adjust cap]
Monthly spending cap

-$0.01
Current balance · Auto-recharge Off

Two things didn't sit right: "I set the cap to $1.02, but $1.08 was used" and "the balance is negative."

What the official documentation says

There's one thing to watch for. Help Center articles are split by target plan, and the content differs. If you're talking about Pro but read the Team-oriented article, you end up thinking you've read something that isn't actually there.

The Pro / Max article

Manage usage credits for paid Claude plans

  • Usage credits are prepaid

    You'll then need to prepay to cover usage beyond your plan limits.

  • You can set the monthly cap yourself

    Monthly spending cap: Set a maximum amount you're willing to spend on usage credits each month.

  • The plan-included allowance resets every 5 hours

    Your session limits reset every five hours as usual.

  • Japan has an expiration (starting 2026-09-10)

    In most cases, usage credits do not expire. However, in certain jurisdictions such as Japan, usage credits expire six months after purchase starting September 10, 2026.

This article contains no statement that the cap can be exceeded. Nothing about the balance going negative, and nothing about what happens to the balance when the month changes. I read the full text to confirm this.

The Team / seat-based Enterprise article

Manage usage credits for Team and seat-based Enterprise plans

This one has an FAQ item: "Why was I able to exceed my spend limit?"

Why was I able to exceed my spend limit? It's possible to slightly exceed your defined spend limit. Our system checks if you're within your limit before you're allowed to make a single request or send a message. Once the request is processed, we calculate your token consumption, which means you may bypass your limit with that request. Once this happens, any subsequent requests will be blocked.

Two key points.

  1. The cap check happens before the request is sent
  2. The consumption calculation happens after the request is processed

Because there's a gap between the check and the calculation, the cap gets overshot by exactly one last request's worth. After that overshoot, subsequent requests are blocked.

The same article also says:

What happens when I reach my spend limit? If your account is configured for usage credits and you exceed your set spend limit, you won't be able to use Claude, Cowork, or Claude Code again until the next billing period, or until your limits are adjusted.

What stops you is the cap, not the balance. And it comes back either at the next billing period, or when you raise the cap yourself.

Example — What happens with "the last one"

Applying the mechanism above to this case's numbers gives the following. This is an example constructed from the official explanation of the mechanism, not something built from actual logs I looked at.

  • The monthly spending cap is $1.02
  • Consumption for the month progresses to $0.99
  • The next request is sent → the pre-check finds "$0.99 is within $1.02," so it lets it through
  • That request's consumption is finalized. Say it was $0.09 — the cumulative total becomes $1.08
  • It finalizes $0.06 over the cap. Everything after this is blocked

The cap isn't "a line where it stops"; it's "a line where, once crossed, it stops the next one." Given that the cost of a single request isn't known in advance, this design is hard to avoid. The more expensive a single request, the larger the overshoot.

The part where the numbers don't add up

That said, the balance-side number doesn't add up under this explanation.

  • Using $1.08 from a $1.03 balance should give -$0.05
  • The screen shows -$0.01

$98.97 / $1.03 / $1.08 are all displayed rounded to two digits, so rounding has some effect. Even so, a 4-cent difference is hard to explain by rounding alone. This part I don't understand.

What became clear this time is that it can't be written as the causal chain "exceeding the cap by $0.06 resulted in a balance of -$0.01."

I asked support

I contacted AI support (Fin). What follows is a quote of the response, and it is an AI support reply, not Anthropic's official position.

The system checks whether you're within the cap before sending a message. However, because actual token consumption is calculated after the request is processed, that request may cause you to exceed the cap. Once you exceed the cap, all subsequent requests are blocked.

As an explanation of the mechanism, this matches the Help Center's description. However, the source cited was the Team / Enterprise article. The Pro article has no equivalent item, so as far as I searched, no official statement applies this explanation to Pro.

Pressing further, this is what came back.

So does that mean the system doesn't stop at <=0, but stops at <0?

Yes, that understanding is correct. (...) The system doesn't behave as "stop at balance≤0," but as "stop after the balance becomes <0."

This framing isn't accurate. What the official documentation describes is the gap between the pre-check and the post-calculation for the spend limit (cap), not a boundary condition on the balance. The cap ($1.02) and the balance ($1.03) are different numbers, yet partway through, the response starts mixing the two (an example comes up: "if the balance is $0.05 and the cap is $1.02").

It was reasonable to read this as simply agreement with my own phrasing being echoed back. Ask a leading question, and you get a straight affirmation back.

There were a few other points that didn't line up.

  • "It's displayed as -$0.01 because it's managed in cents" → the minor unit only explains that the increment is 1 cent, and doesn't explain why the sign is negative. The source cited was the Enterprise Admin API reference, not an article about consumer-facing billing display
  • "Since this usage is within the promotional credit, no charge occurs" → the conclusion is probably correct, but the source cited was an article about payment methods for prepaid API credit, which touches on neither promotional credit nor a negative balance
  • "When it resets on September 1, the balance goes back to 0" → what the screen labels "Resets Sep 1" is the $1.08-used side, not the balance side. The Pro article says nothing about the balance resetting, either

Even when an AI support reply comes with a link, the linked page doesn't necessarily say what it's cited for. When a source is given, open it and check. This time, doing that turned up five places where it didn't match.

Will I be billed?

I'll write only what can be said from the screen.

  • Auto-recharge is off
  • The usage credits toggle is off (the state where the message "Enable usage credits to keep using Claude even after reaching your plan limit" is shown)

No path toward payment is active. A negative balance is just a record that "distributed credit was overused by one cent" — it isn't a state where an invoice gets issued.

Support also answered that no charge occurs. However, as noted above, the source that reply cited doesn't say this. The state of the screen is the more reliable evidence.

What I don't know

  • Why the balance is -$0.01 rather than -$0.05
  • When and how the negative balance gets resolved (does it reset to 0 at the start of the month, or does it just stay?)
  • Whether an official statement describing this overshoot behavior for Pro exists (none found within my search)

Summary

  • The cap isn't "a line where it stops." It stops after being exceeded. Setting it to target a small remaining amount and use it up exactly doesn't work
  • The cap and the balance are different numbers. Describing one in terms of the other always ends up off
  • Help Center articles differ in content by target plan. Don't apply a Team article to a Pro question
  • Check AI support replies by opening the cited sources. The presence of a link isn't proof of correctness
  • Leading questions get affirmations back. Ask "where is that written," not "does that mean..."

Sources