Reference
CSV imports work best when each row has a stable source identifier, date, amount, currency, product context, and enough metadata for payout rules.
Details
Column names can vary by source, but clean imports usually include these fields.
Review mapping and validation output before creating a calculation run.
Reference Tables
Use these checks before uploading a file for calculation work.
| Check | Why it matters | Fix before upload |
|---|---|---|
| Stable row identifiers | Supports duplicate review and audit traceability. | Add or preserve a source transaction ID. |
| Single intended currency | Avoids accidental mixed-currency calculation periods. | Split files by currency when needed. |
| Product context present | Allows rules to match revenue rows correctly. | Add product ID, SKU, catalog ID, or metadata. |
| Refund signs reviewed | Prevents refunds from increasing payout totals. | Confirm negative signs or refund type mapping. |
Troubleshooting
Open mapping review, resolve external product identifiers, and confirm the relevant rules are active for the period.
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.
