Docs / Quickstart: Configure a Payout Rule

Quickstart

Configure payout logic as versioned rules

Rules tell Allocora how to allocate source revenue to payees. They should be explicit, versioned, and reviewed before a close period is finalized.

Before You Begin

  • Create or select the payee that should receive the allocation.
  • Map the products or source identifiers the rule should evaluate.
  • Know the rate, split, tier, floor, cap, or effective dates from the payout policy.

Expected Result

A versioned rule that explains who receives an allocation, which rows qualify, and which rate or split applies.

Steps

Follow this path

Each step keeps source revenue, rules, calculation output, and statement evidence in a reviewable sequence.

  1. 01

    Choose the payee or payee group that should receive the allocation.

  2. 02

    Select the product, source, metadata, or period scope for the rule.

  3. 03

    Enter the percentage, tier, split, floor, cap, or other supported payout logic.

  4. 04

    Set effective dates so prior periods keep their original logic.

  5. 05

    Simulate the rule before running a real calculation.

Details

What to know

Rule design principles

A payout rule should explain who gets paid, what rows qualify, which period it applies to, and how much is allocated.

  • Prefer narrow scopes over broad catch-all rules.
  • Use effective dates when terms change.
  • Use priority intentionally when more than one rule could match.
  • Run simulation before changing active payout logic.

Avoiding rule ambiguity

Ambiguous rules make payout reviews slower. Keep rule names and scopes specific enough for finance and operations teams to understand later.

  • Name rules after the contract or payout policy they represent.
  • Include product or source context when it matters.
  • Review conflicts before creating a calculation run.

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.