AI Agency Invoice Template: Setup Fees, Retainers, Usage

Quick answer: An AI agency invoice should separate the work into clear lines: a one-time setup or build fee (or milestone), the monthly retainer for the period, and pass-through usage such as API, model or automation-platform costs shown at cost or with a disclosed markup. Add the service period, deposit credits, payment terms and any tax that applies.

AI automation agencies build chatbots, AI agents, document-processing pipelines and workflow automations for businesses. The billing is more complex than a typical service invoice because three kinds of charges mix on the same document: fixed build work, recurring support and variable usage that depends on how much the client's automations run.

Get the invoice structure right and clients can see exactly what they are paying for each month. Get it wrong and you end up absorbing surprise API bills or arguing over what the retainer covers. This guide sets out a practical template, a fully worked sample invoice and the contract terms that make the invoice easy to defend.

The four charge types on an AI agency invoice

Charge type	When it is billed	How to show it	Common mistake
Setup or build fee	Once, often as deposit plus balance	Project name, deliverable and percentage billed	Burying setup inside the retainer
Milestone payments	When each agreed stage is accepted	Milestone number, name and acceptance date	Billing milestones before acceptance criteria are met
Monthly retainer	Usually in advance each month	Service period and what is included	Undefined scope that grows each month
Usage pass-through	Usually in arrears, after the month ends	Provider, period, units and rate or total	Paying usage yourself without a cap

Setup and build fees

The build fee covers discovery, process mapping, building the automation, prompt and workflow design, testing and handover. Price it as a fixed project fee based on scope rather than as hours, and split it so you are not funding the client's project.

A common pattern is a deposit before work starts and a balance at launch. Issue the deposit as its own deposit invoice and credit it on the final invoice so the client can see the full fee and what remains. For larger builds, break the fee into stages using milestone payments, each tied to clear acceptance criteria such as "chatbot answers the 40 test questions correctly" or "invoice extraction runs on 100 sample documents".

Describe the build line precisely on the invoice:

Customer support AI agent: build and launch, milestone 2 of 2 (50% of $6,000 build fee), accepted 15 Oct 2026.

Monthly retainers

After launch, automations need watching. Connected apps change their APIs, models are updated, prompts drift and error rates creep up. The retainer pays for that care. Bill it in advance for the coming month, and always print the service period on the line.

Write the retainer scope into your statement of work, including:

• Monitoring and fixing failed runs.
• Updates when connected tools change.
• A fixed allowance of change requests or hours per month.
• Monthly reporting on runs, errors and costs.
• Response times for urgent issues.
• Exclusions: new workflows, new integrations and major redesigns, which are quoted separately.

Our guide to retainer invoices covers advance billing and unused-hours policies in more detail. When a client asks for something outside the retainer, use a change order and bill it as its own line.

Usage pass-through for API and LLM costs

AI automations consume metered services: language model API calls billed per token, automation-platform tasks or operations, vector database storage, transcription minutes, phone numbers for voice agents and so on. These costs scale with the client's volume and can jump if a workflow loops or traffic spikes.

You have two options:

1. Client-owned accounts. The client opens accounts with each provider and adds their card. You build and manage the automation; they pay usage directly. This removes cash-flow risk from you and keeps the data relationship with the client.
2. Agency re-billing. You pay providers and re-bill usage. This is simpler for the client but means you carry the cost until they pay.

If you re-bill, show each provider as a separate line with the period and quantity, keep the provider's usage report as backup, and state whether the price is at cost or includes a handling markup. Agree a monthly cap or an alert level, for example notifying the client if usage passes an agreed amount. Our guide on usage-based billing invoices explains metered line items, and reimbursable expenses covers the at-cost approach.

Worked example: a sample AI agency invoice

An illustrative example. A small AI automation agency built a customer support agent for an online retailer. The contract sets a $6,000 build fee (50% deposit already invoiced and paid, 50% on launch), a $1,200 monthly retainer billed in advance, and usage re-billed in arrears at cost plus a 10% handling fee. The figures are hypothetical.

Line item	Qty	Rate	Amount
Support AI agent build: milestone 2 of 2, launch (50% of $6,000)	1	$3,000.00	$3,000.00
Monthly retainer: monitoring and support, 1-30 Nov 2026	1	$1,200.00	$1,200.00
LLM API usage at cost, 1-31 Oct 2026 (per provider report)	1	$184.37	$184.37
Automation platform usage at cost, 1-31 Oct 2026	1	$45.00	$45.00
Usage handling fee, 10% of $229.37	1	$22.94	$22.94

Here is the arithmetic:

