Know what happens after revenue data is imported

Imported revenue rows are source evidence for payout calculations. Allocora helps map, review, and calculate from them; it does not execute payments after import.

Start Free Try Sample Data

Details

What to know

Import behavior

Importing revenue creates or updates the source evidence available for mapping and calculation readiness review.

Rows need dates, amounts, currency, source identifiers, and product context to be useful.
External identifiers help detect duplicate source rows and support traceability.
Unmapped product identifiers should be mapped before calculation runs are trusted.
Sample data is for learning the workflow and should stay separate from production close work.

Corrections and review

Corrections should be explainable as refunds, adjustments, or new source rows rather than hidden changes to final payout totals.

Review refund and adjustment signs before calculating.
Resolve readiness blockers before generating statements.
Use audit history and retained source context when a payee questions a total.

Reference Tables

Fields and checks

Import behavior checklist

Use this checklist before relying on imported rows in a calculation run.

Behavior	Expected result	User action
Duplicate source IDs	Stable identifiers support duplicate review.	Keep source IDs consistent across imports.
Product mapping	Rows map to products or catalog items before rules can match.	Resolve unmapped identifiers before running calculations.
Refunds and adjustments	Negative or corrective rows affect the payout basis.	Review sign, type, date, and source context.
Sample data	Seeded rows help new users learn safely.	Reset or replace sample data before production close work.

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