CSV column reference for revenue imports

Use this reference when preparing revenue files for Allocora. Column names can vary by source, but each row should contain enough stable information to trace calculations later.

Start Free Try Sample Data

Details

What to know

Import principle

Every revenue row should be traceable back to its original source system and understandable during a later payout review.

Prefer stable external identifiers over row numbers.
Enter the statement start and end dates in the import flow; the period belongs to the batch and is not a CSV row column.
Keep source files by period so later batches and failed retries are explainable.
Use metadata columns for rule scope only when product or source fields are not enough.
Allocora records the batch ID, physical source-row number, and a versioned row fingerprint after acceptance.

Reference Tables

Fields and checks

Recommended revenue columns

Use these fields as the baseline for self-service import preparation.

Column	Required	Purpose
external_revenue_id	Yes	Stable source identifier used for traceability and duplicate review.
transaction_date	Yes	Date used to place the revenue row in the correct close period.
amount	Yes	Revenue, refund, or adjustment amount before allocation.
currency	Yes	Currency code used to avoid mixing incompatible rows in one calculation.
revenue_type	Recommended	Use sale, refund, or adjustment. A selected template can normalize its documented source labels; any other non-empty value fails validation.
external_product_id	Recommended	Product or catalog identifier used for mapping and rule matching.
payee_hint	Optional	Source-side partner, seller, creator, or affiliate reference when available.
metadata_*	Optional	Extra dimensions such as country, channel, campaign, contract, or source system.

Troubleshooting

If this does not work

Rows import but do not calculate.

Check product mapping and rule readiness. Imported rows still need matching products, payees, and rules before they produce allocations.

Refunds increase a payout total.

Review the amount sign and revenue type. Refund rows should usually reduce the allocation basis for the relevant period or original transaction.

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