Published by CXJ Labs, an automation company. Not independent. Read our disclosure.
The Automation Index

Can invoice creation and sending be automated?

Mostly automatable: 83% of task time

The answer

Mostly. Creating the invoice, applying tax and terms, sending it to the right contact and recording its status are almost fully automatable once the deal or job holds the right data. In our model about 85% of invoicing time can go to software. What stays human is billing queries, disputes and unusual work that does not fit a rule.

The tasks, and how much of each is automatable today

Six tasks make up invoicing. Creating the invoice, applying tax and terms, sending it and updating the CRM are 90 to 100% automatable. Checking what is billable is about 80% automatable when deals and milestones are tracked. Handling billing queries and disputes is mostly human, because it is a conversation about money.

TaskActivity typeMin / weekAutomatable
Check what is billable this weekWon deals, ticked milestones and retainer dates are queryable. Variable work billed on judgement, such as extra hours, still needs a person.Collecting data
base rate 64%		9080%
Create the invoice in accounting softwareLine items, amounts and customer come straight from the deal. The 5% left is one-off custom invoices.Processing data
base rate 69%		12595%
Apply the right tax, currency and payment termsStored on the customer record and applied by rule. New countries or tax changes need a person to set the rule once.Processing data
base rate 69%		3090%
Send to the right billing contact with any PO numberBilling contact and PO live on the deal. Missing POs are flagged before sending rather than after rejection.Processing data
base rate 69%		4095%
Record invoice status in the CRMWritten back automatically when the invoice is created, sent and paid.Processing data
base rate 69%		25100%
Answer billing queries and disputesAI can answer 'please resend' and 'what is this for'. Disputes about scope or price need the person who owns the relationship.Interacting with people
base rate 20%		4530%
Whole process35583%

Base rates are McKinsey Global Institute's technical automation potential for each activity type. The share for each task is our adjusted estimate. Method.

Hours saved per week

For a services business sending about 25 invoices a week, invoicing takes about 6 hours of a bookkeeper's or owner's week by hand. Automating the tasks above returns about 5 hours a week, roughly 240 hours a year. The time left goes on queries and disputes, which deserve a person's attention.

Modelled on: A services business billing about 25 invoices a week across one-off projects, milestones and monthly retainers, with the owner and a part-time bookkeeper sharing the work.

  • 25 invoices a week, each taking about 5 minutes to create by hand.
  • Deals in the CRM hold the price, products and billing contact.
  • Some customers need a purchase order number or a specific billing address.
  • Billing queries take about 45 minutes a week to answer.

6 hours a week by hand, 5back with automation. Formula: the sum of each task's minutes multiplied by its automatable share, divided by 60, rounded to the nearest half hour.

Tools that do the job

You need a source that says what to bill, accounting software that issues the invoice, and a connector between them. HubSpot or Pipedrive hold the deal. Xero or QuickBooks create and send the invoice. Stripe handles card payment links. n8n, Make or Zapier move the data and write status back.

Xero
Creates, numbers and sends the invoice; tracks when it is viewed and paid.
QuickBooks
Alternative accounting system with the same invoicing API.
HubSpot
Holds the won deal, line items and billing contact that the invoice is built from.
Stripe
Adds a card payment link to each invoice so customers can pay immediately.
n8n
Watches for billable events, builds the invoice through the accounting API and writes status back.

A simple workflow

The workflow starts when work becomes billable: a deal marked won, a milestone ticked or a month ending on a retainer. It builds the invoice from the deal's line items, applies the customer's tax and terms, sends it from the accounting system with a payment link, and writes the invoice number and status back to the CRM.

  1. TriggerA deal is marked won, a milestone is ticked, or a retainer's billing date arrives.
  2. ValidateCheck the deal has line items, a billing contact and any required PO. If not, ask the deal owner in Slack before going further.
  3. CreateCreate the invoice in the accounting system with the customer's tax, currency and terms.
  4. SendSend from the accounting system with a card payment link, copying the billing contact on the deal.
  5. LogWrite the invoice number, amount and status back to the deal, and update it again when paid.

Keep these human

  • Billing disputes. A disagreement about scope or price is a relationship conversation, not an admin task.
  • Deciding what to bill for variable or out-of-scope work.

Where it goes wrong

  • Incomplete deals. Invoices built from deals missing a PO or billing contact get rejected and delay payment. Validate before creating, not after.
  • Duplicate invoices. A deal moved back and forth between stages can trigger two invoices. Check for an existing invoice on the deal first.
  • Wrong contact. Invoices sent to the buyer instead of accounts payable sit unread. Store a separate billing contact.

What most guides miss

Most invoicing guides start in the accounting software. The faster fix is upstream: make the CRM deal hold everything the invoice needs, and validate it when the deal is won. Missing purchase order numbers and wrong billing contacts cause more late payments than slow invoicing, and they are cheapest to catch before the invoice exists.

The evidence