• Usage subtotal: $184.37 + $45.00 = $229.37.
• Handling fee: $229.37 x 10% = $22.937, rounded to $22.94.
• Invoice subtotal: $3,000.00 + $1,200.00 + $229.37 + $22.94 = $4,452.31.
• Tax: $0.00 in this example, because the agency's adviser confirmed none applies to this client. Your situation may differ.
• Total due: $4,452.31, payable within 14 days.

Notice that the retainer covers November (in advance) while usage covers October (in arrears). Printing both periods prevents the most common client question. The invoice notes should also reference the statement of work and the deposit already paid, for example "Deposit of $3,000.00 received on invoice AI-2026-014". Because the deposit was billed and paid on its own invoice, it is not deducted again here; the milestone line already bills only the remaining 50%.

To build this in our free invoice generator, add each row as a line item with its description, quantity and rate, put the payment terms and deposit reference in the notes, and download the PDF. The generator applies one tax rate to the invoice as a whole, so if only some lines are taxable in your jurisdiction, split taxable and non-taxable charges into separate invoices or confirm the treatment with an accountant. The agency invoice template gives a clean layout for multi-line service invoices.

Tracking usage month to month

Usage lines are the part of an AI agency invoice most likely to be questioned, because they change every month. A simple tracking routine keeps them defensible:

1. Tag usage by client. Use a separate API key, project or workspace for each client with every provider, so usage reports split cleanly without manual allocation.
2. Export reports at month end. Download each provider's usage report for the calendar month and save it with the invoice number in the file name.
3. Reconcile to your own costs. Check that the figures you re-bill match what the provider actually charged you, including any currency conversion.
4. Compare with last month. A sudden jump often signals a workflow loop, a bot being abused or a prompt change that increased token use. Investigate before you bill, and tell the client what happened.
5. Share a short summary. A few lines in the invoice notes, such as runs completed and cost per run, helps the client see value rather than just cost.

If clients own their provider accounts, you will not re-bill usage at all, but it is still worth including a brief usage summary in your monthly report so the retainer's value stays visible.

Numbering and recurring retainers

Agencies issue several invoice types to the same client: deposits, milestones, monthly retainers and occasional change orders. Use one continuous numbering sequence, optionally with a client prefix, such as AI-2026-014, AI-2026-015 and so on. Our invoice number generator helps you set a consistent format.

The generator creates one invoice at a time and does not send or schedule invoices, so for monthly retainers keep last month's details, update the number, dates, service period and usage lines, and download a fresh PDF. If you prefer automatic recurring billing and card collection, run that in billing software and keep the same line-item structure.

Contract terms that support the invoice

An AI agency invoice is only as clear as the agreement behind it. Make sure your contract or statement of work covers:

• Build fee, deposit percentage and milestone acceptance criteria.
• Retainer amount, billing date, included services and exclusions.
• Usage: who owns provider accounts, at-cost or markup, caps and alerts.
• Payment terms, late fees and what happens to automations if invoices go unpaid.
• Ownership of prompts, workflows and code, and handover on termination.
• Data handling and confidentiality for client data passing through AI providers.

The UK government's guide to invoicing and taking payment from customers lists the details invoices should include and is a useful baseline even outside the UK. If you are coming from a marketing background, our marketing agency invoice template shows a similar retainer-plus-project structure. For pricing the work itself, see our guide to pricing AI-assisted work.

AI agency invoice checklist

• Agency name, address, contact details and logo.
• Client's legal name, billing address and any PO number.
• Unique invoice number and issue date.
• Build or milestone line with the percentage of the total fee being billed.
• Retainer line with the service period.
• Usage lines by provider, with the period and at-cost or markup stated.
• Deposit or prior payments referenced in the notes or amount paid field.
• Tax rate and tax ID if applicable.
• Payment terms, due date and payment instructions.
• Reference to the statement of work or contract.

Common mistakes

• Folding the build into the retainer. It hides the value of the build and leaves you exposed if the client cancels after two months.
• Carrying uncapped usage. A looping workflow can rack up provider charges before anyone notices. Set caps and alerts.
• Hiding the markup. If a line says "at cost", it must be at cost. Show any handling fee separately.
• Missing service periods. Without dates, clients cannot tell whether a retainer or usage line is new or duplicated.
• Vague descriptions. "AI services" invites questions. Name the automation, the milestone and the period.
• Billing milestones early. Invoice only after acceptance criteria are met and documented.
• Guessing tax. Digital services tax rules vary by location; confirm before you set a rate.

Bottom line

A clear AI agency invoice separates one-time build work, recurring support and variable usage, with periods, percentages and markups spelled out. Back it with a statement of work that defines each charge, and clients will see a predictable bill rather than a mystery number.