---
title: "Problems and fixes"
description: "Every problem the CWR Workbench can report, in plain English: what is wrong, why it matters, how to fix it and where to fix it."
sidebar_position: 4
sidebar_label: "Problems and fixes"
mdx:
  format: md
---

# Problems and fixes

<!-- Generated from frontend/src/data/cwr-error-catalog.json by frontend/scripts/generate-cwr-public-content.js. Do not edit this file: change the source and run `npm run generate:cwr-public-content` in the frontend folder. -->

Every public Workbench issue is explained in plain English: what is wrong, why it matters, how to fix it and where to fix it in the Workbench. For the meaning of a CWR term, see the [glossary](/docs/cwr/glossary).

In the Workspace the same problems are listed on the work itself. Open the work, and each problem takes you to the field to correct. See [Fix problems on a work](/docs/workspace/catalogue/fix-problems).

## Share errors

### The shares for a right do not add up to exactly 100%. {#shares-total}

**Why it matters:** Incorrect share totals can prevent a work from being processed as intended.

**How to fix it:** Adjust the writer and publisher shares for that right until the total is exactly 100%.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publishers

**Rule:** `cwr_21_shares_total`

### The collection shares for a right add up to more than 100% in a territory. {#collection-share-total}

**Why it matters:** Collection is separate from ownership: it says who actually receives the money in a territory. If a writer keeps a collection share for a right they assigned to their publisher, both parties appear to claim the same money and the society rejects the registration.

**How to fix it:** Check the writer's collection shares against what the writer actually owns. Where the publisher owns the right outright, the writer's collection share for it should be zero.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_nwr_tr14_collection_total`

### A writer or publisher share is outside the allowed 0% to 100% range. {#shares-range}

**Why it matters:** An out-of-range share is not valid CWR ownership data and can prevent processing.

**How to fix it:** Replace the share with a number from 0 to 100.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publishers

**Rule:** `cwr_21_share_out_of_range`

### A writer or publisher share is not a number. {#shares-format}

**Why it matters:** CWR can only carry numeric shares, so the work cannot be processed reliably with this value.

**How to fix it:** Enter a number such as 50 for a 50% share.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publishers

**Rule:** `cwr_21_share_non_numeric`

### A global publisher territory is missing or changes the publisher's synchronization collection share. {#cmrra-collection-allocation}

**Why it matters:** CMRRA expects the publisher's worldwide territory to retain the publisher's applicable synchronization share.

**How to fix it:** Select the CMRRA recipient profile and regenerate the file so the publisher synchronization share remains on the publisher's worldwide territory.

**Where to fix it in the Workbench:** Generate → Recipient society

**Rule:** `cwr_21_cmrra_spt_sr_collection`

### A zero-ownership publisher role has a positive global synchronization collection share whose CMRRA allocation is not yet proven.

**Why it matters:** Ownership and collection are separate in CWR, so replacing this explicit collection value with zero could discard a genuine collection mandate.

**How to fix it:** Review the publisher chain and authoritative CMRRA collection evidence before generating this delivery.

**Where to fix it in the Workbench:** Generate → Publishers and territories

**Rule:** `cwr_21_cmrra_zero_ownership_spt_sr_collection_unresolved`

### A writer territory assigns mechanical collection to a field that CMRRA requires to be zero.

**Why it matters:** CMRRA expects the applicable mechanical collection on the publisher territory, so this allocation can prevent correct processing.

**How to fix it:** Select the CMRRA recipient profile and regenerate the file so the mechanical collection is carried on the publisher territory.

**Where to fix it in the Workbench:** Generate → Recipient society

**Rule:** `cwr_21_cmrra_swt_mr_collection`

### A writer territory assigns synchronization collection to a field that CMRRA requires to be zero.

**Why it matters:** CMRRA's delivery allocation must be represented correctly for the work to be processed as intended.

**How to fix it:** Select the CMRRA recipient profile and regenerate the file; TrackForge will correct this delivery allocation without changing ownership.

**Where to fix it in the Workbench:** Generate → Recipient society

**Rule:** `cwr_21_cmrra_swt_sr_collection`

### A publisher chain has no original publisher or acquirer with an ownership share. {#chain-no-ownership}

**Why it matters:** Each publisher chain starts from a publisher that owns part of the work. The publishers below it collect on that owner's behalf.

**How to fix it:** Enter ownership shares for the original publisher or the acquirer in the chain, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_no_ownership`

