After the release file is readable
Capital context appears only after the song, release path, rights notes and reporting materials can be understood together.
CAPITAL MEMO
When the music, release path, rights notes and reporting materials are clear, ERC organizes the catalog evidence into a private rights-asset memo.
When capital context appears
Capital is not the first public path inside ERC. It appears only after the music, release and rights materials are clear enough to read.
When rights need a partner memo
ERC turns catalog scope, royalty statements, usage history and open questions into a private memo for selected follow-up.
What ERC organizes
This page does not show a funding menu. It groups the materials a partner needs to understand first.
Catalog scope
Track lists, release status, identifiers and included or excluded works.
Royalty statements
Distributor, publisher or platform statements with reporting periods and source notes.
Rights chain
Ownership, splits, approvals, restrictions and unresolved counterparties.
Contracts and recovery notes
Known agreements, recoupment status, obligations and decision points that affect future income.
Partner memo
A concise private note that separates what is known, what is missing and what can be discussed next.
How partners read it
The memo is a reading structure, not a public application form. It helps partners see what is clear and what still needs private confirmation.
Purpose
Make the rights file legible
The memo gives a partner enough context to understand the catalog, rights chain and reporting evidence before a focused follow-up.
Contents
Music, statements and rights notes
It groups release history, royalty evidence, rights chain and material gaps before any follow-up is considered.
Use
Focused follow-up
Partner review, term discussion and document needs move forward from a confirmed project context.
After distribution, not before it
The distribution page explains how music is submitted, prepared, released and supported. The capital memo appears later, to organize catalog scope, reporting, rights chain and partner reading context.
Review Path
ERC first brings music, rights files, royalty statements and partner context into one memo, then moves the project into the right follow-up conversation.
Partner-fit first
The memo is useful when a catalog already has music context, rights notes and reporting evidence worth reviewing together.
Document-led review
The review stays anchored to songs, rights files, statements, split context and the next documents needed.
Release remains the first path
Artists should start with music and release context before capital language becomes useful.
Make the file readable first.
If the release path is not yet clear, start by submitting the music. If the catalog and rights materials are already formed, continue into the rights workspace.
Follow-up review is organized around confirmed music, rights files and partner context.