Royalty Software for Music Publishers: An Evaluation Checklist
By Qlero Team
Evaluate publishing royalty software with a two-writer test: source imports, income splits, advance recoupment, statement evidence and current product scope.
Can the software explain how a society receipt becomes two different writer balances—without treating either balance as proof of payment?
That is a useful test when choosing royalty software for a music publisher. A feature list is only a starting point. Ask each shortlisted provider to process the same small publishing example, show its assumptions and reconcile the output.
This Qlero-authored guide is an evaluation checklist, not a product ranking or a claim of hands-on testing. It focuses on publishing income allocation, writer-specific recoupment and statement evidence. Product documentation and roadmap wording were checked on 30 September 2026.
Define the publishing income you need to account for
Start with your actual sources and agreements. A musical work is distinct from its sound recording. Publishing income can include mechanical, performance, synchronization and print income; the rights, collection arrangements and contracts determine what reaches your business. The U.S. Copyright Office’s educational guide explains these distinctions in a U.S. context. It is not a worldwide contract rulebook.
For your test pack, identify:
- The work, relevant writers and parties entitled to the income you administer.
- The reporting source, income type, territory, currency and relevant dates.
- Whether the reported amount is gross, already reduced by commissions, or already limited to the share you collect.
- The contractual allocation, permitted deductions and income available to recoup each advance.
Do not assume a composition’s ownership percentages are automatically the percentages applied to every receipt. A writer’s direct society income may also sit outside the publisher’s collected pool. For background on that distinction, see publishing administration versus full publishing deals.
A worked test: $10,000, two writers and one advance
Use this fictional example to test a calculation, not as a standard publishing deal or a market benchmark. Assume $10,000 in mechanical income from Germany before a selected 15% sub-publisher commission. Two writers receive 60% and 40% of the amount left after that commission. These are the assumed distributable-income shares, not a claim about copyright ownership.
Assume no further publisher commission, costs, taxes, reserves, currency conversion or payment thresholds. Writer A has a $2,000 outstanding advance, and 100% of A’s allocated mechanical royalties may recoup it. Writer B has no recoupable balance. Do not deduct the sub-publisher commission again if your real source already reports the net amount.
| Calculation | Amount |
|---|---|
| Income before the example’s commission | $10,000 |
| Sub-publisher commission: $10,000 × 15% | $1,500 |
| Pool available to the two writers | $8,500 |
| Writer A’s allocation: $8,500 × 60% | $5,100 |
| Writer B’s allocation: $8,500 × 40% | $3,400 |
| A’s allocation used to clear the advance | $2,000 |
| A’s amount remaining payable: $5,100 − $2,000 | $3,100 |
| B’s amount remaining payable | $3,400 |
The reconciliation is $1,500 commission + $2,000 advance recoupment + $3,100 payable to A + $3,400 payable to B = $10,000. The two payable amounts total $6,500. Clearing A’s advance does not consume A’s entire $5,100 allocation. These are calculated amounts, not evidence that a bank transfer happened.
Now change only A’s outstanding advance to $6,000. Under the same assumptions, A has $900 left to recoup and no additional amount payable from this receipt; B still has $3,400 payable. This second case tests whether the configuration keeps the writers’ balances separate. Neither case proves a particular platform can implement your actual agreement.
Six capabilities to test, with evidence to request
The table is a recommended acceptance test, not a statement that every vendor offers these features or implements them in the same way.
| Capability | Evidence to request in a publishing demonstration |
|---|---|
| Society and administrator income import | Use your actual file layout. Reconcile amounts and row counts; inspect currencies, identifiers, excluded rows and any preparation needed before import. |
| Writer and co-writer allocation | Run the two-writer example above. Confirm the income base and commission order; do not apply a share twice to income already allocated upstream. |
| Structured agreement and recoupment rules | Demonstrate which writer, work, deal and income types can recoup each balance. Test a remaining deficit as well as an advance cleared in full. |
| Source-level statement detail | Trace a writer’s result back to the source, work, income type, period and calculation. Identify detail kept outside the statement and how it can be retrieved. |
| Review and change records | Show who can review and release statements, what changes are recorded, and whether the required history can be exported. A transaction ledger is not automatically a complete change or approval log. |
| Late income and corrections | Add a clearly identified late receipt and a separate correction in a test environment. Show the reporting-period treatment and the process for statements already released or closed. |
Keep the expected results next to the observed results. Mark each requirement as demonstrated, dependent on a particular configuration or service, or still unverified. If the proposed plan excludes a required capability, record the upgrade or additional work rather than marking the test passed.
Questions that expose assumptions before you buy
Can it use your files—not just a clean sample?
Bring representative society, administrator and direct-license records that you are permitted to share, or anonymized equivalents. Include the formats you actually receive. Ask separately about file upload, field mapping, work matching and calculation: passing one step does not establish that the others are correct.
For a PDF source, ask how the figures become structured data and how the conversion is checked. For an income line already reduced by a sub-publisher, ask where that earlier deduction is recorded so it is not applied twice. Do not treat “CSV support” as proof of compatibility with every society’s file or reporting convention.
Can it preserve the right recoupment boundary?
Use an agreement summary checked by the person responsible for the contract. If mechanical income may recoup an advance but another income type may not, include both in the demonstration. If balances may not cross between writers or deals, test that boundary with a deficit.
The question is whether the proposed configuration reproduces the agreed calculation—not whether the product is described as “masters-first” or “publishing-first.” We have not established that either label predicts a vendor’s capabilities. Uncertain contract interpretation needs a qualified adviser, not a software default.
What happens after a statement has been released?
Ask which dates represent usage, source reporting, receipt and your own statement period. Then distinguish a late receipt from an error in an earlier calculation. Have the provider show the permitted correction route, retained evidence and recipient-facing explanation.
Do not assume a historical period can be reopened, or that software automatically recalculates and replaces every affected statement. A proposed adjustment process should explain what changes and what remains unchanged.
Include sync and print income in the test pack
If you administer sync or print income, include a representative license record and its related income. Confirm which rights and amount your publishing business handles; do not combine a composition fee with a separate recording-rights fee merely because they relate to the same placement.
Ask how the system records the work, license reference, counterparty, amount and applicable allocation. Establish whether that requires a supported import, a transaction entry or work outside the platform. A manually entered balance adjustment and an imported income line are not interchangeable unless they produce the intended calculation and evidence.
There is no need to assume these income types always require manual entry, have no structured formats, or are universally harder to process. Test the records you actually receive.
What Qlero’s current documentation establishes—and what to verify
Qlero’s sales-template setup guide documents mapping provider columns, reviewing a sample and reusing saved layouts. Its example-file step accepts CSV, XLSX and XLS. Creating custom templates requires Pro or Enterprise and the relevant template and sales-file permissions. This does not certify every society format, PDF conversion or publishing work-matching workflow.
The royalty calculation guide explains royalty bases, participation and rates; overrides, deductions, escalations and PPD handling are Pro/Enterprise features. The cross-accounting guide describes deficit transfers through contract, account and payee levels. Additional accounts and account settings require Pro or Enterprise, and agreement changes require the relevant write permission. These guides alone do not prove that every publishing sub-publisher chain or writer-and-income-type recoupment rule is available. Ask the team to demonstrate your exact case.
Qlero’s manual advance and adjustment guide also makes an important distinction: the whole entered amount affects the balance, without applying a royalty percentage, and the entry does not send money. Do not enter the example’s $10,000 as a balance adjustment and assume the software will automatically apply the commission and writer split to that entry.
The statement lifecycle documents review, publication and closing. Advanced mode separates publication from closing; Simplified mode combines them. There is no Unpublish action, and closed periods cannot be reopened or recalculated. That lifecycle is not, by itself, evidence of a complete log of every change and approval.
The Artist Portal statement guide describes a publishing-only view using Works instead of Tracks and Releases; Costs are not shown in that view. It distinguishes statement PDF and Sales CSV downloads. Inspect the actual writer-facing output rather than assuming every detail appears in one file.
At the same time, Qlero’s publisher page, checked on 30 September 2026, describes dedicated publishing workflows for rights, mechanicals and licenses as in development. That is Qlero’s roadmap wording, not independent proof of delivery or a claim that all publishing functionality is absent. Confirm what is available today, on which plan, and what remains planned before relying on it.
Frequently asked questions
What is the best royalty software for a music publisher?
This guide does not rank products. Our recommendation is to choose against an agreed test pack: your sources, income allocations, recoupment boundaries and required statement evidence. Record the demonstrated results and the full proposed commercial scope.
Can one system handle both master and publishing royalties?
Evaluate the two workflows separately, then test any intended connection. A shared interface does not prove the required accounting rules, work matching, licensing or registration functions are included. Do not let balances cross merely because the same person is both artist and writer.
How should late society income be handled?
Ask the provider to demonstrate its documented process and check that it fits your reporting obligations. Keep the source dates and reason for the entry visible. Do not assume the process rewrites a closed statement; Qlero’s documented closed periods cannot be reopened or recalculated.
Should mechanical and performance income share one calculation rule?
Only use the same rule where the relevant agreements and income base justify it. Include both in the test if their allocations or recoupment treatment differ. This article’s worked example covers only the selected mechanical-income pool.
How many co-writers can a platform support?
Obtain the limit for the proposed product and plan, then test the number and arrangements in your catalog. We have not verified a universal or unlimited co-writer capacity. Contributor count alone does not establish support for separate recoupment rules.
Does sync or print income have to be entered manually?
Not as a universal rule. Ask about the actual format, supported ingestion route and resulting calculation. Distinguish recording an income source from adding a balance adjustment, and verify which tasks remain outside the product.
Choose on a reconciled result
The useful end product of a demo is a calculation you can follow: the source amount, each permitted deduction, the allocation to each writer, the advance movement and the amount remaining payable. Keep the source files, assumptions and observed output together.
If Qlero is on your shortlist, book a demo with an anonymized publishing example. Ask the team to show which requirements can be met today and document any configuration, service or roadmap dependency before you decide.