Why did my upload join a song already there?
A file named like a song already in the project arrives as its next version. You can take it back out from the version menu.
When a file you drop into a project has the same name as a song already there, once the version marker is taken off the end, it arrives as that song's next version instead of as a second song with the same name. "Gold Hour v1.wav" and "Gold Hour v2.wav" make one song with two versions, and the newer one is what your client hears on the link.
The match is deliberately literal. The names have to be the same after a trailing "v2", "rev 3", "take 4", "final", "master" or "mix" is taken off, and a bare number does not count as a version marker: "Study 2.wav" and "Study 3.wav" stay two songs. A wrong new song is one click to fix and a wrong merge is not, so the rule errs towards leaving them apart.
Whatever was still open on the last version is asked again on the new one, exactly as when you upload a version to a song by hand.
On Free a song keeps three versions. A file that would be the fourth arrives as its own song instead, so an upload is never refused for this.
If a file joined the wrong song, open the version's menu and choose Make this its own song. It leaves with its comments and any approval, and it keeps its version number, because that number is written on the approval record your client holds.
Not covered here? Write to support@soneam.com.