Checking a release’s identifiers and a file’s rows requires view access to Repertoire & Agreements and Sales Files (+ Sales Explorer). If you don’t see Releases under Repertoire or Sales Files under Income, ask your administrator. See User access and roles.
When the file has a catalogue number
Suppose Qlero Records has Nora Lane’s Paper Skies under catalogue numberQLR-001. A sales report contains that number but leaves the UPC empty. The template’s Catalog number field needs to read the incoming code. The same value belongs in Catalog Number on the release’s Overview.
Qlero can match this row to Paper Skies without a barcode. The row becomes Valid when its other required information is also complete and matched.
Open Repertoire › Releases, select the release and check Catalog Number on its Overview. If the release doesn’t exist yet, you can create it with Catalog no. and leave Barcode empty. See Adding new tracks and releases.
Use the existing catalogue number when the report supplies it. Creating a second release for the same product would split sales that belong together.
When the provider uses another code
Suppose the same release arrives under the provider’s codeQLR001-DIG instead of QLR-001. Read that code into Catalog number and link it to the existing release as an alias. Keep QLR-001 as the release’s main catalogue number.
An alias gives Qlero another code to match. External ID, Release title and Release artist don’t provide a release match. Store a code as an alias when it needs to affect sales matching.
For an imported row showing Unmatched release identifier, use the mapping manager’s Releases category. Follow Link to existing repertoire to choose the release and save the incoming code as an alias. Linking saves the alias immediately and can affect future files from any source in your record company, so use it only when the code consistently means this release.
You can also prepare an alias on the release before importing the file. See External IDs and aliases.
When the file has only an ISRC
An ISRC identifies a track. A row with a matching ISRC and no release identifier can be valid, but Qlero doesn’t choose a release from the track’s release list. The track Paper Skies could appear on a single, an EP and a compilation. If the sales need to match a particular release, ask the provider for a barcode, catalogue number or stable product code. A title alone isn’t enough to distinguish editions reliably. When a row contains both an ISRC and a release identifier, both the track and release must match. Resolving the ISRC won’t clear Unmatched release identifier. A row with none of these identifiers shows Missing repertoire identifier.Apply the correction to imported sales
The code was read correctly, but the release or alias was missing. Add or link the repertoire, then revalidate the affected file to retry its invalid rows. The template didn’t read the code. Correct the column mapping, then re-import the file so Qlero reads the stored file again. The template repair guide covers custom-template changes and system-template limits. If the provider supplies a corrected report, import it as a new sales file. Delete the old file only if no period includes it, so you don’t report the same sales twice. A new upload doesn’t reverse royalties already reported from the old file. Follow Revalidate vs re-import for the controls, linked-period restrictions and deletion limits.Next steps
- Connect the matched repertoire to its deals with Assigning contracts and participation.
- Use Sales row statuses to understand any remaining validation or reporting issue.