### An original publisher keeps an ownership share in a chain that has an acquirer. {#chain-original-share-with-acquirer}

**Why it matters:** An acquirer takes over the original publisher's ownership, so the original publisher is listed with no share.

**How to fix it:** Set the original publisher's ownership shares to zero and enter them for the acquirer, or change the acquirer's role.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_original_share_with_acquirer`

### An acquirer has no ownership share. {#chain-acquirer-no-ownership}

**Why it matters:** An acquirer owns the rights it acquired, so it holds a share of at least one right.

**How to fix it:** Enter the acquirer's ownership shares, or change its role if it owns no share.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_acquirer_no_ownership`

### A publisher includes a territory where it collects nothing. {#publisher-territory-no-collection}

**Why it matters:** An included territory tells societies where a publisher collects. With no collection share it says nothing, so it cannot go in the file.

**How to fix it:** Enter the publisher's collection shares for the territory, remove the territory, or exclude it instead.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_publisher_territory_no_collection`

### A publisher has more than one row for one territory with different collection shares. {#publisher-territory-conflicting-shares}

**Why it matters:** Each row becomes its own record in the file. Records for the same publisher and territory with different shares contradict each other, and a society cannot tell which share applies.

**How to fix it:** Keep one row for the territory, or combine the rows into one row that carries every share the publisher collects there.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_publisher_territory_conflicting_shares`

### A writer includes a territory where the writer collects nothing. {#writer-territory-no-collection}

**Why it matters:** An included territory tells societies where a writer collects. With no collection share it says nothing, so it cannot go in the file.

**How to fix it:** Enter the writer's collection shares for the territory, remove the territory, or exclude it instead.

**Where to fix it in the Workbench:** Generate → Work details → Writer territories

**Rule:** `cwr_21_writer_territory_no_collection`

## Identity errors

### A work is missing its stable Submitter Work ID. {#submitter-work-id}

**Why it matters:** The recipient returns this identity in its acknowledgement, and later revisions must use the same value to target the same work.

**How to fix it:** Enter a stable catalogue identifier that will not change when the title changes.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields

**Rule:** `cwr_21_submitter_work_id_missing`

### A Submitter Work ID uses a format the recipient cannot process.

**Why it matters:** An invalid identity can be rejected or returned in an unusable ACK, breaking safe correlation and revision handling.

**How to fix it:** Use 1–14 letters or numbers with no spaces; keep the same value for later revisions.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields

**Rule:** `cwr_21_submitter_work_id_format`

### Two works in the file use the same Submitter Work ID.

**Why it matters:** A duplicate makes the recipient ACK ambiguous and can attach a revision or rejection to the wrong catalogue work.

**How to fix it:** Assign a different stable Submitter Work ID to each work in the file.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields

**Rule:** `cwr_21_submitter_work_id_duplicate`

### An agreement number is longer than 14 characters or has characters a CWR file cannot carry. {#agreement-number}

**Why it matters:** A CWR file holds an agreement number in 14 plain characters. A longer or accented number would reach the society changed, so it could not be matched to your agreement.

**How to fix it:** Enter the agreement number exactly as it was issued: up to 14 letters, numbers and basic punctuation, with no accents. If the number you were given is longer, check it with whoever issued it.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_agreement_number_format`

### An IPI base number is not in the form I-001068130-6: the letter I, nine digits and one more digit, joined by hyphens. {#ipi-base-number}

**Why it matters:** An IPI base number is always 13 characters, and a CWR file holds exactly those 13. A longer or differently written number would reach the society changed, so TrackForge will not cut or alter it.

**How to fix it:** Enter the IPI base number exactly as the society shows it, for example I-001068130-6, or leave it empty: the number is optional. It is not the 11-digit IPI name number, which has its own box.

**Where to fix it in the Workbench:** Work details → Performers

