What you will learn
- How royalty contracts are stored as data
- How sales are imported and linked to titles
- How royalties and advances are calculated
- How author statements are generated
- How disputes are handled per statement
- What to build first in a royalty system
What this project is
Royalties depend on two things that are often kept apart: contract terms and sales records. When terms live in contracts and sales live in channel reports, each statement is assembled by hand, advances are forgotten, and authors dispute figures they cannot check. Late, disputed statements damage author relationships and consume staff time.
Royalty management software stores contract terms per author and title, imports sales per channel into a title-linked format, and calculates royalties and advance balances from those records. Statements are generated on a schedule with their sales records attached, so an author can check every figure, and corrections are recorded per statement rather than argued by email.
Core features
The features below focus on checkable statements, not on generic payment tools.
- Contract records per author and title with rates, thresholds, and advances
- Sales import from multiple channels into a standard, title-linked format
- Royalty calculation from contract terms applied to recorded sales
- Advance tracking showing earnings against advances and balances due
- Author statement generation on a schedule, with sales records attached
- Payment records linked to statements, with payment history per author
- Dispute handling recording author queries and corrections per statement
- Reporting by title, author, and period for publisher and author views
How it is built
Start with the highest-earning titles and their real contracts, before adding the full backlist.
- Build contract records for the highest-earning titles and authors
- Add sales import from the main channels, linked to titles
- Build royalty calculation and advance tracking
- Add author statement generation on a schedule
- Add payment records and dispute handling
- Add reporting and more titles once statements are trusted
Technology considerations
Store contract terms as structured data, not only as contract documents. A royalty rate hidden in a document cannot be applied automatically, and every statement becomes a manual interpretation. Structured terms, with rates, thresholds, and advances, allow calculation and checking.
Attach sales records to statements. An author statement that shows only totals cannot be checked, and disputes become arguments about trust. Statements with their sales records behind each figure let an author verify the payment, which reduces disputes and builds confidence.
Challenges and how to handle them
- Royalty terms vary and are misapplied — solve it by storing contract terms per author and title, applied automatically to sales.
- Sales data arrives in different formats — solve it by importing sales per channel into a standard format, linked to titles.
- Advances are forgotten — solve it by tracking advances and earnings against them, so statements show the balance clearly.
- Statements are assembled late — solve it by generating statements from sales and contract records on a schedule, not by hand.
- Authors dispute statements — solve it by attaching sales records to statements, so an author can check every figure.
Who it is for, and honest limits
This project fits publishers, agencies, and author collectives paying royalties to many authors. It also fits publishers whose author statements are disputed or late. Start with the highest-earning titles and their contracts.
It does not fit a publisher with a single author and simple royalty terms, where a spreadsheet may still be practical, or a firm that pays only flat fees with no royalties. It also does not provide legal advice on contracts. Cost depends on authors, titles, and contract complexity, so confirm with a quote. A useful first version can be judged by a simple test: can the team produce an author statement that the author can check against sales records, without manual assembly? Royalty calculations should also be spot-checked each statement period, so a systematic error is caught on one title rather than on every title.
Frequently asked questions
What is a royalty?
A payment to an author based on sales of their work, calculated from contract terms such as a percentage of revenue or price, often after an advance is earned out.
What is an advance?
A payment made to an author before publication, against future royalties. Royalties earned are first used to repay the advance, and further payments begin once the advance is earned out.
How are royalty terms stored?
As structured contract records per author and title, with rates, thresholds, and advance details. Terms as data allow automatic calculation, while terms in contract text alone require manual interpretation each statement.
How are sales imported?
From sales reports per channel, imported into a standard format and linked to titles. Sales that cannot be linked to a title should be flagged, not ignored.
What does an author statement show?
Sales, royalty rates applied, advance balance, and payment due, per title and period, with the sales records behind each figure available for checking.