Skip to main content
All CollectionsAccounting
How can I increase the number of matches I get when allocating royalties?
How can I increase the number of matches I get when allocating royalties?
Cee avatar
Written by Cee
Updated over 4 years ago

Label Engine uses a few different algorithms when matching royalties. Firstly, it looks for UPC and ISRC codes - if these are the same as for an existing royalty or pre-allocation then there is an instant match.

Next it will try using the Catalogue Number instead of the UPC.

Lastly, it will try matching the artist, title and mix fields with existing royalties or pre-allocations.

Some stores will edit or omit the tracks' artist, title and mix fields meaning that matching using these can be inconsistent if you are importing statements from several different stores. Therefore, if possible, it's best to ensure you are matching using UPC and ISRC codes.

The most important thing to do is ensure that all the data is being correctly imported from your royalty statements. Open your statement in Excel or similar and look for the following data:

UPC
ISRC
Catalogue Number
Artist
Title
Mix

If this data exists in the spreadsheet then it should be displayed when viewing your statement in Label Engine. If anything is missing when you view it in Label Engine (and it appears when you view it in Excel) then you will need to re-import your statement and ensure that the columns are correctly matched up.

If you have no choice but to match using just artist, title, and mix names, please bear in mind that you may have to do a lot of manual allocations the first time you import a statement from a store you've not used before. You may also be asked to match manually if you are matching a royalty from a license as it may have alternate ISRC, UPC and Catalogue Numbers.

We would also ask you to remember that when Label Engine finds a match, this is only a suggestion based on the data you have input into the system. For complete accuracy we recommend manually verifying each match before verifying it.

Did this answer your question?