Skip to main content

Shutting Down Your SaaS? The Deferred-Revenue Refund Obligation You Owe Customers Before You Can Close the Books

Published 11 min readMike ThriftMike Thrift
Shutting Down Your SaaS? The Deferred-Revenue Refund Obligation You Owe Customers Before You Can Close the Books
On this page

You have $180,000 in the bank and a deferred revenue balance of $140,000. The shutdown math most founders do in their head says the company is worth the cash. The accounting says something colder: up to $140,000 of that cash already belongs to customers, because you collected it for service you will now never deliver. Distribute the bank balance to yourselves before settling that obligation and you have not wound down a company — you have spent someone else's money, and the chargebacks, refund demands, and state dissolution paperwork will chase you well past the day the servers go dark.

Shutting down a subscription business is not just cancelling logins and filing dissolution papers. Every prepaid annual plan, every multi-year enterprise deal, every customer credit sitting unused is a liability that has to be settled, refunded, or formally extinguished before the books can close. This guide walks through what you owe, the order to settle it in, and the bookkeeping entries that prove it is done.

The cash in your account is not all yours​

When a customer pays $60,000 upfront for an annual subscription, the cash hits your bank on day one — but you have not earned a dollar of it. You have promised a year of service, and under ASC 606 that promise is a contract liability, presented on most balance sheets as deferred revenue. Each month of delivered service moves one-twelfth of it into earned revenue. If the contract ends early with service undelivered, the unearned remainder does not become your revenue. It becomes money you owe back.

In plain-text books, the lifecycle looks like this: cash in against the liability, then a monthly recognition entry that works the liability down as service is delivered.

2026-01-01 open Assets:Bank:Checking USD
2026-01-01 open Liabilities:Deferred-Revenue USD
2026-01-01 open Income:Subscriptions USD
 
2026-01-05 * "Acme Corp" "Annual plan, paid upfront"
  Assets:Bank:Checking           60000.00 USD
  Liabilities:Deferred-Revenue  -60000.00 USD
 
2026-01-31 * "January revenue recognition"
  Liabilities:Deferred-Revenue  5000.00 USD
  Income:Subscriptions         -5000.00 USD
 
2026-02-28 * "February revenue recognition"
  Liabilities:Deferred-Revenue  5000.00 USD
  Income:Subscriptions         -5000.00 USD

After two months, $10,000 is earned and $50,000 still sits in deferred revenue. That $50,000 is the number that matters on shutdown day. Run this schedule for every active contract — not just the big ones — and total the unearned remainder. That total is your refund exposure before you read a single line of your terms of service.

Two balances founders routinely miss: multi-year enterprise deals, where the portion covering service more than twelve months out sits in non-current deferred revenue and gets overlooked in a current-liabilities-only review; and customer credits and unused prepaid usage balances, which are the same kind of obligation under a different label. Pull both into the exposure total.

On shutdown day, the liability changes shape​

Termination does not erase the obligation — it converts it. The moment you stop delivering the service, the contract liability for undelivered service is no longer "deferred revenue" in any meaningful sense. Accounting guidance treats a termination as the end of the performance obligation, and any amount the customer is entitled to get back is reclassified from deferred revenue to a refund liability: money payable, not service owed.

Book that reclassification explicitly rather than netting refunds straight out of deferred revenue. A separate refunds-payable account gives you a control total — every refund batch draws it down, and whatever is left when the batches are done is either still owed or formally resolved, never a mystery.

2026-06-01 open Assets:Bank:Checking USD
2026-06-01 open Liabilities:Deferred-Revenue USD
2026-06-01 open Liabilities:Refunds-Payable USD
 
2026-06-01 * "Shutdown" "Reclassify unearned balances to refunds payable"
  Liabilities:Deferred-Revenue  50000.00 USD
  Liabilities:Refunds-Payable  -50000.00 USD
 
2026-06-05 * "Refund batch 1" "Pro-rata refunds to annual customers"
  Liabilities:Refunds-Payable  32000.00 USD
  Assets:Bank:Checking        -32000.00 USD

The $18,000 still sitting in refunds payable after batch one is your to-do list in dollars. Work it to zero — through refund batches, honored service, or documented forfeiture — before you touch anything else in the wind-down. If you keep your books in Beancount's plain-text format, this account's balance is the single number that tells you whether the customer side of the shutdown is finished.

Refund, honor, or forfeit: three ways to settle each contract​

Not every unearned dollar has to go back as cash. What you owe each customer depends on your contract terms and the law where they sit — but every contract resolves through exactly one of three doors, and you should sort the whole customer list into them before paying anyone.

1. Refund the unearned time​

This is the default most shutdown guides recommend, and for monthly plans it is trivial: stop billing on the announcement day so there is no unearned balance at all. For annual and multi-year plans, refund the unused months pro-rata from the shutdown date. Check your terms of service first — some promise exactly this — and check consumer-protection law in your customers' jurisdictions, which can require refunds your terms do not mention. Enterprise contracts often have their own termination-for-convenience clauses with specific refund mechanics; follow the contract, not your standard policy.

Practical note: refund through the original payment method where possible. Customers whose refunds never arrive file chargebacks instead, and a wave of chargebacks against a merchant account you are trying to close is a special kind of misery — reserve holds, dispute fees, and a processor that suddenly wants six months of statements.

2. Honor the paid period​