**Rule:** `cwr_21_ipi_base_number_format`

### A value in this file has a character a CWR file cannot carry. {#plain-text-file}

**Why it matters:** A CWR file is plain text. TrackForge stopped rather than write a file a society could not read.

**How to fix it:** Look for accents or symbols in identifiers such as reference and agreement numbers, replace them, and generate the file again.

**Where to fix it in the Workbench:** Generate → Work details

**Rule:** `cwr_21_file_not_plain_text`

### A writer or publisher IPI name number is not in a valid numeric format. {#ipi-invalid}

**Why it matters:** A valid IPI helps the recipient match the correct rights-holder and registration account.

**How to fix it:** Check the IPI name number against society records and enter 9 to 11 digits without spaces or punctuation.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publishers

**Rule:** `cwr_21_ipi_invalid`

### A writer and publisher use the same IPI name number. {#ipi-party-type}

**Why it matters:** Recipients use the IPI registry to distinguish writer persons from publisher organizations. Reusing one IPI across both roles can make the writer role invalid and cause the work to be rejected.

**How to fix it:** Replace the duplicated value with the verified IPI assigned to each party. If the writer's IPI is unknown, leave it blank rather than using the publisher organization's IPI.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publishers

**Rule:** `cwr_21_cross_role_ipi`

### The sender ID is not a valid CWR sender code or publisher IPI name number. {#sender-id}

**Why it matters:** The sender identity tells the recipient who supplied the file and which account owns the submission.

**How to fix it:** Enter the full society-issued sender code or publisher IPI name number without spaces or punctuation.

**Where to fix it in the Workbench:** Generate → Sender details

**Rule:** `cwr_21_sender_id_invalid`

### The sender ID appears to be a shortened version of the publisher IPI name number.

**Why it matters:** A shortened identity can point the submission at the wrong account or prevent the sender from being matched.

**How to fix it:** Copy the publisher's complete IPI name number into Sender ID; TrackForge will place it into the fixed-width header correctly.

**Where to fix it in the Workbench:** Generate → Sender details

**Rule:** `cwr_21_hdr_sender_id_truncated`

### The sender ID is still the example placeholder rather than a real society-issued identity.

**Why it matters:** A placeholder cannot identify the party responsible for the submission.

**How to fix it:** Replace the example with your society-issued sender code or publisher IPI name number.

**Where to fix it in the Workbench:** Generate → Sender details

**Rule:** `cwr_21_sender_id_placeholder`

### No agreement number is given for any publisher you control. {#agreement-number-missing}

**Why it matters:** Without an agreement number, PRS and MCPS register your claim as one you state rather than one backed by an agreement, and societies in other countries may not accept it.

