Marketplace Billing: Revenue Splits, Partner Payouts, and Multi-Party Invoicing

Executive Summary

Marketplaces and platforms face billing challenges that traditional SaaS companies don't: they must bill customers, split revenue with partners, manage payouts to multiple parties, and handle tax obligations across the chain — often in real time. A single customer transaction can involve the platform, one or more sellers, payment processors, and tax authorities, each with their own share of revenue.

Lago provides open-source billing infrastructure designed for these problems, with native revenue-share capabilities, percentage-based charges, and multi-entity support — reducing time‑to‑cash and operational billing errors. Lago handles high-volume metering (1M events/sec), invoices $829M monthly (Oct 2025), and maintains 99.9% historical uptime while serving customers like PayPal and Mistral AI.

This guide covers architecture, implementation patterns, and operational considerations for building marketplace billing systems that scale.

What you'll learn:

• How marketplace billing differs from standard SaaS billing
• Revenue split models and how to implement them
• Multi-party invoicing (who invoices whom, and why it matters)
• Tax implications of marketplace transactions
• Payout management and settlement timing
• Architecture patterns for marketplace billing at scale

Who this is for:

• Engineering teams building marketplace or platform products
• Finance leaders managing multi-party revenue flows
• Product managers designing platform monetization strategies
• Fintech companies building payment or banking-as-a-service products

---

SaaS pricing models — why they matter for marketplaces

Choosing the right saas pricing models affects seller economics, customer acquisition, and platform revenue recognition. Common models that map directly to marketplace flows include flat-rate subscription, tiered, per-seat, usage-based, and hybrid models (subscription + usage). Recent benchmarks show a shift toward value- and usage-based pricing: 78% of surveyed companies adopted value-based pricing and 56% now use usage-based models in 2025 [2]. For implementation patterns and examples of billing models, see Lago's guide to billing models and SaaS usage-based billing. Lago integrates these models into marketplace flows to automate revenue splits and invoicing.

Key takeaways:

• Usage and hybrid saas pricing models align platform incentives with seller/customer value and are increasingly common [2].
• For practical mapping of models to implementation (events, tiers, thresholds), refer to Lago's resources on billing models and SaaS usage-based billing.

---

What Makes Marketplace Billing Different

In traditional SaaS, the billing relationship is straightforward: the company charges the customer, collects payment, and recognizes revenue. Marketplace billing adds layers of complexity.

Key differences:

• Multiple revenue participants. A purchase often involves the platform (commission), the seller/partner (payout), and potentially sub-partners, affiliates, or resellers.
• Gross vs. net revenue recognition. Does the platform recognize the full customer payment (gross) or just its commission (net)? This affects P&L, taxes, and regulatory treatment.
• Multi-directional invoicing. The platform may invoice the customer; the seller may invoice the platform; the platform may invoice the seller for fees — each with different tax and currency treatment.
• Payout timing and cash flow. Platforms may collect immediately but pay sellers on delayed schedules, creating float and operational complexity.

---

Revenue Split Models

Model #1: Commission-Based (Take Rate)

How it works: The platform takes a percentage of every transaction; the rest goes to the seller.

Component	Amount
Customer pays	$100.00
Platform commission (15%)	$15.00
Seller receives	$85.00

Variations:

• Flat percentage (e.g., 15% of all transactions)
• Tiered percentage (e.g., 12% up to $100K/month, 10% above)
• Category-specific (e.g., 20% for digital goods, 10% for physical)

Implementation considerations:

• Track gross transaction volume per seller
• Calculate commission per transaction or per billing period
• Generate invoices for platform fees and seller statements
• Model commission as a percentage charge in the billing engine to keep logic declarative (avoid hard-coding in application business logic)

Example code and billing event patterns are unchanged from standard implementation (see original snippets).

Model #2: SaaS Fee + Transaction Commission (Hybrid)

How it works: Sellers pay a monthly subscription PLUS a per-transaction commission.

Component	Amount
Platform subscription	$99/month
Transaction commission (2%)	Variable
Payment processing (pass-through)	2.9% + $0.30

Why it works:

• Subscription covers platform costs (predictable MRR)
• Commission aligns platform incentives with seller success
• Payment processing fees passed through transparently

Implementation note: send gross transaction events to the billing engine and model the subscription + percentage charge there to centralize revenue recognition and invoicing.

Model #3: Seller Subscription Tiers (Feature-Gated)

How it works: Sellers choose a tier that unlocks features and determines commission rates.

Tier	Monthly Fee	Commission	Features
Starter	Free	20%	Basic listing, standard support
Growth	$49/month	12%	Analytics, priority placement
Pro	$199/month	8%	API access, custom branding
Enterprise	Custom	5%	Dedicated support, SLA

Why it works:

• Predictable platform revenue and upgrade levers
• Lower commissions reward high-volume sellers
• Feature gating drives upsell motion

Implementation: model tiers as plans with subscription charges and attach commission rules per plan in the billing configuration.

Model #4: Revenue Share (Partnership Model)

How it works: Revenue is split among platform and partners based on contribution.

Participant	Share	Basis
Platform	30%	Infrastructure, billing, payments
Technology Partner	40%	Software/service delivery
Reseller	20%	Customer acquisition
Support Partner	10%	Implementation, support

Why it works:

• Aligns incentives across participants
• Scales with revenue growth

Implementation: support configurable split rules, percentage or line-item based splits, and partner payout tracking separate from customer billing.

---

