How to Use Claude Cowork for Accounting and Bookkeeping

You open Claude, and there's a folder instead of a chat window. Your invoices, your QuickBooks link, last week's bank export: all sitting there. Claude reads through them and gets to work, one task at a time. You don't have to type out every step. That's Claude Cowork. If the only Claude you've used is the chat box, this guide is for you. It covers how to use Claude Cowork for accounting and bookkeeping, from first setup to daily workflows.

We already covered the chat-and-Projects version of this in How to Use Claude for Bookkeeping. That guide is still useful, but it's built around pasting context into a conversation. Claude Cowork bookkeeping works differently. Claude operates inside a folder you point it at, with tool access and the ability to run several steps on its own. This guide is Cowork-specific and current as of the July 2026 rollout.

This guide shows you how to use Claude Cowork for real bookkeeping work. You get the exact 3-step setup, how to install the Small Business plugin, and how to connect QuickBooks. You get more than ten Cowork workflows with prompts you can copy and paste today. And you get an honest look at where Cowork stops being enough once you manage more than your own books.

It also covers ground shorter setup guides skip. Projects and Instructions, for work you come back to weekly. The separate Finance plugin, built for firms. Exactly where a Cowork session runs, and what that means for client data. Computer use, as a narrower add-on capability. And a rollout path, from your own books to a small firm running Team-plan controls.

What is Claude Cowork, and how do you set it up for accounting or bookkeeping?

Claude Cowork is a working-session mode where Claude runs multi-step tasks on its own. Instead of one chat thread, Claude works inside a folder you choose, with access to your connected tools, until the task is done. Cowork moved from research preview (starting January 12, 2026) to general availability on all paid plans in April 2026. Setup takes three steps: pick Cowork in the mode picker, run /setup-cowork, then choose "Work in a folder." Add the Small Business plugin (Pro, Max, or Team) and you get six money-management skills on top, from a weekly brief to quarterly tax prep. Cowork runs on the Claude desktop app for macOS and Windows on every paid plan. It also runs on a web and mobile beta that started rolling out July 7, 2026.

Key Takeaways

• Setup is 3 steps, no code: pick Cowork in the mode picker, run /setup-cowork, then click "Work in a folder."
• The Small Business plugin now covers six money skills, not four: /monday-brief, /month-heads-up, /close-month, /price-check, /plan-payroll, and /tax-prep. Desktop app only, Pro, Max, or Team plans.
• QuickBooks connects free, US only: the connector pulls reports, compares your numbers to your industry, and makes invoices and estimates. No QBO plan required.
• You sign off on anything sensitive first: Cowork asks before it sends, posts, or pays.
• It runs while you're away: scheduled tasks fire with no device online.
• Projects carry memory across sessions; a bare folder doesn't: set up a Project if you want Cowork to remember last month's fixes. A one-off "Work in a folder" session won't.
• Cowork sessions run remotely, in an isolated environment, not on your machine: worth knowing before you connect client files.
• It's a workflow tool, not a system of record: one folder, one session at a time. It's not built to run 10-plus client books with an audit trail.

