Docs / Data Retention and Security Basics

Reference

Protect payout evidence and retain what reviewers need

Allocora handles source revenue, payout rules, calculation runs, statements, exports, and audit evidence. Treat that data as sensitive finance operations material.

Details

What to know

Security basics

Use workspace permissions, scoped API keys, and careful export handling to reduce unnecessary access to payout data.

  • Limit administrator and API-key access to trusted users.
  • Store API keys only in server-side secret storage.
  • Share statements and exports only after calculation review.
  • Use audit history when investigating setup or review changes.

Retention basics

Retain source, calculation, statement, and export evidence according to your own finance, tax, legal, and customer-support obligations.

  • Keep source import identifiers and files for periods you may need to explain later.
  • Retain rule history and calculation output for dispute review.
  • Keep downstream payment proof in the payout or accounting system that moved money.

Reference Tables

Fields and checks

Evidence to retain

Use this as a practical retention checklist for payout calculation workflows.

Evidence Why it matters Where to verify
Revenue import source Proves the basis used for calculations. Revenue sources, import history, or retained source files.
Rule history Explains rates, splits, effective dates, and changes. Rule versions and audit history.
Calculation run output Shows reviewed allocation totals and exceptions. Calculation run detail and exports.
Statements and payout exports Supports payee questions and downstream handoff. Statement/export records and retained files.

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.