Viewing sales rows requires view access to Sales Files (+ Sales Explorer). Viewing a period’s Unreported tab also requires view access to Periods & Statements. If you don’t see Sales Files, the period, or its Unreported tab after processing, ask your administrator. See User access and roles.
Before a row can be reported
Invalid. Required data, a repertoire match, or conversion into the file currency is missing. The row stays out of royalty calculation until it’s fixed. Invalid Reason identifies the problem, such as Unmatched ISRC or Missing exchange rate. Follow Resolving invalid lines to correct it and revalidate. Valid. The row passed data validation and hasn’t been reported for any contract yet. Contracts and terms are checked during period processing. If no contract has been reported and at least one awaits reporting without a suspense reason, the row remains Valid even when another contract is in suspense. Missing contracts. Period processing found no Sales contract participation for the matched repertoire. Check its Participation Rates tab and assign a Sales contract at the level the row matches. Start with Invalid rows before investigating contract results. Fixing a term won’t repair an unmatched ISRC.Once contracts have been checked
One row can earn for several contracts. Qlero summarises their results:
For Invalid contracts or Partially reported with invalid contracts, inspect the period’s Unreported tab. Suspense holds shares Qlero couldn’t calculate, with reasons such as Missing Terms, Unmatched Territory, or Missing Contract Exchange Rate. For example, EUR sales for a contract in USD need an applicable conversion rate. If neither the sales file nor the period supplies a usable rate, that contract’s share stays in suspense. Fix the reason before processing those shares again.
For Partially reported, check whether the remaining contracts await another accounting cycle. For Reported, no participating contract awaits reporting. It doesn’t mean the payee has been paid: a matching 0% royalty rate can produce a Reported row with no royalty.
Examples of status changes
A Spotify streaming row for Nora Lane has EUR 100 net receipts, complete data, and a matching track. After import, it’s Valid. Nora’s contract has 100% Sales participation but no sales term. Period processing makes the row Invalid contracts, with Missing Terms in suspense. Add a term: When Territory = Worldwide, AND Sale Type = Stream, THEN 20% of Net Receipts. Recalculating makes the row Reported and produces EUR 20 in royalties, assuming the file, period, and payee use EUR and no deduction or escalation applies. Now suppose Sam Carter’s producer contract also participates at 5%, alongside Nora’s unchanged 100%, but has missing terms. Nora’s share can be reported while Sam’s waits: Partially reported with invalid contracts. Add Sam’s missing sales term before processing his share again.File status vs. row status
A file can show Ready while rows are Invalid or need contract work. Importing… and Revalidating… describe work on the file; wait for it to finish before reviewing rows. See the Sales file glossary for file-level labels.Next steps
- Fix imported data with Resolving invalid lines.
- Review file actions in Manage your sales files.