Royalty statements are PDFs no one wants to read. Patchline’s royalty analysis parses them in seconds, computes totals, finds anomalies (missing platforms, unexpected drops, payment-window cutoffs), and forecasts the next period. Pro+ includes royalty analysis. 5 credits per statement.Documentation Index
Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt
Use this file to discover all available pages before exploring further.
What it does
Upload a PDF → Aria returns:- Total earnings across all tracks
- Per-track breakdown with platform mix
- Per-platform totals (Spotify, Apple, YouTube, Tidal, Amazon, etc.)
- Anomalies flagged automatically
- Period-over-period comparison if prior statements exist
- Revenue forecast for next period
Supported formats
| Source | Status |
|---|---|
| Distrokid | ✓ |
| Tunecore | ✓ |
| CD Baby | ✓ |
| Amuse | ✓ |
| United Masters | ✓ |
| Label statements (custom format) | ✓ — parsing improves with each one we see |
| Publishing statements (ASCAP, BMI, SoundExchange) | ✓ |
| DDEX DSR | ✓ |
How to upload
Web
Sidebar → Royalties → drag-and-drop PDF → wait 30–60s for parse.Via Aria
What anomaly detection catches
Common anomalies the royalty parser flags:| Anomaly | What it means | Example |
|---|---|---|
| Zero earnings on a platform with streams | Payment-window cutoff or platform glitch | ”Late Bloom earned $0 on Apple despite 4,200 streams” |
| Sudden drop on a previously-strong platform | Possible removal or playlist drop | ”Sleeper dropped from 12 on Spotify mo/mo” |
| Track in catalog missing from statement | Distribution gap | ”Mira - November shows on Spotify but isn’t on this statement” |
| Suspiciously consistent earnings | Possible stream manipulation flag | ”Same $43.21 every month — worth checking” |
| Currency conversion losses | Multiple-currency statements | ”USD-equivalent dropped 3% from FX, not from performance” |
Example output
Privacy
- PDFs are stored encrypted with retention appropriate for legal and tax purposes.
- Only you have access — no shared dashboards expose royalty data.
- Patchline does not use royalty statements to train models.
Pricing
| Action | Credit cost |
|---|---|
| Parse a statement (PDF) | 5 |
| Period comparison query | 1 |
| Forecast query | 1 |
| Anomaly re-scan | 1 |
Related pages
- Streaming insights — the stream-side counterpart
- Aria’s research mode — ask “any anomalies in my royalty statements?” to surface flagged lines
- Plans & credits — credit cost
FAQ
Does Patchline pay me royalties?
Does Patchline pay me royalties?
No. Royalties come from your distributor (Distrokid, Tunecore, etc.)
or label. Patchline reads the statements they send you and finds
insights — we don’t sit in the money flow.
What if my statement format isn't supported?
What if my statement format isn't supported?
Email it (with permission) to support@patchline.ai. Each new format
improves the parser. Most major distributors and publishers are
already supported.
Can I export the parsed data?
Can I export the parsed data?
Yes — CSV per statement, or aggregated cross-statement (Scale+).
Is the forecast accurate?
Is the forecast accurate?
Typically within ±10% if you have 3+ months of prior statements.
Less reliable for new releases or seasonal genres.