You wrote the book years ago. The advance is long spent, the royalty statements have settled into a predictable trickle, and then a check shows up that doesn't match any pattern you recognize. A line in the memo field says something like "AI training license" or "text and data mining royalty." Your publisher licensed your backlist — maybe your entire backlist — to an AI company, and your cut just landed in your bank account.
If this hasn't happened to you yet, it probably will soon. If it just did, you likely have three questions: Was this legal? Did I get a fair share? And how do I report this on my taxes? Here's what's actually happening, and what to do about the money.
Why Authors Are Suddenly Getting These Checks
Generative AI models are trained on enormous quantities of text, and increasingly that text is arriving through negotiated licenses instead of scraped from the open web or pulled from shadow libraries. Publishers, who typically hold the digital rights to a book, are the ones signing these deals — and a wave of settlements and licensing agreements has made 2026 the year the checks started arriving in earnest.
The highest-profile example: Anthropic agreed to pay authors roughly $1.5 billion to resolve a class-action lawsuit over training data, with payments scheduled through 2027. Separately, publishers have been striking direct licensing deals with AI companies — some structured as a lump sum per title for a multi-year license, others as ongoing "pay-per-use" arrangements tied to how much the AI company actually draws on the content. HarperCollins, for instance, has offered some authors a fixed lump sum per title for a three-year license. Meta and other AI labs have signed licensing agreements with publishers that are starting to show up as real revenue lines.
None of this happened because publishers suddenly decided to share more generously with writers. It happened because AI companies got sued, and licensing content is now cheaper and safer than fighting infringement claims — or losing them.
Who Actually Owns the AI Licensing Right?
This is the part that trips up a lot of authors, and it's worth getting right before you spend the check. Standard publishing contracts, especially older ones, were negotiated long before "AI training rights" existed as a concept. The Authors Guild's position — and the position most literary agents will tell you to take — is that rights not expressly granted in your contract are retained by you, the author. A publisher licensing your backlist to train an AI model does not automatically follow from a grant of print, ebook, or even standard subsidiary rights (foreign translation, audio, film).
In practice, this means:
- If your contract is silent on AI/text-and-data-mining rights, the publisher generally needs your separate permission to license those rights, and you're entitled to negotiate your own split — not just accept whatever the publisher decided unilaterally.
- If your contract does grant broad subsidiary rights, the specific percentage split still matters. The Authors Guild has publicly pushed back on academic publishers offering authors as little as 25% of AI licensing revenue, arguing that a fair split for most deals should give the author 75–85%, with the publisher's cut scaled to how much actual work they did to facilitate the deal (versus just holding the rights and cashing a check).
- The author's share should flow to you directly and should not be quietly applied against an unearned advance balance. If your royalty statement nets the AI licensing payment against a negative advance balance instead of paying it out, that's worth flagging with your agent or publisher.
If you're an agented author, your agent should be reviewing these clauses now, even for out-of-print or backlist titles you haven't thought about in a decade. If you're self-published or hybrid, you likely already control these rights outright — which is its own bookkeeping wrinkle, covered below.
If You Think Your Split Is Unfair
A check arriving in the mail can feel like a fait accompli, but it usually isn't. If a publisher sends a licensing payment without ever asking your permission, or discloses a split that looks closer to 25/75 in the publisher's favor than the other way around, you have options before you cash it:
- Ask for the underlying license agreement, not just the payment notice. You're entitled to know which specific rights were licensed, to which company, for how long, and under what payment structure (lump sum vs. per-use). A publisher unwilling to share this is a red flag.
- Loop in your agent even for old titles. Agents typically retain a contractual right to review subsidiary income on your behalf, and many are actively renegotiating AI clauses across their entire author list rather than title by title.
- Check whether you're part of a class action instead. If the licensing payment stems from a settlement (like the Anthropic case) rather than a direct publisher deal, there may be a formal claims process with its own deadline — missing it can mean forfeiting your share entirely. Don't assume a single check from your publisher covers every AI-related claim your work might be eligible for.
- Don't sign a broad future rights waiver just to get one check cashed faster. Some publishers have bundled "please confirm receipt" letters with language granting blanket future AI licensing rights. Read anything you're asked to sign as its own contract, not paperwork.
How to Book and Tax the Payment
Once the money is real, the accounting question is straightforward, but it depends on one thing: are you actively in the business of writing, or is this a payment on an old asset you no longer actively manage?
For most working authors, this is Schedule C income, not Schedule E. The IRS distinguishes between royalties from a business you actively operate (reported on Schedule C, subject to self-employment tax) and royalties that are more like passive investment income (reported on Schedule E). If you write regularly, market your work, and treat authorship as an ongoing trade or business — which describes most professional and self-published authors — an AI licensing payment tied to your copyrighted work is generally treated the same way your regular royalties are: as self-employment income on Schedule C, subject to both income tax and self-employment tax (Social Security and Medicare).
A few practical points:
- Expect a 1099, but don't assume it will be coded correctly. Publishers and AI companies issuing these payments may report them on 1099-MISC (royalties, box 2) or 1099-NEC, depending on how their finance team classified the deal. The 1099 box doesn't override the underlying tax treatment — if the income is from your active writing business, it belongs on Schedule C regardless of which box it showed up in.
- Don't let a lump sum push you into estimated-tax trouble. A one-time AI licensing check can be large enough to meaningfully change your tax liability for the year. If you don't normally make quarterly estimated payments, or if this payment is unusually large relative to your typical royalty income, run the numbers before year-end so you're not blindsided.
- Track it separately from ordinary royalties in your books. Even though it lands on the same Schedule C line as your regular book royalties, keeping AI licensing income in its own account or tag makes it much easier to answer the inevitable "wait, where did this come from?" question later — from your accountant, a future agent, or yourself in eighteen months.
- If you're a self-published or hybrid author negotiating directly, you're the one setting the split and the terms, which means you're also the one who needs a clean paper trail: the license agreement, the payment schedule, and which specific titles or rights were included. This is exactly the kind of one-off, easy-to-misplace transaction that a normal royalty spreadsheet isn't built to capture.
- Don't forget the Qualified Business Income deduction. If the payment is Schedule C income from your active writing business, it may qualify for the Section 199A QBI deduction (up to 20% of qualified business income, subject to the usual phase-outs), the same as your regular royalty income. This is a detail a general-purpose tax software default can miss if the income is miscategorized.
- A class-action settlement payment may arrive with its own tax reporting, separate from anything your publisher issues. If your AI licensing income comes from a settlement like Anthropic's rather than a direct publisher license, expect a distinct 1099 from the settlement administrator, and don't assume it's already netted against anything your publisher reported.
Why This Is a Bookkeeping Problem, Not Just a Tax Season Problem
The recurring theme with author income — advances, royalties, foreign rights, audio, and now AI licensing — is that it arrives irregularly, from multiple sources, often with confusing labels, and months or years after the underlying work was done. A publisher statement that nets an AI licensing payment against your advance, a 1099 that miscodes the payment type, or a one-time check you forget to flag as business income by April are all avoidable problems if the income is recorded clearly the moment it lands, not reconstructed from bank statements at tax time.
This is where plain-text accounting earns its keep for authors and other creators with irregular, multi-source income. With Beancount.io, you can record each payment — advance, royalty, foreign rights, AI licensing — as its own tagged transaction in a human-readable ledger, so a strange one-time check doesn't get lumped in with your regular royalty stream or lost entirely. Because it's plain text and version-controlled, you (or your accountant) can review exactly what came in, from whom, and under what license, months or years later. Get started for free and keep your writing income as organized as your manuscripts.