Workspace checkpoint
The workspace should show seeded revenue sources, products, payees, rules, and at least one calculation run tied to the sample workflow.
Tutorial
Complete your first payout calculation with sample data
This tutorial walks through a safe first run: create a workspace, load sample data, inspect rules, run a calculation, generate a statement, and identify the export evidence you can use later.
Before You Begin
- An Allocora account or the ability to create a free workspace.
- A test workspace is recommended. Do not start with production revenue rows.
- Ten to fifteen minutes to complete the sample-data walkthrough.
Expected Result
You will finish with a sample calculation run, payee-level allocation totals, at least one generated statement, and a clear understanding that downstream payout tools still move the money.
Steps
Follow this path
Each step keeps source revenue, rules, calculation output, and statement evidence in a reviewable sequence.
-
01
Choose Start Free and create a workspace.
-
02
In onboarding, select a sample-data workflow such as SaaS Affiliate Payouts or Marketplace Seller Payouts.
-
03
Open Revenue Sources and confirm the seeded source contains sample sale, refund, or adjustment rows.
-
04
Open Products and confirm sample revenue rows are mapped to products or catalog items.
-
05
Open Payees and confirm the sample partners, sellers, creators, or affiliates are present.
-
06
Open Rules and review which payee receives an allocation, which rows qualify, and which rate or split applies.
-
07
Run or open the sample calculation run for the current sample period.
-
08
Review totals, exceptions, unmapped rows, and payee-level allocations before generating statements.
-
09
Generate a sample statement for one payee and inspect the source rows, allocations, adjustments, and total.
-
10
Export statement or payout data only after the calculation output looks explainable.
Screen Checkpoints
What you should see
Run checkpoint
The calculation run should show period totals, payee allocations, review status, and any unresolved blockers before statement generation.
Statement checkpoint
The statement should explain the payee total with source rows or allocation lines instead of showing only a final amount.
Details
What to know
Why sample data first
Sample data lets you learn the workflow without exposing production revenue or sending incorrect payout information downstream.
- You can see the object model before importing your own files.
- You can compare rules and calculation output without changing live close work.
- You can reset or repeat the walkthrough when testing another use case.
Review before statements
Statements should come from reviewed calculation output. If a total looks wrong, resolve the mapping, rule, or source-row issue before creating payee-facing evidence.
- Review unmapped products before trusting totals.
- Check refunds and adjustments for expected sign and period.
- Confirm each payee has the rules you expect.
Reference Tables
Fields and checks
First-run checkpoints
Use this table to confirm the tutorial produced the expected evidence.
| Area | Check | Expected result |
|---|---|---|
| Onboarding | Sample workflow selected | Workspace contains seeded payout data. |
| Revenue | Source rows reviewed | Rows have dates, amounts, currency, and product context. |
| Rules | Allocation logic inspected | A reviewer can explain who receives each allocation. |
| Run | Output reviewed | Totals, exceptions, and payee allocations are visible. |
| Statement | Payee statement generated | The statement explains the calculated obligation. |
Troubleshooting
If this does not work
The sample-data option is not visible.
Open the onboarding flow from the workspace start page or create a new test workspace and choose a sample workflow before importing files.
The calculation has unmapped rows.
Map the external product identifier to an Allocora product, then rerun or reopen the calculation readiness checks.
A payee total looks wrong.
Check the matching rule scope, rate, effective dates, and refund or adjustment rows before generating statements.
Feedback
Was this page helpful?
Send a note if a step is unclear, missing, or out of date.
Apply this in a workspace
Start free, use sample data, then replace examples with your own revenue rows when the workflow is clear.