A small board game studio launches a campaign on a Tuesday morning. By Friday, 6,000 backers have pledged $380,000 for a base game, three expansions, and a pile of exclusive miniatures. The founder opens the business bank account, sees six figures sitting there, and feels — for the first time — like the company actually has money.
It doesn't. Not in the way that matters for the books.
That $380,000 is cash. It is not revenue. The difference between those two words is where a surprising number of first-time publishers get into serious trouble — sometimes tax trouble, sometimes cash-flow trouble, and sometimes both at once, roughly fourteen months later when the freight containers are stuck in port and the "final" printer invoice comes in 20% over quote.
Board game publishing is a strange business to do bookkeeping for, because almost none of the revenue arrives the way accounting textbooks assume. Money shows up in a lump, months or years before the thing it paid for exists. Understanding which bucket that money belongs in — and when it's allowed to move from "we have your cash" to "we earned this" — is the single most important accounting skill a tabletop publisher can have.
The Core Idea: Cash In Is Not Revenue Earned
Accrual accounting runs on one governing rule: you recognize revenue when you've satisfied your obligation to the customer, not when their payment clears. For most retail businesses that distinction barely matters — the sale and the delivery happen in the same five minutes. For a Kickstarter-funded game, the sale and the delivery can be separated by a year or more.
Until you ship the reward, that backer's pledge sits on your balance sheet as a liability, usually labeled deferred revenue (also called a contract liability). You owe them a game, not money back — but until you deliver, the cash you're holding legally belongs to an unfulfilled promise, not to your profit and loss statement. Recognizing it as revenue too early overstates how profitable your studio looks, understates your actual obligations, and can leave you owing income tax on money you've already spent on plastic minis sitting in a container ship.
Most publishing businesses run through more than one of these situations in a single fiscal year. Here are the five that come up again and again.
Scenario 1: Cash on Delivery — Convention and Retail Sales
This is the easy one, and it's worth stating plainly because it's the baseline everything else deviates from. When someone buys your game at a convention booth, on your webstore for immediate shipment, or through a distributor who pays on receipt, the exchange of goods and payment happens essentially at once. Revenue is recognized right then.
There's no deferral, no liability account, no waiting period. If your entire business ran this way, you wouldn't need this article. Almost no crowdfunded publisher's business runs this way exclusively — but it's useful as the control case, because every other scenario is really a variation on "how far apart are the cash event and the delivery event, and what has to happen in between."
Scenario 2: The Kickstarter Campaign Itself
Here's the scenario that catches new publishers off guard. When a backer pledges $65 for the base game and $95 for the deluxe pledge with all the expansions, that money hits your bank account almost immediately after the campaign closes — often 30 to 90 days later, once the platform processes payouts. But you haven't delivered anything. You may not have finished the art. The factory quote might still be a placeholder.
The correct treatment: record the pledge as deferred revenue (a liability) when the cash arrives, and recognize it as actual revenue only when you fulfill the pledge — meaning the game is manufactured, shipped, and delivered to the backer, satisfying your performance obligation.
This is where the timing mismatch becomes a real operating problem, not just a bookkeeping technicality. Industry data on tabletop crowdfunding shows the average board game campaign delivers about 4.3 months later than the original estimate — and that's an average; miniature-heavy campaigns with complex tooling routinely run a year or more behind. So a publisher can be sitting on $380,000 in the bank, all of it technically a liability, for well over a year before any of it converts to revenue they're allowed to count as earned.
Two consequences follow directly from this:
Tax timing matters, and it can work in your favor if you plan for it. Advance payments are still income once you control the cash, but for eligible businesses, there's an accounting method that lets you defer recognizing that income — and therefore defer the associated tax burden — until closer to the year you actually fulfill the reward, rather than the year the pledges came in. Whether your business qualifies, and which method fits your situation, is exactly the kind of question worth raising with a CPA before your first campaign closes, not after.
Spending against undelivered pledges is spending against a liability, not a profit. It's tempting to look at a six-figure campaign balance and start greenlighting the next expansion, a bigger print run, or founder pay increases. The money is real, but it's earmarked. A publisher who treats crowdfunding cash as free cash flow before the current campaign ships is the publisher who ends up unable to cover the reprint when the box dimensions changed and freight costs came in 40% over the original estimate.
Scenario 3: Consignment Sales Through Friendly Local Game Stores
Many publishers place inventory with local game stores or specialty distributors on consignment — the store displays and sells the game, but doesn't pay for it, or take ownership of it, until it actually sells to a customer. You're not invoicing them when you drop off the boxes; you're invoicing them (or recognizing revenue) when their sales report tells you units moved off the shelf.
This matters because it's easy to mentally log consignment inventory as "sold" the moment it leaves your warehouse — it's gone, after all. But for revenue recognition purposes, ownership (and the obligation) hasn't transferred yet. Revenue is recognized when the sales report comes in and the invoice is issued, not when the boxes leave your garage. Tracking consignment inventory separately from owned inventory, and reconciling it against store sales reports monthly, prevents both overstated revenue and — just as commonly — games that quietly go missing from a shelf with nobody noticing for six months.
Scenario 4: Bundled Pledges and Convention Bundle Deals
Deluxe pledge tiers are a hallmark of modern tabletop crowdfunding: base game plus three expansions plus an exclusive playmat plus a metal coin upgrade, all for one bundled price that's cheaper than buying each piece separately. The same pattern shows up at conventions, where a publisher might bundle a core game with an expansion at a discount to move inventory.
When you sell a bundle, you can't just recognize the whole bundle price as revenue for "the game" the moment it ships, especially if some components (say, a stretch-goal expansion) ship in a later wave than others. The transaction price has to be allocated across each component based on its standalone value, and each component's revenue is recognized when that specific piece is actually delivered.
A simplified example: a base game normally sells for $40 and an expansion for $60, but you bundle them at $80. That $80 doesn't get treated as "$80 for the base game." It gets split proportionally — 40% to the base game ($32) and 60% to the expansion ($48) — and each portion is recognized only when that specific item ships. If the base game goes out in wave one and the expansion ships four months later in wave two, your books need to reflect that split, not book the full $80 the day the first box goes out the door.
Scenario 5: Licensing and Royalty Revenue
Once a publisher has a catalog, licensing becomes a real revenue stream — foreign-language editions produced by an overseas partner, a mobile app adaptation, a licensed IP tie-in. These arrangements typically pay based on units the licensee sells, reported periodically (often quarterly) under a contractual royalty rate.
Revenue here is recognized when the licensee's sales report comes in and the royalty is invoiced — not when the licensing agreement is signed, and not when you receive an advance against future royalties (which, notably, is its own flavor of deferred revenue until it's earned out). A publisher with several licensing deals running at once needs a system for tracking which reports have arrived, which are overdue, and which advances are still unearned — otherwise it's very easy to lose track of real money owed to you across a handful of small, irregularly-timed royalty statements.
Why This Matters Beyond "Technically Correct" Accounting
Getting revenue recognition right isn't a compliance exercise for its own sake. For a crowdfunded publisher, it directly answers three questions the founder actually needs to know at any given moment:
- Are we actually profitable, or just cash-rich? A studio holding $380,000 in unfulfilled Kickstarter liabilities and $310,000 in manufacturing and fulfillment costs against it is not sitting on $380,000 of profit. Conflating the two is how publishers overspend on their next project before the current one has shipped.
- What do we actually owe, and to whom? Deferred revenue is a real liability — a debt of goods, not cash, but a debt all the same. Knowing the total unfulfilled obligation across every open campaign, consignment relationship, and pending royalty report is core to knowing whether the business is solvent.
- What will next year's tax bill actually look like? Recognizing income in the wrong period — too early or too late — creates surprises at tax time that are entirely avoidable with clean, contemporaneous records.
Building the Habit From Day One
You don't need enterprise accounting software to track this correctly, but you do need a system that treats "cash received" and "revenue earned" as two genuinely different events, with a clear liability account bridging the gap until fulfillment. Plain-text, version-controlled accounting is a natural fit for exactly this kind of business: every pledge, every consignment shipment, every royalty statement becomes a discrete, auditable entry, and the deferred-revenue liability is always visible as its own line rather than buried inside a lump "Kickstarter income" category.
Beancount.io gives publishers plain-text accounting that's fully transparent and version-controlled — every transaction is traceable, every deferred-revenue balance is a query away, and nothing is locked inside a proprietary format you can't audit yourself. Get started for free and keep your next campaign's books honest from the first pledge to the last box shipped.