A duplicate Ecad recording registration can stop a Brazilian neighbouring-rights payment even when a track is live on every streaming service. Before a label changes distributor, it should compare the recording entry held by its collecting association with the master being delivered: title, performer, recording date, phonogram producer and International Standard Recording Code (ISRC). A clean platform transfer does not settle a conflict in the collective-management database.
Ecad, Brazil’s central public-performance collection office, marks certain overlapping registrations “Em duplicidade.” Its distribution regulation, revised in December 2025, says a registration cannot be released for payment while it has that status. This is a rights-data problem with a concrete fix, not a reason to upload a third copy of the track.
Which details trigger the duplicate flag?
Article 9 describes an operative matching rule: two phonogram entries can be marked duplicate when they share the title, performer and recording date, have at least one phonogram producer in common, and the ISRC or the older GRA identifier is missing from one or both entries. Ecad also requires the recording registration to reference the underlying song and identify the producer, performers and relevant musicians.
The same regulation lists a broader proposed duplicate rule, including entries with the same ISRC, under “transitional provisions” to be implemented when technically and operationally possible. That is not a reliable statement that every identical ISRC is automatically blocked today. The current status of the actual entries matters more than a label’s assumption about what a matching code should do.
A work and a recording have separate registrations. Article 6 says two song registrations with a matching title or alternative title and at least one common author can also be marked duplicate. A label investigating a missing master-side payment should therefore ask its association whether the hold sits on the phonogram, the composition, or both.
Build one evidence file before requesting a correction
Start with the association’s recording record and the distributor’s release export. Put the ISRC, recording title, recording date, performer names, original producer, any licensed producer and release date in one comparison sheet. Add the master ownership agreement and licence or transfer documents that explain any change of distributor or producer credit. Ecad’s rules make the association representing the producer responsible for the phonogram registration.
Then ask the association for the status and identifier of each overlapping entry. Identify which record should remain, which fields are wrong, and whether another association must agree to the change. Do not silently replace an ISRC to make a catalogue look tidy: the code identifies a particular recording, while the registration dispute concerns who and what the database says that recording is.
The Brazilian Union of Composers’ member guide says disputes and duplicate ownership can leave credits retained, and its portal allows members to check retained credits and statements. Ecad says the rights holder obtains a retained-credit report through their association. Ask for that report, the affected usage period and the next statement after the correction; a corrected record and a paid credit are two separate checkpoints.
Keep distribution and collection records aligned
A digital distributor can carry a correct release to services while an Ecad entry remains in conflict. That is why the release export should travel with the rights file at every catalogue handoff. The same title, ISRC and producer evidence used for delivery gives the association a precise way to reconcile its entry, though only the association can correct the collective-management record.
This is the practical extension of our guide to checking Brazil’s retained credits and our explanation of Ecad’s ISRC requirements. For a label managing a catalogue across distributors, the decision is simple: make the association-record comparison part of the transfer checklist, and close the task only when the disputed entry is released and the statement reflects the right recording.