Stripe Connect Platform Reporting Guide

Stripe Connect powers the payments infrastructure behind marketplaces, platforms, and multi-vendor businesses. From ride-sharing apps to freelancer marketplaces to SaaS platforms with integrated payments, Connect handles the complexity of splitting money between multiple parties. But that complexity makes reporting significantly harder than standard Stripe reporting.

This guide covers how to build accurate reports for Stripe Connect platforms, including platform fee tracking, connected account revenue, payout reconciliation, and the metrics that matter for platform businesses.

How Stripe Connect Works (Reporting Perspective)

In a Stripe Connect setup, there are three parties involved in every transaction:

• The customer — who pays for a product or service
• The connected account — the seller, driver, freelancer, or vendor who fulfills the order
• The platform — your business, which facilitates the transaction and takes a fee

Stripe Connect supports three charge models: direct charges, destination charges, and separate charges and transfers. Each model determines where the charge is created and how funds flow, which directly impacts how your financial reports are structured.

Platform Revenue: What You Actually Earn

The most common mistake in Connect reporting is confusing gross transaction volume with platform revenue. If a customer pays $100 for a service and $85 goes to the connected account, your platform revenue is $15 — not $100. This distinction is critical for:

• Financial statements — reporting $100 when you earned $15 inflates revenue
• Tax obligations — you are taxed on your platform fee, not the gross volume
• Unit economics — customer acquisition cost should be measured against platform revenue, not GMV
• Investor reporting — VCs understand the difference and will question inflated numbers

Your Stripe Connect reports need to clearly separate gross merchandise value (GMV), platform fees (your actual revenue), and connected account payouts. For more on structuring financial reports, see our Stripe invoice reporting guide.

Tracking Platform Fees

Platform fees can be structured in several ways, and your reporting must account for each:

• Percentage-based fees — a fixed percentage of each transaction (e.g., 10% of every booking)
• Flat fees — a fixed dollar amount per transaction
• Tiered fees — different rates based on volume, seller tier, or product category
• Subscription fees — monthly fees charged to connected accounts for platform access

The Stripe Connect documentation explains how application fees work at the API level. From a reporting perspective, you need to aggregate these fees across all connected accounts to calculate your total platform revenue, then break them down by fee type, by connected account, and over time.

Connected Account Reporting

As a platform, you need visibility into connected account health — not just for your own reporting, but because their problems become your problems. Key connected account metrics include:

• Active accounts — how many connected accounts processed at least one payment this month
• Account growth rate — new connected accounts added over time
• Revenue per account — average GMV and platform fee per connected account
• Account churn — connected accounts that stop transacting
• Dispute rate by account — which sellers generate the most chargebacks

These metrics function similarly to subscription metrics for SaaS businesses. Account churn is analogous to customer churn, and revenue per account mirrors ARPU. Our guide on Stripe subscription billing covers these parallels in more detail.

Payout Reconciliation

Payout reconciliation is one of the most complex aspects of Connect reporting. Money flows from customers to your platform, then from your platform to connected accounts. The timing of these flows rarely aligns:

• A customer pays on Monday
• Your platform receives the funds (minus Stripe fees) on Wednesday
• The connected account receives their payout (minus your platform fee) on Friday

This timing mismatch creates reconciliation challenges. At any given moment, you need to know how much money is in transit, how much is held on the platform, and how much has been paid out to connected accounts. The Stripe Connect payouts documentation covers the technical mechanics, but the reporting layer requires careful aggregation.

Connecting payout data to your broader cash flow management process is essential for platforms that need to maintain liquidity while managing funds for hundreds or thousands of connected accounts.

Platform-Specific Financial Metrics

Beyond standard revenue metrics, platform businesses should track:

• Take rate — platform revenue divided by GMV. This is the single most important metric for marketplace businesses.
• GMV growth — total transaction volume across all connected accounts
• Liquidity — for two-sided marketplaces, how quickly supply matches demand
• Net revenue retention by account — whether connected accounts grow their volume over time
• Fraud and dispute costs — total losses from chargebacks, refunds, and fraud across the platform

Common Connect Reporting Mistakes

Reporting GMV as Revenue

This is the most common and most dangerous mistake. If your platform processes $1M in GMV with a 10% take rate, your revenue is $100K, not $1M. Misreporting this can create legal, tax, and investor relations problems.

Ignoring Stripe Processing Fees

Platform fees are not pure profit. You still pay Stripe’s processing fee on each transaction. If your take rate is 10% and Stripe charges 2.9% + 30 cents, your net margin per transaction is significantly lower than 10%.

Not Tracking Negative Balances

When refunds or chargebacks occur on connected accounts with insufficient balances, the platform may absorb the loss. Tracking negative connected account balances and your exposure is critical for financial health.

Missing Cross-Border Complexity

If your connected accounts span multiple countries, currency conversion, local tax obligations, and country-specific payout schedules add reporting complexity. Each connected account’s local currency must be tracked and reconciled against your platform’s reporting currency.

Building Your Connect Reporting Stack

Stripe’s built-in dashboard provides basic Connect reporting, but most platforms quickly outgrow it. You need reporting that aggregates data across all connected accounts, calculates platform-specific metrics like take rate and GMV, and provides the reconciliation tools to ensure every dollar is accounted for.

StripeReport connects to your Stripe Connect account and provides platform-level reporting out of the box. Track your real platform revenue, monitor connected account health, and reconcile payouts without building custom reporting infrastructure. For a broader look at invoice-level reporting, start there and layer on Connect-specific views.