Use import templates to start from the right source shape

Import templates prefill column mappings from known source shapes before preview. They do not bypass validation, change revenue math, create payees, execute payouts, or prevent users from overriding a mapping before confirmation.

Start Free Try Sample Data

Details

What to know

How template-assisted import works

Choose a template before uploading a CSV/XLS/XLSX file, or leave the selector on auto-detect. Allocora previews the file, applies template aliases where they match headers, then shows the final mapping for review.

Template suggestions prefill mappings only; required fields, invalid rows, duplicate mapping checks, currency checks, and product-mapping quality checks still run.
Users can override any suggested mapping before import confirmation.
Confirmed imports store the selected template key, name, version, expected source type, required fields, optional fields, and sample filename on the import batch for audit review.
V1 stores mapping and template metadata per import batch; it does not silently set a source-level default template after one import.
Sample CSV files are available from this reference and from the import screen when a template is selected.

Template boundaries

Templates are source-shape helpers, not custom integrations. They do not call external systems or infer contractual payout terms.

Use templates to map dates, amounts, transaction IDs, currencies, product or catalog keys, and optional partner context.
Use Allocora products, payees, rules, and calculation runs to decide who is owed what.
PayPal and Wise templates are sample shapes for payout confirmation reconciliation evidence, not payment execution inside Allocora.

Reference Tables

Fields and checks

Revenue import templates

These templates are available in the revenue import screen and include downloadable sample CSV files.

Template	Use when	Sample file
Generic DSP royalty statement CSV	Music royalty statements with ISRC, line IDs, net royalty, currency, title, and territory fields.	/docs/import-templates/generic-dsp-royalty-statement/sample.csv
KDP book sales/royalty export	Publishing royalty rows with ASIN/ISBN, title, marketplace, transaction ID, and royalty amount fields.	/docs/import-templates/kdp-book-sales-royalty/sample.csv
IngramSpark-style book sales export	Book distributor rows with ISBN, order ID, title, country, and net royalty fields.	/docs/import-templates/ingramspark-book-sales/sample.csv
Draft2Digital-style publishing export	Publishing distributor rows with sale ID, ISBN/title ID, channel, and net earnings fields.	/docs/import-templates/draft2digital-publishing/sample.csv
Shopify seller/creator revenue-share CSV	Order-level seller, creator, or partner revenue-share worksheets with SKU/product and partner context.	/docs/import-templates/shopify-seller-creator-revenue-share/sample.csv
Stripe subscription/affiliate commission CSV	Stripe-derived invoice, subscription, product, affiliate, and commission amount worksheets.	/docs/import-templates/stripe-subscription-affiliate-commission/sample.csv
Paddle or Chargebee subscription commission CSV	Subscription billing commission worksheets with charge, subscription, product/plan, and partner fields.	/docs/import-templates/paddle-chargebee-subscription-commission/sample.csv
Generic revenue-share CSV	Plain revenue-share files with date, amount, external ID, product/catalog key, payee hint, and optional type.	/docs/import-templates/generic-revenue-share/sample.csv

Payout confirmation sample templates

These sample files support reconciliation reference workflows and are not payment execution routes.

Template	Use when	Sample file
PayPal payout confirmation CSV	Reconciling PayPal transaction IDs, payee emails, amounts, currency, paid date, and notes against statement obligations.	/docs/import-templates/paypal-payout-confirmation/sample.csv
Wise batch payment confirmation CSV	Reconciling Wise transfer IDs, recipient references/emails, paid amounts, currency, and transfer dates.	/docs/import-templates/wise-batch-payment-confirmation/sample.csv

Mapping provenance labels

The import preview labels each mapped field so reviewers can see where the suggestion came from.

Label	Meaning	Review action
Template	The selected template matched the file header to an Allocora field.	Review the suggestion and leave it if it matches the source file.
Auto	Allocora generic header aliases matched the field without a selected template.	Review as a generic suggestion.
User override	A user selected a mapping that differs from the template or auto suggestion.	Confirm the override is intentional before import.

Troubleshooting

If this does not work

A selected template still shows missing required mappings.

The file headers did not match enough template aliases. Map the required fields manually or download the sample CSV to compare header shape.

A template maps the wrong product field.

Override External Product/Catalog ID during preview. The final mapping is revalidated and persisted with the import batch.

A payout confirmation template appears in docs but not in revenue import.

PayPal and Wise templates are confirmation sample shapes for reconciliation evidence. Revenue import currently exposes the eight revenue templates.

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