How to Track Artist Royalties: A Step-by-Step Guide
Last updated: August 18, 2026
Tracking artist royalties is not the same as watching stream counts. A label needs to connect each reported revenue line to the correct recording, artist agreement, reporting period and payment. That process becomes more important as the catalog grows, because small metadata or contract errors repeat across every statement.
This guide focuses on the practical label workflow: organizing master-recording data, reading distributor reports, reconciling royalties and preparing transparent artist statements. Publishing, performance and neighboring-rights income may also exist, but those sources are administered separately and depend on the relevant rights, territories and organizations.
What artist royalty tracking should achieve
A useful royalty system should answer five questions:
- Which recording generated the income?
- Which platform and reporting period does it belong to?
- Which contract determines the artist’s share?
- Which documented costs, balances or adjustments apply?
- What amount has been stated and paid?
If the label can answer those questions from retained records, it can explain a statement, investigate a discrepancy and reproduce the calculation later. If the answer depends on one person remembering what happened, the system is not reliable.
Start by separating the revenue sources
Master-recording income
Digital distributors report income connected to the delivered sound recordings. The recording is commonly identified through its ISRC, together with release, artist and platform information. NexaTunes Distribution reports this DSP income to the contractual partner.
Composition and publishing income
The underlying composition is a different right from the master recording. Songwriter, composer and publisher income may be administered through publishers, collecting societies or other organizations depending on the territory and rights involved.
NexaTunes Distribution does not automatically administer all composition rights, and it does not provide Sync pitching. TR Publishing is part of the wider T&R Media structure, but publishing remains a separate service and contractual relationship.
Sync and other licences
A licence for music used with visual media is not a normal DSP royalty line. It may involve both master and composition permissions. NexaTunes does not broker or pitch music for film, television, advertising, Netflix or similar productions.
Do not merge all income into one undifferentiated “royalties” total. Keep each source tied to the correct agreement and statement provider.

Step 1: create a master catalog register
The catalog register is the bridge between a distributor’s data and the label’s contracts. Every released recording should appear once with stable identifying information.
Recommended fields include:
- internal catalogue number;
- release title;
- track title and version;
- primary and featured artists;
- ISRC;
- release barcode;
- imprint or sublabel;
- original release date;
- master owner or licensor;
- artist contract reference;
- territories and term;
- statement recipient;
- current delivery status.
Use the same spelling and version names that were delivered to the platforms. A remix, radio edit and original mix should not be merged merely because they share a composition title.
Why ISRC matching matters
Artist names and track titles can vary, but an ISRC is intended to identify a specific recording. It is therefore one of the most useful keys for matching revenue lines to a catalog record.
Matching should not rely on the ISRC alone. Check the title, version, artist and release context as well. A duplicated or incorrectly reused identifier can otherwise move revenue into the wrong contract calculation.
Step 2: convert contracts into calculation rules
A royalty statement cannot be prepared correctly unless the agreement has been translated into operational fields. Record what the contract actually says rather than applying a default assumption to every artist.
Depending on the agreement, the calculation record may need:
- artist or rightsholder name;
- contract start and end dates;
- applicable recordings or releases;
- revenue-share percentage;
- definition of the calculation base;
- permitted costs or deductions;
- advance and recoupment balance;
- statement frequency;
- payment requirements;
- currency and tax documentation;
- special rules for collaborations or remixes.
Do not invent missing deal terms during statement preparation. If a contract is unclear, place the item into a review queue and resolve it through the responsible human decision-maker.
Step 3: preserve the original distributor statement
When a monthly statement becomes available, save the original document and detailed CSV before creating working copies. The source file should remain unchanged so that later calculations can be checked against it.
NexaTunes places the monthly statement in the contractual partner’s dashboard. The partner submits an invoice, and payment follows the agreed 30-day settlement period. There is no minimum payout threshold.
The detailed CSV contains platform and track-level data and can be searched by reporting period. Data is available as received from the DSPs, so the normal platform reporting delay remains. It should not be described as real-time royalty reporting.
Use a consistent archive structure
Store each reporting period with:
- the original statement;
- the original CSV;
- the invoice sent to NexaTunes;
- proof of the received payment;
- the working reconciliation file;
- artist statements issued;
- payment records;
- notes about adjustments or disputes.
A filename should identify the provider, period, entity and file type. Avoid replacing previous versions without preserving the history.
Step 4: reconcile the statement before calculating artists
Reconciliation checks whether the source data is complete and internally consistent before contract calculations begin.
Check the statement total
Confirm that the detailed lines add up to the statement total, allowing for clearly identified adjustments. If the totals do not reconcile, stop and investigate before issuing artist statements.
Match every line to the catalog
Use ISRC, artist, title and release information to assign each line. Keep unmatched items in a separate exception list. Do not force a match simply to make the totals disappear.
Review reporting periods
The month in which a statement is issued is not necessarily the month in which the streams occurred. DSPs report on different cycles, and later corrections can affect previous activity. Retain the actual usage or sales period supplied in the data.
Check currency and adjustments
Where reports contain different currencies or platform adjustments, use the values and conversion information provided in the source data. Do not reconstruct a supposed per-stream rate from a public average.
Identify penalties and chargebacks
DSP penalties, chargebacks and documented platform costs can reduce reported income. NexaTunes passes through applicable platform actions and contractual charges. These items should be recorded clearly and reviewed against the relevant release and agreement.

