Month-end close is the most consistent time sink in finance operations. A small-company controller spends three to five business days a month closing the books. Most of that time is not analysis. It is chasing down expense categorizations, matching vendor invoices to payments, and reconciling what happened in the operating business with what the books say.
Connecting QuickBooks, Google Drive, and Gmail to Claude through CorpusIQ collapses the translation work. The close does not get shorter because Claude does accounting. It gets shorter because Claude gathers context in seconds that used to take hours.
The current close, honestly audited
Walk through a typical monthly close.
Day one: run the P&L and balance sheet. Scan for anything that looks wrong. Export to a spreadsheet.
Day two: chase down miscategorized transactions. Email the ops team asking what a $4,800 Amazon charge was. Open Drive to find the vendor contract that governs a specific recurring expense. Scroll through invoices in Dropbox or Drive to confirm what got paid and what did not.
Day three: reconcile accounts receivable. Look up customer-specific payment terms. Cross-reference email threads where a customer promised to pay "this week." Update the cash forecast.
Day four: build the monthly management report. Pull P&L against budget, AR aging, cash position, key KPIs. Reformat into a template.
Day five: review with the CEO, answer follow-up questions, often by going back to QuickBooks for a different slice of the same data.
The pattern is clear. About 70% of the work is moving information from one place to another. 30% is actual judgment.
The Claude-assisted close
Same five days, different distribution.
Before close day, run Claude against QuickBooks for a first pass. "Flag any transactions over $2,000 this month that look miscategorized based on vendor name." "List AP with amounts significantly different from the same vendor's historical average." "Which customer balances moved by more than $10,000 this month?"
During close, ask Claude questions as they come up. "What does the contract with Acme say about their payment terms?" Claude queries Drive for the Acme contract, pulls the clause. "What did the ops team say about the $4,800 Amazon charge last month?" Claude searches Gmail for relevant threads.
For management reporting, ask Claude to build the summary directly. "Compare the P&L for this month to the trailing six-month average. Highlight any line that moved more than 20%." "Give me an AR aging report grouped by customer, with any past-due balances flagged."
The close does not take zero days. It takes half as many.
What changes in practice
Three things change.
First, context is instant. The controller stops waiting on email replies to categorize transactions. If there is any written record (Slack, email, Drive doc), Claude surfaces it in seconds.
Second, the surface area of questions the CEO can ask expands. If a follow-up takes five seconds instead of twenty minutes, more questions get asked. That is the real productivity gain: more iterations per close, which means better understanding, which means better decisions.
Third, the management report becomes a conversation, not a deliverable. The controller and CEO sit down, ask Claude questions, get answers. No one is scrolling through a 12-page PDF.
How to set it up
Three connectors, one afternoon.
- Sign up for CorpusIQ at corpusiq.io. Solo $29.95/month covers QuickBooks, Drive, and Gmail plus the other 37+ connectors.
- Connect QuickBooks Online via OAuth. Read-only.
- Connect Google Workspace. Grant Drive and Gmail read-only scopes.
- Add the CorpusIQ MCP server to Claude.
Test by asking Claude a first question that spans all three: "What is the AR balance for Acme Corp, what does their contract in Drive say about payment terms, and what did the last email thread discuss about the most recent invoice?"
Sample prompts for a real close
- "Give me a P&L for the month versus the same month last year. Highlight any line item more than 15% different."
- "List every transaction over $1,000 this month that is not categorized."
- "Show me customers with balances over $10,000. For each, summarize the most recent email thread about their payments."
- "Find the master services agreement with Acme in Drive. What does it say about late payment penalties?"
- "Which vendors have we paid more than $5,000 this month and what do the corresponding invoices in Drive confirm we paid for?"
- "Give me a summary of close-relevant emails from the last 30 days: anything mentioning invoice disputes, payment delays, or contract changes."
- "Compare cash position this month to 3 months ago. What are the top 5 line items driving the difference?"
What stays manual
Claude does not do these. Nor should it.
Judgment on classification when the vendor relationship is genuinely new or unusual. A human has to decide whether that software subscription is marketing or engineering.
Sign-off on the financial statements. Claude produces drafts; a controller or CFO signs.
Tax and compliance filings. Claude can surface source data but a qualified preparer handles filings.
The point of this workflow is not to remove the human from finance. It is to remove the hours of translation between systems so the human spends their time on the 30% of the close that requires judgment.
See also
FAQ
Does this replace my accountant?
No. It replaces the data-gathering busywork your accountant or controller does before the actual analysis. Final sign-off still requires a human with financial judgment.
Do I need all three connectors?
QuickBooks is the minimum. Adding Drive and Gmail multiplies the value because most close questions span systems.
Is it safe to connect Gmail?
Read-only OAuth, zero storage. Claude can search Gmail but cannot send, delete, or modify messages.