Docs / Multi-Payee Revenue Split Guide

Guide

Split revenue across multiple payees with audit-ready rules

Multi-payee revenue splits need deterministic calculations when more than one partner, seller, creator, or contractor shares the same source revenue.

Details

What to know

Split design

Start by deciding whether the split is product-based, partner-based, source-based, or metadata-based.

  • Use payees for each recipient of calculated payout obligations.
  • Use products or metadata to scope which rows should split.
  • Use versioned rules so historical periods stay reproducible.
  • Review remainder amounts so the split math is explainable.

Operational review

Review the run before exporting. A split is only useful if finance can explain it later.

  • Confirm all intended payees are included.
  • Inspect any rows without a matching rule.
  • Compare totals against the source revenue period.
  • Export statements and payout files after review.

Reference Tables

Fields and checks

Worked revenue split example

Use this example when more than one payee shares the same source revenue.

Input Example value Calculation note
Eligible order revenue USD 2,400.00 One marketplace order or grouped order rows.
Seller share 70% Configured as an allocation to the seller payee.
Creator share 10% Configured as a second allocation to the creator payee.
Platform retained amount 20% Left as remainder or modeled as an internal payee, depending on workflow.

Spreadsheet before / Allocora after

Use this comparison to prevent split logic from becoming hidden in workbook formulas.

Spreadsheet before Allocora after Why it matters
One row is duplicated for each recipient. One revenue event can be evaluated by a multi-payee rule. The source amount remains clear while allocations are separated.
Split percentages are embedded in formulas. Allocations are explicit rule fields. Reviewers can see why each payee received a share.
Remainders are checked manually. Run output shows allocation totals and remainder context. Close review can catch missing or excess allocation.
Exports are hand-assembled. Exports come from reviewed statement-ready output. Downstream payout files stay tied to the calculation run.

Examples

Sample CSV rows and formula

These rows show one order that can be split between multiple payees.

Sample marketplace CSV row

external_revenue_id,transaction_date,amount,currency,revenue_type,external_product_id,metadata_order_id,metadata_seller_id,metadata_creator_id
order_9001,2026-05-07,2400.00,USD,sale,marketplace_item_44,order_9001,seller_22,creator_08

Simple split formula

seller_due = 2400.00 * 0.70
creator_due = 2400.00 * 0.10
platform_remainder = 2400.00 - seller_due - creator_due

Feedback

Was this page helpful?

Send a note if a step is unclear, missing, or out of date.

Email Support

Apply this in a workspace

Start free, use sample data, then replace examples with your own revenue rows when the workflow is clear.