Retainer invoicing for agencies: net 30 and extra hours

Agencies rarely lose money on the work. They lose it in the gap between finishing the work and getting paid: an invoice that goes out on the 6th instead of the 1st, net 30 that quietly becomes net 55, extra hours nobody billed because they were not in the template. This guide covers how to structure retainer invoicing so the money arrives on the terms you agreed.

What a retainer invoice should contain

A retainer is a fixed amount for an agreed scope, billed on a schedule. The invoice should make three things obvious:

• The period it covers. "Retainer, October 2026" beats "Monthly services." When a client's finance team matches invoices to purchase orders, the period is what they match on.
• What was included. A line for the retainer itself, and a separate line for anything outside it.
• When it is due and how to pay. The due date as a date, not just "net 30", and the payment options.

Bill retainers in advance, on the same day every month. The 1st is the usual choice: the client knows it is coming, and your cash arrives before the month's payroll rather than after it.

Extra hours and project work

Most retainers have a cap. The client gets 20 hours of design a month for $3,500, and some months they need 26. Decide up front how overages work, and put it in the contract:

• Billed in arrears at an hourly rate. Six extra hours at $175 is $1,050, added to the next invoice as its own line.
• Rolled into a project quote. Bigger asks, a website revamp or a campaign, become a one-off invoice with its own scope and due date.

Either way, the extra work should appear on the same client account as the retainer, so one list shows everything that client owes. The failure mode is extra hours logged in a time tracker, project invoices in a second tool, and the retainer in a third, with nobody able to say what Acme owes you right now without opening all three.

Net 30, and what it actually means

Net 30 means payment is due 30 days after the invoice date. It is the default for business clients, and larger companies often ask for net 60 or net 90 because their payment runs happen on a fixed schedule.

Longer terms are a cost you should price in. On a $3,500 monthly retainer, moving from net 30 to net 60 means you carry an extra $3,500 of unpaid work at all times. Across 20 clients that is $70,000 of your money sitting in their accounts. Accept it for clients worth it; charge for it, or ask for a card or bank debit, for the rest.

A few practical rules:

• Set terms per client, not globally. A startup on net 15 and an enterprise on net 60 can both be right.
• Print the due date on the invoice, as a date. "Due November 30, 2026" gets paid; "net 30" gets interpreted.
• Send it on the day. An invoice sent five days late is due five days late.

Reminders on the due date, and after

Most late payments are not refusals. The invoice went to someone who left, it sat in an approval queue, or it was simply forgotten. A reminder fixes most of them, as long as it actually goes out.

A schedule that works without souring the relationship:

1. A few days before the due date: a short heads up with the amount and a link to the invoice.
2. On the due date: a polite note that it is due today.
3. 7 days after: a reminder that it is overdue, still friendly.
4. 14 to 21 days after: a firmer note, and a human follow up from whoever owns the account.

The key is that it runs for every invoice, in your name, without anyone remembering to do it. The reminder you forget to send to your biggest client is the one that turns net 30 into net 70.

One invoice per client, not one per workstream

A client with two retainers (say, design and development) plus an extra sprint this month could get three invoices, or one. Finance teams almost always prefer one: one approval, one payment, one line in their system.

A consolidated invoice lists each retainer and each extra as its own line, with one total and one due date. It also makes your own month end simpler, because one client's status is one invoice.

Here is the November 1 invoice for a typical client on net 30:

Line	Amount
Design retainer, November 2026	$3,500.00
Development retainer, November 2026	$4,000.00
Extra design hours, October (6 × $175)	$1,050.00
Total due December 1, 2026	$8,550.00

Bank transfer, card, or bank debit

Clients pay agencies in three ways, and each has a trade-off:

• Bank transfer. The default for larger clients. No card fees, but the money arrives with a reference you have to match against the invoice. Record it against the invoice when it lands so the invoice closes and the reminders stop.
• Card. Fastest, and the easiest for small clients. Card fees on a $8,550 invoice are real money, so many agencies offer card for smaller invoices only.
• Bank debit. The client authorizes you once, and each invoice is collected from their account on the due date. It combines the low fees of a transfer with the certainty of a card. For retainer clients who pay the same amount every month, it is often the best of the three.

Whatever you offer, put every option on the invoice page itself, so the person holding the invoice can pay it in one sitting.

Month end, in one look

If the setup above is in place, month end is a look at a single list: which invoices went out, which are paid, which are overdue and how many days. An aging view (current, 1 to 30 days late, 31 to 60, over 60) tells you where to spend a phone call. If your over 60 column has anything in it, that is the one call to make this week.

yRecurring bills retainers on the day you choose, puts project invoices on the same client, prints your payment terms, sends reminders on the due date and after, and takes card, bank transfer or bank debit through your own accounts. See how it works in retainer billing for agencies.