How to Use Claude for Month-End Close With QuickBooks and PayPal

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Use Claude for Month-End Close With QuickBooks and PayPal.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Use Claude for Month-End Close With QuickBooks and PayPal.

Claude can prepare a month-end close packet if you connect QuickBooks and PayPal with every write tool set to Blocked, or upload exports instead. It matches PayPal activity to the ledger and bank and lists each difference as a question, so your accountant gets the source files, exceptions and draft commentary to approve.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Neither connector is read-only out of the box. Both publish tools that create, change or send things, and asking Claude to “only read” is an instruction, not a permission boundary. The boundary is a setting, covered below. One availability check first: Intuit's own help article says the QuickBooks connector is currently limited to customers in one region, with others to follow, so confirm it is offered for your account before planning around it; the export route needs no connector at all.

How do you set the close boundary before connecting Claude to financial accounts?

Set the close boundary by writing two lists: what Claude may do and what it may not. Claude may retrieve approved reports, compare transactions, calculate differences and draft questions. It may not post entries, change categories, reconcile accounts in the live system, send invoices, issue refunds or pay anything. Put both lists in the task instructions and check that the actual tools and credentials support the intended restriction.

The Intuit QuickBooks listing shows 74 tools: the ones this close needs, such as the balance sheet, receivables ageing and sales by customer, sit beside write tools that create customers, create, update or delete invoices and import transactions. The PayPal listing shows 28, including list_transaction, list_disputes and get_refund, but also create_refund, pay_order, send_invoice, cancel_sent_invoice and accept_dispute_claim. Any of those would turn a preparation task into a live financial action.

