Purpose of Downloading Statement Files From Providers

This page explains how to download the correct royalty statement file from Statement Provider interfaces before importing it into Reprtoir.

In many cases, import issues are not caused by file formatting problems, but by downloading the wrong report, the wrong export format, or an incomplete dataset from the provider platform.

Core Principle: Always Export, Never Rebuild

Royalty statements must always be:

• exported directly from the provider interface
• downloaded in their original reporting format
• imported without reconstruction or recomposition

Never:

• rename the statement
• copy paste data into a new spreadsheet
• rebuild a statement manually
• merge multiple reports into one file
• adjust totals to match expectations

If the exported file cannot be imported as is, the correct action is to identify the correct export option, not to recreate the data.

Selecting the Correct Report

Most providers offer multiple reports covering different scopes, rights, or timeframes.

Before downloading, always confirm:

• the report corresponds to the correct rights type
• the report matches the expected Statement Template
• the reporting period is complete
• the currency is correct

Common mistakes include:

• downloading a summary instead of a detailed report
• exporting a dashboard view instead of a raw statement
• selecting a publishing report instead of a master report
• exporting a report aggregated by period instead of line level usage

Reprtoir requires line level, non aggregated data.

Choosing the Correct Export Format

Whenever multiple formats are available:

• prefer CSV over XLSX
• avoid PDF or web only exports
• avoid proprietary or visual formats

CSV files:

• preserve raw values
• avoid spreadsheet auto formatting
• are safer for dates and numeric values

If XLSX is the only option:

• never edit formulas
• never recalculate sheets
• export a single relevant tab as CSV when needed

Common Provider Interface Pitfalls

The following interface behaviors frequently lead to incorrect exports:

• default filters applied without notice
• pagination limiting exported rows
• hidden columns excluded from export
• totals included at the bottom of files
• mixed scopes in a single report

Always:

• remove filters before export
• confirm the number of rows matches expectations
• verify that no totals or summaries are appended

When a Provider Requires a Specific Export Path

Some providers require very precise steps to export the correct file.

Typical examples include:

• selecting a specific report type among multiple similar ones
• disabling aggregation options
• choosing a legacy format instead of a newer dashboard export
• exporting separate reports for different rights or channels

These cases are documented in provider specific instruction pages.

If a “Read” link is present for a provider in the Supported Statement Providers tables, it means:

• the provider interface has known pitfalls
• a specific export path must be followed
• the instructions must be applied exactly

Always follow the linked provider page in priority.

Verifying the Downloaded File Before Import

Before importing, quickly verify that:

• the file is not empty
• the header is present
• columns match the expected template
• data appears complete for the selected period
• no obvious summaries or totals are present

This verification should be visual only.

Do not modify the file unless required by an import error.