Some founders keep the lights on until the longest prepaid period runs out, delivering service instead of cash. This converts the liability into earned revenue month by month, exactly like the normal recognition entries above, and it can be the right call when the cash is already spent and refunds would come from the founders' pockets. It only works if you can actually deliver: data security, uptime, and support obligations continue for every customer whose period you are honoring, and "we shut down but kept one server on" still needs someone answering the support inbox. Set a hard end date, announce it early, and give every user a data export before access ends — the export window is the part customers remember.

3. Recognize non-refundable forfeitures — with paperwork​

If your terms genuinely make prepaid fees non-refundable and no law overrides that, the unearned balance is recognized as revenue at termination rather than refunded. ASC 606 permits this: consideration to which you have an enforceable right, with no remaining obligation, is revenue when the contract ends. But "our terms say non-refundable" is a legal conclusion, not a bookkeeping one — get counsel to confirm it holds in the states and countries where your customers are, and document the conclusion per contract cohort. Then book the forfeiture as its own entry, dated on the termination date, so the revenue is visibly tied to the shutdown event rather than smeared across ordinary subscription income.

2026-06-01 open Liabilities:Deferred-Revenue USD
2026-06-01 open Income:Forfeited-Prepayments USD
 
2026-06-01 * "Shutdown" "Recognize non-refundable balances at termination"
  Liabilities:Deferred-Revenue  12000.00 USD
  Income:Forfeited-Prepayments -12000.00 USD

One rule covers all three doors: never mix them within a single contract without writing down why. "Refunded the enterprise tier, forfeited the self-serve tier" is a defensible policy. Ad-hoc per-customer decisions with no paper trail look arbitrary when a regulator or a plaintiff's lawyer asks about them later.

The wind-down accounting sequence​

Customer refunds are the emotional center of a shutdown, but they sit inside a longer sequence, and the order matters because cash only flows downhill. Work it in this order:

  1. Freeze new obligations. Stop new sales, turn off auto-renewal, and cancel your own vendor contracts and auto-renewing subscriptions. Every new dollar of deferred revenue created during a wind-down is a dollar you will have to refund with wind-down cash.
  2. Build the exposure schedule. Every active contract, its unearned balance, its refund terms, and which of the three doors it goes through. Total it. This number — not the bank balance — is what the company can distribute after everything else is paid.
  3. Pay the refunds. Run refund batches against the refunds-payable control total from largest to smallest, reconciling the account after each batch. Keep the merchant and bank accounts open until the last batch clears plus one full chargeback window.
  4. Settle everything else you owe. Vendors, contractors, accrued payroll and unused PTO payouts, sales tax and payroll tax filings. Employee wages and tax authorities have priority over owners in every dissolution statute — they get paid before any distribution, without exception.
  5. Collect what you are owed. Chase outstanding receivables now, while the entity still exists to enforce them. Uncollectible balances get written off; whatever remains assigned or sold goes at its realizable value, not face value.
  6. File the final returns. Mark every return final: federal and state income tax, final payroll returns and 1099s, sales tax closeouts. Corporations file Form 966 within 30 days of the dissolution resolution. The final-year balance sheet should zero out — no deferred revenue, no refunds payable, no receivables — because there is nothing left to carry.
  7. Distribute the remainder and dissolve. Only now, with every liability at zero and the tax accounts closed, do the remaining assets go to owners per the operating agreement or share structure. Then file the articles of dissolution and close the EIN, bank, and merchant accounts.

Founder-run dissolutions typically involve dozens of compliance tasks across legal, tax, and operational tracks — board resolutions, state filings, foreign-qualification withdrawals, payroll account closures. If the list above already feels long, that is the point: use a dissolution checklist or a wind-down service rather than memory, because the tasks you forget are the ones with penalties attached.

Mistakes that follow you past the shutdown​

Distributing cash before refunds are settled. This is the big one. Owners who take distributions while customer refund claims are still outstanding can face clawback actions to recover the money — dissolution statutes in most states make distributions to owners subordinate to creditor claims, and prepaid customers are creditors. Keep a cash reserve against the full exposure schedule until every contract is resolved, and do not distribute a dollar before that.

Forgetting the non-current balance. Multi-year prepayments often put most of the liability in non-current deferred revenue, which a hasty wind-down review skips. An enterprise customer who prepaid three years and got eighteen months of service is owed eighteen months back. The exposure schedule must include both current and non-current balances.

Closing the merchant account too early. Refunds and chargebacks need a live merchant account to flow through. Close it before the last refund clears and you will be issuing paper checks or wire transfers to customers one by one — assuming you still have their details. Keep it open through the final chargeback window, then close it.

Booking shutdown revenue in the wrong period. Forfeited prepayments are recognized at termination, not dribbled out over the original service schedule. Getting this wrong leaves deferred revenue on a dissolved company's final return — a balance sheet that claims the dead company still owes service it will never deliver.

Treating the final return as optional. A dissolved entity with unfiled final returns keeps accruing failure-to-file penalties against people who thought they were done. File everything, mark it final, and keep the books and refund records for at least seven years — the same retention horizon as any other tax record, because a dissolved company's returns can still be examined.

Your last useful step​

Before you announce anything, build the exposure schedule: every contract, every unearned dollar, every customer credit, current and non-current. That one schedule turns the shutdown from an anxious downhill slide into a finite list of obligations with dollar amounts attached. Refund what is owed, honor what you promised to deliver, document what the contracts let you keep — and when refunds payable reads zero, the customer side of your shutdown is provably finished. Everything after that is paperwork.

Source: https://beancount.io/blog/2026/11/08/shutting-down-saas-deferred-revenue-refund-obligation-guide

Published: November 8, 2026