**How to fix it:** Add your agreement number to each publisher you control (Submitter Agreement # in the Workbench, Your agreement reference in the workspace), then check again. This is a warning: the file can be made without it.

**Where to fix it in the Workbench:** Generate → Publishers → Submitter Agreement #

**Rule:** `cwr_21_ice_assumed_claim_no_agreement`

### A CAPASSO file includes a sub-publisher or publishing administrator whose external CAPASSO relationship cannot be verified here. {#capasso-linked-party-affiliation}

**Why it matters:** CAPASSO accepts a sub-publisher or publishing administrator only when that party is directly affiliated with, or linked to, CAPASSO. An unconfirmed relationship can cause the registration to be rejected.

**How to fix it:** Confirm the CAPASSO affiliation or link for every sub-publisher and publishing administrator before submitting the file.

**Where to fix it in the Workbench:** Your CAPASSO affiliation or agreement records, before submission

**Rule:** `cwr_21_capasso_linked_party_affiliation_unverified`

### The sender name is missing. {#sender-name}

**Why it matters:** The recipient needs the sender name to identify who supplied the registration file.

**How to fix it:** Enter the company or publisher name exactly as it appears in society records.

**Where to fix it in the Workbench:** Generate → Sender details

**Rule:** `cwr_21_sender_name_blank`

### The selected sender type is not supported by the Workbench generator. {#sender-type}

**Why it matters:** The Workbench must encode a supported sender identity before it can build a valid header.

**How to fix it:** Choose Publisher (PB) as the sender type.

**Where to fix it in the Workbench:** Generate → Sender details

**Rule:** `cwr_21_sender_type_invalid`

### A writer is missing a name. {#writer-name}

**Why it matters:** A work cannot be registered reliably without identifying each writer.

**How to fix it:** Enter the writer's last name and, where available, first name.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_writer_name_blank`

### A publisher is missing a name. {#publisher-name}

**Why it matters:** The recipient needs the publisher name to identify and route the claimed interest.

**How to fix it:** Enter the publisher name exactly as it appears in society records.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_publisher_name_blank`

### The same writer appears more than once on one work. {#duplicate-writer}

**Why it matters:** Duplicate writer rows can double-count shares or create conflicting identities.

**How to fix it:** Keep one row for the writer and combine any duplicated shares into that row.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_duplicate_writer`

### A publisher record does not have a consistent, unique interested-party identifier. {#publisher-identity}

**Why it matters:** Publisher territory and writer-link records use this identifier to attach rights to the correct publisher.

**How to fix it:** Regenerate the file so each publisher has one unique identifier that is repeated on its related territory and writer-link records.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_5_5_5_spu_interested_party`

### A publisher's society is not a society code.

**Why it matters:** A CWR file names each society by its code. A value that is not one tells the receiving organisation nothing about where to send the share, so the work cannot be registered.

**How to fix it:** Choose the publisher's society by name for each right it holds a share of, then generate again.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `publisher.society.invalid`

### A writer's society is not a society code.

**Why it matters:** A CWR file names each society by its code. A value that is not one tells the receiving organisation nothing about the writer's membership, so the work cannot be registered.

**How to fix it:** Choose the writer's society by name, or leave it blank if it is unknown, then generate again.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `writer.society.invalid`

### A writer record does not have a consistent, unique interested-party identifier. {#writer-identity}

**Why it matters:** Writer territory and publisher-link records use this identifier to attach rights to the correct writer.

**How to fix it:** Regenerate the file so each writer has one unique identifier that is repeated on related territory and publisher-link records.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_5_9_4_swr_interested_party`

### A recording ISRC is not a valid ISRC. {#recording-isrc-invalid}

**Why it matters:** An ISRC has 12 characters: a two-letter country code, a three-character registrant code, the last two digits of the year and a five-digit number. Societies use it to link recordings to the work, so an invalid one is rejected.

**How to fix it:** Correct the recording's ISRC from the label's or distributor's records, or leave it blank.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → ISRC

**Rule:** `cwr_21_recording_isrc_invalid`

## Structure errors

### A publisher territory does not match the selected AllTrack account territory. {#alltrack-account-territory}

**Why it matters:** AllTrack applies one territory policy to the entire account and can overcount mechanical shares when worldwide and country territories overlap.

**How to fix it:** Select the AllTrack profile that matches the account agreement and use only that included territory across the file.

**Where to fix it in the Workbench:** Generate → Destination rules and Publishers → Territories

**Rule:** `cwr_21_alltrack_account_territory_scope`

### CAPASSO takes Africa only, and a territory on this work says something else. {#capasso-africa-territory}

**Why it matters:** CAPASSO accepts Africa-only territories for writers and publishers. A worldwide or other territory can register the wrong territory with CAPASSO or get the work rejected.

**How to fix it:** On the party named, remove the territory rows that do not match (for example World), or replace them: the 54 African countries for a publisher, Africa for a writer. With no rows, TrackForge fills in the right ones for CAPASSO. In the Workbench, also choose CAPASSO — Africa administration under Destination rules.

**Where to fix it in the Workbench:** Generate → Destination rules and Writers/Publishers → Territories

**Rule:** `cwr_21_capasso_africa_territory_scope`

### A work has no writers. {#no-writers}

**Why it matters:** At least one writer is required to identify the authorship being registered.

**How to fix it:** Add each person who composed the music or wrote the lyrics.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_no_writers`

### A performer has no name. {#performer-name}

**Why it matters:** Each performer in the file must be named.

**How to fix it:** Enter the performer’s name, or remove the empty performer.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Performer / Artist

**Rule:** `artist.name_missing`

### A new work registration has no publisher. {#missing-publisher}

**Why it matters:** The generator needs a publisher interest to represent who is administering the new registration.

**How to fix it:** Add the administering publisher, or record the appropriate writer as self-published.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_missing_publisher`

### A writer is missing their role in creating the work. {#writer-designation}

**Why it matters:** The writer designation is required to describe whether the party composed, authored or adapted the work.

**How to fix it:** Choose the writer's role, commonly Composer (C), Author (A) or Composer/Author (CA).

**Where to fix it in the Workbench:** Generate → Work details → Writers → Role

**Rule:** `cwr_21_writer_designation_blank`

### A publisher has an unsupported relationship type. {#publisher-type}

**Why it matters:** The relationship type determines how the publisher is represented in the CWR ownership chain.

**How to fix it:** Choose the relationship that matches the agreement: Original Publisher, Publisher Administrator, Acquirer, Sub-publisher or another supported type.

**Where to fix it in the Workbench:** Generate → Work details → Publishers → Relationship

**Rule:** `cwr_21_publisher_type_invalid`

### There are no works in the generation request. {#no-works}

**Why it matters:** A CWR registration file needs at least one work transaction.

**How to fix it:** Add a work manually or import one or more works from CSV.

**Where to fix it in the Workbench:** Generate → Works

**Rule:** `cwr_21_no_works`

### A publisher record has an invalid field or lacks a society code for a claimed right. {#publisher-society}

**Why it matters:** Without valid publisher identity and routing data, the claimed interest may not be processed correctly.

**How to fix it:** Add the publisher's three-digit society code for each claimed right, correct any other reported field, and regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_5_4_4_spu_field_validation`

### A publisher holds a share of a right but has no society for that right.

**Why it matters:** The society tells the receiving organisation where to send that share. Without one the share has nowhere to go, so the work cannot be registered.

**How to fix it:** Choose the publisher's society for each right it holds a share of, or set that share to zero, then generate again.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `publisher.society.missing`

### An uncontrolled writer claims a share without a society code or a link to a controlling publisher. {#writer-society}

**Why it matters:** The recipient needs either the writer's society routing or a publisher link to understand who administers the claimed share.

**How to fix it:** Add the writer's society code, or add the publisher-writer link that identifies the controlling publisher, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Writers and publisher links

**Rule:** `cwr_21_5_10_3_swr_record_validation`

### A controlled writer holds a share of a right, but neither the writer nor the writer's publisher has a society for that right.

**Why it matters:** The society tells the receiving organisation where to send that share. Without the writer's society, or one on the writer's publisher, the share has nowhere to go, so the work cannot be registered.

**How to fix it:** Choose the writer's society for that right, or the society of the publisher that collects it, then generate again.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `writer.society.missing`

### A territory entry is not one societies recognise. {#territory-unknown}

**Why it matters:** Societies route collection by territory, so each entry must be a country, a region or a list they recognise. TrackForge reports the entry instead of guessing a territory or treating it as worldwide.

**How to fix it:** Replace the territory with a country or region name, a list of countries, or a worldwide entry with exclusions, then check again.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_territory_unknown`

### A territory entry is a territory that no longer exists. {#territory-inactive}

**Why it matters:** Retired territories such as the Soviet Union or Yugoslavia no longer exist in the territory list societies use, so they cannot register or route collection for them.

**How to fix it:** Replace the retired territory with the current countries you collect in, then check again.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_territory_inactive`

### A publisher territory record has an invalid territory, collection share or inclusion setting. {#publisher-territory}

**Why it matters:** Publisher territory records define where and for which rights the publisher collects.

**How to fix it:** Check the publisher's territory, inclusion or exclusion setting, and collection shares, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Publisher territories

**Rule:** `cwr_21_5_7_3_spt_record_validation`

### A publisher territory field is invalid or does not match its publisher.

**Why it matters:** A territory must link to the correct publisher and contain valid shares and territory data to be processed reliably.

**How to fix it:** Correct the publisher link, collection shares or territory code reported for the territory, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Publisher territories

**Rule:** `cwr_21_5_7_4_spt_field_validation`

### A writer territory record has an invalid territory, collection share or inclusion setting. {#writer-territory}

**Why it matters:** Writer territory records define where and for which rights the writer collects.

**How to fix it:** Check the writer's territory, inclusion or exclusion setting, and collection shares, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Writer territories

**Rule:** `cwr_21_5_11_3_swt_record_validation`

### A writer territory field is invalid or does not match its writer.

**Why it matters:** A territory must link to the correct writer and contain valid shares and territory data to be processed reliably.

**How to fix it:** Correct the writer link, collection shares or territory code reported for the territory, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Writer territories

**Rule:** `cwr_21_5_11_4_swt_field_validation`

### A publisher-writer relationship does not link to valid publisher and writer identities in the same work. {#publisher-writer}

**Why it matters:** The relationship tells the recipient which publisher controls the writer's interest.

**How to fix it:** Correct the publisher and writer links so both refer to parties in the same work, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Publisher-writer links

**Rule:** `cwr_21_5_12_2_pwr_record_validation`

### A controlled-writer record appears after an uncontrolled writer. {#writer-record-order}

**Why it matters:** CWR recipients process controlled-writer records before other writers and can reject the whole work when those blocks are reversed.

**How to fix it:** Regenerate the file so all controlled writers and their territory and publisher links appear before uncontrolled writers.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_nwr_tr18_record_order`

### A publisher chain does not start with an original publisher or income participant. {#chain-first-publisher-role}

**Why it matters:** Societies read each chain from the publisher that holds the rights. A sub-publisher, administrator or acquirer can only appear below that publisher.

**How to fix it:** Start the chain with the original publisher and link the other publishers below it.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_first_publisher_role`

### A publisher chain has more than one original publisher. {#chain-second-original-publisher}

**Why it matters:** Societies read each chain from its one original publisher. A second original publisher starts a chain of its own.

**How to fix it:** Give the second original publisher its own chain, or change its role if it acts for the first publisher.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_second_original_publisher`

### An acquirer does not follow an original publisher in its chain. {#chain-acquirer-without-original}

**Why it matters:** An acquirer is listed after the original publisher whose rights it acquired.

**How to fix it:** Put the original publisher first in the chain with the acquirer below it, or change the acquirer's role.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_chain_acquirer_without_original`

### A publisher excludes territories but includes none where it collects. {#exclusions-without-collection}

**Why it matters:** An exclusion takes a territory out of an area where the publisher collects. With no such area there is nothing to take it from.

**How to fix it:** Add the territory where the publisher collects, with its collection shares, or remove the excluded territories.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_publisher_exclusions_without_collection`

### Two publishers you control collect the same right in the same territory. {#publisher-collection-overlap}

**Why it matters:** Only one of your publishers can collect each right in a territory. Overlapping territories leave it unclear who should be paid, so societies reject the registration.

**How to fix it:** Change one publisher's territories so no right is collected twice in the same territory.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_publisher_collection_overlap`

### A territory is attached to a publisher you do not control. {#opu-territory-scope}

**Why it matters:** A registration lists territories only for the publishers you control. Where an outside publisher collects is for that publisher to register.

**How to fix it:** Attach the territory to a publisher you control, or remove it, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Territories

**Rule:** `cwr_21_opu_territory_scope`

## Format errors

### The International Standard Musical Work Code (ISWC) is not in the expected format. {#iswc-format}

**Why it matters:** A malformed ISWC cannot reliably match the work to its existing international registration.

**How to fix it:** Check the ISWC against society records and enter it in the form T-000.000.000-0.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → ISWC

**Rule:** `cwr_21_iswc_format`

### The International Standard Musical Work Code (ISWC) has the wrong final check digit. {#iswc-check-digit}

**Why it matters:** An incorrect check digit means the identifier does not validate and may not match the intended work.

**How to fix it:** Copy the complete ISWC again from an authoritative society record.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → ISWC

**Rule:** `cwr_21_iswc_check_digit`

### A work is missing its title. {#title-blank}

**Why it matters:** The title is a mandatory work identity field used to process and match the registration.

**How to fix it:** Enter the work's registered title.

**Where to fix it in the Workbench:** Generate → Work details → Title

**Rule:** `cwr_21_title_blank`

### A work duration is not in hours, minutes and seconds format. {#duration-format}

**Why it matters:** A malformed duration cannot be encoded correctly in the fixed-width CWR record.

**How to fix it:** Enter the duration as HH:MM:SS, for example 00:03:45.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Duration

**Rule:** `cwr_21_duration_invalid`

### A work duration is set to zero. {#duration-zero}

**Why it matters:** A zero duration can be mistaken for known zero-length data rather than an unknown value.

**How to fix it:** Enter the actual duration, or clear the field when the duration is unknown.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Duration

**Rule:** `cwr_21_duration_zero`

### A work language is not a recognised two-letter code. {#language-code}

**Why it matters:** An unrecognised language code cannot be interpreted consistently by the recipient.

**How to fix it:** Choose a recognised two-letter language code such as EN, ES, FR or DE.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Language

**Rule:** `cwr_21_language_invalid`

### A work has an unsupported version type. {#version-type}

**Why it matters:** The version type tells the recipient whether this is the original work or a modified version.

**How to fix it:** Choose Original for the first version or Modified for an arrangement, translation or adaptation.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Version

**Rule:** `cwr_21_version_invalid`

### A writer record contains an invalid field or society code.

**Why it matters:** Invalid writer identity or routing data can prevent the writer's interest from being processed correctly.

**How to fix it:** Correct the reported writer field and use the writer's three-digit society code, then regenerate the file.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_5_10_4_swr_field_validation`

### A work title uses only characters a CWR file cannot carry. {#title-unrepresentable}

**Why it matters:** CWR files carry titles in Latin letters, digits and basic punctuation. Characters from other scripts, such as Cyrillic or Japanese, are left out, and a work cannot be registered without a title.

**How to fix it:** Enter the work title in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Title

**Rule:** `cwr_21_title_unrepresentable`

### A work title has letters a CWR file cannot carry. {#title-letters-unrepresentable}

**Why it matters:** CWR files carry titles in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society would register the work under the wrong title.

**How to fix it:** Enter the work title in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Title

**Rule:** `cwr_21_title_letters_unrepresentable`

### A writer's last name uses only characters a CWR file cannot carry. {#writer-name-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Characters from other scripts, such as Cyrillic or Japanese, are left out, and a writer cannot be identified without a name.

**How to fix it:** Enter the writer's last name in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_writer_name_unrepresentable`

### A publisher name uses only characters a CWR file cannot carry. {#publisher-name-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Characters from other scripts, such as Cyrillic or Japanese, are left out, and the society needs the publisher's name to identify the claim.

**How to fix it:** Enter the publisher name in Latin letters, for example its romanised form or the name registered with the society, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_publisher_name_unrepresentable`

### An alternative title has letters a CWR file cannot carry. {#alternate-title-letters-unrepresentable}

**Why it matters:** CWR files carry titles in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society would record the wrong alternative title.

**How to fix it:** Enter the alternative title in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Alternative Titles

**Rule:** `cwr_21_alternate_title_letters_unrepresentable`

### A writer's name has letters a CWR file cannot carry. {#writer-name-letters-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society could match the wrong writer.

**How to fix it:** Enter the writer's name in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Writers

**Rule:** `cwr_21_writer_name_letters_unrepresentable`

### A publisher name has letters a CWR file cannot carry. {#publisher-name-letters-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society could match the wrong publisher.

**How to fix it:** Enter the publisher name in Latin letters, for example its romanised form or the name registered with the society, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Publishers

**Rule:** `cwr_21_publisher_name_letters_unrepresentable`

### A performer name has letters a CWR file cannot carry. {#performer-name-letters-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society would record the wrong performer.

**How to fix it:** Enter the performer name in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Performer / Artist

**Rule:** `cwr_21_performer_name_letters_unrepresentable`

### A record label has letters a CWR file cannot carry. {#recording-label-letters-unrepresentable}

**Why it matters:** CWR files carry names in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society would record the wrong record label.

**How to fix it:** Enter the record label in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details

**Rule:** `cwr_21_recording_label_letters_unrepresentable`

### An album title has letters a CWR file cannot carry. {#album-title-letters-unrepresentable}

**Why it matters:** CWR files carry titles in Latin letters, digits and basic punctuation. Accented letters are written as plain letters, but letters from other scripts, such as Cyrillic, Greek or Japanese, would be left out, so the society would record the wrong album title.

**How to fix it:** Enter the album title in Latin letters, for example its romanised form, then check the work again.

**Where to fix it in the Workbench:** Generate → Work details

**Rule:** `cwr_21_album_title_letters_unrepresentable`

### A title is too long for the CWR file. {#text-too-long}

**Why it matters:** The CWR file holds at most 60 characters for a title, and a few letters, such as ß, take two; TrackForge will not cut it short, because the society would register a different title from yours.

**How to fix it:** Shorten the title to fit, for example by using the form registered with the society.

**Where to fix it in the Workbench:** Generate → Work details

**Rule:** `cwr_21_text_too_long`

### A work date is not a real date. {#work-date-invalid}

**Why it matters:** Societies record work dates exactly. A date that does not exist, such as 30 February, cannot be sent.

**How to fix it:** Enter a real date for the work, or leave it blank.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Copyright date

**Rule:** `cwr_21_date_invalid`

### A recording release date is not a real date. {#recording-release-date-invalid}

**Why it matters:** Societies record the first release date exactly. A date that does not exist, such as 30 February, cannot be sent.

**How to fix it:** Enter the recording's real first release date, or leave it blank.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Release Date

**Rule:** `cwr_21_recording_release_date_invalid`

### A recording duration is not in hours, minutes and seconds. {#recording-duration-invalid}

**Why it matters:** A CWR file stores a duration as hours, minutes and seconds, with minutes and seconds below 60. Other values cannot be sent.

**How to fix it:** Enter the recording length as minutes and seconds, such as 3:45, or leave it blank.

**Where to fix it in the Workbench:** Generate → Work details → Advanced fields → Recording Duration

**Rule:** `cwr_21_recording_duration_invalid`

## File errors

### A fixed-width CWR field contains data that does not meet its format or length rule. {#record-length}

**Why it matters:** Invalid field data can prevent the record, work or file from being processed correctly.

**How to fix it:** Correct the source data in the system that created the file, regenerate it, and validate the new file.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_2_1_6_field_validation`

### The CWR file header contains invalid or missing sender information. {#header-fields}

**Why it matters:** The header identifies the sender and file version; an invalid header can cause the whole file to be rejected.

**How to fix it:** Correct the sender or header settings in the system that created the file, then regenerate it.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_3_5_3_hdr_field_validation`

### The CWR group header is missing required information or is in the wrong format. {#group-header}

**Why it matters:** The group header opens and identifies a transaction group; an invalid one can prevent the group from being read.

**How to fix it:** Regenerate the file from the source system so it creates a complete group header.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_3_6_3_grh_field_validation`

### The file does not use the required CWR line endings. {#line-endings}

**Why it matters:** Incorrect line endings can make the whole fixed-width file unreadable or cause it to be rejected.

**How to fix it:** Regenerate the file from the source system and avoid opening and resaving it in a text editor.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_crlf_line_endings`

### The CWR file is incomplete or its header, group and trailer records are in an invalid order. {#file-structure}

**Why it matters:** A malformed control-record structure can cause the whole file to be rejected before its works are processed.

**How to fix it:** Regenerate the complete file from the source system and validate the new copy.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_3_4_file_level_validation`

### A line starts with an unknown or misplaced CWR record type. {#record-prefixes}

**Why it matters:** The record prefix tells the recipient how to interpret every fixed-width line; an invalid prefix can prevent processing.

**How to fix it:** Regenerate the file from the source system and avoid manually changing its record codes.

**Where to fix it in the Workbench:** Your publishing administration system, then Validate

**Rule:** `cwr_21_2_1_5_record_prefixes`