Music Royalty Management Software Development

Automated ingestion of royalty statements from Spotify, Apple Music, Amazon Music, YouTube Music, Tidal, Deezer, and 40 or more additional stores and DSPs. Each DSP delivers data in its own format -- CSV, TSV, XLSX, or proprietary formats via SFTP or API. For DSPs that implement the DDEX ERN (Electronic Release Notification) standard, the pipeline consumes structured DDEX message files directly, reducing the mapping overhead compared to raw CSV parsing. The ingestion pipeline normalises all incoming data to a common schema: track, ISRC, territory, streams, download units, and gross revenue. ISRC (International Standard Recording Code) identifies the specific recording; ISWC (International Standard Musical Work Code) identifies the underlying composition. Both identifiers are used during ingestion so master recording royalties and publishing royalties are attributed separately without manual lookup. Statements from Harry Fox Agency and Music Reports for mechanical royalties in the United States, and from SoundExchange for digital performance and master recording royalties, are processed through the same ingestion pipeline with format-specific parsers. Digital distribution royalties arriving via aggregators like DistroKid, TuneCore, or CD Baby are parsed from their statement formats and normalised to the same schema. New DSP formats are added as a configuration change, not a code change, so when a new distribution partner or store sends statements, the integration does not require a development sprint.

Mechanical royalties (from streaming services, downloads, and physical sales) and performance royalties (from PROs including ASCAP, BMI, and SESAC) follow different rate structures, reporting timelines, and split configurations. The system processes each income type according to its own rules. Mechanical royalties are calculated against statutory or negotiated rates depending on the territory and deal type -- US statutory mechanical rates set by the Copyright Royalty Board differ from negotiated rates in the UK or Australia. Performance royalty distributions from PROs are ingested as statement data and matched to compositions in your catalog by ISWC or work registration number. Neighbouring rights royalties -- collected for featured artists and session musicians from broadcasters and public performance by entities like PPL in the UK and SoundExchange in the US -- are tracked as a distinct income type with their own split configuration separate from the publisher split. Sync licensing income from film, TV, and advertising placements is recorded per licence deal with the relevant territory and use type documented against each payment. Master recording royalties via SoundExchange for non-interactive streaming (internet radio, satellite radio) are processed with US and Canadian split rules applied separately from other territories. Royalty rate tables by territory and use type are maintained in the system configuration so when statutory rates change or new territory rates are added, the update applies to all future processing without touching the underlying code.

Split sheets are stored as live data linked to the recording or composition they govern -- not as PDF documents filed away from the payment system. Each split record carries the rights holder's identity, their ownership percentage, the income types their split applies to (master vs. publishing, mechanical vs. performance), the territory scope, and the effective date range. Co-writer and co-publisher percentages are stored separately and must sum to 100% for each income type before the split sheet is approved -- the system validates this before any royalty processing runs against the title. When a royalty payment is processed, the system applies the correct split for the income type and reporting period. For titles with complex arrangements -- multiple co-writers, different splits for mechanical versus performance, controlled and non-controlled composition designations -- the split logic handles the full configuration without manual intervention. Split amendments are versioned so historical payouts can be reproduced exactly as they were calculated at the time, which is the foundation for a clean audit trail if a rights holder disputes a past statement. Black Box royalty recovery is supported: the system flags distributions from PROs that cannot be matched to a registered work in your catalog, creating an unclaimed rights queue for your team to review, match against existing titles, and claim before the PRO's window closes. The registry also stores each rights holder's tax status -- US 1099 reporting for domestic payees and W-8BEN documentation for international rights holders -- so withholding is applied correctly at payout time.

Statements generated directly from the processed royalty data -- not from a spreadsheet export that someone formatted manually. Each statement shows income by DSP, territory, income type, and period, with the split calculation applied to arrive at the rights holder's net payment. The statement format breaks out mechanical royalties, performance royalties, sync income, neighbouring rights, and digital distribution earnings as separate line items so a co-writer can see exactly what their share of each income type was for the period, rather than receiving a single unexplained number. Statements are generated on a schedule -- monthly, quarterly, or annually depending on the rights holder agreement -- or on demand for audit or deal purposes. Rights holders receive their statement by email or through a portal where they can view current and historical statements, drill into line-item detail, and download PDFs. Statement data is exportable in formats compatible with accounting software such as QuickBooks or Xero. Tax withholding applied during the payout period is shown on the statement as a separate line, with the gross payment and the withheld amount both visible, so the rights holder's accountant has the information needed for their own tax filing. Statement generation for a full catalog processes in minutes, not weeks, which changes the economics of how frequently you can distribute statements to rights holders.

Payment runs triggered from the processed royalty data with a single approval step. Each payment is linked to the statement it corresponds to so the audit trail is complete from DSP statement through to bank confirmation. Payment methods include ACH for domestic US payments, wire transfer for international rights holders, and PayPal for rights holders who prefer it -- each method is configured per rights holder in the payment profile, and the system selects the correct method at run time without manual routing. Tax withholding management is applied at disbursement: US residents receive 1099 forms for annual royalty income above the IRS reporting threshold; international rights holders with W-8BEN documentation on file have the appropriate treaty withholding rate applied, with the withheld amounts remitted separately to the relevant tax authority and documented against the payment record. Minimum payment thresholds are configured per rights holder so small balances accumulate until they reach the threshold rather than generating payment processing fees on tiny amounts. Payment status is tracked from initiation through to bank confirmation and matched to the bank record. Finance teams see a full payment history by rights holder, period, and income type without manual reconciliation. Audit trail for royalty disputes is complete: any past payment can be traced back to the specific statement lines it was calculated from, the split configuration that was active at the time, and the DSP statement files that provided the underlying data.

A catalog registry that ties every recording and composition to its rights holders, ISRC and UPC codes, release dates, territories, and deal terms. Catalog data is the foundation that makes royalty processing accurate -- if a recording is not correctly registered with its splits and rights holder identifiers, the royalty attributed to it cannot be correctly disbursed. The catalog module supports import from existing systems, bulk ISRC registration via CSV upload, and territory-level rights restrictions so a recording's mechanical rights in the United States can be assigned to a different publisher than its rights in Europe. ISRC identifiers for recordings and ISWC identifiers for compositions are stored together where the link between a specific recording and the underlying composition has been established, enabling the system to process both master and publishing royalties from a single ingested stream entry. Changes to ownership or split configurations are effective-dated so historical calculations are not affected by current changes -- a catalog acquisition or rights reversion does not retroactively change past statements. The registry also supports catalog data export in standard formats for registration with ASCAP, BMI, SESAC, SoundExchange, and PROs in other territories, reducing the manual effort of keeping registrations current across multiple organisations when a new release is added to the catalog.