Billing Management

Automate invoicing with AI: what works today and what doesn't

By Darren Clark · 12 min read

Illustration: A pair of hands passing a single sealed envelope to a plain mechanical arm that holds it without gripping, bold flat silhouette

AI invoicing is software that uses a language model to draft, check or send invoices from the work you've already done, instead of you building each one by hand. Today it's good at drafting from data you already have and answering questions about it. It's not good at deciding what you should charge, and it shouldn't send money-moving actions without a person's yes.

That's the honest summary. One agency owner I talked to put his own feeling about the whole category as "Dear God, AI, just enough." I think that's the right test. You want enough AI to remove the typing, and not one bit more than you can check.

This guide covers what AI invoicing does well, what it doesn't, whether ChatGPT can do it, and how to automate invoicing in five steps. It's written for a small agency owner who bills on retainers, milestones or hours and wants the invoices to stop eating the first week of every month.

What is AI invoicing?

AI invoicing is the use of a language model, inside or alongside invoicing software, to produce or manage invoices. It reads structured data such as hours, milestones and rates, or plain-English instructions, and turns it into a draft invoice, a reminder or an answer. A person approves what matters.

Three things get called "AI invoicing", and they are not the same:

  • A writing helper. A button that drafts the wording of an email or an invoice description. Useful, small, and it doesn't touch your numbers.
  • An assistant that answers questions. You ask "who owes me money?" in plain English and it answers from your real billing data.
  • An operator. It takes actions inside the system, such as drafting an invoice from a closed milestone, and queues them for approval.

Most of the confusion on this subject comes from vendors using one word for all three. When you assess a tool, ask which of the three it is.

What does AI invoicing actually do today?

Today AI invoicing reliably does four things: it drafts invoices from work that's already recorded, it answers questions about your billing data in plain English, it writes and schedules reminders, and it takes actions you've asked for inside limits you set. It works because it's reading data that already exists, not guessing.

It drafts invoices from the work

The strongest use is drafting the invoice from the thing that triggered it. A milestone is marked complete, a week ends, a retainer cycle comes round. The invoice is drafted at your rates with the work attached, and you review it.

In Handl, the invoice automation page lists the triggers: a project starting, a milestone starting or completing, a date, or on demand. For hourly work, tracked time syncs from Harvest, Toggl, Clockify or Hubstaff and becomes time-and-materials invoice lines, so the invoice reflects the hours that were worked rather than what you remember.

It answers questions about your billing

You ask, in plain English, "which invoices are due this week?" or "who owes me money?" and the assistant answers from your real data. This is less glamorous than drafting and probably saves more time, because the alternative is building a report to find out.

It writes and schedules reminders

Overdue invoices followed up on a schedule, with the tone getting firmer as time passes. The writing is the easy part. What the system adds is that it happens on a schedule, the same for every client, without you deciding to be the bad guy.

It takes actions inside limits you set

This is the part that separates an operator from a chatbot. Handl's AI agent can create projects, set up milestones, draft and send invoices, record payments, manage clients and pull reports, using well over a hundred tools. Anything that moves money goes through a proposal queue first: the agent drafts, you get an approve or reject card, in the app or in Slack.

Illustration: a long conveyor of identical sheets passing under a single small lamp, one sheet lifted toward the light, bold flat graphic

What doesn't AI invoicing do?

AI invoicing doesn't decide your prices, doesn't know about work that was never recorded, and shouldn't send invoices without a person's approval until you've seen it get it right. It can't invent hours you didn't track, and it can't tell a client relationship needs a phone call instead of an email.

Being specific about the limits is more useful than being vague about the strengths:

  • It can't bill for time you never logged. If the hours were never tracked, there's nothing to draft from. The tool is only as good as the records it reads.
  • It doesn't set your rates or decide scope. Those are commercial decisions. It applies the rates you've set.
  • It shouldn't send on day one. Automatic sending is off by default in Handl. Milestone invoices are drafted for you to confirm and send, and recurring invoices can send themselves only once you switch that on.
  • It doesn't replace your accounting system. Handl pushes invoices to QuickBooks or Xero, so your books stay where your accountant expects them. The invoices are the output, not the ledger.
  • It can't charge a card nobody saved. Clients are charged automatically only if they opt in to auto-pay. Otherwise they get a pay-now link.
  • It doesn't remove your judgment. A client who's gone quiet after a dispute doesn't need a scheduled reminder. They need you.

Can I use AI to generate invoices?

Yes. You can use AI to generate invoices, either by asking a general assistant to write one from details you give it, or by using billing software that drafts invoices from tracked work. The second is more reliable, because the numbers come from records instead of from a prompt.

The difference is where the facts come from. When you ask a general assistant to "make an invoice for 40 hours at $95", it formats what you told it. When billing software drafts from your project, the hours, the rates and the milestone value are already in the system. The first saves you typing. The second removes the step where a wrong number could get in.

Can ChatGPT generate an invoice?

Yes, ChatGPT can generate an invoice, as text or a layout you paste into a document. It does that well. What it can't do is know which work you did, send the invoice, collect the payment, remind the client, or keep a record. It formats an invoice. It doesn't run your invoicing.

It's a reasonable one-off tool. If you need a single invoice and you have the details to hand, it'll write you a clean one. The trouble starts on the second month, when you need to remember what you billed last time, the numbers need to match what you tracked, and someone needs to chase it.

If you want a template to fill in yourself, there's a free invoice template and an invoice tracker. Both are spreadsheets and neither involves AI.

There is a way to get both: connect an AI assistant to a system that holds the real data. That's what MCP is for, and it's covered below.

Is there a way to automate invoices?

