Virtual Assistant Invoice Template: What Belongs on It When You Bill by Retainer

A virtual assistant invoice template is the first thing most VAs download and the first thing they outgrow. The free ones are built for a freelancer who does a job and sends a bill. You do something different. You sell a block of hours every month, and the invoice has to explain what happened to them.

Search for one and you get a dozen near-identical results: logo at the top, a table with description, quantity, rate and total, a payment terms line at the bottom. That layout is fine for a one-off project. It says almost nothing useful about a retainer, which is where the disputes start.

What a retainer invoice has to say

Take a client on a 20-hour monthly retainer at $35 an hour. The invoice for $700 looks complete. Then the client asks whether you actually used 20 hours, and you either know the answer or you don't. If the invoice only says "Virtual assistant services, 20 hrs," you are asking them to trust you. Most will. The ones who don't will ask in month five, when the number looks high to them for reasons you can't reconstruct.

So the first thing the template needs is a breakdown, not a total. Hours by category works better than hours by task. "Inbox management, 6.5 hrs. Calendar and travel, 4 hrs. Research, 5.5 hrs. Bookkeeping entry, 4 hrs." Four lines that add up to 20. A client can read that in ten seconds and decide it looks right.

Second, it needs the billing period written out as dates, not just "October." If your month runs the 15th to the 14th because that is when the client signed, say so. Ambiguity about periods is how work from the 14th ends up on two invoices or none.

The fields most templates leave out

Hours included versus hours used. A line that reads "Retainer: 20 hrs included, 22.5 hrs used" does a lot of work. It tells the client they went over before the overage line shows up, which means the overage line is not a surprise.

Overage rate, stated separately. If you charge $35 for retainer hours and $45 for anything beyond them, put both on the invoice. Don't blend them into one average. The first time a client sees a blended rate they will do the math and decide you are inconsistent.

Rollover or expiry. If unused hours do not carry over, the invoice should say how many expired. "3.5 hrs unused, not carried forward per agreement" feels blunt, but it is a lot less awkward than explaining the policy for the first time in month three. We covered the policy side of this in the post on rollover hours. The invoice is where the policy gets applied.

Subcontractor work. If another VA on your team did eight of those hours, the client usually does not need to know who. They do need the hours to be accounted for. Keep a clean internal record that ties each invoiced hour to whoever did it, because you will need it for paying your sub anyway.

A due date, and a late fee you will actually apply. "Net 15" is a normal VA term. Pair it with a late fee only if you intend to charge it. An unenforced late fee teaches clients that the due date is a suggestion.

Where a static template starts to hurt

A spreadsheet or a Word file works for one client. It works less well at three. At five it becomes a part-time job you don't bill for.

The failure is not the template. It is where the numbers come from. You track time somewhere, usually a timer app or a notes file, then copy totals into the template by hand. Every copy is a chance to misread a total. Every month you reopen last month's file, change the dates, and hope you caught every field. At some point you invoice a client with the previous client's retainer rate still sitting in a cell. That is a bad email to write.

The other cost is timing. When invoicing is a manual chore, it slips. The 1st becomes the 4th, then the 8th. Clients pay on a lag from receipt, so every day you wait pushes your cash back by the same amount. If you have ten days of slippage across four clients, you are floating real money for no reason.

A working template, in prose

If you are staying with a manual template for now, here is the structure that holds up. Header with your business name, the client's name, invoice number and issue date. Billing period as a date range. A summary block: hours included, hours used, overage hours, expired hours. Then the category breakdown. Then the amounts: retainer fee, overage charges, any reimbursable expenses listed separately. Then payment terms, due date, and how to pay.

Keep it to one page. If a client has to scroll, they stop reading the middle, and the middle is where the hours are.

Number your invoices in a sequence that makes sense to you and stick with it. Some VAs prefix with a client code, like ACME-2026-10. It makes searching your own records painless, and it makes your bookkeeper's life easier at tax time.

What to automate first

If you are going to automate one piece, make it the link between logged time and the invoice. The template layout is a one-time decision. The hours are the part that changes monthly and the part that is easiest to get wrong. Anything that pulls the totals straight from your time entries removes the copy step, and the copy step is where most errors and most late invoices come from.

Second, automate the recurrence. A retainer is the same invoice every month with different hours. Generating it on a schedule, with the right client and the right rate, means the only thing you review is the breakdown.

Neither of those needs a big system. They do need the time entries and the invoice to live in the same place.

One more thing worth putting on the invoice

A single line of plain text at the bottom: "Questions about any line item, reply to this email." It sounds trivial. It tells the client that asking is welcome and expected, which makes them less likely to sit on a question for two weeks and then mention it alongside a payment delay.

If you are tired of rebuilding the same document every month, FocalVA's tools for virtual assistants tie logged hours to retainer invoices so the breakdown writes itself. It will not fix an unclear agreement, but it will stop the arithmetic from being the problem.