Billing
How hosting renewals and grace periods actually work
Renewal is not one event. It is a notice, a charge, a grace period, a suspension and a deletion — and the gaps between them are where customers are lost.
9 min read · Reviewed 2026-09-21
In short
Invoice-and-pay raises a document and waits for the customer to act. Automatic charging holds a payment instrument and takes the money on a schedule. Automatic charging does not wait for the customer to act, and it moves the burden of proof onto you: you must be able to show what was authorised, when, and for how much. One workable arrangement is automatic charging for renewals and invoice-and-pay for anything unusual.
These are not two settings on the same thing. They are different commercial relationships with different legal texture, and mixing them up produces a familiar billing complaint: I did not agree to that charge.
What each one actually is
| Invoice-and-pay | Automatic charging | |
|---|---|---|
| What you hold | Nothing. A document and a due date. | A stored payment instrument and a mandate to use it. |
| Who acts | The customer, each time. | You, on a schedule. |
| Collection rate | Lower. Every cycle is a chance to forget. | Higher, until a card expires. |
| The dispute it invites | "I never got the invoice." | "I did not agree to that amount." |
| What you need to be able to show | That you sent it. | What was authorised and when, and any advance notice your terms, the payment method or the law where you trade require. |
| Cash flow | Lumpy. | Predictable. |
The first rule
Tell them before you take it. A renewal notice sent some days before the charge, naming the amount and the date, gives the customer a chance to object before the money moves rather than after it — which is when a disagreement is cheapest to settle. It costs one email.
The second rule: the amount you charge must be the amount on a document the customer can see afterwards. If the charge and the invoice can disagree — because a price changed between the two — you have built a dispute generator.
What automatic charging demands of your records
- The mandate: when the customer agreed, to what, and by what means. A tick box with no record is not a mandate.
- The schedule: what is charged, how often, and from when. A subscription with no recorded start is one nobody can audit.
- Every attempt, including the failed ones. A retried charge that succeeds on the third attempt should show three lines, not one.
- A stopping rule. Cancellation must stop future charges immediately and verifiably, and that stop must be visible to the customer.
Never let a cancellation and a scheduled charge race. If a customer cancels on the morning of a renewal, the answer must be deterministic — and it must be the one your terms describe, not whichever job ran first.
When invoice-and-pay is the right answer
Keep it for anything unusual: one-off work, migrations, overages, anything negotiated. These are the amounts a customer is most likely to query, and an invoice they have to actively pay is an invoice they have actively seen. It is also the right model for larger business customers, who often have a purchase-order process that automatic charging simply cannot satisfy.
A workable hybrid
- Recurring hosting renews automatically, with a notice before each charge.
- Anything one-off is invoiced and paid.
- A failed automatic charge falls back to an invoice with a payment link and a grace period, rather than an immediate suspension.
- Refunds are always a deliberate act by a named person, never automatic.
That combination collects reliably and keeps the surprising amounts on the model where surprise is least damaging.
How this looks in GENV
GENV records invoices, payments and billing subscriptions as separate facts that point at each other rather than as states of one record. A payment belongs to a customer, not to an invoice, and applying it to an invoice is its own recorded act — which is what lets an overpayment or a part payment be represented honestly instead of being forced into a status field. No real payment gateway is connected in the current build, so GENV collects nothing today: automatic charging is not built, and invoice-and-pay runs only against GENV's own practice gateway, which takes no money.
Questions
How long should the notice before a renewal charge be?
Long enough for the customer to act if they want to stop it, and never shorter than any period your terms, the payment method or local consumer law set. There is no universal figure; as an example, a business might choose seven to fourteen days for annual terms, which leaves time to update a card or cancel. Check it against the rules that apply to you.
Should a failed payment suspend hosting immediately?
Not as a default. A failed charge can be an expired or replaced card rather than a decision to leave, and a grace period with clear warnings gives that customer time to fix it while everything keeps working. Suspending at once treats both the same.
Can I switch an existing customer from invoicing to automatic charging?
Only with a fresh, recorded agreement. Migrating somebody onto automatic charging because your new system supports it is taking money on an authority they never gave.