Guide
Can Claude create invoices?
Claude can already summarize your reports. Drafting a real invoice with line items inside the ledger is a write action, and that depends on the connector, not the model.
Claude can create invoices when its accounting connection exposes a write tool like `create_invoice`. With a custom connector for QuickBooks Online or Xero, Claude drafts the invoice with the right customer, line items, and amounts inside your ledger. Sending the invoice and recording payments are separate, gated actions that wait for your approval.
Key takeaways
- Default accounting connections lean read-only, so Claude can summarize reports but not draft documents in the books.
- A custom connector adds write tools, so Claude drafts invoices with line items against the right customer and accounts.
- Sending an invoice and recording payments are gated steps that run only after you confirm them.
- The connector authenticates as your own accounting login and never gets more access than you already have.
Why can't Claude already create invoices?
Because most accounting connections are read-leaning. The native Xero connector, for example, is read-only: it pulls reports and answers questions but cannot draft an invoice or code a bill. Creating an invoice is a write action, and it needs a connector that exposes a dedicated `create_invoice` tool.
That read layer is still valuable. Claude can walk through a profit and loss, flag overdue receivables, and explain what changed month over month.
But the moment the answer is now invoice them for it, the work bounces back to manual entry unless the connection includes write tools scoped to your books.
What does invoice creation look like in practice?
You describe the work, and Claude drafts the invoice inside the ledger: the right customer, line items with quantities and rates, the correct account and tax treatment, and a due date. In QuickBooks Online or Xero the draft lands where your bookkeeper already works, ready for review before anything is sent.
A typical flow with a custom accounting connector:
- Draft the invoice with line items via
create_invoice. - Add or update the customer record if it does not exist yet.
- Code a related bill or expense to the right account.
- Send the drafted invoice only after you approve it.
Because the draft lives in the real ledger, there is no re-keying between Claude and your accounting software.
Will Claude send invoices or take payments on its own?
No. Drafting and sending are deliberately separate. Sending an invoice puts a document in a customer's inbox, and recording a payment changes your books, so both are gated actions that run only after you confirm them. Claude prepares everything, and you approve the step that makes it real.
Money-adjacent actions always pause
Anything outbound or hard to reverse, like sending an invoice, recording a customer payment, or deleting a record, waits for your explicit confirmation. Drafting can flow inside the conversation; committing to the ledger and the customer does not.
Which accounting tools does this work with?
QuickBooks Online and Xero are the common cases, and both work well with a custom connector: drafting invoices and bills, adding contacts, recording expenses, and posting entries for your approval. The same pattern extends to other ledgers and even in-house billing systems, as long as there is an API to build against.
Both connectors authenticate through OAuth as your own accounting user, so Claude inherits your role limits and company file access, nothing more.
If your billing runs through a system with no directory listing at all, that is exactly what a custom build is for.