Skip to Content
What you can doMatch Stripe payouts

Match Stripe payouts against your books

For finance teams who check Stripe against the ledger by hand every morning. Each day the assistant pulls yesterday’s Stripe payouts and charges, matches them against your accounting records, and reports only the exceptions: amounts that don’t match, missing entries, unexpected refunds. A person looks at the three that matter, not the three thousand that match.

What you need

  • A Stripe restricted key that may only read (payouts, charges, refunds).
  • Read access to your ledger through an API: for example a small read-only query service in front of your accounting database.
  • Somewhere for the report to go: a Slack or email tool, or an address of yours that receives it.

How to build it

  1. Add Stripe. Open APIs, click Connect an API, pick SDK / npm and add the stripe package. Then, under Tools, Create tool, SDK / npm package, make tools for listing payouts, charges and refunds (see Turn a code library into tools).
  2. Keep the key safe. Save the Stripe key in Credentials; the tools read it when they run, never in a prompt.
  3. Connect the ledger. Open APIs, click Connect an API, pick OpenAPI / Swagger, give its description link and click Connect API. If it is a single call, create an HTTP tool instead.
  4. Create the assistant. Open Agents, click Create agent and switch to Autonomous. In Instructions, write: “Get yesterday’s payouts and charges, match them to the ledger by amount and reference, and report only what doesn’t match.” Pick the tools under Tools and APIs.
  5. Keep it read-only. On its Constraints tab, add “Never create or change a charge or refund”. The read-only Stripe key is what makes sure of it.
  6. Run it daily. On its Overview tab, turn on Schedule with an interval of 1440 minutes, and have it send the report with a Slack or email tool, or to your own address through the Webhook card.

Ideas

  • Let it propose a correcting ledger entry and ask a person to approve it first (see Approvals).
  • Turn on verification so a second model checks each flagged exception.
  • The same works for other payment providers with an API or an npm package.
Ask your databaseContract review