Step 5: apply the artist agreement
Once the source data is reconciled, calculate the amount under the correct contract. The calculation should show its sequence rather than only the final number.
A clear calculation can show:
- gross eligible income;
- source adjustments or chargebacks;
- contractually permitted costs;
- net calculation base;
- artist share;
- opening recoupment or balance;
- new recoupable costs where permitted;
- payments or credits;
- closing balance and amount due.
Not every agreement uses all of those fields. The principle is to include only what the relevant contract supports.
Collaborations and multi-artist releases
A platform’s featured-artist field does not determine the contractual royalty split. Collaborators may have separate agreements, one joint agreement or a payment handled by the primary artist. Use the documented deal, not the platform display.
Sublabel calculations
A directly controlled sublabel can be identified through catalogue numbers and internal mapping. NexaTunes does not automatically create or pay a separate revenue account for each imprint. The contractual partner performs the internal allocation.
Step 6: prepare an understandable artist statement
An artist statement should let the recipient understand what period, catalog and calculation it covers. It does not need to expose unrelated artists or the label’s entire distributor file.
Useful statement sections include:
- artist or payee;
- statement period and issue date;
- covered recordings;
- income by platform, territory or release where available;
- contractual rate and calculation base;
- documented costs and adjustments;
- advance or recoupment movement;
- opening and closing balance;
- amount due;
- invoice or payment instructions;
- contact route for questions.
Use consistent labels across periods. A recipient should not have to learn a new statement layout every month.
Step 7: record invoices and payments
A statement shows the amount calculated. A payment record shows what was actually transferred. Keep both.
Record the invoice number where one is required, payment date, amount, currency, transaction reference and the statement period settled. If the amount is carried forward, document the reason and opening balance for the next period.
Do not mark a royalty as paid merely because the distributor paid the label. The artist payment is a separate event under the label’s own agreement.
Streaming analytics versus royalty statements
Streaming dashboards are useful for marketing and audience analysis. They may show plays, listeners, saves, playlist activity or geography earlier than the financial statement.
Those figures will not always match royalty rows one-to-one. Reporting windows, filtered activity, subscription types, territories, later corrections and platform policy actions can all affect the relationship between an analytics number and final reported income.
Avoid public per-stream estimates when checking a statement. There is no single universal rate that can validate every platform, territory and period. Use the actual provider statement and its underlying data.
Monthly royalty tracking workflow
| Stage | Action | Control |
|---|---|---|
| Source | Download statement and CSV | Preserve original files unchanged |
| Reconcile | Match totals and catalog lines | Separate exceptions and unmatched ISRCs |
| Map | Assign contracts and sublabels | Use the catalog register |
| Calculate | Apply documented deal terms | Review unclear contracts manually |
| Approve | Check statements before issue | Second-person review for material changes |
| State | Send artist statement | Retain the issued version |
| Pay | Record invoice and transfer | Update balances and payment reference |
| Archive | Close the reporting period | Keep source, calculation and evidence together |
Common royalty tracking errors
Using dashboard totals without the CSV
A total does not identify the recordings and reporting periods behind it. Retain the detailed source data.
Assuming analytics equals payable royalties
Audience data and financial statements serve different purposes and can update on different timelines.
Applying one split to every artist
Each calculation must follow the relevant agreement. Similar-looking deals may contain different costs, terms or recoupment rules.
Paying the wrong entity
Artist names, project names and legal payees are not always identical. Use the contractual recipient and verified invoice details.
Losing previous statements
Royalty questions often arise long after the reporting period. Preserve issued statements and the files used to create them.
Ignoring platform penalties
Artificial streaming and policy violations can lead to chargebacks, withheld royalties and contract termination. Record the affected release, evidence and cost treatment.
Mixing distribution and publishing
A distributor statement does not prove that every composition or neighboring-rights payment has been collected. Track those sources separately.
When a spreadsheet is no longer enough
A controlled spreadsheet can work for a small catalog with simple agreements. Warning signs that specialist royalty software may be needed include:
- many artists or rightsholders;
- multiple imprints and contract types;
- advances and recoupable costs;
- rate escalations or territory-specific terms;
- large statement files;
- repeated manual corrections;
- difficulty reproducing previous calculations;
- the need for separate creator portals or automated statements.
NexaTunes has an internal split tool that supports label-statement work, but payments and contractual artist accounting remain the label’s responsibility. A separate royalty system may be appropriate where the label’s deal complexity requires it.
Frequently Asked Questions
Does NexaTunes provide real-time royalty data?
No. Reporting is as current as the data supplied by the platforms. Natural DSP reporting delays apply.
How often does NexaTunes provide statements?
Statements are made available monthly. The contractual partner submits an invoice, and payment follows the agreed 30-day settlement period.
Is there a minimum payout threshold?
No. NexaTunes does not apply a minimum payout threshold.
Does NexaTunes pay every artist automatically?
No. NexaTunes reports and pays the contractual partner. The label remains responsible for artist statements and onward payments.
Can a label track several sublabels in one account?
Yes, where the sublabels are directly controlled internal imprints. The detailed CSV can be mapped by catalogue number, artist and release. Independent third-party labels cannot be hidden behind the main account.
Does a distributor collect every type of music royalty?
No. Distribution reports master-recording income from the relevant DSP relationship. Publishing, performance, neighboring-rights, Sync and other income may require separate administration depending on the rights and territory.
Why does a streaming dashboard not match the statement exactly?
Analytics and financial reporting use different cycles and controls. Reporting delays, territories, adjustments, filtered activity and platform rules can change the final data.
Build an exception queue instead of hiding problems
Not every royalty line will match automatically. A responsible workflow keeps unresolved items visible until they can be assigned from evidence.
An exception queue can include:
- unknown or missing ISRC;
- artist or track name that does not match the catalog register;
- release assigned to the wrong imprint;
- income reported outside the expected contract term;
- negative adjustment without a clear reference;
- duplicate line that requires verification;
- collaboration without an approved split document;
- payment recipient whose invoice or account information is incomplete.
Record the source file, reporting period, amount, issue, responsible reviewer and resolution. When the item is resolved, retain the explanation rather than deleting the exception history.
Artist statement review checklist
Before issuing a statement, a second review should confirm:
- the correct artist, legal payee and contract were used;
- the statement period and source report are identified;
- all included recordings belong to the agreement;
- the reported income agrees with the reconciled working file;
- percentages and calculation bases match the contract;
- deductions and recoupable costs are documented;
- opening and closing balances roll forward correctly;
- previous payments are recorded once, not twice;
- the amount due agrees with the payment instruction;
- no unrelated artist data is disclosed.
This review is especially important when a contract changes, an advance is introduced, a catalog moves between imprints or a platform chargeback affects several periods.
Data governance for long-term royalty records
Royalty records contain financial and contractual information. Access should be limited to people who need it for accounting, management or approval. Artist statements should be shared only with the correct recipient and should not contain unrelated catalog data.
Keep a stable folder and naming structure, protect working files from accidental overwriting and retain a record of who approved material changes. If a formula or contract mapping is changed, document the effective period and the reason.
The process should also survive staff changes. A new finance or label manager should be able to locate the source statement, understand the calculation and reproduce the closing balance without relying on private messages or undocumented memory.
How to investigate a royalty question
When an artist asks about a missing or unexpected amount, begin with the issued statement and work backwards:
- identify the recording, platform and reporting period in question;
- locate the original distributor line;
- verify the catalog and contract mapping;
- check the calculation, adjustments and balance movement;
- review whether the activity falls into a later DSP reporting cycle;
- prepare a written answer supported by the retained records.
Do not promise a correction before the source has been checked. Some differences are errors; others are timing, analytics-versus-royalty misunderstandings or documented platform adjustments.
Conclusion
Accurate artist royalty tracking depends on a clear chain from catalog record to distributor statement, artist contract, calculation and payment. The purpose is not only to find a total. It is to make every material line explainable.
NexaTunes gives the contractual partner monthly reporting and a detailed CSV covering platforms and tracks. The label then applies its own artist agreements, prepares statements and records onward payments. With a stable catalog register, documented contracts and a repeatable reconciliation process, that work remains manageable as the roster grows.
Editorial Transparency: This article was created with the assistance of GrandRanker AI and reviewed, edited, fact-checked, and approved by the NexaTunes editorial team before publication.
If you’re looking for a reliable way to distribute your music to major platforms, NexaTunes offers direct distribution with transparent terms.