Published by Qlero
Bring sales files, catalog records and contract terms into a royalty reporting workflow. Use matching templates to import income, review calculated statements, and publish them to payees.
Content last updated:
Each label client brings its own catalog, deal terms and reporting needs. A Qlero organisation can contain multiple record companies, with team roles assigned to selected companies or the whole organisation. Plan your company structure and access before importing client data, and confirm the entity allowance and commercial scope in your quote.
A record company can configure its logo and accent colour for the Artist Portal. Without that setup, the portal uses Qlero's branding. Branding does not change the artist's contract partner or who handles payment questions. Confirm the branding scope and any plan or add-on requirements with Qlero before committing to a client rollout.
Use a sales-file template that matches the provider and column layout. Custom template creation is available on Pro and Enterprise; its editor accepts CSV, XLSX and XLS example files up to 20 MB. Map the required fields, save the template and test a small import. Review row statuses and totals before calculation: invalid data or missing contracts need attention before the affected royalties can be reported.
With Payments enabled, prepare payments according to each payee's billing type, review a run and download payment CSV or Excel files and applicable self-bill PDFs. For manual processing, arrange bank transfers outside Qlero first. Executing the run then records the payments as paid, reduces payable balances and sends payment emails; it does not transfer money through your bank. That recording action cannot be undone.
DDEX repertoire delivery is available on Pro and Enterprise for record companies with a recordings licence. Set the company's DDEX Party ID and ask Qlero to onboard the delivery partner and SFTP connection. Qlero processes ERN 3 and ERN 4 NewReleaseMessage files for selected track, release and label metadata. This is separate from royalty-sales imports. Update and takedown message types do not change the repertoire; deals and participation rates still need their own setup. Confirm any API integration separately for your systems and plan.
Comparing platforms? The 2026 buyer's guide covers the seven criteria that separate royalty systems. Running publishing catalogs too? See Qlero for music publishers.
An organisation can contain multiple record companies, and team members can be assigned access to specific companies. Discuss how your label clients, contracts and reporting should be organised, and confirm the number of entities and plan scope in your written quote.
The Artist Portal can show the record company's configured logo and accent colour. Confirm which branding options and commercial terms apply to your setup; the artist's record company remains their point of contact for earnings, deals and payment timing.
Choose a template matching the provider's file layout or create a custom template on Pro or Enterprise. Map the required fields and review processed rows before calculation. Unmatched ISRCs, missing exchange rates or contract problems need correction; check the row status and the period's Unreported view rather than assuming every row is ready to report.
The documented DDEX workflow receives repertoire metadata through an onboarded partner's SFTP delivery on Pro or Enterprise with a recordings licence. It does not ingest royalty-sales reports or replace contract setup. Bring your delivery, accounting and BI requirements to a demo so Qlero can confirm the API scope, setup and commercial terms for each connection.
Bring your catalog, deal terms, or reporting questions. We'll show you the parts that matter to your team.