Multi-Party Invoicing: Who Bills Whom

Pattern #1: Platform as Merchant of Record

The platform invoices the customer, is legally responsible for the transaction, handles refunds, and manages tax collection. This simplifies customer experience and centralizes tax remittance but usually leads to gross revenue recognition.

When implementing: integrate payment processor features (e.g., Stripe Connect for Connect-style flows) and a tax provider for automated remittance [3].

Pattern #2: Seller as Merchant of Record (Facilitated)

The seller invoices the customer; the platform facilitates payment and bills the seller for platform fees. This supports seller autonomy and typically leads to net revenue recognition for the platform.

Pattern #3: Hybrid (Split Invoicing)

Both platform and seller appear on the customer's invoice, useful when transparency is required for enterprise customers or regulation. Billing systems should support itemized invoices, credit notes, and correlated seller statements.

---

Technical Architecture for Marketplace Billing

Transaction Flow (concise)

1. Customer places order
2. Platform calculates splits (commission, seller payout, tax)
3. Payment collection (charge customer; optionally hold in escrow)
4. Invoice generation (customer invoice; seller fee invoice)
5. Payout processing (seller payouts, tax remittance)
6. Revenue recognition (gross vs. net per accounting policy)

Data Model (example SQL)

(Original SQL snippet retained — core tables: transactions, revenue_splits, payouts, seller_invoices.)

Billing System Integration (concise)

• Track customer-side usage events for billing
• Track seller-side fee events as subscription usage
• Batch payouts and settlement processing
• Use tax provider integrations and PSP connectors for automated calculations and payments

For payment orchestration patterns and PSP choices, see Lago’s guide to payment gateways.

---

Tax Considerations for Marketplace Billing

Marketplace tax rules vary by jurisdiction. Key decision: who collects and remits tax (marketplace facilitator vs. seller). Many US states require marketplace facilitator collection; EU VAT rules apply for certain B2C transactions. Integrate a tax provider that supports marketplace rules and automated remittance to reduce compliance risk.

Best practice: calculate tax on full customer price using a tax provider; keep seller statements and platform invoices consistent with the chosen merchant-of-record model.

---

Revenue Recognition: Gross vs. Net

Decision drivers (ASC 606 / IFRS 15 style indicators):

• Control over price and fulfillment → principal (gross)
• Agent relationship with limited control → agent (net)

Business impact:

• Gross recognition increases reported revenue and COGS; net recognition shows lower top-line but cleaner platform margin reporting. Consult accounting counsel for final treatment.

---

Payout Management and Refunds

Payout timing options: real-time, daily, weekly, monthly — choose based on seller needs and cash flow. Implement holds/reserves for fraud and refunds; common reserves are 5–10% released after 30–60 days for new sellers.

Refund strategies:

• Option C (clawbacks applied to future payouts) is common: implement seller balance adjustments and credit notes to keep ledgers clean.

See Lago’s deep dive on refunds, coupons, and credit notes for practical ledger patterns. Refunds, Coupons & Credit Notes: Why They Are Different

---

Scaling Marketplace Billing

• Batch event processing (hourly/daily aggregates) to reduce event volume
• Multi-currency billing: bill customer in customer currency, settle seller in seller currency, report in platform base currency; store exchange rates with transactions
• Seller self-service portal with earnings, invoice downloads, and tax docs reduces support significantly (case study: self-service reduced billing tickets ~80%)

Lago’s platform is built for high-throughput metering and complex hybrid pricing models to enable these outcomes at scale.

FAQ: Marketplace Billing

Q: Build vs. buy?

A: Unless billing is core IP, use a billing platform. Marketplace billing complexity typically requires 6–12 months to build and significant ongoing maintenance; modern billing platforms reduce time-to-cash and billing errors by centralizing revenue splits and tax logic [1].

Q: How to handle disputes?

A: Build a dispute flow that holds payouts, collects evidence, and adjusts seller balances via credit notes or balance adjustments.

Q: Seller chargebacks?

A: Define policy: who absorbs costs, how thresholds affect trust, and how to prevent via fraud detection.

Q: Reporting sellers need?

A: Transaction-level detail, monthly statements, tax documents (1099-K/VAT), real-time dashboard, and CSV/API exports.

Q: How to price take rates?

A: Benchmark by category (example ranges):

• Digital marketplaces: 15–30%
• Service marketplaces: 15–25%
• B2B marketplaces: 5–15%
• SaaS marketplaces: 10–20% (often with subscription fees)

---

Conclusion & Recommendations

Marketplace billing compounds the complexity of saas pricing models with multi-party splits, tax, and settlement requirements. Principles for success:

• Decide merchant-of-record early (affects tax and revenue recognition)
• Model revenue splits in the billing layer (not application code)
• Automate tax calculation with a marketplace-aware tax provider
• Expose seller self-service to reduce support and accelerate payouts

Lago’s open-source billing platform consolidates hybrid and usage-based saas pricing models, revenue-share rules, and multi-entity invoicing to speed time‑to‑cash, reduce billing errors, and scale operations. Lago’s developer traction and reliability (9,176 GitHub stars; $829M invoiced monthly, Oct 2025) demonstrate production readiness.

Start building or modernizing marketplace billing with Lago: Lago

---

Related Resources

• 7 billing models you need to know if you work on pricing
• SaaS Billing Systems That Handle Complex Pricing Models
• Partner Billing deep dive

Call to action: For architecture review, migrations, or pilot projects, contact Lago via the homepage: Lago