Stripe transactions vs payouts

When moving Stripe data into accounting software, one of the first decisions is what level of activity you want to import.

You can represent the individual transactions that happen inside Stripe, or focus primarily on the payouts Stripe sends to your bank account.

BalanceFlow's Stripe workflows are designed around individual transaction activity. This preserves the underlying payments, refunds and fees instead of reducing a period of Stripe activity to its eventual bank deposits.

Transactions and payouts represent different things

A customer payment doesn't normally move directly from the customer into your bank account.

Stripe processes the transaction first. Fees can be deducted, payments can be refunded, and multiple transactions can accumulate before Stripe sends a payout to your bank.

A simplified flow looks like:

Customer transactions → Stripe balance → Stripe payout → Bank account

That distinction matters when deciding what data to import.

Importing payouts

A payout represents money transferred from Stripe to your bank.

Suppose Stripe processes these transactions:

If you work only from the bank side, the activity may appear simply as a $145.20 deposit.

That's useful for confirming what reached the bank, but it doesn't describe everything that produced the deposit.

The two customer payments and $4.80 of processing costs are no longer visible as separate accounting activity.

Importing individual transactions

A transaction-level workflow preserves that detail.

Instead of starting with the $145.20 payout, you work with the underlying Stripe activity:

Together, those transactions explain the $145.20 that Stripe can later pay out.

This is the approach BalanceFlow recommends for its Stripe import workflows.

The payout still matters, but it serves a different purpose: it represents the transfer of money from Stripe to your bank rather than the original customer activity.

Why BalanceFlow focuses on transactions

Transaction-level data preserves more information.

You can keep individual payments visible, account for processing fees separately, retain refunds, and trace activity back to individual Stripe records.

It also avoids treating the amount deposited into your bank as though it were necessarily the original sale amount.

The trade-off is that transaction-level accounting requires more preparation. A Stripe export contains more information than a simple QuickBooks bank transaction import expects, and payments, refunds and fees need to be represented consistently.

That's the part BalanceFlow is designed to simplify.

See How to import Stripe transactions to QuickBooks for the complete workflow.

Net transactions vs separate fees

Transaction-level importing doesn't necessarily mean every component needs its own row.

BalanceFlow supports two approaches.

With a Net import, each Stripe transaction remains a single output row. The payment, refund and fee information is used to calculate the appropriate values without creating separate fee transactions.

With a Split Fee import, the underlying components are represented separately, allowing the payment and processing fee to be handled independently.

If you want fees recorded separately, see How to split Stripe fees for QuickBooks import.

Where payouts fit

Importing individual transactions doesn't make payouts irrelevant.

If you use a clearing account for Stripe, the transaction activity changes the balance held by Stripe. When Stripe sends a payout, that payout represents a transfer from the clearing account to your actual bank account.

In simplified form:

Customer payment → increases Stripe balance

Stripe fee or refund → reduces Stripe balance

Stripe payout → transfers Stripe balance to your bank

This gives the payout a clear role without using it as a substitute for the transactions that created it.

For more on this approach, see Using a clearing account for Stripe reconciliation.

Which data should you export?

For BalanceFlow's built-in Stripe templates, start with the transaction-level Stripe export rather than a list containing only payouts.

The resulting CSV can then be transformed into the structure required by your accounting workflow.

See Prepare a Stripe CSV for QuickBooks import for the fields and export process.

The practical distinction is simple: transactions explain what happened in Stripe; payouts explain when the resulting balance moved to your bank.

For accounting workflows where you want to preserve the underlying activity, BalanceFlow is built around the former.