A Stripe payout reaches the bank as one number. Inside it are the charges,
the refunds, Stripe’s fees and any disputes. Zeno reads them from Stripe and
records each payout as one deposit that adds up to exactly what reached the
bank. Stripe works with QuickBooks Online books.
The result: each payout is one entry on its own bank line, with sales, refunds and fees where your books need them.
Connect Stripe
Start on Connections
Under Clients → Connections, pick the client and press Connect Stripe. Stripe asks you, or the
client, to install Zeno: a read-only app. It reads payouts, the
transactions in them, charges, disputes, invoices and customers, and it
cannot move money or change anything in Stripe.
Choose where the money goes
Once per client: the bank account payouts land in, and an account for
sales, refunds, Stripe fees, disputes and adjustments. Choose them on the
Stripe card, or ask your AI to set them from the client’s chart; Zeno refuses an account that is not there and
changes nothing. A dispute’s own fee goes with Stripe’s fees.
What Zeno reads
The last 90 days of payouts the first time, then new payouts several times a
day, unattended. To read them sooner, ask your AI to sync: it reads the
client’s bank feeds, Stripe and Square at once. A payout shows in Bank feeds, on the bank line it made, with its split and its state: still being
read, ready to plan, planned, or posted. A payout made by hand in Stripe has
no breakdown, so Zeno leaves it for you to record.
Charges that pay invoices
A charge inside a payout is not always a new sale. When it pays an invoice
already in the books, or a payment someone already recorded (QuickBooks
Payments, a sync app, or by hand), Zeno settles it instead of booking the
income twice. A recorded payment still in Undeposited Funds is deposited by
the payout. An open invoice the charge pays gets a payment recorded against
it, and the payout deposits that. Zeno matches a charge by the invoice number
it carries, or by the customer and the exact amount, and only when exactly one
invoice or payment fits. When two could fit, the charge stays a sale and the
plan names both, so you decide. Everything else is booked as sales.
For a client who never invoices, set Charges to Charges are sales on the connection’s card, or ask your AI to.
Your AI sees what Zeno sees
Ask your AI to open a payout and it gets every transaction Zeno read from
Stripe: the ids, amounts and fees, and what each charge carries (the description, the invoice number, the customer’s name and email, metadata),
beside what Zeno proposes each charge settles. When a charge could pay two
invoices, or Zeno missed a match, tell your AI which one. It plans it that
way, Zeno checks it against the books, and you approve the plan as usual.
Plan them
Ask your AI to plan the client’s Stripe payouts. Each payout becomes one
deposit on the bank line it caused, so the line and the deposit are one
entry, not two. Nothing posts until a person approves the plan.
Zeno holds a payout back, and says why, when its bank line has not arrived
yet, and refuses one whose parts do not add up, is in another currency, or
is already in a plan.
When Stripe takes money from the bank instead, to cover refunds or fees
larger than the sales, that withdrawal is planned as a check from the bank
account, with each part on its own line.
Disconnect
Disconnect on Connections stops the reading and forgets Zeno’s
access. Payouts already read and anything posted stay. To revoke the app in
Stripe too, uninstall Zeno in the Stripe dashboard; if that happens first,
Connections shows Stripe as needing a reconnect. 
