Allocora
Docs / Quickstart: Import Revenue Data

Quickstart

Import revenue data without losing calculation control

Revenue rows are the source facts Allocora evaluates. Import them carefully so every calculation can be traced back to the original source.

Start Free Try Sample Data

Before You Begin

  • Prepare one file for the next distinct statement period and confirm its inclusive start and end dates.
  • Confirm the file includes dates, amounts, currency, product context, and source identifiers.
  • Use a test workspace first if the import format is new.

Expected Result

Imported revenue rows that can be mapped, reviewed, and evaluated by payout rules without editing historical source data in place.

Steps

Follow this path

Each step keeps source revenue, rules, calculation output, and statement evidence in a reviewable sequence.

  1. 01

    Open Revenue Sources and choose the existing CSV/XLS/XLSX source that owns this statement history.

  2. 02

    Choose Import next statement period, enter the inclusive period dates, and upload the file.

  3. 03

    Review the detected template version, column mapping, row summary, currency, and source identifiers before confirming.

  4. 04

    Open Import History to verify the retained period, SHA-256 fingerprint, row outcome, retry lineage, and finalization audit evidence.

  5. 05

    Resolve unmatched products and Import Suspense issues, then run readiness checks before creating a calculation run.

Details

What to know

Keep recurring statements on one source

A CSV/XLS/XLSX source keeps multiple retained import batches. Each accepted batch has its own statement period, file fingerprint, template and mapping snapshot, row provenance, status, and audit evidence.

  • Allocora accepts a distinct non-overlapping later period on the same source.
  • The exact same file is blocked for that source even if its filename changes.
  • A pending, processing, or not-yet-finalized batch must finish before the next batch starts.
  • A failed atomic import commits no financial rows and can be retried from its stored artifact with linked retry history.
  • Older completed imports without a period must be classified once in Import History before another batch can be admitted.

Good import hygiene

Treat source revenue as append-only evidence. Corrections should arrive as refunds, adjustments, or new import rows instead of editing historical rows in place.

  • Keep raw external IDs stable; Allocora also records the batch, source row number, and versioned row fingerprint for provenance.
  • Separate test data from production data.
  • Confirm currency before mixing rows into a calculation period.
  • Map external product identifiers before running allocation rules.

What happens after import

Allocora does not pay anyone after import. It prepares governed revenue rows that can be evaluated by rules in a calculation run.

  • Unmapped rows should be resolved or intentionally ignored.
  • Refunds and adjustments should be reviewed for sign and source context.
  • Calculation readiness checks help avoid incomplete runs.

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