Purpose of the Data Error Step

The Handling Data Errors step serves two distinct purposes within the royalty processing workflow.

First, it allows the resolution of critical blocking errors that prevent the system from calculating royalties. As long as these errors exist, the affected statement lines cannot enter the calculation engine.

Second, it enables the standardization of heterogeneous data coming from multiple royalty sources, ensuring that reporting, analytics, and exports remain consistent over time.

This step ensures that all imported data complies with Reprtoir’s standard data model before royalties are calculated, while simultaneously allowing the Organization to progressively build a unified and reliable royalty database.

If no Data Errors are detected, this step is skipped automatically.

---

What Is a Data Error

A Data Error occurs when a required field is missing, invalid, or cannot be interpreted according to Reprtoir’s standard rules.

Data Errors are evaluated at the statement line level and may impact the system’s ability to calculate royalties or to normalize data for reporting and analytics.

Data Errors typically affect:

• asset identification
• royalty splits and contracts
• dates and reporting periods
• territories
• sale types
• retailers or source providers

Unlike Amount Errors, Data Errors do not concern financial totals. They concern data validity, interpretability, and standardization.

---

Two Categories of Data Errors

Not all Data Errors have the same impact on the calculation engine.

◼ 1. Critical Calculation Errors

These errors prevent the system from calculating royalties. As long as at least one of these errors exists in a statement line, the line cannot be processed.

Typical causes include:

• missing or unknown assets
• missing royalty splits
• missing or invalid contracts
• missing mandatory identifiers required by the selected Statement Template

These errors must be corrected or quarantined before the workflow can continue.

◼ 2. Formatting and Standardization Errors

These errors do not prevent calculation, but prevent Reprtoir from normalizing data into a consistent, auditable, and analyzable structure.

Their purpose is to unify heterogeneous data coming from multiple royalty sources into a single internal standard.

They are essential to:

• ensure consistent reporting
• enable accurate analytics
• reconcile divergent naming conventions across providers
• build a unified royalty database over time

This standardization layer is a core strength of Reprtoir, especially when ingesting data from many different Statement Providers.

---

When Data Errors Are Detected

After mapping confirmation and amount validation, Reprtoir analyzes each statement line and verifies that all mandatory fields are present, valid, and interpretable.

If a required value is missing, unknown, or incompatible with the system rules, the corresponding line is flagged and appears in the Data Errors step.

Data Error Statuses

Each Data Error has a status indicating its processing state.

Only lines in “Corrected” or “Quarantined” status allow the workflow to continue.

---

Reviewing Data Errors

The Data Errors screen displays:

• the list of affected statement lines
• the error type for each line
• the current status of each error

You can filter errors by type using the left sidebar to focus on specific issues, such as assets, dates, territories, or retailers.

---

Correcting Data Errors

To correct a Data Error:

1. Locate the error in the list
2. Right click the line, or click the three dots on the right
3. Select the “Make Correction” action
4. Edit the required values in the correction panel
5. Click the “Save” button

Corrections are applied immediately to the affected lines.

---

Typical Correction Cases

Asset Related Errors (Critical)

These errors block royalty calculation.

Without a valid Asset or a valid Contract, Reprtoir has no legal or accounting basis to calculate royalties.

Formatting and Standardization Errors

These errors allow Reprtoir to normalize heterogeneous data into a consistent internal model.

Example of Retailer Standardization

If one source reports “iTunes Store”, another reports “iTunes (Apple)”, and a third reports “iTunes US”, Reprtoir allows the user to define a single internal Retailer and create matching rules mapping all source values to it.

This ensures consistent reporting and analytics across all royalty sources.

---

Automatic Rule Creation

When correcting a Data Error, Reprtoir automatically creates or updates Standardization Rules.

These rules are reused in future statement imports to:

• apply the same correction automatically
• reduce manual intervention
• ensure consistency across reporting periods

Rules are recorded during the calculation phase and can be reviewed in the Rules section.

---

Putting Errors in Quarantine

Purpose of Quarantine

Quarantine allows you to temporarily exclude specific statement lines that cannot be resolved immediately, without blocking the entire workflow.

Quarantined lines:

• are excluded from royalty calculations
• do not generate balances or statements
• remain traceable and correctable later

---

How to Quarantine an Error

To quarantine a Data Error:

1. Right click the error line, or open the contextual menu
2. Select the “Quarantine” action
3. Confirm the action

The error status changes to “Quarantined”.

---

Rules for Proceeding

Before continuing:

• All Data Errors must be either “Corrected” or “Quarantined”
• No error can remain in “To correct” status

Once this condition is met, click the “Confirm Errors” button at the bottom right of the page.

---

Important Processing Notes

• Do not assume you are done after the first correction pass
• Correcting one error may reveal additional errors
• Always review the list again before confirming

---

Recommended Processing Order for Multiple Statements

When processing multiple Royalty Statement Incomes from the same Statement Provider, it is strongly recommended to proceed chronologically and one statement at a time.

Corrections and standardization rules created during the Handling Data Errors step are only applied to future imports once an Income has completed the full processing workflow, including calculation.

As a result:

• Errors corrected on an earlier statement automatically benefit subsequent statements from the same Provider
• Only new errors, or errors that were explicitly quarantined in a previous statement, will appear on the next one
• The same correction does not need to be applied multiple times across statements

Processing statements out of order or in parallel may lead to duplicated correction work, as rules created in one Income are not yet available to others that have not reached the calculation stage.

Following a chronological, sequential approach ensures:

• faster processing over time
• progressive data normalization
• reduced manual intervention
• consistent reporting across periods

This approach is especially important when onboarding a new Statement Provider or processing historical back catalogs for the first time.

---

Relationship with Other Steps

Handling Data Errors occurs after Handling Amount Errors and before Review.

This step ensures that all data entering the calculation engine is valid, standardized, auditable, and suitable for reliable royalty calculations and reporting.

During this step, every correction or standardization decision made by the user can result in the creation of a Rule. These Rules allow the system to automatically apply the same decisions to future Royalty Statement Incomes processed with the same Statement Template.

For a detailed explanation of how Rules work, how they are applied, and how they can be reviewed or removed, refer to the dedicated “About Rules” page.

---