Generate a statement from reviewed calculation output

Statements should come after a reviewed calculation run. They turn calculation output into payee-facing evidence without changing money movement.

Start Free Try Sample Data

Before You Begin

Complete or open a calculation run for the close period.
Resolve unmapped products, unmatched rules, and unexplained exceptions.
Confirm the output is ready for payee or finance review.

Expected Result

A statement generated from reviewed calculation output, plus settlement-snapshot-bound Close Package V1 or payment-ready export evidence for downstream accounting or payout workflows.

Steps

Follow this path

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

01
Open a completed calculation run.
02
Review totals, exceptions, payee allocations, and unmapped rows.
03
Lock the run once the output is final enough for statements and payment-ready exports. Locking freezes the versioned settlement snapshot used by every downstream amount.
04
Generate statements for the selected payees.
05
Download the completed statement ZIP; the run page confirms the request before the browser receives the attachment.
06
Export Close Package V1 ZIPs or payment-ready payout CSV presets for downstream review.

Details

What to know

Statement readiness checklist

Do not generate payee-facing statements until source rows, product mappings, and rule output have been reviewed.

The calculation run completed without unresolved blockers.
The close period and source selection are correct.
Payee totals match the expected review view.
Adjustments and refunds have understandable context.

What a statement represents

A statement explains calculated obligations. It is not proof that money has already moved unless your downstream payment workflow adds that status.

Use statements for payee transparency.
Use Close Package V1 for finance review, payout rail handoff, and close evidence.
Review the three-decimal canonical obligation beside the currency-minor-unit settled payout, rounding delta, settlement status, and exclusion reason.
Use audit history when a payee questions a calculated amount.

How grouped tier adjustments reach statements

For a retroactive grouped tier, Allocora keeps revenue-linked allocation lines and the payee-level catch-up or true-down as separate evidence. The canonical gross ledger combines them exactly once before contract economics and statement totals are calculated.

The current-period base remains tied to the revenue rows that produced it.
A non-zero retroactive tier adjustment appears as its own calculation component with snapshot evidence.
Gross allocated includes both sources exactly once; reserve, recoupment, clawback, hold, and minimum-threshold logic then determines net payable.
If gross for a payee is negative, Allocora records the unpaid amount as refund/clawback carry with zero net payable. Later positive gross consumes that carry first, and a zero-activity run preserves the balance as explicit evidence.
Configured opening, advance, expense, and clawback balances initialize the first authoritative payee/currency period. Later periods start from the prior canonical locked component closings, even when the payee profile has a newer version.
Each component exposes start, applied, and end values. Total Closing Balance is the sum of the closing balance components; current-period reserve and threshold holds remain separate until a release ledger exists.
Statements, exports, reconciliation, and evidence bundles use the same canonical gross-ledger projection and immutable settlement snapshot. Gross-accrual journals use the gross projection directly; payable-ready journals use included settled liability, preserve excluded canonical liability, and add an explicit rounding-adjustment expense leg when required. Replacement and adjustment run lineages use Adjustment Delta exports and are blocked from journal CSV until delta-aware journal entries are supported.

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.

Start Free Browse Docs