What Cowork actually is (and how it's different from Chat or Projects)

Claude Chat and Projects are conversations. You paste in context, ask questions, and Claude answers from the thread. Cowork works differently. It's a session tied to a folder, with plugins and connected tools, that can run several steps in a row. You don't have to spell out each one.

In practice: asking "what does a good month-end close checklist look like" is Chat. Running /close-month and having Claude walk your QuickBooks data against that checklist, that's Cowork. For the chat-and-Projects version, six prompts and no Cowork surface, see How to Use Claude for Bookkeeping. Want the wider map first? Our pillars on Claude for bookkeeping and Claude for accounting cover every way to put Claude on your books. This guide covers what Cowork adds.

Cowork runs on the same engine as Claude Code, Anthropic's developer tool. Every task walks through five visible steps: Understand, Plan, Execute, Verify, Deliver. Claude asks clarifying questions first. It shows its plan in the sidebar before it starts. It works across your files and connected tools. It checks its own output. Then it hands you finished files with a summary. You can interrupt and redirect at any point. And Claude asks approval before anything risky.

That five-step loop is also the fastest way to decide which mode fits a task. A goal that's still forming, or a question you want to think through in a few turns, is Chat. A clear deliverable, or a job that touches multiple files or sources, is Cowork. If the output you want is text to read, stay in Chat. If the output you want is a finished file or an action taken, hand it to Cowork.

Put in bookkeeping terms: "how do I categorize a mixed personal-business charge" is a Chat question. You mainly want to reason through the answer. "Categorize every uncoded QuickBooks transaction from the last 30 days and flag anything over $500 for me" is a Cowork task. It's multi-step and multi-file. It ends with something done, not just something explained. Say a /close-month run turns up an unexpected number mid-task. You can redirect before it finishes. No need to wait for the whole result and start over.

One more surface worth naming: Claude Code is Anthropic's tool for developers. It's not covered here. Cowork is built for a folder full of business files, not code.

Set up Cowork for bookkeeping in 3 steps

Step 1: pick Cowork in the mode picker

Open Claude on desktop and find the mode picker. It's the same spot where you'd pick a model or a chat mode. Select Cowork. That switches you from a single chat into a working session.

Step 2: run /setup-cowork

Type /setup-cowork and follow the guided setup. This step sets your working folder and Cowork's starting permissions: what it can read and touch before you approve anything else.

Step 3: "Work in a folder"

Click Work in a folder and point Cowork at the folder you want it in. Your bookkeeping folder. Your client folder. Wherever your files live. This is the scope Cowork works in for the rest of the session, and it's the guardrail we come back to later. Cowork only reads and acts inside the folder you set here.

Platforms: Cowork runs on the desktop app (macOS and Windows) on every paid plan. A web and mobile beta started rolling out on July 7, 2026, starting with the Max plan. If you're not on desktop yet, check whether your plan has beta access first.

Work in a folder vs. a Project: which to use

A "Work in a folder" session is scoped to that one session. Close it and start a new task tomorrow, and Cowork starts from zero again. No memory of what you fixed. No saved instructions. A Project is different. It's a dedicated workspace with its own files, instructions, and memory that carries across sessions. You can build one three ways: start from scratch, import an existing Chat project, or point it at a folder you already use.

The decision rule is simple. A one-off task, or a single month-end close you'll only run once this way, is fine in a plain folder session. Anything you'll come back to weekly, a client's books, a recurring close cycle, a standing tax-prep relationship, belongs in a Project. Set it up once and Cowork stops starting from zero every time you open it.

Instructions: set standing rules once

Cowork takes standing instructions at three levels, and it's worth knowing which is which before you write one. Global instructions live in Settings, then Cowork, then Global instructions (desktop app only), and apply to every task you run, in any folder. Project instructions live in the right panel of a Project and apply only inside that Project. Organization instructions are admin-set and apply across Chat, Cowork, and Code for the whole team.

Instructions aren't the same thing as Skills. An instruction applies to every task, quietly, in the background. A Skill loads only for the specific kind of task it's built for, and it's shareable with teammates the way /close-month is. A concrete example of a bookkeeping global instruction: "always flag transactions over $500 for review before categorizing them." Set that once, and every Cowork session in every folder honors it without you repeating yourself.

Connectors: the third customization layer

Instructions and plugins aren't the whole picture. Connectors are the third piece, and they work differently than either one. A connector doesn't just read your QuickBooks data. It can write back: update a record, post a categorized transaction, save a file. You enable a connector from the Customize panel, and you authorize it once, not every session.

That write-back capability is exactly why the guardrails section below matters so much. A read-only connector can't do damage on its own. A write-authorized one can, if nobody checks its work first. This is also where Team and Enterprise plans add a layer solo operators don't have. An admin decides which connectors the whole org can use. The admin also sets whether each one is read-only or write-authorized, before anyone on staff even opens Cowork.

Install the Small Business plugin (this is where the bookkeeping skills live)

Cowork alone gives you a working folder and tool access. The Small Business plugin adds bookkeeping skills on top. It needs the desktop app, and a Pro, Max, or Team plan. It's not open to every plan.

To install: in Cowork, go to Customize, then Plugins, click +, and pick Small Business.

That installs six skills. Each one covers a different piece of the money side of your business.

Two of the six share one piece underneath: /month-heads-up and /plan-payroll both run on a cash-flow-snapshot block. It reads your cash balance, open invoices, bills due, and incoming settlements. Then it builds a 30, 60, and 90-day forecast, with tight weeks flagged. That block does real work behind two different skills. It's not duplicating the same logic twice.

A few mechanics worth knowing before you run any of these. Some skills run others in sequence. When they do, Claude asks you for a decision between steps. A bigger job still comes down to one ask at a time, not a wall of questions up front. You can run any skill through the / picker, or just ask in plain English. Corrections persist, too. Tell /invoice-chase you chase overdue invoices at 15 days instead of 30. That change is saved for the next run, not just this one.

These six skills map directly to the workflows below, plus one QuickBooks-connector report pull that doesn't need a skill at all.

Not every plan sees the Small Business option. If Customize, then Plugins, doesn't show it as a choice, your plan doesn't include it yet. Check your current plan against Pro, Max, or Team before you troubleshoot anything further.

Connect QuickBooks (the short version)

This is the short version of the Claude Cowork QuickBooks setup. For the full walkthrough, connector setup, OAuth, and what Claude can and can't read, see Connect QuickBooks Online to Claude.

Short version: go to Connectors, pick QuickBooks, and click Connect. Sign in through Intuit. One thing worth saying plainly, not burying in a footnote: the QuickBooks connector is US customers only.

You don't need an active QuickBooks Online plan to use it. You can supply the data yourself. Once connected, Claude can pull reports, compare your numbers to your industry, import transactions, and create invoices, estimates, and payment links. Intuit says your QuickBooks data isn't used to train Claude.

One more plain statement: there's no official Xero connector in the current Small Business plugin table. If you run Xero instead of QuickBooks, the plugin's money skills won't reach your books the same way today. More on that in the FAQ below.

This one connection feeds most of what's below. The industry-benchmark comparison in the reports workflow, the reconciliation in /close-month, the cash view in /plan-payroll, all of it reads through this same QuickBooks connector. Get this step right once, and the rest of the setup below builds on top of it.

10+ Cowork workflows you can run today

Each of these Claude Cowork accounting workflows comes with a prompt you can copy and paste. Each one also comes with what Claude does, and what you should check before you act on it.

Monday morning financial brief (/monday-brief)

Prompt: Run /monday-brief, or ask in plain words: "Give me this week's brief: cash position, notable transactions, and anything that needs my attention."

What Claude does: pulls current data through the QuickBooks connector and drafts a summary.

What you check: any number that looks off before you act on it. Claude reads what your account can read. It doesn't make the judgment call for you.

Month-end close checklist (/close-month)

Prompt: Run /close-month for the current period. Or, plain words: "Close out this month and tell me what needs my attention."

What Claude does: checks QuickBooks transactions against your processor settlements by matching amount and date. It flags mismatches, uncategorized transactions, duplicates, and missing receipts. You clear each flag in plain words, something like "the Coastline charge is packaging, cost of goods." Claude then hands you a reconciliation spreadsheet plus a one-page close packet for your accountant.

Here's what that flag list looks like on an illustrative month. Say /close-month turns up four items. A PayPal settlement hasn't matched to any QuickBooks deposit yet, flagged as a mismatch until the timing catches up. A $340 charge posted twice: a straightforward duplicate. A $58 charge from a new vendor: uncategorized. And a $210 hotel charge with no receipt attached. You clear each one the way you'd explain it to a person. "The PayPal settlement is still in transit, give it a day." "The duplicate is a bank sync glitch, delete the second one." "The $58 charge is software, categorize it as subscriptions." "The hotel was a client trip, I'll upload the receipt tonight." Claude updates the reconciliation spreadsheet as each flag clears, then builds the close packet once the list is empty. The dollar amounts here are illustrative. Your own flags will carry your own numbers. The pattern holds regardless of the count. However many flags a real month turns up, you're clearing each one in plain English, not hunting through a spreadsheet line by line. For the deeper walkthrough, with scheduling, the difficult 20%, and what a full close needs beyond reconciliation, see the full month-end close with Claude Cowork guide.

What you check: every category it picks, and any account that doesn't match cleanly. This is a checklist helper, not an auto-close.

Payroll planning (/plan-payroll)

Prompt: Run /plan-payroll for the next pay period. Or, plain words: "Walk me through payroll and flag anything I should know first."

What Claude does: builds a 30-day cash view from your bank balance, open invoices, and bills due. It marks the low point and your payroll dates, then drafts a plan.

What you check: all of it, before it becomes a payment. Payroll is exactly the kind of action Cowork asks you to approve first. More on that in the guardrails section below.

Invoice chasing (/invoice-chase)

Prompt: Run /invoice-chase for your overdue invoices, or ask in plain words: "Chase down everyone who owes me money and draft the follow-ups."

What Claude does: ranks late customers and drafts follow-up notes matched to each one's payment history.

What you check: tone and accuracy on every draft before it sends. Sending needs your OK here. It's not automatic.

QuickBooks reports and benchmarking (connector, no skill needed)

Prompt: Ask in plain words: "Pull my [specific report] and show me how it compares to industry numbers for my business type." A concrete version: "Pull my P&L for this quarter and show me how my margins compare to other businesses in my industry."

What Claude does: pulls the report through the QuickBooks connector and adds the comparison. No Small Business plugin skill is needed for this one.

What you check: any comparison against your own business. Generic industry numbers don't always fit your model.

Tightest-week radar (/month-heads-up)

Prompt: Run /month-heads-up, or ask in plain words: "What does the next 30 days of cash look like, and which week should I watch closest?"

What Claude does: reads the next 30 days of cash, flags the tightest week, and notes what to watch before month-end.

What you check: the assumptions behind any invoice or bill it's counting as certain. A forecast is only as good as what's actually going to land on time.

Margin and pricing check (/price-check)

Prompt: Run /price-check for [product or service line], or ask in plain words: "Show me my margins by product and where my break-even pricing sits."

What Claude does: builds a margin-by-product table and break-even pricing scenarios from your QuickBooks data.

What you check: the underlying cost assumptions. This shows you the numbers. It doesn't set your price for you.

Quarterly taxes and 1099 prep (/tax-prep)

Prompt: Run /tax-prep for [quarterly estimate / year-end 1099 list].

What Claude does: calculates quarterly estimated taxes, or builds a year-end 1099 list formatted for your accountant. The 1099-NEC filing threshold for tax year 2026 is $2,000 under OBBBA. Verify any contractor count Cowork produces against that current threshold before you rely on it.

What you check: every contractor total against your own records before you hand the list off. This is prep, not filing.

Document triage with a Context.md briefing file

Prompt: Sort everything in this folder into subfolders by document type, then write a Context.md file summarizing what's here: filing status or entity, income sources, key numbers, and anything missing. Or, shorter: "Sort this folder by document type and give me a one-page summary of what's here and what's missing."

What Claude does: sorts a folder of statements, invoices, and receipts into subfolders, and drafts a one-page Context.md briefing plus a list of what's flagged as missing. This pattern comes from the Cowork user community. It's not an official Anthropic skill. It's worth trying anyway, because it turns a folder dump into something you can actually read before a meeting.

What you check: the missing-documents list first, then skim Context.md for anything mis-filed before you rely on it. Community reports put the setup-time savings at six to eight hours. That's walking into a close or a tax-prep meeting with a one-page brief instead of a folder dump. Your results will vary with how messy the folder started.

Receipts and statement folder triage

Prompt: Go through this folder of receipts and bank statements, match receipts to transactions where you can, and flag anything without a match. Or, narrower: "Just check last month's receipts against my QuickBooks transactions and tell me what's missing."

What Claude does: cross-references receipts against statement lines, and flags both orphaned receipts and orphaned transactions.

What you check: every flagged item. This catches candidates. It doesn't decide what's deductible.

Categorize a folder of bank statements (bulk first-pass books)

Prompt: Categorize every transaction in these bank statements against the QuickBooks default chart of accounts. Build a balance sheet and P&L, and flag any transaction you weren't sure how to classify.

What Claude does: reads through a folder of PDF bank statements, including scanned or image-based ones. It categorizes every transaction against a standard chart of accounts, the QuickBooks default in this case. It builds pattern rules on the fly as it goes. Say it sees three coffee-shop charges from the same vendor tagged as meals. It applies that same rule to the fourth and fifth without asking again. Recurring vendors get classified automatically. Anything it's not confident about gets flagged for a second pass instead of guessed at silently. The output is a categorized transaction spreadsheet plus a balance sheet and a P&L built from it. For the full first-pass workflow, with the chart of accounts, worked flag examples, and reconciling back to your bank, see the guide to doing your books from bank statements with Claude.

What you check: the classifications, since Cowork may categorize a charge differently than you would. And every flagged transaction. Transfers between your own accounts are one common reason. Credit-card payments and opening balances with no statement behind them are two more. Those are the usual reasons something lands on the flagged list instead of the confident pile.

This is a fast first-pass draft you review, not a finished set of books. Treat the output the way you'd treat a new hire's first categorization pass. Useful, mostly right, and worth a real read before you call it done.

These eleven cover the everyday surface. More skills ship inside the Small Business plugin over time, and the same prompt-and-review pattern applies to whatever's added next.

Notice the shape that repeats across all ten. A prompt you can copy. A short description of what Claude actually does with your data. A specific thing to check before you trust the output. That shape holds whether the skill is /monday-brief or something Anthropic ships next month. Learn the pattern once, and a new skill in the plugin isn't a new thing to figure out. It's the same review habit, pointed at a new task.

The Finance plugin (a separate install, built for firms)

Small Business isn't the only pre-built plugin Anthropic ships for Cowork. There's a separate Finance plugin. Anthropic also ships role-based plugins for sales, legal, and marketing. The marketplace describes Finance as covering "journal entries and reconciliation to financial statements and variance analysis." That's a broader, firm-oriented toolkit than Small Business's owner-facing money skills. It's built for people doing the accounting, not just running a business.

Installing it works the same way, but there's an extra step worth knowing: Customize, then Plugins, select the plugin, then Customize again. Running Customize on the Finance plugin sets off a short interview. Claude looks through your connected tools for signs of which systems your team actually uses. It asks you a handful of confirming questions. Then it rewrites the plugin's skills to reference your specific tools, and adds the matching connectors, before packaging it for install. You're not stuck with generic instructions written for nobody's stack in particular.

Org admins can manage plugins centrally for a whole team, which matters more here than it does for Small Business. A firm standardizing on the Finance plugin wants every staff member's install pointed at the same tools. Not five different customize sessions drifting apart from each other.

Where does that leave the choice? Solo operators and small businesses running their own books will likely stay on Small Business: weekly briefs, month-end close, payroll, pricing, tax prep. Bookkeeping and accounting firms doing journal entries and variance work as a regular part of the job are a different story. That's the audience the Finance plugin is actually built for.

Automate it: scheduled tasks and Routines

You don't have to be at your computer for the workflows above to run. Type /schedule inside any Cowork task, or open Scheduled in the left sidebar to view, create, or manage scheduled tasks. Scheduled tasks run remotely: no computer awake, no desktop app open required. That's a real distinction from a session you're actively watching. Once it's scheduled, it runs on Anthropic's side and waits for you to check the result.

A sample bookkeeping schedule, built the same way for every item. Run the skill once, type /schedule inside that task, then set how often it repeats.

• Monday mornings, weekly: /monday-brief, scheduled to repeat every Monday, waiting in your inbox when you sit down.
• Mid-month, monthly: /month-heads-up, scheduled around the 15th, so the tightest week of the month shows up before it arrives, not after.
• The 1st of the month: /close-month for the period that just closed, scheduled to repeat monthly, so the close packet is ready early instead of assembled in a scramble.
• Quarterly, ahead of each estimated-tax deadline: /tax-prep, scheduled to repeat each quarter, giving you a buffer to review before you file.

That's four scheduled tasks running without you in the room. Each one does the reading, matching, and drafting work the same way an interactive session would. The mechanics below cover what happens with anything that needs your sign-off.

None of that requires you to remember to open Claude that day. It requires setting the schedule once.

Say a scheduled run needs something it doesn't have access to: a connector that needs re-authorizing, or a folder it can't reach. It stops there and waits. It doesn't guess, and it doesn't work around a missing piece on its own. You'll see the gap the next time you check in, not a silently wrong result.

As of this writing, Cowork's usage limits are doubled through August 5, 2026. Reading this later? Check current limits before you count on the same headroom. Scheduled tasks still count against your usage the same as a session you run yourself. The doubled window is worth using while it lasts, especially if you're setting up a recurring schedule for the first time.

One more mechanic worth knowing: a scheduled task doesn't wait for you to notice it ran. It finishes and drops its output where you can find it. If it hit anything that needs your sign-off, that approval request is still waiting the next time you open Claude. Nothing sends, posts, or pays just because a schedule fired unattended. The same approval gate from the guardrails section below applies to every scheduled run.

Guardrails: what Cowork asks before it acts

Six things worth knowing before you hand Cowork real work. Some are the plain rules you'll use every day. Some are the setup underneath them.

You approve before anything sends, posts, or pays. That's true across every workflow above. Drafts wait for your OK before a reminder goes out, a transaction posts, or a payment moves. Run /invoice-chase and Claude writes ten follow-up notes. It doesn't send any of them until you say go. Run /plan-payroll and Claude drafts the run. It doesn't move a dollar until you approve it, line by line if you want to.

Where sessions actually run. This is the one most people skip past, and it's worth slowing down for. A Cowork session runs remotely, in an isolated, temporary environment created for that one session, on Anthropic's servers (beta). It can't reach your home or company network, and it's removed when the session ends. Claude reaches your local files, browser, and apps only through the Claude Desktop app, and only for folders you've connected. If the desktop app is offline, the session can't reach your computer at all. That's a materially different model from "Claude runs on my laptop," and it's the model worth knowing before you connect a client's books.

Read tools vs. write tools. Cowork's tools split into two classes. Read tools, reading an inbox, taking a screenshot, are lower-risk. Write tools, creating a calendar invite, deleting a file, running a command, clicking something, carry more risk and are treated with more caution. Human oversight is recommended in high-stakes scenarios. For bookkeeping, that splits cleanly: reading your QuickBooks ledger to draft /monday-brief is a read action, low-stakes on its own. Posting a categorized transaction, or sending a payment reminder, is a write action. That's exactly where the approval gate in the first guardrail does its job.

No training on your business data. Anthropic doesn't train on your business data. QuickBooks data isn't used to train Claude either, per Intuit. That's a specific, checkable claim, not a vague reassurance. It's worth confirming against the source, not taking any guide's word for it, including this one. Weighing data-security questions more broadly before you connect client books? Our security guide covers what to check.

Prompt-injection review. An action-review system scans for prompt injection before Claude executes a write action. That's one more layer, not a substitute for reading what you're approving. A bad line hidden in a document you feed Cowork is exactly the kind of thing this check exists to catch. But the approval gate above is still your last line of defense.

Firm-level controls, if you're reading this as a firm. A few notes if you're evaluating Cowork for a bookkeeping or accounting firm rather than your own books. Cowork activity isn't captured in Anthropic's Compliance API yet, the system built for compliance audit logs. If compliance logging is a requirement today, that gap matters. Team and Enterprise owners have a workaround. They can stream Cowork events to their own monitoring tool, called a SIEM, using OpenTelemetry, a standard method apps use to send activity logs. That gives an audit-adjacent record in the meantime. Team and Enterprise owners can also turn off web search for Cowork and Chat in Organization settings, under Capabilities. Admins control which connectors are open org-wide, and whether each one is read-only or write-authorized.

Computer use, one more capability that touches this same trust question, gets its own section next. It's a separate, narrower feature with its own safeguards, worth knowing on its own terms rather than folding into the guardrails above.

Taken together, these six guardrails are the reason the worked /close-month example above reads the way it does. Claude surfaces every flag and drafts every clearing note. Nothing about a client's books changes without you reading and answering each one.

Computer use in Cowork: when it helps, when to skip it

Computer use is a separate, narrower capability inside Cowork, worth knowing on its own terms. Status, plainly: research preview, available on Pro and Max plans only, desktop macOS and Windows, not Team or Enterprise.

Before Cowork resorts to clicking around your screen, it works through a priority order. Connectors come first, fastest and most reliable, because they talk to an app's API directly instead of guessing at pixels. The browser comes second, through Claude in Chrome, when a connector doesn't exist for the tool you need. Screen interaction is the last resort, used when neither of the first two paths reaches what you're asking for.

Computer use can technically click anything on your screen, so the safeguards match that risk. Claude asks a permission prompt before it touches a new application. Investment, trading, and crypto apps are blocked by default. You can extend a user-managed blocklist yourself. And the same prompt-injection review from the guardrails section above still runs. Anthropic's own guidance is direct: don't grant access to banking, healthcare, or government apps. Start with simple tasks. Keep prompts specific.

Here's the practical framing for bookkeeping. Computer use isn't needed for any of the ten workflows above. They all run through connectors, the fastest and most reliable path. It starts to matter when Cowork hits a tool with no connector path yet. Think a niche invoicing app, or a vendor portal with no API. That's when you'd need Claude to work through the screen instead. For most bookkeeping and accounting work today, that's the exception, not the rule.

Say a vendor's payment portal has no API and no connector, and you need Cowork to pull last month's activity from it. That's a real computer-use case. It's also a good moment to check the plan gate first: Pro or Max only, desktop only. If you're on Team, Enterprise, web, or mobile, computer use isn't available yet, whatever the task.

Where Cowork stops (and what that means for client books)

Cowork is genuinely good at the ten-plus workflows above. One person, working through one folder, getting real bookkeeping done without spelling out every click.

It's also, by design, one folder, one session at a time. It doesn't hold state across many clients. It isn't a system of record. There's no built-in audit trail showing who approved what, when, across a roster of client books. Every session starts fresh, without memory of last week's fixes, unless you set up a Project the way the setup section above describes. What you taught it Monday doesn't carry to Friday on its own, in a bare folder session. Managing books for more than yourself, or more than a couple of clients? See how AI bookkeeping tools handle multiple clients at once before you decide Cowork alone covers it.

That's not a knock on Cowork. It's doing what it's built for. It's also why Growthy exists as a separate layer. Growthy connects straight to QuickBooks Online. It pattern-learns from your fixes per client. It reviews every transaction with you before it posts, the same approve-first posture Cowork uses. It's just built to run many client books at once, 10 to 30-plus, with an audit trail. Growthy is 85% accurate on first import. You review the rest. And if your work runs into tax season, the same operator stack covers workpapers through our sister product, TracePrep for tax workpaper automation.

Get started with Growthy. Get started and see what it catches on your first import.

Give Cowork a ledger it remembers: the Beancount trick

Here's the honest problem underneath everything above. A bare Cowork session has no database. The categorized transactions from a workflow like the bulk bank-statement one above live in a one-off spreadsheet, with nothing persistent behind them. Close the session, and the structured record goes with it. That's unless you built a Project to hold it, or you're deliberate about saving the output somewhere.

One technique from the Cowork user community closes part of that gap for free. Ask Claude to keep the books in Beancount instead of a spreadsheet. Beancount is an open-source, plain-text double-entry accounting system written in Python, with roughly 5,800 stars on its GitHub repo as of this writing. Every transaction and every account lives in a plain text ledger file you own. That file is git-friendly and portable. Hand it to a colleague, or drop it in a shared folder. Or open a fresh Claude session pointed at the same file and pick up exactly where you left off. It's closer to how a QuickBooks Desktop file works than to a cloud subscription.

Prompt: Use Beancount to keep the books for these statements. Use the QuickBooks default chart of accounts and stick to the Beancount format so the ledger stays valid.

To see the numbers, Fava is Beancount's open-source web interface. Point it at your ledger file and it renders a trial balance, a balance sheet, and a P&L. Or skip Fava and have Claude build a small custom reporting view on top of the same file, if you want something more tailored. For the full setup, the syntax primer, and the git workflow, see the guide to giving Claude a permanent Beancount ledger.

Here's the honest limit, and it's the same one this guide keeps coming back to. The Beancount trick is a clever, free way to give your own books a persistent ledger instead of a one-off spreadsheet. The same goes for a couple of simple clients' books. But you're hand-wrangling text files. There's no pattern memory learning across a roster of 30 client books the way there is with a purpose-built tool. And there's no built-in audit trail of who approved which change, and when. That's the exact line where a DIY text-file ledger stops and a productized book of record begins. It's the same review-and-approve territory Growthy covers above, just built to carry the volume a hand-maintained ledger can't.

A bookkeeper's rollout plan: solo operator to firm

Everything above is real and usable today. The question most readers actually have is where to start, and where the natural next step is once Cowork earns your trust. Three stages, roughly in order.

Stage one: solo, your own books. Cowork on desktop is enough to start. "Work in a folder" gets you through your first close without any setup overhead. Add the Small Business plugin and the QuickBooks connector. That gives you five or six workflows covering most of what a solo operator needs weekly. Skip Projects and Instructions at this stage. They're overhead you don't need yet, not a requirement to get started.

Run the same folder for a few weeks before you add anything else. If you notice yourself explaining the same context to Claude every Monday, that's your signal to move to stage two, not before.

Stage two: a handful of clients, still one person. This is the stage where the setup section above starts to matter most, especially the Projects-vs-folder decision. This is where Projects earn their keep. Set up one Project per client, not one shared folder for everyone, so memory and instructions don't bleed between clients. A standing rule that's right for one client's chart of accounts is wrong for another's. A Project instruction like "this client's contractor payments always route through Bill.com, never a manual check" belongs at the Project level, not Global, because the next client on your roster probably pays contractors a different way. Use Global Instructions sparingly, since they apply to every task in every folder. Reach for Project instructions instead when a rule is specific to one client's books. Worth naming honestly at this stage: Cowork's one-session-at-a-time design means you're still the one holding continuity across clients. Nothing about Projects removes that. You're the connective tissue between five separate Cowork relationships, not Cowork itself.

Stage three: a firm, multiple staff. This is where the Team plan's admin controls start to matter. Connector governance. Event streaming to a monitoring tool for an audit-adjacent record, the option covered in the guardrails section above. Org-wide instructions that keep every staff member's Cowork sessions consistent. Evaluate the Finance plugin if journal entries and variance work are a regular part of the job, not just month-end. And this is also the honest point. The answer to "who runs 10 to 30-plus client books with an audit trail" stops being Cowork alone. That's the natural line. It's not a sales pitch tacked onto the end of a feature list. The Growthy bridge above already made the case for what that looks like.

Wherever you're starting, the setup section above works the same way at every stage. What changes is how much structure you build around it.

Troubleshooting and common gotchas

A few things that trip people up, worth knowing before you hit them rather than after.

QuickBooks connector is US-only. Non-US readers hit a wall here immediately. It doesn't extend to Xero through an official connector yet either. So if you're outside the US, or you run Xero, expect a gap. The Small Business plugin's QuickBooks-dependent skills won't reach your books the way this guide describes.

Small Business and Finance plugins both need the desktop app. If you're on the web or mobile beta, don't expect plugin parity yet. The beta covers Chat and Cowork sessions themselves; plugin installs are a desktop-app feature for now.

Plan gating is real, and it's not the same gate for every feature. Pro, Max, or Team opens up the Small Business plugin. Pro or Max specifically, not Team or Enterprise, opens up computer use. A Free plan or an unsupported tier blocks both. The error you'll see is usually just the option not appearing in Customize, under Plugins. It's rarely an explicit denial.

A bare "Work in a folder" session has no memory. If last month's corrections aren't showing up this month, that's usually not a bug. You're probably running a fresh folder session instead of a Project, and a fresh session starts exactly where the name implies: fresh.

The desktop app needs to be open and online for an interactive session to reach local files. A scheduled task is different, as the automate section above covers. An interactive session you're actively using, one pointed at local files and connected folders, needs the desktop app running to reach them. If Cowork says it can't see a file you know is there, check whether the desktop app is actually open first.

A Chat conversation and a Cowork session aren't the same memory. They're both under one home tab, and it's easy to assume context carries between them. It doesn't, unless you import a Chat project into a Cowork Project on purpose. If Cowork seems to have no idea what you discussed in Chat yesterday, that's expected, not a glitch.

A skill correction that "didn't stick" is usually a Project mismatch, not a bug. Corrections persist for the next run of a skill, but that memory lives inside the Project you made the correction in. Say /invoice-chase reverted to chasing at 30 days instead of the 15 you taught it. Check whether you're running it from the same Project. A different folder, or a fresh session, starts over.

Frequently asked questions

Once you know how to use Claude Cowork for daily bookkeeping, these are the questions that come up next.

What is Claude Cowork, and how is it different from Claude Chat or Projects?

Cowork is a working-session mode where Claude runs multi-step tasks on its own. It works inside a folder you choose, with tool access, and can finish those tasks without you spelling out every step. Chat and Projects are conversation threads where you paste in context and ask questions. Cowork reached general availability on all paid plans in April 2026, after a January 2026 research preview.

Which Claude plans include Cowork?

Every paid Claude plan includes Cowork. Pro runs $20 a month. Max runs $100 or $200 a month. Team runs $25 a seat on Standard, or $125 a seat on Premium. The Small Business plugin narrows that further to Pro, Max, or Team. It also needs the desktop app.

Is Claude Cowork available on Mac, Windows, and web or mobile?

Yes on desktop, macOS and Windows, on every paid plan. Web and mobile are in beta, announced July 7, 2026, rolling out step by step, starting with Max. Not on Max? Check your account before you assume web or mobile access is live yet.

Is it safe to connect QuickBooks or client data to Cowork?

Anthropic says it doesn't train on your business data. Intuit's own help article confirms QuickBooks data isn't used to train Claude either. Cowork only reads what your connected accounts can already read. It runs each session in an isolated remote environment. It only acts inside the folder you gave it. For more on data-security questions around AI bookkeeping tools in general, see our security guide.

Can Cowork actually send invoices, post transactions, or pay bills in QuickBooks?

It can draft plenty: reminders, categories, payment plans, invoices. But it asks for your OK before anything actually sends, posts, or pays. You don't need an active QuickBooks Online subscription to connect the tool in the first place, either. You can supply the data yourself if you're not on a QBO plan.

What's the Small Business plugin, and do I have to install it separately from Cowork?

Yes, it's a separate install. Cowork gives you the working-session mode. The Small Business plugin adds bookkeeping skills, six of them as of this writing, on top. Install it from Cowork's Customize menu, under Plugins.

Can Cowork run bookkeeping tasks on a schedule without me at my computer?

Yes. Scheduled tasks run with no device online. Type /schedule inside a task, or open Scheduled in the sidebar. A weekly /monday-brief or a recurring close checklist can run without you sitting in front of Claude at all.

How does Cowork compare to Growthy for actually running client books day to day?

Cowork is a workflow tool: one folder, one session at a time. Growthy is built to run many client books at once. It connects directly to QuickBooks Online, pattern-learns per client, and runs 10 to 30-plus client books with an audit trail Cowork doesn't have. Both share the same review-and-approve posture. Growthy just carries more volume than Cowork was built for. Think of it this way: Cowork is a very capable assistant for your own desk. Growthy is the system underneath a whole roster of desks.

What's the difference between the Small Business plugin and the Finance plugin?

Small Business is owner-facing: weekly briefs, month-end close, payroll planning, pricing, tax prep. Finance is a separate, broader plugin built for firms, covering journal entries and reconciliation through financial statements and variance analysis. Both install from the same Customize menu. Finance also runs a short customize session first, rewriting its skills to your team's specific tools before the install finishes. Most solo operators and small businesses stay on Small Business. Bookkeeping and accounting firms doing journal entries and variance work regularly are the Finance plugin's fit.

Does Cowork work with Xero, or only QuickBooks?

There's no official Xero connector in the current Small Business plugin table. The plugin's money skills are built around QuickBooks and, for a couple of skills, PayPal. If Xero is your system, the workflows in this guide won't reach your books the way they reach a QuickBooks connection today. You can still point Cowork at a folder of Xero exports for general document work. You just won't get the six connected skills running against live Xero data the way this guide describes them. That gap is worth checking again before you commit a Xero-based practice to Cowork as its main bookkeeping tool.

Does Cowork remember what I taught it last month?

Only if you set it up to. A bare "Work in a folder" session has no memory once it ends. A Project is different: it carries files, instructions, and memory across sessions. You can build a Project three ways: start from scratch, import an existing Chat project, or point it at a folder you already use. Say you tell /invoice-chase to chase at 15 days instead of 30 inside a Project. That correction is saved. It applies the next time you run the skill inside that same Project.

What happens to a scheduled task if my laptop is closed?

Nothing stops. The scheduled run doesn't need your laptop, as the FAQ above covers. Your laptop can be closed, asleep, or off entirely, and the task still runs and waits for you to check the result.

Can Cowork create journal entries?

Not through the Small Business plugin. Journal entries and reconciliation are Finance plugin territory, described in the marketplace as covering journal entries and reconciliation through financial statements and variance analysis. If journal entries are a regular part of your work, that's the plugin to look at, not Small Business.

Does Cowork keep a permanent ledger, or is Beancount required?

Not on its own. A bare Cowork session has no database behind it, so a categorization run's output normally lives in a one-off spreadsheet. Beancount is a free, optional workaround. It's a plain-text ledger file Claude can write to and read back from, session to session. It's popular in the Cowork user community for exactly this reason. It's not built into Cowork, and it's not a requirement. It's one way to get a persistent record without paying for anything, if you're comfortable maintaining a text file yourself.

What admin controls does a Team or Enterprise account get?

Team and Enterprise owners get connector governance: which connectors are available, and whether each one is read-only or write-authorized. That's a per-connector setting, not one org-wide switch. QuickBooks read access and a payment connector's write access can be governed differently under the same admin. They can turn off web search for Cowork and Chat in Organization settings. They can set org-wide instructions that apply across the whole team. And they can stream Cowork activity to their own monitoring tool for an audit-adjacent record, the option covered in the guardrails section above. Formal compliance logging inside Cowork itself isn't there yet.

That's how to use Claude Cowork for your own books, whether you're a solo operator or a small team. The setup. Six money skills across two plugins. Projects and Instructions for work you come back to weekly. The security behind every session. Computer use as a narrower add-on. A rollout path from solo to firm. And a schedule you can automate once you trust it. It's not a bookkeeping system on its own. It was never built to be.

Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice.