The most common complaint from accountants using Claude Cowork in their first week is not about output quality — it's about friction. Every analysis session starts the same way: export a CSV from QuickBooks, save it to downloads, drag it into Cowork, repeat for the prior period, repeat for the budget. That's 10–15 minutes of setup before any actual work happens, multiplied across every client and every session. Claude Cowork's accounting software integration eliminates this layer entirely. This guide covers the setup for the three platforms where CPA firm clients are concentrated: QuickBooks Online, Xero, and NetSuite.
This article is part of the Claude Cowork for accountants series. For the full workflow list, see 9 CPA firm Cowork workflows. For month-end close specifics, see Claude Cowork for month-end close.
The Named Plugin Combination: Cowork + QuickBooks + Google Drive
The CPA Firm Standard Stack
This combination covers the majority of small-to-mid-market CPA practice workflows. QuickBooks provides live financial data; Google Drive provides client workpapers, prior-year files, and engagement documents; the Cowork canvas analyses all sources together; the Month-End Variance Skill runs the analysis on demand. Setup time: approximately 60–90 minutes to configure all three connectors and build the core Skill.
For SharePoint-based firms (Microsoft 365 rather than Google Workspace), substitute the SharePoint connector for Google Drive — identical functionality, different authentication flow.
QuickBooks Online Connector
The QuickBooks Online (QBO) connector is the most commonly configured accounting integration in CPA firm Cowork deployments. It provides read access to your QBO data — reports, transactions, chart of accounts, customer and vendor records — directly from the Cowork canvas. Once configured, you start a Cowork session, reference your QBO connection, and the current financial data is available without any CSV exports.
Setup: QuickBooks Online Connector
Go to Cowork Settings → Connectors → Add Connector. Search for "QuickBooks Online" in the connector library.
Authenticate via Intuit OAuth. Cowork redirects to the Intuit OAuth screen. Sign in with your QBO admin credentials or an accountant credentials account with appropriate access. Approve the requested scopes (read access to reports, transactions, chart of accounts).
Select which QBO companies to connect. If you manage multiple client QBO files, you can connect multiple companies as separate connections. Name each connection clearly ("Client A — QBO", "Client B — QBO") so your prompts can reference them.
Test the connection. In a new Cowork canvas, type: "Using the [Client Name] QuickBooks connection, pull the Profit & Loss report for [current month] and show me the top 10 expense accounts by amount." Verify the data returns accurately.
Set read-only permissions. In QBO, ensure the connected user account has "Reports Only" access at minimum. You do not need Cowork to write to QBO — read access is sufficient for all analysis workflows. Limiting to read-only reduces your security surface area.
What the QBO Connector Enables
- Pull current-period P&L and balance sheet without exporting
- Access transaction-level data for specific accounts
- Run variance analysis against prior periods (Cowork calls both periods directly)
- Analyse customer aging, vendor payables, and bank balances in real time
- Ask Cowork to identify anomalous transactions in specific account ranges
Xero Connector
Xero's connector operates on the same principle as QBO — OAuth authentication, read access to reports and transactions, no CSV exports required. The key difference for CPA practices is Xero's multi-organisation architecture: a single Xero practice login can access all your client organisations, and the Cowork connector supports connecting multiple Xero organisations as separate data sources.
Setup: Xero Connector
Go to Cowork Settings → Connectors → Add Connector. Search for "Xero" in the connector library.
Authenticate via Xero OAuth 2.0. Use your Xero practice account login. If you use Xero HQ (the accountant portal), authenticate with your HQ credentials to gain access to all connected client organisations.
Select organisations to connect. From your list of connected Xero organisations, select which client organisations to expose to Cowork. You can connect all or a subset. Each organisation appears as a separate named connection.
Set scope to read-only. In Xero's OAuth consent screen, ensure you're granting read access only. The connector does not require write access for any analysis workflow.
Test with a balance sheet pull. In a new canvas: "Using the [Client Name] Xero connection, pull the balance sheet as at [date] and calculate the current ratio and quick ratio." Verify accuracy against the Xero portal.
What the Xero Connector Enables
- Pull balance sheet, P&L, and cash flow statement for any period
- Access tracking categories for segment analysis (department, project, location)
- Pull accounts receivable and payable ageing reports
- Run multi-period variance analysis across up to 12 months simultaneously
- Analyse bank reconciliation status and unreconciled transactions
NetSuite Integration via Custom MCP Server
NetSuite does not have a native Cowork connector in the standard connector library. Enterprise clients running Oracle NetSuite are served via a custom MCP (Model Context Protocol) server that connects Cowork to NetSuite's SuiteAnalytics Connect or SuiteScript APIs. This is a technical integration that requires development effort — typically 2–5 days for a standard configuration — but it enables Cowork to interrogate consolidated multi-subsidiary financials, run saved search queries, and pull role-specific data in real time.
The MCP Approach for NetSuite
The MCP server acts as a secure intermediary: it exposes specific NetSuite data endpoints as tools that Cowork can call. You define which data Cowork can access (e.g., "consolidated P&L by subsidiary", "transaction detail for account range 5000–5999") and the MCP server enforces those boundaries. Cowork never has direct access to NetSuite credentials or admin functions.
Define data requirements. Determine what NetSuite data your Cowork workflows actually need. Typically: consolidated financial reports, budget vs actual, subsidiary P&Ls, trial balance exports. Scoping this tightly reduces build time and security surface area.
Build the MCP server. This is a development task. Our MCP server development service handles this for accounting firms, typically delivering a working NetSuite MCP server in 3–5 business days. The server is deployed in your own infrastructure or a managed cloud environment.
Register the MCP server in Cowork. Add the server URL and authentication credentials to your Cowork Enterprise configuration. The NetSuite data endpoints then appear as available tools in your Cowork canvas.
Test with a consolidated pull. Run a test query: "Pull the consolidated P&L for all subsidiaries for Q3 and show me the intercompany eliminations." Verify the output matches the NetSuite consolidated report.
For a detailed technical walkthrough of MCP server architecture, see our guide to Model Context Protocol for enterprise deployments.
Other Accounting Platform Integrations
Sage Intacct
Sage Intacct provides a REST API that can be accessed via a custom MCP server, similar to NetSuite. For standard exports (general ledger, financial reports, consolidations), the CSV export approach works well — Intacct exports are consistently formatted and Cowork reads them reliably. A native Intacct connector is in development on the Cowork roadmap.
Microsoft Dynamics 365 Finance
Dynamics 365 Finance integrates with Cowork via a custom MCP server connecting to the Dynamics OData API. This is the preferred approach for enterprise manufacturing, government, or multi-entity clients running Dynamics. Setup complexity is similar to NetSuite — approximately 3–5 days for a standard configuration.
CCH Axcess and Thomson Reuters Practice CS
No native connector exists for either platform. The practical workflow: export the engagement data (trial balance, workpapers) from CCH or TR in CSV or Excel format, and load into the Cowork canvas for analysis. Both platforms produce clean, consistently formatted exports that Cowork reads natively. The export step adds 3–5 minutes per session but is otherwise seamless. For tax preparation software specifically (CCH Axcess Tax, UltraTax CS), the same export approach applies.
The Cowork + Xero + Slack Named Combination for Team-Based Practices
The Collaborative Close Stack (Multi-Accountant Firms)
For accounting firms with multiple staff working on the same client close, this combination adds a Slack integration that notifies the team when a Cowork close analysis is complete, posts the summary commentary directly to the client's Slack channel (internal), and flags any items requiring partner review. The workflow runs autonomously: staff accountant triggers the close analysis, Cowork generates variance commentary via Xero, Slack posts the summary and flags items, partner reviews and approves. The close happens without the partner waiting for the staff accountant to complete the analysis first.
FAQ
Does the QuickBooks connector work with QuickBooks Desktop (not Online)?
The native Cowork connector supports QuickBooks Online only. QuickBooks Desktop operates on a different architecture without a cloud API. For Desktop users, the practical workflow is to use QBO export functionality or the QuickBooks Desktop export to CSV and load into Cowork manually. If you manage many Desktop clients who haven't migrated to QBO, building a custom CSV import workflow using Cowork Skills is the recommended approach — the template handles the formatting once, and the process becomes: export CSV, drop into Cowork, run Skill.
Can a single Cowork session access multiple clients' QuickBooks data simultaneously?
Yes. If you've configured multiple QBO connections (one per client), your Cowork canvas can reference any or all of them in the same session. This is useful for benchmarking: "Compare the gross margin percentages for Client A, Client B, and Client C using their latest QBO data." Each connection is isolated — accessing Client A's data does not expose it to Client B's data in any way. This multi-connection capability is available on Claude Enterprise accounts; it may be limited on individual Pro or Max plans.
What security controls should I put in place for accounting software connectors?
Three non-negotiable controls: (1) read-only access only — no write access to any accounting system for any Cowork connection; (2) separate credentials — use a dedicated service account or accountant credentials account for each connection, not your personal admin login; (3) regular access review — check quarterly that each connection is still active, necessary, and using appropriately scoped permissions. Additionally, under Claude Enterprise, all data accessed through connectors is processed within your enterprise security boundary and not used to train Anthropic's models. For firms with additional compliance requirements (SOC 2, ISO 27001), our Claude security and governance guide covers the full control framework.
Stop Exporting CSVs. Connect Cowork to Your Accounting Software Directly.
Our certified architects configure QuickBooks, Xero, and NetSuite integrations for accounting firms. Most standard setups are live within two days. Book a call and we'll scope your specific integration requirements.