{"id":26326,"date":"2026-11-05T18:36:05","date_gmt":"2026-11-05T18:36:05","guid":{"rendered":"https:\/\/interspacemusic.com\/blog\/weight-the-audio-audit-by-the-income-at-risk\/"},"modified":"2026-11-05T18:36:05","modified_gmt":"2026-11-05T18:36:05","slug":"weight-the-audio-audit-by-the-income-at-risk","status":"publish","type":"post","link":"https:\/\/interspacemusic.com\/blog\/weight-the-audio-audit-by-the-income-at-risk\/","title":{"rendered":"Weight the Audio Audit by the Income at Risk"},"content":{"rendered":"

In September, tracks older than 18 months accounted for an implied 58.9% of Korea\u2019s top-400 digital usage<\/a>. That makes older recordings a practical focus for a catalogue buyer, including the question of how much income depends on audio whose origins have not been documented.<\/p>\n

An artificial intelligence (AI) audio check can identify that exposure before a catalogue deal closes<\/a>. The useful result is not a count of flagged tracks. It is a ranking of the income attached to each flag, followed by a decision about what the seller must document and which risk the buyer is willing to carry.<\/p>\n

Start with the income, then inspect the audio<\/h2>\n

A catalogue can contain many recordings with different earnings. Giving every recording the same audit priority would spend equal time on unequal financial exposure. Instead, put the earnings record beside the audio inventory and begin with the tracks that contribute most to the income being purchased. That follows the income-weighted approach to flagged tracks in catalogue due diligence<\/a>.<\/p>\n

For an independent label considering a sale, the same order helps before a buyer enters the room. Identify the recordings that drive the proposed deal, gather the documentation for their audio, and resolve gaps while the label can still explain how each recording was made and delivered. A buyer can use that order to decide where further review will affect the transaction. The point is to connect a question about a recording to the cash flow that recording contributes.<\/p>\n

The Korean top-400 figure measures digital usage, not catalogue earnings<\/a>. A buyer therefore needs the target catalogue\u2019s own income records before using listening patterns to set an audit priority or a price. The 58.9% figure shows why older tracks deserve attention; it cannot supply the royalty amount at risk in a particular deal.<\/p>\n

A detection flag starts a documentation request<\/h2>\n

An audio scan can expose earnings tied to recordings that nobody has documented<\/a>. That is a useful diligence finding, but the next step belongs to the rights file. A detector flag cannot establish who made a recording or who owns its rights<\/a>. Treating the flag as a final ownership decision would skip the work needed to understand what the buyer is acquiring.<\/p>\n

For each flagged recording, the buyer should ask the seller to connect the delivered audio to its creation and rights documentation. The answer should be recorded against that track\u2019s earnings, so the parties can see both the unresolved question and its financial weight. If the seller supplies a clear record, the buyer can close that item. If the documentation remains incomplete, the parties can address that specific exposure in the transaction instead of treating every flagged recording alike.<\/p>\n

This also gives a selling label a concrete preparation task. Assemble the records for its highest earning audio first, then work down the income ranking. A complete file for a low earning track does little to answer a question about a recording on which much more of the proposed purchase depends.<\/p>\n

Put each unresolved item into the terms<\/h2>\n

The available responses are distinct: an AI diligence scan can feed into escrow, indemnity or price terms before closing<\/a>. Each places the unresolved issue somewhere different in the deal. The parties should choose a term by looking at the earnings attached to the recording and the documentation still needed, rather than applying one deduction to every detection flag.<\/p>\n