Freelance Music Royalty Auditor (Top 1% Only)

Job Description

About Revorion

Revorion is an AI-powered royalty reconciliation and revenue recovery platform. We find the money that artists, songwriters, publishers, and rights holders are owed but never receive — and we're building the technology that makes recovery systematic rather than episodic.

We work with major music publishers, management companies, and rights holders on catalogs that matter.

The Role

We're looking for an exceptional freelance music royalty auditor who can own every aspect of a royalty audit end-to-end — not a reviewer, not a checker, but someone who does substantive, original analytical work and stands behind it.

You'll work directly with our team on live client engagements: scoping audits, interpreting contracts, reconciling royalty statements against contractual terms, tracing income streams across societies, DSPs, distributors, labels, publishers, and sub-publishers, quantifying underpayments, and building findings that hold up when the counterparty's business affairs or royalty team pushes back.

You will receive contracts, royalty statements, catalog files, rate schedules, and source-level transactional data and be expected to turn them into defensible claims with a clear evidentiary trail.

This starts as a freelance engagement. For the right person, there is a real path to full-time work — but we start freelance, and we both find out.

What You'll Do

\n
• Conduct full-scope royalty audits across mechanical, performance, sync, digital, international, and other royalty streams
\n
• Reconcile label, publisher, distributor, and PRO statements against contractual terms, rate schedules, catalog data, and underlying transaction records
\n
• Turn contracts into audit logic: interpret royalty rates, escalations, deductions, reserves, recoupment provisions, controlled-composition clauses, territory-specific terms, and other contractual provisions, then test actual payments against them
\n
• Trace revenue across the chain — DSP to distributor to label to publisher to writer — and identify where money is lost, misallocated, delayed, or underpaid
\n
• Identify, document, and quantify claims including unpaid royalties, misapplied rates, unmatched income, black-box exposure, missing escalations, incorrect deductions, currency-conversion issues, and foreign sub-publishing discrepancies
\n
• Reconstruct royalty calculations independently when necessary, from contract terms through source data to the final statement
\n
• Build audit workpapers and findings memos that are precise, reproducible, and strong enough to negotiate from
\n
• Work comfortably with very large royalty datasets, including engagements involving millions of transaction rows
\n
• Work alongside our technology — validating what our AI catches, identifying what it misses, and distinguishing genuine claims from false positives
\n
• Help translate audit methodologies, judgment calls, and recurring failure patterns into repeatable rules, product requirements, and automated audit logic
\n

Who You Are

\n
• Exceptional at the craft. We're looking for someone in the top tier of practicing music royalty auditors: someone who has personally led complex audits, found material underpayments others missed, and can defend every finding down to the underlying contract provision and transaction data
\n
• Deeply experienced. You've run real audits against real counterparties — labels, publishers, distributors, PROs, or other royalty-paying entities — and recovered real money
\n
• Broad enough to lead, deep enough to catch what others miss. You don't need to be the world's foremost expert in every royalty stream, but you should have deep expertise in multiple areas and enough breadth to lead a complex audit from start to finish
\n
• Forensic. You know where royalty systems tend to break, which assumptions need to be tested, and which apparently minor discrepancies can point to much larger problems
\n
• Detail-oriented to the point of obsession. A misapplied controlled-composition clause, incorrect escalation, improper deduction, or currency conversion performed using the wrong methodology does not get past you
\n
• Substantive. You do the work yourself, at a high level, and your analysis is the product
\n
• Technically capable. You are highly proficient in Excel and comfortable manipulating large datasets. SQL, Python, royalty accounting systems, or other analytical tooling are a strong plus
\n
• AI-forward. You're interested in figuring out which parts of expert royalty auditing can be systematized and which still require human judgment
\n
• Built for start-up culture. Fast, direct, low-ego, high-ownership. No bureaucracy to hide behind
\n

Strong candidates will often have many of the following:

\n
• 7+ years of royalty accounting, royalty audit, forensic accounting, music business affairs, or closely related experience
\n
• Personally led royalty audits resulting in meaningful recoveries
\n
• Experience auditing major labels, publishers, distributors, societies, or sophisticated independent rights holders
\n
• Experience independently reconstructing royalty calculations from contract terms and underlying source data
\n
• Familiarity with large-scale DSP and transactional royalty data
\n

These are indicators, not rigid requirements. Demonstrated ability matters more than pedigree.

Logistics

\n
• Freelance to start; potential path to full-time, including equity
\n
• Remote is fine, or work from our offices in NYC
\n
• We expect to pay premium market rates for exceptional experience: we want the best and pay for it
\n
• Send us your hourly rate with your application
\n

How to Apply

Email your resume to View email address on ziprecruiter.com with the subject line: "Detail-oriented top 1% royalty auditor"

In the body of the email, include:

\n
1. Your full name
\n
2. Your hourly rate
\n
3. Three bullet points describing the areas of royalty auditing where you believe you are genuinely exceptional
\n
4. Describe the most difficult or material royalty discrepancy you personally identified. Tell us:
\n

\n
• What was wrong
\n
• How you found it
\n
• How you proved it
\n

Applications that don't follow these instructions exactly won't be read. Detail-oriented starts now.