There are three ways to get QuickBooks Online data into Claude: the official QuickBooks connector (read and write, and it can send invoices and overdue reminders, currently for United States organisations), the Intuit MCP server (free, runs locally, around 145 tools including proper aged receivables reports), and a CSV export from the QuickBooks reports screen (no connection at all, works everywhere). Once connected, a skill can produce aged receivables, DSO, late fee schedules, statements and chase drafts.
QuickBooks is ahead of Xero on one thing that matters for receivables: it can actually send. It is behind on nothing much else.
Our receivables skill for QuickBooks, in the open. It reads all three routes below: the QuickBooks connector, the Intuit MCP server, or a plain CSV export. Aged receivables, DSO, late fee schedules, statements and chase briefs, every figure computed by a bundled script rather than by the model.
Get the skill on GitHubWorks in Claude, Claude Code, Codex and Cursor. Setup for each route is in the repository.
Details below are correct as at August 2026. Intuit has shipped quickly here, so check current regional availability on Intuit's developer site before you build a process around it.
| Route | Read | Write | Send email | Best for |
|---|---|---|---|---|
| CSV export | Yes | No | No | Anyone, any country, many clients |
| QuickBooks connector | Yes | Yes | Yes, US organisations | Fastest setup, no developer account |
| Intuit MCP server | Yes | Yes | No | Aged receivables reports, PDFs, detail work |
Start here if you are unsure, or if you work across a book of clients.
This is the only route that handles many companies in one run. Every connector holds a single company at a time, so a bookkeeper with twenty clients exports once per client into one folder each and processes them together.
It also keeps the data scope small. You are handing over one receivables report rather than granting access to the entire ledger, which is a much easier conversation with a client who is cautious about AI.
Intuit published an official connector, and in July 2026 added invoicing actions to it. You enable it in your AI app's connector settings and sign in with your QuickBooks login. There is no developer account and no app registration.
It reads your data, creates and updates invoices, and it can send invoices and reminders on overdue invoices. That send capability is currently limited to United States organisations, and payment links require QuickBooks Payments approval.
If you are a US business, this is the shortest route to a working setup by some distance.
Intuit publishes an official MCP server that runs on your machine. It is free and exposes around 145 tools across 29 entities.
For receivables work it is the strongest option on either platform, because it includes real aged receivables reports rather than making you assemble the ageing yourself. It also returns invoice PDFs.
Setup involves registering a free app on Intuit's developer site and a one-time browser sign-in. Two things to plan for. Production OAuth needs a public HTTPS redirect, which is a small hurdle on a local machine. And the refresh token expires after about 100 days, so put a reminder in the calendar or you will find the connection dead at the worst moment.
While you are only reading data, set the write-disable environment flags. There is no reason to leave write access on for a reporting workflow.
Statements do not exist in the API. There is no statement endpoint, so a skill that offers customer statements is building them itself from open invoices and payments. That is fine, and worth knowing when you compare tools.
The local server cannot send. Sending is a connector capability, not an MCP one. If you are running the local server, chase emails come out as drafts.
Nothing triggers. No connection fires when an invoice goes overdue. Every run starts because a person asked for it.
One company at a time. As with every connector on every platform.
Do not let the model add up your ledger
Language models are unreliable at totalling a hundred numbers, and the failure is quiet: the figure looks plausible and is wrong by a few hundred dollars. Any skill you trust with a client file must compute totals, ageing buckets and fees in a script, then show the workings so the numbers can be checked.
Our skill for this is open source under the MIT licence: accounts-receivable-skills on GitHub. It reads all three routes above, computes every figure in a bundled Python script with nothing to install, and ships 59 tests against a fixture ledger with hand-computed answers. See also the guide to Claude Skills for accountants and the parallel Xero setup guide.
QuickBooks lets you update an existing invoice, so a fee can go on the original document or onto a separate invoice, whichever your process prefers. Xero locks approved invoices, which forces a separate fee invoice.
A separate invoice is still usually the better choice. The customer can query, pay or have the fee credited without touching the debt underneath it, and your ageing stays clean.
Late fees work as leverage. An invoice that grows moves up the payment run, and the reminder that a fee applies does more work than the fee ever collects. The condition is consistency: a fee you announce and never charge teaches customers your terms are optional. The enforceable rate is the one written into your contract, and caps differ by state, so confirm your terms before quoting a figure.
Even at its best, with a US organisation on the connector that can send, the sequence still starts with a person. Somebody opens a session, asks for the overdue list, reviews the drafts, and approves the send.
Miss a week and the whole ladder slips a week. The invoice that lapsed on Saturday sits there, no fee applied, no reminder sent, until someone remembers.
💡 Paidnice insight
We publish an AI skill and we still run the chasing through automation, because they are different jobs. The skill gives you judgement when you ask for it. Automation applies the same policy to every invoice on the day it lapses, which is where the result comes from. Customers cut their average wait for payment in half within 30 days, and none of that depends on someone opening the ledger on a Monday.
If you want the policy to run itself, that is what Paidnice for QuickBooks does: reminders on schedule, late fees applied under your own rules, statements without a trigger, and escalation that happens whether or not anyone was at the desk.
Yes. Intuit publishes both a connector you enable in your AI app's settings and a free local MCP server on GitHub. The connector needs no developer account; the MCP server gives deeper reporting tools.
Through the connector, yes, currently for United States organisations. Through the local MCP server, no. Outside the US the practical answer is drafts, or software that connects to QuickBooks directly.
No. The server and the developer app are free. The cost is setup time and remembering that the refresh token expires after roughly 100 days.
Not from the API, which has no statement endpoint. A well-built skill assembles the statement itself from open invoices and payments and renders it as a printable document.
Set the write-disable flags if you only need reporting, and treat everything drafted as a draft. For the tightest scope, export the A/R Aging Detail report and give the skill that one file instead of ledger access.
Paidnice takes the pain out of getting paid for thousands of businesses using Xero and QuickBooks.
Try it Now - It's FreeNo card required.
Optimize your cash flow with our suite of financial tools designed for AR professionals. Calculate DSO, aging analysis, late fees, and more.
Request an AI summary of Paidnice
