# Prepaid support hours: terms, balance and what happens at zero

https://krokul.com/en/blog/prepaid-support-hours/ · Krokul Team · Updated 2026-11-01

Service managers and finance managers sell support as a block of hours and then argue about what the block covers. This guide defines the terms, shows the balance arithmetic and compares the three things that can happen when the hours run out.

**Short answer.** Prepaid support hours are a block of hours a client pays for in advance, usually per month, against which the team’s logged time is counted. The contract sets four terms: the allotment, what happens to unused hours, the overage rate and when the client is told. At zero, work stops, continues at the overage rate or waits for approval.

## What are prepaid support hours?

Prepaid support hours are hours of help that a client buys before the work happens. Each logged hour reduces the balance until it reaches zero. They are one of the ways a service company keeps its revenue in step with its effort, as described in the guide on [billing for all the work you deliver](https://krokul.com/en/blog/topics/billing-delivered-work/).

- **Prepaid support hours** — Prepaid support hours are a block of hours a client pays for in advance and draws down as the team logs support work.
- **Hour pool** — An hour pool is the number of hours available in a period, against which logged hours are counted.
- **Allotment** — The allotment is the number of hours included in each period, for example 10 hours per month.
- **Overage** — Overage is the hours worked after the pool is used up, priced at the overage rate.
- **Rollover** — Rollover is a term that lets unused hours carry into the next period, with or without a cap.

## Which terms should a prepaid support contract include?

A prepaid support contract needs four terms, and each one answers a question the client will eventually ask. Writing them before the first request removes most of the later disputes. The wording in the right column is an example to adapt.

The four terms of a prepaid support block:

| Term | Question it answers | Example wording |
|---|---|---|
| Allotment | How many hours come with each period, and for what price | 10 hours per calendar month for £750 |
| Rollover | What happens to hours the client did not use | Unused hours expire at the end of the month |
| Overage rate | What an hour costs once the pool is used up | £85 per hour, invoiced after the month closes |
| Notice | When the client hears that the pool is nearly gone | The owner writes at 90% used and when the pool is exceeded |

Rollover has three common settings. Hours expire at period end, hours carry over once, or hours carry over up to a cap such as 20% of the allotment. Expiry is the easiest to run, because each month is a clean account. A carry-over needs a second number on every balance, the hours brought forward, and a rule for which hours are spent first.

## What happens when prepaid hours reach zero?

When prepaid support hours reach zero, the contract should name one of three outcomes: work stops until the client buys more, work continues at the overage rate, or the team asks for approval before each further hour. Every client interprets silence in the way that costs them least, so the choice has to be written down.

Three outcomes at zero:

| Outcome | What the client sees | Best when |
|---|---|---|
| Work stops until the client buys more hours | A delay, and a request to top up | Capacity is tight and every hour has another buyer |
| Work continues at the overage rate | An extra line on the next invoice | Requests are small and urgent, and the rate is in the contract |
| The team asks for approval before each further hour | A message with the hours so far and a price | Overage is large or the client has a spending limit |

Whichever outcome you choose, the client should hear about it before the invoice does. A message at 90% used gives the client time to decide, and a message when the pool is exceeded confirms the price of the next hour. The guide on [billing retainer overage](https://krokul.com/en/blog/bill-retainer-overage/) covers rates, thresholds and the wording of that notice.

## How do you calculate the balance and the overage?

The balance of a monthly pool is the allotment minus the billable hours logged in that month. A negative balance is the overage in hours, and multiplying it by the overage rate gives the extra amount to invoice.

Example: one month of a 10-hour support package:

| Line | Calculation | Amount |
|---|---|---|
| Monthly package | 10 hours included | £750.00 |
| Hours logged in the month | 13.5 hours |  |
| Hours over the pool | 13.5 − 10 = 3.5 hours |  |
| Overage | 3.5 hours × £85 | £297.50 |
| Total for the month | £750.00 + £297.50 | £1,047.50 |

Overage = (hours logged − allotment) × overage rate, when hours logged exceed the allotment. In the example, (13.5 − 10) × 85 gives £297.50. A package with no overage rate in the contract leaves the 3.5 hours with no price, so the rate belongs in the contract before the first hour is logged.

## Which mistakes cause disputes over prepaid hours?

- Leaving rollover unwritten. The client assumes unused hours carry over and the provider assumes they expire. State the rule as one sentence in the contract.
- Letting overage accumulate without a message. The client finds out from the invoice and challenges every hour. Tell the client at 90% used and at zero.
- Counting hours at the end of the month. Entries made from memory run low. Ask the team to log time the day the work is done.
- Mixing two kinds of work in one pool. Support requests and project work then compete for the same hours. Give each its own pool or its own project.
- Skipping the overage rate. Without a price, extra hours are either given away or argued about. Put the rate in the same clause as the allotment.

## What should a prepaid hours clause checklist contain?

Copy the list below into the support contract or the order form, and fill in the numbers. For clients on a continuing arrangement, the package invoice itself can be issued on schedule, as the guide on [invoicing retainers automatically every month](https://krokul.com/en/blog/automate-retainer-invoicing/) explains.

- Allotment: hours per period and the price of the package.
- Period: calendar month, and the time zone that closes it.
- What counts as an hour: billable support work, with the minimum increment, for example 15 minutes.
- Rollover: expire, carry over once, or carry over up to a cap.
- Overage rate: price per hour after the pool, and when it is invoiced.
- Outcome at zero: stop, continue at the overage rate, or ask for approval.
- Notice: the thresholds at which the client is told, and who sends the message.
- Refunds: whether unused hours are refundable or lapse.

## How Krokul tracks the pool and warns at zero

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. Its project card keeps a prepaid block as a pool of hours, next to the logged time and the money.

In the Hours block of a project, enter the Hours budget, set the Pool to Per month and fill in the Hourly rate over the pool. A project with a monthly pool is marked as a Support package; in the Krokul palette the mark sits in the status hint. Every hour logged on the project, from the timer, a task, a ticket or the Log hours button, enters the Hours log and the balance.

A monthly pool counts the hours of the current calendar month in the company’s time zone and starts again with the next month, so unused hours expire. The card shows this month’s hours against the pool. Once the pool is exceeded, a “+N h over the package” mark appears next to the figure, the bar extends past the package, and three tiles below it show the amount to invoice at the overage rate, the cost of the hours and the margin. An empty overage rate leaves the hours over without an amount to invoice. The card counts all logged hours, while the completion certificate takes only the billable ones.

Logging time is never blocked at zero, so the team keeps working at the overage rate unless the owner decides otherwise. When the pool is exceeded, Krokul sends the project owner a notification once for that month, within the hour, and a new month sends a new one. It applies to projects in the In progress status. The Projects list has two ready-made filters, one for pools near the limit (90% or more, not yet exceeded) and one for pools already exceeded. The owner then writes to the client with the numbers from the card.

At month end, the Create act button builds the completion certificate from the month’s hours: one line for the package and one line for the hours over it at the overage rate. Hours already included in a certificate are not counted again. If hours are over and the overage rate is empty, Krokul refuses to create the act and asks you to set the rate. The [monthly hour pool in Krokul](https://krokul.com/en/solutions/projects/) is part of the projects and billing setup.

![Support package project card: this month 13.5 of 10 hours in red, pool used up, 3.5 hours over and £297.50 to invoice](https://krokul.com/img/en/blog/prepaid-hours-pool-card.webp)

## Frequently asked questions

### Do unused prepaid hours roll over?

That depends on the contract. The three common settings are expiry at the end of the period, one carry-over, and a carry-over up to a cap. A monthly pool in Krokul starts again each calendar month, so unused hours expire.

### How many hours should a support package include?

Base the allotment on the hours the client used in recent months, and keep a margin of one or two hours. A package that is always exhausted in the first week sets up an overage conversation every month.

### Can a client get a refund for unused hours?

Only when the contract says so. Decide in advance whether unused hours lapse or are refunded, and write the rule next to the rollover term.

### When should the client be told that the hours are running out?

Tell the client at around 90% used and again when the pool is exceeded. The first message lets the client decide about a top-up, and the second confirms the price of the next hour.

### Should prepaid hours be invoiced before or after the work?

Invoice the package at the start of the period, because the hours are paid for in advance. Invoice the overage after the month closes, when the number of extra hours is known.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
