Use cases · Money · Daily at 6:00 PM

Every payout matched to its invoice, every evening

Reconciliation slips because it is boring and it can wait. Then quarter-end arrives and a three-month-old discrepancy takes an afternoon to unwind.

Your Squad teammate closes each day at 6:00 PM on a visible schedule. It matches payouts against invoices, fees against expectations, and refunds against records, reading Stripe and QuickBooks directly. A clean day gets one quiet line in the activity feed. A mismatch gets a ticket while the trail is one day old.

The daily log files itself in Docs. Month-end close starts from a reconciled book, and your accountant gets a folder instead of a shoebox.

How it runs
01
Connect the money tools

Stripe for payouts, QuickBooks for the other side. Read access only; the teammate never writes to either.

02
It matches at 6:00 PM

Every payout is traced to its invoices. Fees and refunds are checked against expected amounts. The run timeline shows the work.

03
Clean days stay quiet

One line in the activity feed: matched, count, total. No report to read when there is nothing to say.

04
Mismatches become tickets

Both sides of the record, the difference, and the likely cause, in one ticket. Resolve it in the thread; the resolution is logged with the day.

05
Recurring causes get named

The processor that always settles a day late stops raising tickets once you confirm the pattern. The rule goes to memory with your name on it.

06
Close starts from done

Month-end pulls the daily logs from Docs into one reconciled summary. Hours, not days.

What lands on your desk
A mismatch, one day old
MISMATCH — Sep 2 payout

Stripe payout:        $8,412.60
Invoices matched:     $8,530.00
Difference:           -$117.40

Likely cause: refund on invoice #1371 ($99) plus a currency-
conversion fee on the Oslo order ($18.40). Both records attached.

If that reads right, tap confirm and I will log both against
their invoices.

[ Confirm ]  [ Something is off — dig deeper ]
What you get
  • Discrepancies surface in one day, not one quarter.
  • Every mismatch arrives with both records attached.
  • Known patterns stop raising noise once you confirm them.
  • A daily reconciliation log your accountant trusts.
Works with
StripeQuickBooksSheets

Your teammate connects through the integrations you approve, works on its own computer with its own browser, and asks you before anything irreversible.

Your first month
Day 0

You connect Stripe and QuickBooks. Read access only.

Day 1

The first 6:00 PM run matches the day clean. One quiet line in the feed. It feels like nothing; that is the point.

Week 1

The first mismatch ticket arrives with both records and the cause. Ninety seconds to resolve, same day it happened.

Month 1

Month-end close takes an afternoon-turned-hour: the dailies were already reconciled. Your accountant asks what changed.

Squads also run