Allocora
Docs / CSV Imports

Reference

Prepare CSV imports for governed payout calculations

CSV imports work best when each statement has a clear period and every row has a stable source identifier, date, amount, currency, product context, and enough metadata for payout rules.

Start Free Try Sample Data

Details

What to know

Import each statement as a retained batch

Reuse the same CSV source for each later statement. Enter the inclusive statement period before upload, review the preview, and confirm only after the period, mapping, template version, currency, and row summary are correct.

  • A later non-overlapping period is accepted on the existing source.
  • An exact replay or an inclusive overlap with an accepted batch is rejected.
  • Import History keeps the period, file fingerprint, template version, counts, retry lineage, finalization time, and audit event.
  • If a legacy completed batch has no period, classify it once from Import History before continuing.

Suggested columns

Column names can vary by source, but clean imports usually include these fields.

  • External revenue ID.
  • Transaction date.
  • Amount and currency.
  • Revenue type such as sale, refund, or adjustment.
  • External product identifier.
  • Optional metadata such as country, channel, partner, or contract reference.

Before you calculate

Review mapping and validation output before creating a calculation run.

  • Resolve unmapped product identifiers.
  • Open Import Suspense for blocked rows, duplicate IDs, suspicious spikes, or template mismatches that need review after the import job completes.
  • Confirm refunds and adjustments use the expected sign.
  • Keep sandbox files separate from production imports.

Reference Tables

Fields and checks

Minimum CSV checks

Use these checks before uploading a file for calculation work.

Check Why it matters Fix before upload
Statement period known Prevents two accepted batches from claiming the same close period. Confirm the inclusive first and last day covered by the statement.
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

If this does not work

The import finishes but the calculation run reports unresolved rows.

Open Import Suspense for the selected source, resolve or reprocess blockers, then confirm product mappings and active rules for the period.

Allocora says the file was already accepted.

Open Import History for the source and review the existing SHA-256 batch. Renaming the same file does not make it a new statement.

Allocora says the statement period overlaps.

Compare the inclusive start and end dates with accepted batches in Import History. Correct the period or upload the statement for the next distinct period.

The next import is blocked by a historical batch with no period.

Open Import History, enter that completed batch’s known historical period, save it once, then start the next non-overlapping import.

The batch is completed or failed but still says Finalizing.

Allocora is finishing suspense and audit evidence. The recovery task safely retries stale finalization without importing the statement rows again.

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