This guide explains how manual payouts and top-ups in Stripe affect Per Payout mode within Summary Sync in Synder.
It applies only when:
- Stripe is used as the payment platform
- Your account is on Summary Sync, and per-payout mode is selected as the summary period option
- The clearing account shows unexplained differences
This guide does not apply to:
- other integrations (Amazon, PayPal, etc.)
- other sync modes (Per Transaction or Summary Daily/ Monthly)
How Per Payout mode works (Summary Sync — Stripe)
In Summary Sync with Per-Payout summary period, Synder groups transactions based on Stripe payouts. Each payout includes all related sales and all related fees.
Synder creates one summarized record including a single payout and all its corresponding transactions and fees.
You can view the following guides for a better understanding of the Summary Sync and Per-Payout mode:
How Summary Sync works
Per Payout mode synchronization
Summary Sync — aggregating data daily or per payout
Important Things To Know
Per-Payout mode relies on payouts reflecting actual transaction activity (sales minus fees). If the Stripe balance is adjusted manually, this relationship no longer holds. The most common cases are manual payouts and top-ups. In practice, this mode works best with automatic Stripe payouts, as manual balance changes can affect grouping and reconciliation.
Manual payouts
Manual payouts are payouts where the amount is selected manually in Stripe instead of using automatic payout scheduling.
Synder expects each payout to match the total of the underlying transactions. With manual payouts, the payout amount may not match transaction totals, and transactions may be partially included or excluded. As a result, Synder cannot correctly group transactions into the payout.
What to do
- Use automatic payouts in Stripe where possible
- Avoid manually selecting payout amounts
- If manual payouts are required, handle reconciliation manually
Top-ups
Top-ups are manual additions of funds to the Stripe balance. They are not customer payments and not revenue.
Per-Payout Summary mode works only with transaction-based balances. Top-ups increase the balance without being linked to sales or fees, so payouts may include amounts that Synder cannot match.
What to do
- Do not treat top-ups as sales
- Record them separately in the accounting system (e.g., transfer or adjustment)
- Do not expect Synder to include them in payout grouping
Troubleshooting
My payout amount doesn’t match the included transaction amount
This usually happens when the payout includes items not reflected as normal transactions (manual payouts, top-ups, adjustments, or currency effects).
What to do
- Compare the Stripe payout breakdown (gross, fees, refunds, adjustments) with the summary
- Check for manual payouts or top-ups in Stripe
I see transactions outside the date range I imported
In Per-Payout mode, summaries are built from the full payout content. A payout can include transactions with earlier transaction dates.
What to do
- Don’t remove them as “wrong date” immediately
- Verify they belong to the same Stripe payout
- If needed, re-import with a wider date range to include the full transaction list associated with the said payout.
I don’t see a payout summary for the dates I imported
This usually happens when the payout is not yet available, or the imported date range does not fully cover the payout activity.
What to do
- Wait until the payout is finalized in Stripe
- Re-import using a wider date range (include days or weeks before the payout date)
- If available, use the option to refresh or update summaries after import
Frequently asked questions
What if I use the invoice date as the transaction date?
- If you sync with an invoice date: Synder creates separate invoice summaries on invoice dates, while Per-Payout summaries handle payments, fees, and payouts. This means you will see invoice summaries on invoice dates and payout summaries on payout periods.
- If you sync with the payment date, no separate open‑invoice summaries are created. Instead, AR is affected inside per‑payout summaries when payments come in, and invoices are allocated by month rather than by day.
What happens if I enable Per Payout while Stripe payouts are set to Manual?
If you enable Stripe Per-Payout in Synder but your Stripe payouts are manual, Stripe will not provide payout‑linked balance transactions. Synder will not be able to generate per‑payout summaries. You will effectively see:
- No new Stripe per‑payout summaries, or
- Summaries that never leave “pending / not finalized” state.
Once you switch Stripe to automatic payouts, new payouts will start to form per‑payout summaries going forward. Historical manual payouts still won’t magically become proper per‑payout summaries because Stripe never exposed the necessary payout linkage.
Can I use Stripe Per Payout together with RevRec?
No. RevRec and Stripe Per-Payout are not compatible. RevRec groups Stripe payments into its own summaries, while Per-Payout relies on Stripe payout‑linked activity. Because of this, payments already grouped by RevRec cannot be re-grouped into per‑payout summaries.
How does Stripe Per-Payout work with my e-commerce platform (e.g., Shopify + Stripe)?
When Per-Payout is enabled, all Stripe payments that belong to Stripe payouts are included in Stripe per‑payout summaries. Your e‑commerce summaries will then include only non‑Stripe activities.
How to reconcile my manual payouts with the help of Synder?
Please refer to this guide for more information: How to Reconcile Manual Payouts
