Author Royalty Statements: Payable Figures That Survive Amendments and Reserve Changes

Royalty statements depend on contracts nobody reads twice

Each royalty period, every title needs the same arithmetic done carefully: units and receipts from the period's sales, the rate tier the contract sets for that volume, a reserve held against returns, any unearned advance still to recoup, and the split if the book has more than one author. Then each author's total is compared with the minimum payout, and anything under it is held for the next period.

The titles table lives in Airtable, the royalty contracts and amendments are PDFs in Dropbox, and the period's sales come from Stripe. The tier schedule and the statement policy are documents in Google Drive. Late in the cycle, an amendment letter turns up in Gmail, finance publishes a new flat reserve, or a returns figure is corrected, and every title the change touches has to be recomputed from its inputs, not adjusted from last week's number.

Who works in the room

Fin is the room's default agent and owns the arithmetic. For the first pass it reads the thirty contracts in Dropbox through parallel helpers and gets one set of terms back, so every title starts from its own contract. Myco takes the worksheet review and the author correspondence, and Fin hands each recomputed title to Myco with a mention in the thread, so the reply quotes the figure the royalties manager approved. Fin reads Stripe through a lasting grant the finance controller approved for this room, while Myco drafts in Gmail as the person it is working for.

A royalty period from first pass to statements

The policy's recording conventions say which Airtable fields every title gets, and the room guidelines add the rule that matters most at the end: close-out creates new statement records and never edits an existing one.

A new reserve after the arithmetic is done

The flat reserve revision is the change most likely to leave a stale figure. It replaces each contract's own reserve for every recompute from then on, including titles that were not paying when the revision arrived and so were never recomputed. When a returns correction or an advance notice reopens one of those titles later, Fin uses the revised reserve for its format, not the figure in its Dropbox contract, and says so on the row.

An advance repayment is not a reason to pay on its own. It clears the unrecouped balance, but the title pays only if its net after reserve is positive and the author's total clears the payout threshold. Fin works through the full rule order for each reopened title, and Myco checks the result against the worksheet before the royalties manager sees it.

What the checks catch

• A title reopened late in the period that still carries its contract's reserve instead of the revised flat figure
• A title marked payable only because its advance was repaid
• An amended tier schedule applied to more titles than the two the letters name
• An author total just under the payout threshold that was released anyway
• A close-out step that would update an existing statement record instead of creating a new one

What stays with people

• Approving every royalty, disposition and payment status before Airtable is written
• Confirming that an amendment letter is signed and in force
• Replying to authors and their literary agents, which Myco prepares as drafts in Gmail
• Signing the statements and releasing payment

Integrations in this workflow

Kylon is not royalty accounting software, and it does not replace yours. It sits across the tables, files and payment records the team already keeps, and the work that links them runs in one room.

• Airtable
• Dropbox
• Gmail
• Google Drive
• Slack
• Stripe

• Airtable holds the titles table with every royalty field, and the statements table where close-out records are created
• Dropbox keeps the royalty contracts and amendment letters
• Stripe provides each title's sales and returns for the period
• Google Drive holds the statement policy, the tier schedules, the reserve revision and the generated worksheet
• Gmail carries amendment threads and author questions, and each reply is a draft a person sends
• Slack is where finance posts reserve changes and the contracts manager flags new letters

Where to start

Take one period and one imprint. Connect the Airtable base with the titles and statements tables, point the room at the Dropbox folder of contracts, then give the room guidelines the rule everything else depends on: every recompute starts from the contract, the sales and the current reserve policy, and the royalties manager approves each figure before it is written.

“Every recompute starts from the contract and the sales, never from last week's answer.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.