How to Bill Clients for Hosting and Domain Renewals
By Mark Fulton · · 13 min read
Last verified:

The cleanest way to bill hosting and domain renewals is to have the client own the accounts and pay the provider directly, with you holding admin access. If the client wants you to handle it, resell the service on an annual invoice sent about 45 days before the provider charges you, with the pass-through cost and your management fee as separate line items. If you already run a maintenance plan, fold hosting into it as a bundled price. Pick one of these three models per client, write it into the contract, and never leave renewals as something you quietly pay with your own card.
The third option, the quiet card, is how most developers end up here. You set up a site, register the domain on your own account because it was faster, and put the hosting on your own plan. Eleven months later a charge shows up on your statement for a site you finished a year ago. You message the client, they say they will "look into it," and three weeks later you are either eating the cost or watching a live business site go offline. Neither outcome is a billing system.
This post lays out the three models, who carries the risk in each, what the annual renewal invoice should look like, what to do when the client does not pay, and when it makes more sense to stop itemizing and sell a care plan.
General information, not tax or legal advice. Sales tax on hosting and domain resale varies by state and country, so confirm the treatment with a local accountant.
Who should own the hosting and domain accounts?
Ownership decides everything else: who gets the renewal notice, whose card is charged, and who can fix things when they break. You have three realistic choices.
| Client-owned | Resold | Bundled into a care plan | |
|---|---|---|---|
| Account holder | Client | You | You |
| Who pays the provider | Client, directly | You, then you invoice the client | You, out of the plan fee |
| Your access | Admin or delegated user | Full | Full |
| What you invoice | Nothing for renewals, or an hourly fee if you handle them | Pass-through cost plus management fee, once a year | One monthly or annual plan price |
| Who eats a failed payment | Client | You | You |
| Markup possible | No, but you can bill time | Yes, but expect scrutiny | Yes, folded into the plan price |
| Best for | Most clients, especially anyone with an existing business | Clients who want zero involvement | Ongoing clients paying you monthly already |
| Main risk | Client ignores the notice and the domain lapses | You carry the float and the liability | Plan price drifts below your real cost |
For the domain specifically, default to client ownership. The registered name holder is the party the registrar and ICANN deal with, and it is the party that bears responsibility if there is ever a dispute over the domain. Developers who run domain registration for clients often describe it as a hassle that the fee does not justify. A client with their own registrar login can move a site to a different developer without asking you for anything, which is a good property to build into the relationship from day one, not a threat.
For hosting, the choice is looser. Some clients are happy to set up an account on a provider you recommend, add you as a collaborator, and pay the bill themselves. Others do not want a login at all. If they want zero involvement, resale or bundling is a legitimate service, and you can charge for the responsibility. The rule is that you choose the model on purpose and the client agrees to it in writing before launch, not after the first surprise charge.
Two practical details help whichever model you pick:
- Register the domain under the client's legal name and a contact email they actually read. Registrars send the expiration notices to that address. A dead inbox is the number one reason a client never sees the warning.
- Put every renewal date in one place. If the domain, hosting, and any paid licenses renew in different months, move them so they land on a single date where the provider lets you. One annual invoice is easier to send, easier to explain, and easier to collect than four small ones.
How do you bill for pass-through renewals?
Pass-through means you are passing along a cost you did not create. The client pays what the provider charges, and you add a line for your own time. Keep those two things visibly separate.
A pass-through renewal has three parts:
- The provider cost, at cost. Domain registration, hosting plan, SSL if it is not bundled, and any paid plugin or service license. Name each item, the provider, and the term it covers.
- Your management fee, as its own line. This covers the work of watching renewal dates, paying on time, keeping credentials current, and responding when something breaks. Charge it as a flat annual amount or as time, and say which.
- Tax, where it applies. Whether hosting and domain resale is taxable depends on where you and the client are. This is the part to check with an accountant.
Itemizing is a deliberate choice, and it is the right one for most freelancers. A client who sees "Hosting, 12 months, $240" and "Renewal management, $60" understands exactly what they are paying for. A client who sees "Hosting and domain: $380" starts wondering what the margin is. Forum discussions of developers who mark up domains show a wide range of practice. Some report adding a small flat fee per renewal, some bill the domain at cost plus half-hour increments of their time, and some mark up heavily. The common thread among the setups that do not cause arguments is transparency: the client can see what the provider charged and what you charged for your own work.
Markups on resold hosting are not inherently wrong. You are carrying a payment obligation on the client's behalf, and the risk of a failed card or a late payer is real money. If you resell hosting, price in enough margin to cover support time and the occasional unpaid month. Just be honest about it. Label the line "Hosting (managed)" instead of pretending it is a pass-through if it includes your margin. If you want a way to express that margin without looking like you are padding, the care plan model in the last section is the honest version.
Whatever you charge, set it before you launch. The web development invoice line items guide covers how to word third-party costs so that finance teams approve them on first read, and the same wording rules apply here.
What goes on an annual renewal invoice?
An annual renewal invoice is a normal invoice with a few extra details that matter because it arrives once a year, when nobody remembers the context. Here is a sample. The amounts are illustrative, not market prices.
Invoice 2026-0148, issued 14 January, due 28 January (net 14)
| Description | Qty | Amount |
|---|---|---|
| Domain registration: examplebakery.com, 1 year (renews 1 March 2027), at cost | 1 | $18.00 |
| Hosting: Standard plan, 12 months (renews 1 March 2027), at cost | 1 | $144.00 |
| Renewal management: monitoring, payment, credential upkeep, 12 months | 1 | $60.00 |
| Total | $222.00 |
Notes on the invoice: Services listed renew automatically on 1 March 2027. If this invoice is not paid by 28 January, the renewal will not be processed and the domain and hosting may lapse. Unpaid renewals can cause the site and email to go offline.
Why each detail is there:
- The renewal date appears next to the item. It tells the client what the money buys and when the deadline is. Without it the invoice reads like a random bill.
- The due date sits well before the provider charges you. The invoice above goes out about 45 days ahead and is due about 30 days before the renewal. That gap is your buffer for slow approvals and one round of reminders.
- The consequence is stated plainly. One neutral sentence about what lapses if the invoice goes unpaid is information, not a threat.
- The term is explicit. "12 months" tells the client this is a recurring annual charge so it does not become a new surprise next year.
Use net terms that fit the lead time. A 14-day term issued 45 days ahead leaves room to chase. The net terms, deposits and late fees post covers how to pick terms so this is not a negotiation every year.
The reminder email
Send the invoice with a short email, then follow up on a fixed schedule. This is a version you can adapt:
Subject: Renewal invoice for examplebakery.com, due 28 January
Hi Dana,
The domain and hosting for examplebakery.com renew on 1 March. The invoice is attached and due 28 January, which gives us a month of margin before the provider charges.
Nothing changes on your end: same plan, same domain, same setup. The invoice shows the provider cost and my management fee separately.
If you would like to renew for longer or change plans, tell me before the due date.
Mark
Follow up at 14 days, 7 days, and 3 days before the due date with one line each. The invoice number and the renewal date should be in every message. If you need wording for the reminders that follow a missed due date, the late fee wording post has it.
What happens when the client does not pay the renewal?
Plan for this before it happens, because the failure modes are different for each model.
Client-owned accounts. The provider emails the client, and their card either works or it does not. Your exposure is small. If the domain is critical, ask to be added as a billing contact so that you see the notices too. Hosting providers send reminders, and domain registrars are required to as well. ICANN's Expired Registration Recovery Policy says registrars must notify the registered name holder at least twice before a gTLD registration expires, approximately one month and one week out, and the registrant has to be able to renew after expiry during the recovery period. That helps, but it all goes to the registrant's email address, which is the reason to keep that address healthy.
Resold or bundled accounts. Here the exposure is yours. Decide ahead of time what you will do and write it in the contract:
- A grace period. For example, you will keep services running for 14 days past the due date while you chase.
- A suspension right. After the grace period you may suspend the site, with notice. Say that backups stay intact and the site is restored once payment clears.
- A reactivation fee, if you want one. Keep it modest and spelled out.
- A clear line on the domain. If you hold the registration, state that the client can request transfer of the domain to their own account at any time once invoices are paid.
Resist the urge to let the domain lapse as leverage. A site going dark on a client who forgot is a much worse conversation than an overdue invoice, and a lapsed domain can be bought by someone else. Suspend hosting if you must. Protect the domain.
Card failures on automated billing. If you charge a card on file for a hosting subscription, assume some payments will decline and plan for it. Stripe's documentation on automatic payment retries says its Smart Retries are enabled by default for new accounts, configured for up to eight retries within two weeks, and that payments cannot be retried when the issuer returns a hard decline such as a lost or stolen card until a new payment method is supplied. A backup payment method and an email to the client at the first failure cut most of the problem. If you invoice instead of charging a card, the same discipline applies to the reminder schedule above.
If the invoice goes seriously overdue, treat it like any other unpaid invoice. The client won't pay your invoice post covers the full escalation ladder.
What if a client lets the domain expire?
It happens, and it is worse than an unpaid invoice because it can take down their email too. If you are the registrant, renew it immediately and invoice the renewal with a note. If the client is the registrant, tell them in writing, with the date and what lapses, and offer to help renew. Either way, keep the message dated and factual. That record is useful if the client later claims they were never warned.
When does a care plan beat itemized renewals?
Itemized renewals make sense when the client has no ongoing relationship with you. You build a site, they own the accounts, and you invoice a modest management fee once a year, or nothing at all.
A care plan makes sense when you already bill the client every month. At that point a once-a-year hosting and domain invoice is an extra moving part, with its own reminders and its own chance to go unpaid. Bundling removes it. You pick a plan price that covers the hosting cost, the domain cost spread over twelve months, the monitoring and updates you perform, and a margin. The client sees one line, "Website care plan, monthly," and never has a renewal conversation.
The trade-off is that you carry the cost risk. If the hosting provider raises prices, your margin shrinks until you raise the plan. Review the plan price once a year, and write the contract so you can adjust it with notice. The website maintenance retainer packages guide walks through building the tiers from your own hours and rate, and hosting is just one more cost line in that calculation. If the care plan is billed monthly, the retainer invoicing post covers how the invoice itself should read.
A rough decision rule:
- No ongoing work, client is comfortable with logins: client-owned. Offer an annual management line if they want you watching renewal dates.
- No ongoing work, client wants zero involvement: resold with an annual renewal invoice, itemized.
- Monthly work already: bundle it into the care plan.
Make the renewal invoice a copy-paste job
The annual invoice is the same document every year with new dates. Build it once in the invoice generator, save it, and duplicate it each January. Update the dates, check the provider prices, and send it. The data stays in your browser, no account required.
FAQ
Should the domain be registered in the client's name?
Yes, in almost every case. The registered name holder is the party the registrar and ICANN recognize, and they carry the responsibility if there is a dispute. Registering under their name with their email also means they can take the domain to another developer without needing your help. If you register it temporarily to get a site live, transfer it to the client at handoff and put the transfer in your project checklist.
How far ahead should I send the renewal invoice?
About 45 days before the provider charges you, with a due date around 30 days before the charge. That leaves room for one slow approval and two reminders. Some domain registrars and hosting providers invoice their own renewals up to 60 days out, so check when your provider bills you and work backward from that date.
Can I add a markup to hosting I resell?
Yes, as long as you are upfront about it. Label the line as managed hosting instead of at cost, and make sure the price covers your support time and the risk of a failed payment. If a flat markup feels awkward to explain, charge pass-through at cost plus a separate management fee, or bundle it into a care plan.
What if a client lets the domain expire?
Contact them right away in writing and check whether the registrar still allows renewal. Registrars must allow the registrant to renew during the recovery period after expiry under ICANN's policy, though fees and the length of that window vary by registrar. If you hold the registration, renew it and invoice it. If the client holds it, document your warning and offer to help.