Combine music royalty statements into one Excel earnings tape
By Perpendis · Published 16 Aug 2026 · Reviewed 16 Aug 2026
DistroKid, TuneCore, CD Baby, Symphonic, ASCAP, the MLC, publisher exports — any mix, any
period. One normalized dataset, verified to the cent.
Files never leave your browser Tied out against each statement's own totals Full results, no account
One cent in binary repeats forever — a float keeps 64 bits and stops at the red mark. This engine keeps exact decimals. Every pixel above is a real bit of 1/100.
Drop statements here — or click to choose
CSV, TSV, TXT or ZIP · multiple files welcome
Waiting for statements
Downloads
Your saved sessions
Summaries only — your statements were parsed in this tab and never uploaded.
Loading…
Drop any mix of statements Every file tied out to the cent Excel tape + CSV, yours to keep
What this proves — and what it doesn't
TIED proves the extraction, not the source. Extracted rows sum to the statement's own
printed totals within $0.01. It cannot prove the vendor reported your royalties correctly.
SELF-CONSISTENT is normal. Most machine exports print no totals — internal checks
passed, there was simply no stated total to reconcile against.
Unknown formats are best-guess. Unmatched layouts get a header-vocabulary mapping,
labelled as such. Unreadable amounts become warnings — never silent zeros.
Nothing is uploaded. Parsing runs in WebAssembly in this tab — go offline and it
still works. Saved history stores summary numbers only. Downloads use a free account's
allowance of 120 pages a month (1 page = 500 rows); on-screen results are never limited.
Plain-English walkthroughs of the messy parts — reading, converting and reconciling statements.
All guides →
Bigger job?
Catalog sale, diligence, or a back-office backlog — including label PDFs, foreign-society
files and legacy formats — handled under NDA, tie-out on every statement.
Perpendis built the Nash royalty engine (Rust → WebAssembly) that runs on
this page, and wrote the format references from each vendor's own documentation and the
engine's test fixtures. These pages were drafted with AI assistance and checked line by line
against those sources. Corrections welcome:
platform@vbounds.com.