Yes. You automate invoices by defining what triggers each one, connecting the tools that hold the work, and letting software draft them to your rules. The five steps below take a small agency from manual invoicing to drafted invoices that you only have to review.

How to automate invoicing: five steps

Step 1. List your billing types. Write down how each client is billed: retainer, milestone, hourly, or a mix. Each type has a different trigger, so each needs a different rule. Don't try to use one setup for all of them.

Step 2. Name the trigger for each. A retainer is triggered by a date. A milestone is triggered by completion. Hourly work is triggered by the end of a period. If you can't name the trigger, the invoice will depend on you remembering, which is exactly the thing you're trying to remove.

Step 3. Connect the sources of truth. The invoice should read from where the work is recorded. In Handl that means a project tool (Jira, Asana, Monday, ClickUp or Linear) for milestones and a time tracker (Harvest, Toggl, Clockify or Hubstaff) for hours.

Step 4. Set the approval rules. Decide what the system may do alone and what needs a yes. Handl's autonomy settings are configurable per action. The sensible start is suggest-only: the system drafts everything and you approve each send. Loosen it once you've seen it get a few cycles right. Hard limits such as amount caps stay in place whatever you choose.

Step 5. Review for a month, then loosen. For the first cycle, check every draft against what you'd have done by hand. Fix the rules where they differ. After a month or two, the drafts will be right often enough that approval is a glance.

Illustration: five stepping stones across a stream, the last one lit, bold flat graphic

What's the difference between invoice automation and AI invoicing?

Invoice automation is rule-based: when X happens, create invoice Y. AI invoicing adds a language model that handles the parts rules can't, such as answering questions in plain English, or taking a request like "bill the Acme milestone" and acting on it. Good tools use both.

Rules are predictable, which is what you want for money. A language model is flexible, which is what you want for asking questions and for the awkward cases. The sensible design uses rules for what must always happen the same way, and the model for the interface and the exceptions.

That matches how Handl works. The triggers that draft invoices are rules you define. The AI agent is how you talk to the system, whether that's in the app, in Slack or from an outside AI tool, and it acts inside the same limits either way.

Does it have MCP or an API?

Handl has an MCP server. MCP, the Model Context Protocol, is an open standard that lets AI assistants such as Claude, ChatGPT or Cursor call tools in another system. Point your assistant at Handl and it can read your billing data and act on it, inside the same limits as the app.

This is the answer to a question one owner asked me: "does it have MCP, or at the very least an API?" For MCP, yes. Through it, an outside assistant can query projects, invoices, clients, milestones and payments, pull aging and cash-flow reports, and draft and send invoices. It can also list and approve the agent's proposals without leaving the tool.

The guardrails carry over. Every call runs under your autonomy settings and your role permissions. An assistant acting through MCP can't do anything you couldn't, and anything that moves money still lands in the proposal queue for a human yes. Access is scoped to your agency. Details are on the MCP page.

Two things to know about the plan: the AI agent in the app and in Slack is in every Handl plan from $29 a month, while connecting outside assistants over MCP is on the Team plan ($99 a month) and up.

I'm deliberately not making claims on this page about a separate public API. MCP is what's documented and what I can stand behind.

How do you choose an AI invoicing tool?

Choose by what the tool acts on, what it lets you control, and where it puts the result. Ask five questions: where do the invoices get their numbers from, what can it do without asking me, where does the invoice end up, does it work with my existing tools, and what does it cost?

  1. Where do the numbers come from? Tracked time, milestones and set rates are good. A prompt box is not.
  2. What can it do without asking? You want per-action control, and sending off by default.
  3. Where does the invoice end up? In your accounting system, with the same number. Handl creates the invoice in QuickBooks or Xero with the same invoice number, dates, currency and line items.
  4. Does it fit what I already use? Your project tool, time tracker, accounting software and AI assistant.
  5. What does it cost? Look for a flat plan price rather than per-message charges. Handl's is by plan, from $29 a month, with a 7-day free trial.

What does this look like in practice?

In practice, a billing cycle looks like this. Work gets done and recorded in the tools your team already uses. The triggers fire, and drafts appear. You open the drafts list, check each one, and send. Questions about money are answered by asking.

Take a small agency with a retainer client, a milestone project and an hourly client. On the first of the month the retainer is drafted. When the last ticket on a milestone closes in Linear, the milestone invoice is drafted. At the end of the week, tracked hours become an hourly draft. You approve three drafts instead of building three invoices. If a client asks "what's this charge?", the portal answers from the project history before it reaches your inbox.

That's the "just enough" version. The system does the typing and the remembering. You do the checking and the deciding. Connect your project and time tools, then ask Handl which invoices are due this week or who owes you money. The AI agent page walks through the three ways to reach it, and the invoice automation page shows the triggers.

FAQ

Will AI send invoices without me knowing?

Not unless you set it up that way. In Handl, automatic sending is off by default, and anything that moves money goes through an approval queue until you've chosen to loosen it. Recurring invoices can send themselves only once you switch that on.

Is it safe to give an AI access to my billing data?

Ask the vendor what it can do and under what limits. In Handl's case, every action runs under your autonomy settings and role permissions, and access is scoped to your agency. That is a design choice worth asking about in any tool.

Do I still need QuickBooks or Xero?

Yes. Handl isn't your accounting system. It drafts and sends the invoice and pushes it to QuickBooks or Xero, where your books, bank feeds and tax work stay.

Is AI invoicing worth it for a very small agency?

If you invoice a handful of clients a month on one simple retainer, a template and a calendar reminder is probably enough. It starts to pay once you have mixed billing types, time from several tools, or any month where an invoice went out late because you forgot.

Darren Clark ran digital agencies for over 20 years before building Handl.

← All resources