How available credit batches are consumed

Your balance is not one number in a box. It is the sum of several batches, each with its own remaining amount and expiry, and POM AI spends them in a fixed order.

The order

When an operation runs, the account selects from batches that are active and not yet expired, in this sequence:

1. Subscription batches before top-up batches.
2. Within a group, the batch expiring soonest first.
3. If two expire together, the older batch first.

An operation can span several batches: if the first has 40 credits left and the operation costs 60, it takes 40 from that batch and 20 from the next.

Why this order

Subscription credits are time-limited and are replaced when the subscription renews. Top-up credits last much longer. Spending the perishable allowance first means the reserve you paid for separately survives.

The effect is that a top-up acts as a buffer rather than as a parallel wallet. It is drawn on only once the current subscription allowance is exhausted.

What this means in practice

Your top-up sits untouched until it is needed. If the account still has subscription credits, the top-up figure will not move. That is correct behaviour, not a fault.

A renewal can make unused subscription credits disappear while the top-up stays. The subscription batch is replaced on renewal; the top-up is not. See Credit expiration.

Timing matters near a renewal date. Work done just before a renewal draws on the batch that is about to be replaced — a good use of it. Work postponed until just after draws on the new batch, and the old one is gone.

You cannot choose which batch to spend. There is no selector. If you need spending separated between projects or clients, separate the accounts, not the batches.

Reading the breakdown

My Account → POM AI Management shows the batches:

• Subscription credits — the group total, then each batch with its remaining amount and expiry.
• Top-up credit batches — the group total, then each batch labelled by its order, with the date it was added and its expiry.

To predict what the next operation will spend, find the subscription batch with the nearest expiry and a remaining amount above zero. That is where it will come from.

Whole numbers, no partial credits

Operations are priced as whole credits and rounded up, so a batch is drawn down in whole units. A batch can be left with an odd remainder that a later operation will finish off before moving to the next batch.

Refunds and reversals

If an operation is interrupted after consumption has been recorded, the account can return the credits to the batches they came from, in the same proportions. It does not create a new batch, so the original expiry dates still apply.

Returned credits are therefore not fresh credits. A reversal shortly before a subscription batch expires still leaves those credits expiring on the original date.

Several domains, one order

Every authorized domain draws on the same batches in the same order. There is no per-domain allocation and no reservation.

A per-domain spending limit caps how much a given domain may consume in total; it does not give that domain its own batch. See Plans, credits and domain capacity.

Planning around the order

• Schedule large jobs before a renewal rather than after, to use the allowance that is about to lapse.
• Keep a top-up reserve if deadlines are firm; it will still be there when the subscription batch runs out.
• Do not interpret a static top-up figure as unused money — it is a buffer behaving as designed.
• Check the batch expiring soonest when you want to know what a job will actually draw on.