Claude Code clears a Stripe bookkeeping backlog
Davis reports building Stripe, Mercury and QuickBooks skills with Claude Code to create matched deposits and clear 166 bank-feed transactions, retaining manual QuickBooks matching.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Inspect [payout and invoice mismatch] and available APIs. Build tools that preserve payment links and payout IDs, skip already-deposited payments and create reviewable matching deposits. Keep final bank-feed matching with me.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Ryan Davis
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Davis reports building Stripe, Mercury and QuickBooks skills with Claude Code to create matched deposits and clear 166 bank-feed transactions, retaining manual QuickBooks matching.
- Human involvement
- Davis works with Claude Code on the integration and retains manual QuickBooks matching. The resulting books are his reported outcome, without an independent audit.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Investigate why Stripe payouts do not match individual invoices.
- Identify the bank-feed API limitation before designing the integration.
- Build payout-breakdown, bank-match and linked-deposit skills.
Ryan Davis has 166 unreconciled bank transactions in QuickBooks for his hosting business. Stripe batches payments and deducts fees and loan repayments, so the deposited amount differs from individual invoices. Claude Code helps him investigate the integration constraint: the bank-feed items awaiting review are not available through the API he intended to use.
Instead, Davis and the agent build Python skills that reconstruct matching deposits. Stripe provides the payout breakdown, Mercury helps confirm the corresponding bank deposit and the QuickBooks tool links WHMCS payment identifiers. The tool checks whether payments are already deposited, records fee deductions and retains the payout identifier as an audit note.
Davis reports running the reconciliation command across outstanding payouts, then manually selecting Match in QuickBooks for each bank-feed transaction. He says the 166-item backlog is cleared and the profit-and-loss statement is ready for tax preparation. This is his report, without an independent bookkeeping audit. Claude Code built and debugged the integration; the resulting command performs the repeatable processing, rather than establishing that an agent autonomously submitted accounts. The useful recovery is to identify what the API cannot expose and create the linked evidence that the existing application's human matching step needs.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Ryan Davis
Frequently asked questions
Why not edit the bank feed directly through API?
Davis reports that the awaiting-review bank-feed items were not exposed by the API, so he created matching deposits instead.
How are duplicate deposits avoided?
The reconciliation tool checks whether the linked payments have already been deposited before creating a new deposit.
What remained manual?
Davis selected Match for each bank-feed transaction in QuickBooks after the tools created the corresponding deposits.
More details
Remaining steps
- Check duplicate deposits and retain payout identifiers and payment links.
- Run the tool, then manually match QuickBooks bank-feed transactions.
About this account
Claude Code researches the API constraint and builds the cooperating tools; the authored reconciliation command performs repeatable deposit creation before human matching.
Firsthand account by Ryan Davis; original publication date verified against Original page byline May 3, 2026; public HTML datePublished 2026-05-04T00:03:21+00:00 crosses the UTC date boundary. Outcomes are the author’s reports, not independently reproduced. Suggested prompt written by Agents In Use; not the author’s original prompt.
Credit: Ryan Davis
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Python skills · Stripe API · Mercury · QuickBooks Online · WHMCS
Stripe payout reconciliation · Linked deposits · Manual bank matching
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.