This guide describes how to deliver CWR (Common Works Registration) files to AllTrack for work registration, and how to retrieve the acknowledgment (ACK) files we return.
Please read it fully before your first transmission and keep it for reference.

1. What we accept

Standard	CISAC Common Works Registration (CWR)
Version	CWR 2.1
File extension	Files must end in .V21 (uppercase). AllTrack only picks up files matching this extension.
Encoding	Plain text, fixed-width records, one record per line, as defined by the CWR 2.1 functional specification.
Filename	CWR standard convention CWyynnnnsss_rrr.V21 (see Section 5).

2. AllTrack receiver code

AllTrack CWR receiver code: 786

Use 786 as the receiver segment (rrr) when naming the CWR files you send us (see Section 5). This identifies AllTrack as the destination society/agency for the transmission.

3. Do you need a sender code?

Short answer: no — you don't need to obtain a sender code from AllTrack or CISAC in order to submit CWR. You simply need to generate a valid file header and file name.

Every CWR file begins with a Transmission Header (HDR) record that carries your sender type, sender ID, and sender name. These are mandatory in the CWR 2.1 spec, so your HDR must be well-formed:

• Sender type — a 2-character code: PB (Publisher), SO (Society), AA (Administrative Agency).
• Sender ID — your 9-character CWR/CISAC sender code, or your IPI Name Number. (An 11-digit IPI may be split across the sender-type + sender-ID fields per the CWR convention.)
• Sender name — your registered submitter name.

AllTrack does not maintain a sender whitelist. We do not reject your files because the sender code isn't pre-registered with us. Instead, your identity is established by the dedicated SFTP account/folder we provision for you — every file dropped in your folder is attributed to your AllTrack member account automatically.

Practically: send a spec-valid HDR with your real sender ID (CWR sender code or IPI). You do not need to request or register a special sender code with AllTrack before you begin.

4. Work Territories

Collection shares in CWR are territory-specific: each publisher (SPU) record is followed by one or more territory (SPT) records stating the collection shares for a given territory. AllTrack, however, does not administer works on a per-territory basis — the territory in which we collect for you is fixed by your AllTrack membership agreement, not by the works you register.

When we ingest a work, we read the collection shares from the SPT record matching the territory covered by your agreement. Any other SPT territories are not processed:

• SPT records for territories outside your agreement are ignored — they do not create territory-specific shares on the work.
• Sending SPT records on specific works for a sub-territory of your AllTrack account-level agreement territory (ex: sending 'US' when your agreement is 'WORLD') will not limit the territories for which we collect for that work.

Practically: include exactly one SPT record per publisher, stating the collection shares for the territory named in your AllTrack agreement (for most members this is WORLD or UNITED STATES). If you are unsure which territory your agreement covers, confirm with your AllTrack contact before your first delivery.

5. Filename convention

Name each CWR file using the standard CWR pattern: CW yy nnnn sss _ rrr .V21

CW	Literal prefix for a CWR work-registration file.
yy	Two-digit year of creation (e.g. 26).
nnnn	Your sequence number for the transmission (e.g. 0001), zero-padded.
sss	Your sender code.
rrr	Receiver code = 786 (AllTrack).
.V21	CWR version 2.1 extension (required).

Example: CW260001123_786.V21

6. SFTP connection

Protocol	SFTP (SSH File Transfer Protocol)
Host	sftp.alltrack.com
Port	22
Username	<USERNAME> (provided separately)
Password	<PASSWORD> (provided separately)

7. Folder layout

Your SFTP account contains the following folders:

Folder	Direction	Purpose
/NEW NOTIFICATIONS	You → AllTrack	Upload your CWR (.V21) files here. AllTrack polls this folder, ingests each file, then moves it to the archive folder.
/ACKs	AllTrack → You	AllTrack writes an acknowledgment (ACK) file here for each transmission we process. Poll this folder to retrieve them.
/PROCESSED	AllTrack (archive)	Files we have already picked up are moved here, so you can confirm receipt.

Exact folder names for your account are confirmed during provisioning and may differ slightly from the standard layout above.

8. Delivery workflow

1. Generate a CWR 2.1 file with a valid HDR (your sender identity) and a filename using receiver code 786.
2. Upload it to /NEW NOTIFICATIONS via SFTP.
3. Upload the file completely before it becomes visible — use a temporary name or .tmp suffix and rename to .V21 only once the upload finishes, so AllTrack never ingests a partial file.
4. AllTrack ingests the file, registers the works, and moves the original to /PROCESSED.
5. Retrieve the corresponding ACK from /ACKs and reconcile it against your submission. The ACK reports per-transaction acceptance, conflicts, and rejections.

9. Acknowledgments (ACK)

For each processed transmission, AllTrack returns a CWR ACK file to /ACKs. The ACK identifies AllTrack as the sender and your organization as the receiver, and reports the outcome of each transaction (AS accepted, AC accepted with changes, RA rejected, etc.). Please build ACK reconciliation into your workflow so registration issues are caught early.

10. Support & onboarding checklist

• ☐ SFTP credentials received and connection tested against sftp.alltrack.com:22.
• ☐ Folder access confirmed (/NEW NOTIFICATIONS, /ACKs, /PROCESSED).
• ☐ Sender identity (type + sender ID / IPI + name) confirmed in your HDR.
• ☐ Filename convention verified, using receiver code 786.
• ☐ A small test CWR file delivered and its ACK successfully retrieved.

For onboarding help or technical questions, contact the AllTrack team at <SUPPORT-EMAIL>.

---

AllTrack — CWR Onboarding Guide • Confidential: intended for the named delivery partner only. • Credentials and receiver code should be verified with your AllTrack contact before first delivery.