Reference
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.
Details
Every revenue row should be traceable back to its original source system and understandable during a later payout review.
Reference Tables
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 | Classifies the row as sale, refund, adjustment, credit, or other source event. |
| 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
Check product mapping and rule readiness. Imported rows still need matching products, payees, and rules before they produce allocations.
Review the amount sign and revenue type. Refund rows should usually reduce the allocation basis for the relevant period or original transaction.
Feedback
Send a note if a step is unclear, missing, or out of date.
Start free, use sample data, then replace examples with your own revenue rows when the workflow is clear.
