How Kobi Omenaka Uses Claude Code to Send Invoices Faster

In a recent LinkedIn post, Kobi Omenaka discusses how using Claude Code to prepare invoices has changed the pace of his administrative work. This article reports on Omenaka’s post and examines the workflow he describes; it is not written by Omenaka.

“My invoices go out the day I’m asked now, not next month 🧾”

Omenaka says invoicing used to involve searching emails for client details and a purchase order number, then entering the information into FreeAgent. He estimates that process took about an hour per invoice, leading him to delay the work and, in turn, receive payments later. His account highlights a familiar small-business problem: routine paperwork can become a bottleneck when it requires repeated manual steps.

A connected workflow for invoice preparation

According to Omenaka, Claude Code now handles much of the information gathering and draft creation. His setup connects Gmail to Claude and links an accounting application. He notes that Xero and QuickBooks offer connectors, while FreeAgent requires a small app created through its developer site.

Omenaka describes asking the tool to locate a recent order email, verify whether the customer is already listed in FreeAgent, add the contact if needed, and prepare an invoice. The goal, as he presents it, is to give the assistant a complete task rather than manually transfer details between email and accounting software.

“find the most recent order email from BFI, check they’re a contact in FreeAgent, set them up if not, create the invoice and send me a link to the draft.”

The example also shows why the result is a draft rather than an automatically sent invoice. Omenaka says he checks that the purchase order number and email addresses are correct, then sends the invoice himself. The human review remains part of the workflow, especially where an incorrect detail could affect billing or reach the wrong recipient.

Less delay, with a review step

Omenaka says the instruction takes him about 30 seconds to give, compared with the hour he previously spent assembling the information. His post frames the benefit as both saved time and a quicker path to sending invoices. Earlier billing may help reduce delays in the payment process, though the post does not quantify any change in how quickly customers pay.

What the post leaves for the operator

Omenaka’s approach depends on configuring account access and checking the draft before it goes out. In that sense, his example is not simply about automating invoicing; it is about delegating information gathering and preparation while retaining a final human decision.

“Check the draft. Is the PO number in? Are the emails right?”

Omenaka closes by saying he plans to share the prompts and setup kit, and asks readers which administrative task they tend to postpone. His post offers a specific illustration of how AI tools might streamline a small-business routine, while leaving accuracy checks and the decision to send with the user.