---
id: KB-CD-004
url: https://app.codecontract.io/help/credits-and-billing/i-have-run-out-of-balance
idioma: en
categoria: creditos
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CD-002, KB-CD-003]
citadoPor: [KB-CD-007, KB-CD-009, KB-CD-011, KB-CD-005]
---

# I have run out of balance

_What stops, what carries on, and how to get moving again in five minutes._

**Responde a:** i have run out of credits · cannot send due to insufficient balance · what happens when credits run out · top up balance urgently

It almost always happens mid-batch and in a hurry. The first thing to know is that nothing has broken: what already went out carries on.

## What stops and what does not

| Keeps working | Waits |
| --- | --- |
| What was already sent, reminders included | New sends |
| Signatures in progress | Automatic reading of new documents |
| Viewing, searching and downloading | New SMS and WhatsApp |
| A third party delivering or signing | — |

> [!NOTE]
> That third parties are unaffected is the important part: nobody outside learns you ran out, and whoever was signing can finish.

## How to get moving

1. **Top up from the credits screen.**
2. **Return to the batch that stopped and relaunch only for those left out.**
3. **Set the low-balance alert if you had not, so it does not happen mid-batch again.**

> [!WARNING]
> When relaunching, filter for those who received nothing. Sending again to people who already had it duplicates the request and confuses them.

> [!IMPORTANT]
> If it happened on a batch with a deadline — an amendment that had to go today — prioritise topping up and relaunching over investigating why it ran out. The breakdown can wait until tomorrow.

**Is prepared work lost?**

No, it is still there; it is only waiting for balance.

**Can I go into negative balance?**

It depends on your configuration. By default, no.

**How long until it is available?**

Topping up is immediate.

## Ejemplos

**A batch of 400 amendments stops at 260 for lack of balance.**

- Tops up
- Relaunches filtered to the 140 who received nothing

→ All 400 go out the same day and nobody receives the document twice.

**The balance runs out and work stops.**

- Warns before reaching the threshold

→ Topping up happens with time to spare.

**Nobody knows how much is left until something fails.**

- Checks the balance regularly

→ Running out stops being a surprise.

**It runs out at a critical moment.**

- Estimates the peak month separately

→ The peak is covered in advance.

**It is topped up and runs out again weeks later.**

- Reviews which activity consumes most

→ The cause is tackled rather than the symptom.

**An automated campaign empties the balance overnight.**

- Reviews what is scheduled before launching

→ Consumption is decided rather than discovered.