Start here: your metadata is not paperwork after the music. It is part of the release.
Metadata is the information delivered with your audio — artist names, track titles, featured artists, songwriters, ISRCs, version labels, explicit flags and credits. Platforms display your music largely as it is delivered to them, and they use that same information to match plays to profiles, recordings and rights holders.
When the metadata is clean, streams land on the right artist page, songs show up in search, and royalties can match to the right people. When it is messy, the music can still be good — and still end up split, mislabelled, hard to find, or unpaid until somebody repairs it.
These are the mistakes that cause the most trouble, and how to avoid them before delivery.
One release says one spelling, the next adds a capital, drops punctuation, or shortens the name. To a person that looks like the same artist. To a platform, inconsistent spelling and formatting can split your catalogue across profiles or attach a release to somebody else with a similar name.
Pick one exact spelling for your artist name — capitals, spaces and punctuation included — and use it identically on every release. If you have released before, copy it from your existing profile, do not retype it from memory.
The same rule applies to featured artists and songwriters. Consistency is what lets the system keep one artist together as one artist.
A featured artist belongs in the featured-artist credit field, in their own field — not typed into the track title, and not added as a second main artist when they are not one.
Putting names in the title — for example, writing "(feat. ...)" into the title field when your distributor has a separate credit field for it — creates messy, inconsistent listings, and it can conflict with how platforms want titles formatted. Putting a featured singer in as a main artist can also send the release to the wrong profiles and change how the credit reads everywhere it is delivered.
Straight rule: one artist per field, in the order you want them shown, with each person in the role they actually played — main artist, featured artist, remixer, producer, composer or lyricist.
This is the mistake that costs publishing money, not just tidy listings.
If songwriter credits are missing, use a stage name where a legal or registered name is expected, or do not match the registration for the song, the publishing side cannot match cleanly. In Canada, that includes your SOCAN registration: SOCAN can only pay the right people for a work when the work is registered with the correct writers and ownership shares.
Agree the splits in writing before release, while everyone is still friends. List every writer, use the names they are registered under, and make sure the percentages add up. "We will sort it out later" is how royalties end up unmatched, held, or paid to the wrong split.
Your distributor delivering the recording does not fix this for you. Delivering the master and registering the song underneath it are two different jobs.
Your ISRC identifies one specific recording. Reusing a code from another recording, mistyping it, or letting a new distributor generate a fresh code for an unchanged recording splits that recording's history and reporting across two entries.
If you already have an ISRC for a recording, supply it exactly as assigned. If you do not have one, let your distributor assign it — then write it down and keep it. Same audio, same ISRC. New recording, new ISRC.
A remix, live version, instrumental, radio edit or clean version needs to be labelled as what it is, in the version field — clearly and consistently. If it is not, listeners, platforms and reporting systems can confuse it with the original, and a fan can end up playing or buying the wrong version.
Explicit tracks work the same way in reverse: mark the track explicit using the explicit flag. Do not type an "E" or the word "explicit" into the title to do that job — platforms add their own explicit marker. Getting the flag wrong either way hurts you: a missed flag can get a release flagged or pulled back for correction, and a wrong flag can limit where a clean song is welcomed.
Your track and release titles are not a poster. Do not add search terms, other artists' names, dates, "new single," genre labels or promotional phrases to a title to try to get noticed.
Platforms treat keyword-stuffed names and misleading titles as a quality and infringement problem, not as clever marketing. At best it looks unprofessional everywhere the release appears. At worst the delivery is delayed, corrected, or rejected until it is cleaned up.
Keep the title as the title. Put credits in the credit fields, versions in the version field, and promotion in your promotion.
If your cover art shows an artist name or title, spell it exactly as it appears in your metadata. A cover that says one thing and metadata that says another creates confusion for listeners, for platforms checking the delivery, and for anyone trying to find the release later.
Check the art, the titles and the credits together as one package before delivery — because that is how the release will be seen.
Bad metadata does not just create a royalty problem months later. It hurts you on release week:
A split profile means your new song is not where your existing fans and followers are looking.
A wrong artist match means streams and followers build somebody else's page instead of yours.
Messy titles and credits make a release harder to search for and harder to trust.
A delivery that fails a platform's metadata checks can be delayed or sent back for correction, and corrections after release have to go back through your label or distributor — they are not an instant edit on the platform.
Unmatched songwriter information means publishing royalties cannot flow the way recording royalties do, even if the stream itself was counted.
None of that is a problem with the song. It is a problem with the label on the song.
Before any release is delivered, read this list out loud with the release in front of you:
Artist name spelled exactly as on your existing profiles, punctuation included.
Every featured artist, remixer and collaborator in their own credit field, in the right role and the right order.
Track titles clean — no featured names, search terms or promo text stuffed in.
Songwriters listed under their registered names, splits agreed in writing and totalling correctly, and the song registered — in Canada, that means your SOCAN registration matches.
ISRC correct for each recording — existing code reused for unchanged audio, new code only for a new recording.
Version labelled correctly (remix, live, instrumental, radio edit, clean) and explicit tracks flagged with the flag, not the title.
Cover art name and title spelled exactly as in the metadata.
If any line does not check out, fix it before delivery. A fix before release is a five-minute job. A fix after release is a repair job through your distributor, with the release live and wrong in the meantime.
Platforms are not going to guess what you meant. They deliver, display and match what you send them.
Clean metadata will not make a bad song good. Messy metadata can absolutely make a good song hard to find, hard to credit, and hard to pay.
Releasing through RayzorDistro? We check the credits and release details with you before delivery, because it is far easier to get them right once than to chase a statement later. Start at www.rayzordistro.com.
Start here: the Rayzor community now has a home that is not a feed.
The Rayzor Discord is open. It is where track submissions, contests and listening parties now run side by side — built for the independent artists who release, record and make music with Rayzor, and open to anyone who makes their own.
Join here: https://discord.gg/P9unpK7kJm
Playlist Parties placements have always been earned through submission and a decision — never bought. The Discord is now a second submissions door alongside the Rayzor Song Submissions group on Facebook.
Every submission is answered within 48 hours. Every track goes through the same check it would get anywhere else at Rayzor: human-made music only, reviewed on arrival. Placement is earned, never sold, and no payment changes a decision.
Song of the Week — one track, one genre, voted by the members. Week 1 is open now, genre: Indie.
Best Playlist — your Spotify playlist, genre rounds, capped at 15 tracks. Round 1 is open now, genre: Indie.
The rotating contest room — Best Artwork is running now, with lyric, verse, chorus and cover rounds to follow.
Cover Challenge — Rayzor picks the song. If you have a cover of it, enter it: your cover goes head-to-head against the original, and the covers that beat it face off in a final.
Standing challenges — in #cover-challenge and #remix-challenge, your version goes up against the original for a 7-day vote, any time you are ready.
Winning covers earn a place on Playlist Parties — Covers. Contest winners are spotlighted in the server. And one rule covers every contest in the building: no AI-generated music, and every contestant is verified at intake, before their entry counts.
In #track-feedback, giving real feedback on other artists' tracks earns you points — and a submission costs points. Artists who show up for each other get heard. It keeps the submissions channel honest, and it means the feedback in there is written by people who actually listened.
Listening parties run in the Listening Lounge voice channel while contest voting is on — hear the entries the way they were meant to be heard, with the people who made them in the room.
The first 50 people through the door get a permanent Founding Member badge. Some of those seats are already gone.
Feeds bury independent music. A room full of artists who submit, vote, give feedback and show up for listening parties does not. If you make music — yours, human-made, no shortcuts — there is a seat in there with your name on it.
Join the Rayzor Discord: https://discord.gg/P9unpK7kJm
Start here: if you release music, every recording you put out needs its own fingerprint.
That fingerprint is the ISRC — the International Standard Recording Code. It is a 12-character code that identifies one specific recording, and only that recording, for its whole life. Platforms, distributors and rights organizations use it to match a play to the right recording, so the right account gets credited.
Get the ISRC wrong and the system does not guess. Plays can attach to the wrong recording, a catalogue can split into pieces, and money that should have matched cleanly has to be chased and repaired later.
An ISRC identifies a recording — the master — not the song underneath it.
That distinction matters:
Record the same song twice, and you have two recordings. Each one gets its own ISRC.
Put that same unchanged recording on a single, then later on an album, and it is still the same recording. It keeps the same ISRC.
A remix, a live version, an instrumental and a radio edit are each different recordings from the original, even when the song is the same. Each one needs its own ISRC.
The song itself — the composition, melody and lyrics — is a separate thing. In Canada, songwriters deal with SOCAN for performing royalties for the composition, and a composition has its own identifier system (an ISWC, assigned through the rights organizations). A release as a product — a single or an album for sale or streaming — has another code again, a UPC for the release.
Straight version: ISRC = one recording. ISWC = one composition. UPC = one release product. Mixing those three up is where a lot of confusion starts.
An ISRC is 12 alphanumeric characters, usually shown in four parts. A Canadian example, with a made-up registrant code, looks like this: CA-XXX-26-00001
CA — the country code for Canada. It shows the country of the agency that issued the registrant's prefix, not necessarily where the song was written or recorded.
XXX — the registrant code, three characters assigned to the person or company authorized to assign ISRCs for those recordings.
26 — the year of reference: the last two digits of the year the ISRC was assigned. It is not automatically the year the song was recorded, and it does not change if you re-release the recording later.
00001 — the designation code, five digits the registrant assigns to make that one recording unique. The same designation is never reused by that registrant in the same year.
Once assigned, an ISRC stays with that recording permanently. You never reuse an ISRC for a different recording, and you never recycle one from a recording you took down.
An ISRC on its own also does not prove who owns a recording today. Rights can change hands; the code identifies the recording, it is not a deed.
You do not have to invent these. There are two normal routes:
Your distributor assigns them. Most distributors will assign an ISRC to each track at delivery if you do not supply your own. If a distributor assigned the code, that code stays with the recording — write it down and keep it, because it is the code you will need if you ever move that recording.
You get your own registrant code. Labels and artists who assign their own codes get a registrant prefix from their national ISRC agency. In Canada, that agency is CONNECT Music Licensing, acting on behalf of Music Canada. The wider system is administered internationally by the IFPI, under the ISO 3901 standard.
Either route works. What does not work is having no record of which code belongs to which recording.
Keep the same ISRC when the audio itself has not changed:
The same recording moves from a single to an album or a compilation
The same recording is re-delivered, including if you change distributors
The same recording is released in another territory or format
Get a new ISRC when you have a materially different recording:
A new performance or a re-recording of the same song
A remix, an edit, or an alternate version
A live recording
A remaster or restoration that materially changes the audio
An edit that changes the recording's length in a real way — the guidance used by agencies including CONNECT treats a change of playing time of more than 10 seconds as a new recording
Changing a title spelling, a cover image, or other metadata does not, by itself, create a new recording. Changing the audio does.
The most common and most expensive mistake here is the distributor move: an artist switches distributors, lets the new distributor generate fresh ISRCs for unchanged recordings, and now the same recording lives under two codes. Streaming history and reporting split across two entries instead of carrying over. If you move, bring your existing ISRCs with you and supply them at delivery.
For every recording, write down and keep:
Track title and version (original, remix, live, instrumental, and so on)
ISRC, exactly as assigned, hyphens or no hyphens
Who assigned it — you, or which distributor
Release(s) it appeared on, and the release date
That one list will save you on every re-release, every catalogue move, and every royalty question that starts with "which version is this?"
One recording, one ISRC, for life. Same audio, same code. New audio, new code. Never reuse a code, and never let a recording leave your hands without writing its code down.
Releasing through RayzorDistro? We check the ISRCs and credits with you before delivery, because a code fixed before release is a five-minute job — a code fixed after release is a repair job. Start at www.rayzordistro.com.
Start here: a stream is not a direct deposit.
When somebody plays your song, no money jumps straight into your bank account. The payment travels through several sets of hands first, and each step takes time. Once you understand the chain, royalty statements stop looking mysterious — and you can spot the problems that actually delay or lose your money.
Spotify, Apple Music, YouTube, Tidal and the other services each record what was played, where it was played, and under what kind of account. A stream from a paid subscription in Canada does not pay the same as an ad-supported stream in another country. Downloads, streams and video plays are also counted differently.
Behind the scenes, the platform matches the play to a specific recording. This is one reason your ISRC matters: it is the code that identifies that exact recording, as opposed to another mix or master of the same song.
The services do not report every play the moment it happens. They close a reporting period, check the activity, remove plays they judge invalid, and then send reports and money to distributors in batches.
That reporting lag is normal. A song released this month can be played every day and still not produce its first royalty payment until a later reporting cycle — often a couple of months down the road, sometimes longer. Different services also move at different speeds, which is why one month's statement can contain activity from different months on different platforms.
Your distributor receives a large statement covering many artists and recordings. It has to match every line to the right account using the recording's identifiers and metadata.
This is where small mistakes get expensive:
A misspelled artist or songwriter name can split one catalogue into pieces.
The wrong ISRC can attach plays to the wrong recording.
Missing songwriter or split information can leave publishing money unmatched.
A takedown, copyright claim or duplicate delivery can hold money while the problem is sorted out.
None of this means the money has vanished. It usually means somebody has to fix the record before the money can be credited cleanly. Clean metadata at delivery is how you avoid the repair job later.
After the distributor applies the deal you signed up for, the royalties appear as a balance in your account. A payout is a separate step: the money still has to be withdrawn or paid out using the payment details on file.
Keep those details current. An old email address, an expired payment method or incomplete tax information can stop a payout even when the royalty statement itself is correct.
Most distributor statements deal with the recording — the master. The song underneath the recording can earn separately for its songwriter and publisher.
In Canada, songwriters commonly deal with SOCAN for performing royalties. Mechanical and other publishing royalties may flow through different organizations and licences depending on how and where the music is used. Registering the song, naming every writer and agreeing the splits are separate jobs from uploading the audio — and they matter just as much.
If two people wrote the song, do not leave the split as a handshake and a memory. Write it down while everyone is still friends.
You cannot make a platform report faster. You can control the things that stop your money from matching up:
Lock the artist name, featured artists, song title and credits before delivery.
Use the correct ISRC for each recording, and get a new one when the recording itself changes.
Agree songwriter splits in writing.
Register your songs with the right rights organizations.
Never buy fake streams or playlist placement. Invalid plays can be removed, royalties can be clawed back, and a release can be taken down.
Keep your distributor account and payout information up to date.
Royalties are slow because several businesses have to count, verify, report and match the same play before anyone gets paid. That delay is built into the system. Losing money because the names, codes or splits were wrong is not built in — that part is preventable.
Releasing through RayzorDistro? We check the credits and release details with you before delivery, because it is far easier to get them right once than to chase a statement later. Start at www.rayzordistro.com.
Rayzor is built by a working musician and engineer, and it is built for the same. Music generated by AI apps is not accepted here — not for distribution promotion, and never on Playlist Parties playlists. Using AI tools inside a human production is a different thing: AI mastering of your own recording is fine, and we offer it. The line is simple. A person made it, or it does not go out under our name.
Five things, ready before you upload, and your release goes smoothly. 1. Your final audio, WAV preferred. 2. Cover art, square and clean — 3000 by 3000 pixels is the standard we build to. 3. Your full credits list — everyone who played, wrote or produced. 4. Your ISRC if the song already has one; if not, one gets assigned. 5. A release date far enough out for pre-saves and pitching. Your dashboard has a release checklist that walks you through all of it.