What are Royalty Matching Identifiers?

Royalty Matching Identifiers are technical reference codes used to automatically match statement lines with the correct items in your catalog during royalty processing.

They are the backbone of automated Royalty Accounting. Without reliable identifiers, statement lines cannot be matched, splits cannot be calculated, and royalties cannot be allocated correctly.

In Reprtoir, matching is always identifier driven. Descriptive metadata such as titles, artist names, or labels are never sufficient to guarantee accurate matching.

Why Identifiers Are Critical

Royalty statements are produced by external parties using their own internal systems. As a result:

naming conventions are inconsistent
titles may be truncated, localized, or altered
artist names may vary across territories
catalog metadata is often incomplete

Identifiers provide a stable and unambiguous reference that allows Reprtoir to reconcile external statement data with your internal catalog.

If an identifier is missing, incorrect, or stored in the wrong field, the statement line cannot be matched automatically.

Identifier Driven Matching Logic

Reprtoir processes royalty statements by applying the following principles:

matching is performed using identifiers only
each Statement Template defines which identifiers are supported
identifiers are evaluated according to the template scope
multiple identifiers may be accepted for the same asset type

If a statement line contains at least one valid identifier supported by the selected template and present in the catalog, matching can occur.

If no supported identifier is found, the line remains unmatched and must be corrected or quarantined.

Identifier Scope Depends on the Statement Template

Identifiers do not exist in isolation. Their meaning depends entirely on the Statement Template used.

The same identifier type may represent different catalog items depending on context:

an “ISRC” in an audio template refers to a sound recording
an “ISRC” in a video template refers to a video recording
an “ISRC” in a works template refers to an ISRC stored in the work identifier dedicated field, not a track

This is why the Template Name is always evaluated before any matching occurs.

The template defines both the expected identifier types and the catalog fields in which they are searched.

Common Identifier Types

Depending on the statement scope, Reprtoir may rely on identifiers such as:

album identifiers
track identifiers
video identifiers
work identifiers
product identifiers

Each identifier type must be stored in the correct catalog object and field to be usable for matching.

Placing a valid identifier in the wrong asset type or field is equivalent to not having the identifier at all.

Multiple Identifiers for the Same Template

Some templates support more than one identifier for the same asset type.

When a template indicates multiple identifiers, this means:

statement lines may contain either identifier
both identifiers are supported for matching
Reprtoir will attempt matching using all supported identifiers

This flexibility is designed to accommodate differences in provider reporting practices while maintaining deterministic matching logic.

Identifier Presence in the Catalog

For matching to succeed, identifiers must meet all of the following conditions:

the identifier must exist in the statement file
the identifier must be supported by the selected template
the identifier must be stored on the correct asset type
the identifier must be stored in the correct identifier field

If any of these conditions are not met, the line will not be matched automatically.

Relationship with Error Handling and Corrections

When identifiers are missing or invalid, Reprtoir exposes the issue during the processing workflow.

Depending on the situation, you may:

add missing identifiers to existing catalog items
create missing assets or works
correct identifier formatting
standardize values using rules
quarantine lines that cannot be resolved

Once corrected, matching can proceed without altering the original statement file.

Identifier Documentation and Reference Tables

Supported identifiers are documented in several places:

the Supported Statement Providers tables
provider specific instruction pages
dedicated identifier reference pages

These references describe exactly which identifiers are expected, how they are interpreted, and where they must be stored in Reprtoir.

Always consult these references before ingesting a new statement, especially when working with a provider or template for the first time.

Key Takeaway

Royalty Matching Identifiers are not optional metadata. They are the core mechanism that enables automated, reliable, and scalable royalty processing.

Correct template selection, correct identifier storage, and correct identifier interpretation are mandatory conditions for successful Royalty Accounting in Reprtoir.