--- title: "Author Royalty Statement Workflow With AI Agents | Kylon" description: "How a publisher's royalties team computes author royalties, applies payout thresholds and reserve changes, and creates statements in one Kylon room, each figure approved." url: "https://kylon.io/use-cases/author-royalty-statements" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Author Royalty Statements: Payable Figures That Survive Amendments and Reserve Changes Use Case7 min read # Author Royalty Statements: Payable Figures That Survive Amendments and Reserve Changes Royalties for every title are computed from its contract in Dropbox and its period sales in Stripe, recomputed when amendments or a new reserve arrive, and written to Airtable only after the royalties manager approves. Close-out creates fresh statements. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## 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 People - Royalties manager Approves every title's figures and payment status, and signs the statements - Contracts and rights manager Confirms amendment letters and rights reversion dates - Finance controller Publishes reserve policy changes and releases payment Agents - FinRoyalty calculator Reads each title's contract in Dropbox and its period sales in Stripe, applies the tier schedule, reserve and advance, and proposes the royalty, disposition and payment status AirtableDropboxStripeGoogle Drive - MycoStatement checker Checks the generated worksheet and every recomputed title, drafts replies on author and amendment threads, and prepares the new statement records Google DriveAirtable[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) 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. ```mermaid flowchart TD royalty["Fin computes each title's royalty
from its contract and Stripe sales"] payout["Fin totals each author against
the minimum payout"] approve["Royalties manager approves each
figure and payment status"] worksheet["Myco checks the worksheet against
the approved figures"] letter([An amendment letter
turns up in Gmail]) reserve([Finance publishes a
new flat reserve]) amend["Fin re-derives only the titles
the letters name"] letters["Contracts manager
confirms the letters"] replies["Myco drafts each reply with the
payable amount, for a person to send"] recompute["Fin recomputes every paying title
with the new flat reserve"] controller["Finance controller confirms
the revision applies"] reopen([A returns correction or advance
notice reopens a title]) rederive["Fin re-derives it with the revised
reserve, and Myco checks it"] statements["Myco creates one new statement
record per released author"] sign["Royalties manager signs
the statements"] royalty --> payout --> approve --> worksheet worksheet --> letter & reserve letter --> amend --> letters --> replies reserve --> recompute --> controller --> reopen --> rederive replies & rederive --> statements --> sign class royalty,payout,worksheet,amend,replies,recompute,rederive,statements agent class approve,letters,controller,sign person class letter,reserve,reopen event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Dispositions | Each in-scope title gets a royalty from its Dropbox contract, its Stripe sales and the tier schedule, and a disposition such as pay, unearned or co-authored split | Fin | The royalties manager approves before Airtable is written | | Payout threshold | Each author's payable titles are totaled and released or held against the minimum payout | Fin | The royalties manager approves each payment status | | Worksheet review | The generated worksheet is checked against the approved figures and every correction is listed | Myco | The royalties manager confirms the corrections | | Contract amendments | The two titles named in the amendment letters are re-derived under the amended tier schedule, and both threads get a reply with the payable amount | Fin, then Myco for the replies | The contracts manager confirms the letters and a person sends each reply | | Reserve revision | Every title currently paying is recomputed with the new flat reserve by format | Fin | The finance controller confirms the revision applies | | Returns and advance notices | The two titles named are re-derived from their inputs under the standing reserve policy | Fin, checked by Myco | The royalties manager approves | | Statements | One new statement record per released author is created from the final figures | Myco | The royalties manager signs the statements before they go out | Stages of a royalty period. Titles, authors and amounts in this example are illustrative. ## 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](https://kylon.io/integrations/gmail) - Google Drive - [Slack](https://kylon.io/integrations/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. Set-up prompt Set up our author royalty statements desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Dropbox, Gmail, Google Drive, Slack and Stripe. Tell me which ones still need connecting. 2. Ask me who works this desk: the royalties manager, the contracts and rights manager and the finance controller. Help me invite them to this Room. 3. Build a Royalty Titles App with Title, Format, Payable and Status, one record per in-scope title. Pull the current titles from the Airtable base. 4. Read each title's contract in Dropbox and its period sales in Stripe, apply our tier schedule, reserve and advance from Google Drive, and propose a royalty, disposition and payment status for each title. Show me any title carrying its contract reserve instead of the revised flat figure, any title marked payable only because an advance was repaid, any amended tier schedule applied beyond the titles our rules name, any author total under the threshold we set released anyway, and any close-out step that would edit an existing statement record. 5. Draft replies on amendment and author threads in Gmail and prepare new statement records. Hold every draft and every Airtable write until the royalties manager approves each figure and payment status, the contracts and rights manager confirms each amendment letter is signed, and the finance controller confirms any reserve revision. 6. Write the rule order and who approves what into this Room's guideline, including that every recompute starts from the contract, the sales and our current reserve policy, and that close-out creates new records only. 7. After one clean period, offer to turn the first-pass contract reads into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Ad Creative Approvals: A Launch Board That Matches What Is Actually Live The agency's launch sheet is audited against live Meta Ads campaigns and Instagram posts, every creative gets a status and a launch window on the Miro board, and holds, budget cuts and late approvals are absorbed mid-wave. The desk lead approves every board change. Media, publishing & agenciesApprovals & reviewsMarketing operations ](https://kylon.io/use-cases/ad-creative-approvals)[ ### Ad Delivery Make-Goods: Every Shortfall Settled as a Bonus Placement or a Credit Insertion orders are reconciled against delivered impressions and contract terms in one Kylon room. Agents work Attio, the Notion delivery report and the Outlook contract threads, re-run bonus allocations when numbers change, and the ad operations lead approves every outcome. Media, publishing & agenciesMarketing operations ](https://kylon.io/use-cases/ad-delivery-makegoods)