Viewing templates requires view access to Templates, and viewing sales file rows requires view access to Sales Files (+ Sales Explorer). If you don’t see Templates or Sales Files under Income, ask your administrator. See User access and roles.
Three names with different jobs
Template provider. The group a template belongs to, such as FUGA. One provider can have several templates for different file layouts. The provider is optional on a custom template; choosing one groups it in the Library but doesn’t set the source or store on its sales rows. Source. The distributor or licensing partner that supplied the sales, such as FUGA or The Orchard. Each sales row has its own source. Store. The platform or outlet where the sale or use happened, such as Spotify or Apple Music. Each sales row also has its own store. Choose the provider for the file layout and the source and store for what the sales actually represent.One file, several stores
For example, Qlero Records receives a FUGA report containing streams of Nora Lane’s Midnight Run. It uses FUGA Streaming Report, a template grouped under the FUGA provider. The report includes sales from two platforms:
Both rows use the same template and source. The store changes because the streams happened on different platforms.
If Qlero Records later receives a report of Spotify sales through The Orchard, the source is The Orchard and the store is still Spotify. Use the template that matches that report’s layout. You don’t need a separate Spotify store for each distributor.
How the names reach your sales rows
The template reads source and store values from the file, or supplies defaults for values the file leaves empty. A custom mapping translates the file’s wording into a configured name:FUGA B.V. can map to the source FUGA.
Keep the incoming wording in the mapping and use one consistent source name for the partner. Creating a second source just for a spelling variation would split sales that belong together. The Template glossary explains column mappings, defaults and custom mappings.
A row stays invalid until it has both a recognised source and a recognised store. Assigning the FUGA template provider won’t repair Missing source or Missing store. Use Resolving invalid lines to identify the missing information, then follow Revalidate vs re-import to apply the correction.
Where the distinction matters
Finding templates. Look under FUGA in the Library to find the layouts you use for FUGA reports. Checking imported sales. The Source(s) shown for a sales file summarises the sources on its rows. Open the file’s Lines tab to inspect each row’s Source and Store. A file from FUGA can include several stores, as in the example above. Setting royalty rules. Sales terms can match a row’s Source and Store. Use a Source condition when the deal varies by distributor, or a Store condition when it varies by platform. A rule for Spotify can cover Spotify sales from several distributors. The template provider isn’t a condition in the term builder. To create or rename the configured names, see Template Providers, Sources and Stores.Next steps
- Put the names to work in First-time setup: templates & import sales files.
- Set rates by source or store with Creating and linking contract terms.