# BTR Music usage report — flat-file layout

Profile id: `DSR-FlatFile/BasicAudioProfile/BTR-1.0`. UTF-8, one record per line, **tab**
separated, **pipe** (`|`) as secondary delimiter inside a cell. No header row; record type
is the first cell. Sorted by BTR track id then territory. File name `BTR_<PARTNER>_<YYYY-MM>.tsv`.
A CSV twin (`.csv`, with a header row) carries the same rows for spreadsheets.

**Usage definition:** a qualified stream — 60 seconds of playback for a standard-length track
(scaled for very short or very long tracks), counted once per stream. `qualified_streams` is that count; `unique_listeners` is the distinct listeners behind them. Territory = listener's country (ISO 3166-1 alpha-2), `ZZ` = unknown.

BTR Music's DDEX Party ID is pending registration; the header will carry it once issued. Until then sample files show `PADPIDA-PENDING` in the SenderPartyId (BTR) position.

| Record | Columns (in order) |
|---|---|
| `HEAD` | `HEAD`, `DSR`, ProfileId, SenderPartyId (BTR), SenderName, RecipientPartyId (your DPID), RecipientName, MessageId, MessageCreatedDateTime, PeriodStart, PeriodEnd, Currency, ServiceDescription |
| `SY01` | `SY01`, SummaryId, UseType, CommercialModelTypes (pipe-separated), Territory, ServiceName, NumberOfUsages |
| `RE01` | `RE01`, BlockId, DspReleaseId (= ICPN), ICPN, ReleaseTitle, DisplayArtist, LabelName, PLine, ReleaseType |
| `AS01` | `AS01`, BlockId, ISRC, Title, DisplayArtist, Duration (ISO 8601), DspResourceId (BTR track id), DspResourceUrl |
| `SU01` | `SU01`, BlockId, ISRC, UseType, CommercialModelTypes, Territory, NumberOfUsages, NumberOfUniqueUsers, PeriodStart, PeriodEnd |
| `FOOT` | `FOOT`, NumberOfLines (incl. FOOT), NumberOfBlocks, TotalUsages |

One block per track: `RE01`, `AS01`, then one `SU01` per territory.

CSV columns: `period, isrc, upc, track_title, artist, release_title, territory, qualified_streams, unique_listeners, btr_track_id`.

This layout follows the DDEX DSR flat-file architecture (Part 1 v1.4) and Basic Audio Profile
record naming. Column sets are BTR's published subset; a full DSR profile mapping is provided on
request after the DDEX implementation licence exchange.