How to Use AI to Read Your Royalties and Streaming Data

Why royalty data is where AI earns its keep

The core idea in this cluster is human for the art, AI for the ops. Royalty and streaming data is where that split is most obvious, because reading a distributor statement is pure ops work. There’s no creativity involved. It’s just translating a spreadsheet into answers, and AI is genuinely good at that.

A typical monthly royalty statement from a distributor might cover 30 or 40 rows if you have a small catalog, or hundreds if you’ve been releasing for a while. Each row is a different combination of track, DSP, country, and reporting period. Gross sits next to net with no explanation of what came out in between. Numbers from three months ago show up alongside this month’s because that’s how DSP reporting cycles work. A streaming dashboard is a different kind of mess: filters, date ranges, and track-level breakdowns you have to click through one at a time.

Feeding that to an AI assistant and asking plain questions is one of the highest-value things you can do with it. You’re not asking it to invent anything. You’re asking it to read what’s already there and give you a summary a human would take twenty minutes to write. That’s the task it’s built for.

The prompts that surface useful answers

Vague prompts get vague output. “Summarize my royalty statement” gives you a paragraph that restates the columns. These questions pull something you can act on.

• “What changed between this statement and the previous one?” Paste both statements and ask this. AI will flag which tracks moved up or down, which territories appeared or disappeared, and whether total gross went the same direction as net.
• “Which three tracks earned the most, and does anything look off about any of them?” The second half of that question matters. You want AI to flag a track that earned unexpectedly high or low relative to its stream count, which can point to a territory discrepancy or a rate anomaly worth digging into.
• “My gross was $X but net was $Y. What usually explains that gap?” This gets you a plain explanation of what comes out between gross and net: distributor fees, splits, recoupment, VAT. It’s a comprehension question, and it’s the one I’d give a newer artist before they spend time confused by a statement. For the full mechanics of how that gap works, reading your royalty statement covers it without shortcuts.
• “Which DSPs and territories are driving the most revenue?” Useful when you’re deciding where to put marketing spend or which playlist ecosystems to focus pitches on. AI can rank them from the raw rows faster than you can.
• “Explain what [line item] means in plain language.” Distributor statements have line items labeled for accounting software, in language artists rarely use. AI is good at translating those. Just know that for anything that affects a real payment decision, you want confirmation from your distributor or a professional before you rely on a chatbot’s read.
• “Are there any tracks with streams but zero earnings? What might cause that?” Spotify’s 1,000-stream minimum is one reason. Wrong rights ownership metadata is another. AI won’t know which one it is for your specific track, but it can lay out the possibilities so you know what to investigate. For background on the minimum threshold, how Spotify royalties work has the details.

model your gross, your splits, and your break-even with the free royalty calculator →

Treat the summary as a first pass

This is the guardrail I want to be direct about, because the stakes matter. AI can misread a royalty statement. When column headers are ambiguous, when a CSV export has inconsistent formatting, or when gross and net appear in adjacent columns without obvious labels, the model can mix them up. It can round figures in ways that compound across rows. It can confidently summarize a total that’s wrong by a meaningful margin because it missed a row with a different date format.

This isn’t a reason not to use it. The speed gain is real, and for a first pass on a complex statement it’s genuinely useful. It’s just a reason to verify before you make a decision from the numbers it hands you.

What you're handing over when you paste a statement

A royalty statement has your earnings, your track names, your territory breakdown, and sometimes your splits or agreement details. When you paste that into a third-party AI tool, the question isn’t whether it’s useful. It’s what happens to the data afterward.

Most of the major AI assistants let paid subscribers opt out of having conversations used for training, and their enterprise or API tiers usually have stronger data protections by default. Free tiers typically have more permissive retention policies. The honest advice is to check the tool’s data use policy before pasting financial data, and if you’re unsure, strip anything that goes beyond what the AI actually needs to answer your question. It doesn’t need your bank details to tell you which tracks earned most.

For your Velveteen catalog data, there’s a cleaner path. Vee reads your earnings and streaming analytics directly inside the platform, so you can ask the same questions without pasting anything into an outside tool. The data doesn’t leave Velveteen.

Asking Vee about your Velveteen earnings

For questions about your Velveteen catalog, Vee is the version that reads your actual numbers instead of working from a pasted export. It has access to your overall earnings, per-track earnings, and streaming analytics directly from your account, so “what did my top track earn last quarter” or “how are streams trending on my last release” comes back from real data.

The line to be clear about: Vee reads your Velveteen data. It does not read a PDF royalty statement you got from DistroKid or TuneCore or anyone else. For those, the paste-into-a-general-assistant approach in the earlier sections is what you’d use. The two tools do different things and neither replaces the other.

For the full picture of what Vee can and can’t do, including the other catalog and pitch actions it handles, what Vee can do has the complete list.

Same approach, different format: streaming analytics

Everything above applies to streaming dashboards too, with one practical difference. Streaming data usually comes as a CSV export or a screenshot rather than a structured statement, and AI handles both differently.

For a CSV, paste it and ask the same kinds of questions: which tracks are growing, which are declining, which sources or territories are driving most of the plays. AI can rank and compare rows faster than building a pivot table, and for a catalog of reasonable size, the answers come back in seconds.

For a screenshot, the model can read what’s visible, but it can’t scroll or click through to additional data. If you’re working from a dashboard screenshot, be specific about what’s in frame. Don’t ask it to compare trends if the image only shows this month. Give it what it needs to answer the question.

If your catalog is on Velveteen, Vee can pull streaming analytics directly without the export step. Ask “how are streams trending on my last three releases” and it reads your actual data. For external platforms, you’re exporting and pasting.

put your stream counts into the royalty calculator to see what they’re worth in dollars →

Where this fits in the bigger picture

Reading data is one of the two things AI does well in a music business context. The other is drafting words. The sibling guide on writing your artist bio and EPK with AI covers that side with the same skeptical eye.

The point of both is the same: keep the parts that are actually creative human. Hand the dense, repetitive, purely analytical work to a tool that’s faster at it than you are. A royalty statement at midnight is exactly that kind of work. You have better things to do with your attention.