Two invoicing systems moved into the chat window
On 17 August, Holdings launched invoicing that runs inside Claude, ChatGPT and Cursor. You ask in the conversation, the invoice goes out, the client pays by card or ACH through Stripe, and you can ask in the same thread whether it has been paid. It costs nothing. CEO Jason Garcia explained why: the company earns a margin on payments collected rather than on a subscription, so it can give invoicing away. Full double-entry accounting is a $25 a month add-on.
Two days later, on 19 August, HoneyBook opened HoneyBook MCP. HoneyBook is a client management system for freelancers, mostly photographers, designers and event producers, and its connector is available as a community-reviewed connector in Claude. The agent can open and update projects and leads, add notes to a client record, produce and send invoices and contracts from the user's saved templates, and issue a standalone payment request. HoneyBook runs each request in an isolated environment, restricts outbound access to HoneyBook only, and never exposes credentials to the model.
Two launches in one week, on the same protocol, aimed at the same audience. That is no longer a coincidence.
What changed for the business owner
Until now the AI sat next to the invoicing system. It drafted the message to the client, and the owner copied it into another screen, filled in a form, and hit send. MCP deletes the second screen. The action happens from the conversation.
The difference is small across one invoice and large across thirty. A one-person business does not put off issuing an invoice because it is hard. It puts it off because it is one more thing to open at the end of the day. Shorten the distance between deciding and doing, and invoices go out earlier, and the money arrives earlier.
This is also the third time this month the same thing has happened. QuickBooks shipped a collections agent, and Holdings and HoneyBook opened their own actions to an outside agent. The market has moved from adding an AI feature to a product to handing an agent the keys to the product.
Where it breaks in Israel
Neither system produces an Israeli tax invoice. There is no allocation number from the Tax Authority on it, and it is not built to the structure required here. Above 5,000 shekels before VAT your client cannot deduct input VAT against a document like that, and anyone running their books this way finds out at their accountant rather than in the chat.
That leaves an odd situation. The whole chain is automated, from drafting to collection, and it stops exactly at the point where the document has to be legal. An Israeli freelancer working with overseas clients can use this for collection and payment tracking and still issue the invoice itself in an Israeli system. Two places instead of one, which is precisely what this was supposed to save.
Worth checking before you connect it
An agent that can send an invoice can send it to the wrong client. A standalone payment request that went out twice is an awkward phone call, not a bug. Start with read-only access, watch for a week what the agent proposes to do, and only then let it send. HoneyBook gives granular control over what the model can see, and that is the place to use it.
The direction is clear enough, and it will reach the Israeli tools too. The only question is who connects an MCP server first to a system that already knows how to request an allocation number.