So set the boundary in two places. First, open Customize > Connectors, select each connector and set every create, update, delete, send, pay, refund and accept tool to Blocked (Anthropic's help centre says tool permissions are grouped by type, such as read-only and write/delete, so you can block the whole write group), leaving the report and list tools on Always allow or Needs approval. If your account shows no per-tool permissions for a connector, leave it disconnected and use the export route. Second, set the permission control in the message box to Manual. Anthropic's help centre explains why both matter: in Auto mode, rolling out as the default on Pro, Max, Ultra and Team, tools marked Needs approval can run without asking unless an automated check flags them, whereas Blocked tools are denied in every mode. On Team and Enterprise, an owner can apply the same restriction to everyone. Anthropic's safety guide adds the general rule: in any mode, stay close to tasks with real-world consequences and stop one that looks off.

The read-only QuickBooks connection tutorial covers that setup separately. For this close, use export-only preparation if you cannot demonstrate that prohibited actions are unavailable. Keep one untouched source folder outside the working copy. The owner and accountant should be able to review the packet without granting Claude the ability to fix the underlying books.

Which reports and statements should you collect for a close packet?

Collect one consistent set of reports and statements, with one reporting cut-off throughout. Record the business, period start and end, currency, accounting basis and export time. Payment dates, transaction dates and the date a transfer reaches the bank can differ. Ask the accountant which date and basis govern each comparison. Do not merge reports merely because their filenames contain the same month.

From QuickBooks, collect the trial balance, profit and loss statement, balance sheet, PayPal account or clearing-account detail, bank detail, customer balances and supplier balances relevant to the close. This is a proposed evidence set, not a claim that every connector can return every report. If a report is unavailable through the connection, export it through your ordinary authorised workflow and note that route in the packet.

From PayPal, collect the opening and closing balance evidence, transaction activity for the period, fees, refunds, transfers and open disputes relevant to the account. Preserve transaction identifiers and currencies. Obtain bank evidence independently for receipts of PayPal transfers. Do not use a PayPal transfer notification as the only proof that money reached the bank.

Ask Claude to list the retrieved coverage before calculating anything: first transaction date, last transaction date, record count, currency and any missing pages or fields. A successful tool response can still be a partial result. If completeness is uncertain, obtain a full export and compare totals. Keep the original source file so a reviewer can inspect what Claude actually received.

For a suggested working structure, use Sources, Reconciliation, Exceptions and Accountant questions. Give every source a short identifier, such as PP-ACTIVITY-01 or QB-PAYPAL-01. These are example filing labels. A reconciliation row should refer to those identifiers and the original transaction reference, so a reviewer does not need to read a long conversation to find the supporting evidence.

Follow $12,000 of PayPal receipts through the month

Consider an illustrative HVAC contractor receiving some customer payments through PayPal. All figures below use one currency, with no foreign exchange, reserve movement or separate hold included in this simplified balance. The opening PayPal balance is $1,250. Customer receipts total $12,000, refunds total $600, fees total $360 and transfers out total $10,000. The expected closing balance is $2,290.

Illustrative movementEffect on PayPal balanceRunning balance
Opening balance$1,250$1,250
Customer receipts+$12,000$13,250
Refunds−$600$12,650
Fees−$360$12,290
Transfers to bank−$10,000$2,290
Closing balance evidence$2,290Difference $0

Ask Claude to reproduce that movement bridge from the source transactions. A bridge is simply an opening balance plus additions less deductions, arriving at the closing balance. Require a transaction-level supporting list for each movement group. The $360 fees are fictional observed fees in the example, not a published PayPal tariff or a percentage you should apply to other payments.

Now compare QuickBooks. Its PayPal ledger shows a closing balance of $2,530 because only $360 of the $600 refunds has been recorded in this illustration. The $240 difference is a question supported by the missing refund reference. Claude should show the $2,530 ledger balance, $2,290 PayPal balance and $240 difference. It should not create a balancing entry or conclude that PayPal lost money.

Bank evidence shows $9,900 received from the $10,000 transfers, with $100 still in transit at the cut-off. Keep that as a separate transfer timing item. It does not change the PayPal closing balance if the $100 has already left PayPal in the source record. Ask the accountant how to reflect the timing item in the books, using the later bank receipt as evidence when available.

This produces two different exceptions: a $240 refund not reflected in the ledger and a $100 transfer not yet received by the bank. Netting them into a single $140 difference would hide the work required. Keep each source, explanation, amount, responsible person and status visible. The accountant can resolve the recording issue while tracking the transfer timing independently.

If the spreadsheet side of the bridge is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

How do you get Claude to produce an exception ledger instead of a repair story?

Ask Claude for an exception ledger by using a prompt that asks for evidence and proposed questions, with changes explicitly excluded. Provide the period control sheet, relevant exports and the approved treatment rules. If you are using a connector, have Claude name the read operation it intends to use and the source it expects to retrieve. Decline a request that introduces a write action into the preparation task.

Prepare a draft close packet from the supplied QuickBooks, PayPal
and bank evidence. No posting, categorising, refunds, payments,
sending, deletion or live reconciliation changes are authorised.
First list source coverage, period, basis, currencies and missing data.
Build the PayPal opening-to-closing movement bridge. Match transfers
to bank evidence and compare the PayPal closing balance with its
QuickBooks ledger balance. Keep timing and recording differences separate.
For each exception give source references, amount, evidence, question,
owner and status. Do not invent an explanation or plug a difference.
Create draft commentary only after the checks, with unresolved items visible.

An acceptable illustrative exception row reads: “REFUND-24; $240; present in PayPal activity, absent from supplied QuickBooks detail; accountant to confirm accounting treatment and posting status; awaiting review.” The wording leaves room for a later discovery that the item exists under another reference. “Post missing refund now” would exceed the preparation task and assume a conclusion before the accountant has checked.

Use statuses such as matched, timing item, missing evidence and accountant decision. Add a fifth status for resolved after the owner has obtained confirming evidence. Do not use a confidence percentage to replace evidence. A claimed 98% match is hard to judge unless the reader can see what was matched, which amounts remain and whether the unmatched items matter.

The payout reconciliation tutorial explores the wider gross-to-net problem. Here, preserve the distinction between customer receipts, refunds, fees, balances and transfers. Money moving from PayPal to the bank is generally part of following the same funds through the records; ask the accountant how it should be presented rather than counting the transfer as another sale.

Which seven tests stop a neat close packet hiding bad matches?

Seven tests check that a neat close packet is not hiding bad matches; the first is that one bank receipt must not satisfy two transfers.

One bank receipt must not satisfy two transfers

Suppose two illustrative $500 transfers appear on different days, while only one $500 bank receipt is available. Matching by amount alone could mark both transfers complete. Require each bank record to be used once and preserve the transfer identifier where available. The correct output leaves one transfer unresolved and asks for further bank evidence, rather than treating identical amounts as identical transactions.

Net cash must not erase the fee

An illustrative customer payment is $900, with a $50 fee and $850 net movement. If the ledger records only $850 as revenue, the pack should flag the gross-to-net presentation question. Do not automatically add another $50 expense without checking what is already recorded. Show the source amounts and ask the accountant whether revenue and fees have been recorded under the approved policy.

A refund near the cut-off needs two date checks

A sample $80 refund is requested before month-end but appears in the payment activity after the cut-off. Keep both the request evidence and the recorded transaction date. Ask the accountant which period and treatment apply. Claude should not move it into the earlier period merely to make the customer correspondence and payment report appear to agree. Timing questions deserve explicit labels.

A dispute is not automatically a completed refund

A $200 illustrative dispute remains open. The evidence says the customer challenged the payment; it does not say the business lost the dispute or that a $200 refund has completed. Put the status and relevant references in Exceptions. Ask the accountant to decide whether any accounting adjustment or disclosure is needed. Leave customer responses outside this close task unless separately authorised.

Reserved funds need a separate explanation

Imagine a statement distinguishes $300 held funds from the amount available for transfer. Do not subtract the hold again without understanding how the reported balances are defined. Record total balance, available amount and held amount using the source's labels. Ask the accountant to confirm which figure belongs in the ledger comparison. A reserve or hold can change availability without being the same event as a fee.

Two currencies should not become one unexplained total

If a second currency appears, split the reconciliation by currency and stop the single-currency example. Preserve original amounts and any source conversion records. Do not ask Claude to choose an exchange rate from memory. The accountant should confirm the valuation basis and any conversion entries. A combined number that happens to equal the ledger total is not evidence that the foreign-currency movements were treated correctly.

The opening balance can carry last month's problem

A sample opening ledger balance is $1,350 while the prior approved PayPal reconciliation closed at $1,250. Flag the $100 opening difference before investigating current receipts. Otherwise Claude might try to explain it through this month's fees or transfers. Retain the previous approved reconciliation and identify any changes to earlier records with the accountant before calling the new month complete.

What separate checks do balances, movements and coverage need?

A month-end close needs four separate checks: the activity bridge, the ledger balance, transfers against bank evidence and completeness. The first check is whether the source activity bridges from opening to closing balance. The second is whether the ledger agrees with the appropriate closing balance, with documented reconciling items. The third is whether transfers match independent bank evidence. The fourth is completeness: all relevant records and report pages are included. None of those checks substitutes for the others.

Intuit's reconciliation guidance says to compare transactions and, when a difference remains, check the beginning balance, ending balance and ending date, then any manually entered transactions for errors or duplicates. It also notes that you can choose to finish and accept a difference, in which case QuickBooks creates an adjusting journal entry for the amount; Intuit says to talk to your accountant first and that resolving the difference is usually better. Put that on the packet's do-not list. A plug can manufacture a zero; a proper reconciliation explains how each amount reached the result, and the accountant reviews anything that changes a previously reconciled period.

For the main illustration, the evidence checklist should read: activity bridge zero; ledger-to-PayPal difference $240 awaiting refund review; transfer-to-bank difference $100 awaiting receipt; single currency confirmed; no unexplained missing export pages. That is a useful draft packet even though the close is not yet approved. It tells the accountant exactly what remains to be resolved.

After approved bookkeeping corrections, obtain a fresh ledger export and rerun the checks. If the refund is recorded correctly, the $240 ledger difference should disappear. When the $100 bank receipt becomes available, update the timing item's evidence and status. Do not edit the old packet so it appears to have been complete earlier; retain versions showing how the exceptions were resolved.

What should the accountant's hand-off contain?

The accountant hand-off should contain a cover note, untouched source files, the reconciliation workbook, supporting transaction matches, open questions and proposed adjustments clearly labelled for review. Keep the proposed-adjustments list separate from posted entries. If no changes have been made by Claude, say so in the cover note. The accountant needs to know whether they are reviewing a draft or checking actions already taken.

A concise illustrative cover note reads: “The PayPal activity bridge agrees to $2,290. QuickBooks shows $2,530; the attached $240 refund needs review. Of $10,000 transfers out, $9,900 is supported by bank receipts and $100 remains in transit. No live entries, refunds or payments were made during preparation. Please confirm the proposed treatment and any further evidence required.”

Use Claude's file-creation capability to prepare a workbook and readable document if it is enabled for your account. Open the downloads and inspect formulas, references and attachments. Avoid a packet that consists only of a confident narrative in chat. The trial-balance reporting tutorial is the next job once the accountant has approved the close inputs.

Assign questions to a role and deadline: owner supplies missing receipts; bookkeeper checks whether a refund was recorded elsewhere; accountant approves treatment. Use placeholders rather than real personal details in a reusable example. One specific question per row is easier to resolve than a long paragraph that mixes refund, bank and revenue issues under “please check these figures”.

If you want help setting access boundaries and an exception hand-off for your own books, I offer one-to-one AI consultations for small businesses.

When should you repeat the Claude close routine?

Repeat the routine only after the first packet is checked. For a first attempt, allow an illustrative 30 minutes to gather records, 30 minutes to inspect matches and 20 minutes to prepare questions. These are planning allowances, not measured Claude timings. Count the accountant's review effort separately. If preparing the evidence takes longer than the manual close, improve exports and identifiers before adding automation to a weak process.

At the time of writing, Claude's pricing page lists connectors on every plan, Free included, and Pro at $20 a month billed monthly; running the close as a scheduled task needs a paid plan, because Free cannot hand off or schedule tasks. Anthropic's small-business page suggests Pro for one person and Team for a business with more than one. Your QuickBooks and PayPal subscriptions are separate costs, and owner time, accountant review and any extra usage you approve belong in the budget too.

Anthropic's small-business page also describes a ready-made “Close the books” workflow that checks your books against Stripe and Shopify, flags anything odd and explains the month in plain English for your accountant. The same page says you install a Small Business plugin, pick what Claude handles and set when each job runs, such as at month-end, and that bills wait for your approval before they are paid. If you take payments through PayPal, the manual bridge in this tutorial is still worth running once by hand, so you know what a correct packet looks like before a scheduled one arrives.

Keep a reusable close instruction, period control sheet and acceptance checklist, but create a fresh source set each month. Do not let last month's unresolved item disappear simply because the prompt asks for current-month activity. Carry forward open items in a separate list with their original references. That preserves continuity without copying old explanations into new transactions.

Practise the fallback once: disconnect live sources, supply the saved exports and confirm that a colleague can reproduce the movement bridge. Record any missing report or unclear identifier. If the connection fails on the next close day, that tested export route lets preparation continue without widening access or asking the assistant to reconstruct transactions from memory.

Approve the routine for reuse when the accountant can trace each figure, distinguish timing from recording errors and see what Claude was permitted to do. The owner should still review the packet before sharing it. A good close assistant reduces preparation work while leaving the books, payment decisions and final accounting approval under the responsible people's control.

Further reads

Sources: Anthropic marketplace listings, Intuit QuickBooks and PayPal connectors; Use connectors to extend Claude's capabilities; Get started with Claude Cowork; Use Claude Cowork safely; Create and edit files with Claude; Claude for small business; Claude pricing. Intuit, Use Claude to enter transactions and get insights in QuickBooks; Fix issues at the end of a reconciliation in QuickBooks Online. Checked 18 November 2026. All transaction figures and planning allowances are illustrative; accounting decisions require accountant approval.

Have a specific process in mind?

Describe the job in your own words on a 1:1 call and I'll show you what AI you can use for it with the tools you already pay for.

Book a 1:1 call with me