Partner, SDO CPA LLC / CEO, Growthy
You signed your first annual customer last month. $12,000 hit your bank in one wire. That's not $12,000 of revenue this month. That's $1,000 of revenue this month. The other $11,000 is something called deferred revenue. It sits on a balance sheet you don't have yet. Welcome to SaaS accounting. Cash and revenue stop being the same number the day you sell your first subscription.
Most SaaS founders figure this out the hard way. They run their books like a consulting business for nine months. They hit December and find their P&L shows $200K in revenue. Only $40K was actually earned. Or they pay a freelance designer $4,200. Then they panic-Google "do I owe a 1099" the week of January 31. The mistakes that hurt later are the ones you didn't know you were making in Month 1.
This guide walks the first 12 months. Day 1: pick a general ledger. Week 1: chart of accounts. Month 1: Stripe and one journal entry. Month 3: contractor tracking. Month 6: a bit of ASC 606 know-how. End of year: clean enough for a future audit. No CPA-shop jargon. No "you must use ASC 606 from day one" panic. Just what to set up, what to skip, and when.
What is SaaS bookkeeping and how is it different from regular small-business bookkeeping?
SaaS bookkeeping records subscription revenue, deferred revenue, contractor costs, and processor fees. It matches the books to when value is delivered, not when cash moves. A regular small business records a $1,000 sale when the customer pays. A SaaS business sells a $1,200 annual subscription. It records $100 of revenue per month for 12 months. The rest sits as a deferred revenue liability until earned. The pieces that matter in year one: a chart of accounts with deferred revenue and processor fees. A Stripe link that splits gross sales from fees. Contractor payment tracking from dollar one (1099-NEC threshold is $600 per contractor per year). Monthly recognition habits. You don't need full ASC 606 audit-ready books in year one. You do need books that won't be a nightmare to clean up in year two.
A consulting firm bills a client $5,000 in March. They get paid in April. They book $5,000 of revenue in March (or April, if cash basis). A SaaS company sells a $12,000 annual subscription in March. They get paid $12,000 in March. They book $1,000 of revenue per month for 12 months. The other $11,000 isn't revenue yet. It's a promise to deliver software for the next 11 months. That sits as a liability called deferred revenue.
This timing gap is the whole game. Cash hits when you charge. Revenue hits as you deliver. The two numbers will not match in any given month. Not after you've sold a single annual plan. If your books show them matching, the books are wrong. Most generic bookkeeping software handles this badly. Or not at all without setup work. Picture a founder seeing their bank balance ($180K) next to their "revenue" P&L line ($180K) in month two of selling annual plans. Something's broken. Probably the recognition, not the bank.
Most CPAs serve small businesses across many industries. The default chart of accounts they push is built for a consulting firm or a restaurant or a contractor. It has no deferred revenue account. It does not split hosting from general software expense. It does not capitalize commission costs. (You'll want to do that later if you pay sales commissions on multi-year deals.) None of this is your CPA being lazy. SaaS is one of dozens of industries they touch. Their template covers 80% of clients. You're in the other 20%.
You can defer full ASC 606 audit-grade revenue recognition. You can defer commission capitalization until you have a sales team. You can defer multi-element arrangements until you sell bundled products. You cannot defer clean categorization. Un-cleaning it later is hours of work per month of mess. You cannot defer deferred revenue tracking once you sell your first annual plan. You cannot defer processor-fee handling once Stripe takes 2.9% + 30 cents off every transaction.
Your first call is the system of record. That's the bookkeeping software that holds your chart of accounts, your transactions, your trial balance. The two most common picks are QuickBooks Online and Xero. A third option is less common but worth knowing. You can start on a SaaS-native general ledger built for subscription books from day one.
Your CPA probably uses QuickBooks Online. They'll suggest you do too. There's nothing wrong with this. QBO is the default for a reason. It works. Your CPA knows it. Every bookkeeper in the country can use it. For most year-one SaaS founders, QBO plus a few add-ons is fine. The trap isn't QBO itself. The trap is defaulting to QBO without thinking about what year three looks like. Some founders pick QBO. They outgrow it at $1M ARR. Then they face a painful move to a SaaS-native GL. With two years of messy past data to clean up.
A general ledger built for subscription businesses from day one. Deferred revenue accounts come pre-set. Stripe and Maxio and Chargebee links produce clean recognition entries on their own. Not just bank-feed dumps you have to re-sort. Contractor 1099 tracking is built in. The AI part means the sorting, the matching, and the monthly close steps get done by software. Not by a bookkeeper at $50 per hour. Growthy is one example. There are others. None of them have the brand recognition of QBO.
Mode 1 means QBO or Xero as the system of record. A SaaS-native tool layers on top to handle subscription billing and recognition. Mode 2 means starting directly on a SaaS-native general ledger as the system of record. QBO never enters the picture. Mode 1 is the easy path. Especially if your CPA's already set you up. Mode 2 avoids a move later. But you trade that for picking a less-mainstream system. Your future CPA may not know it. Rule of thumb: if your CPA already has you on QBO, stay Mode 1 for year one. If you're picking fresh and don't have a CPA yet, weigh Mode 2 hard before you default.
The chart of accounts (COA) is the list of buckets every transaction gets sorted into. Revenue, cost of goods sold, operating expenses, assets, liabilities, equity. Each bucket has a number and a name. Most generic COAs come with 80 to 120 accounts. You'll use maybe 30 in year one. The question is whether the right 30 are in there. Or whether you'll have to add and re-sort later. A SaaS-ready chart of accounts has accounts a generic small-business COA doesn't.
These are the accounts you'll need within the first 90 days of selling subscriptions. Deferred Revenue (Current) for subscriptions billed but not yet delivered, with a 12-month or less span. Deferred Revenue (Non-Current) for multi-year prepays where some revenue won't be earned for more than 12 months. Software Hosting Costs as a COGS sub-account. AWS, GCP, Cloudflare bills go here, not into general Software Expense. Payment Processing Fees as its own line, split out from gross sales. Customer Refunds and Credits as a contra-revenue account.
These don't bite in month one. They bite in month six. Contract Assets, for cases where you've delivered service but not yet billed (rare in self-serve, common in enterprise). Customer Credit Liability, for prepaid credits or wallet balances that haven't been used. Capitalized Software Development, if you have engineers building product features that meet the rules to capitalize. Most early-stage SaaS expenses everything. This matters later. Capitalized Commissions, if you start paying sales commissions on multi-year deals. Foreign Exchange Gain/Loss, if you have non-USD customers or vendors.
The most common COA mistake in year one: adding 200 accounts because a blog post said you'd need them. You won't. Add the 10 to 15 SaaS-specific accounts above and stop. Every account you add is one you have to map a transaction into during reconciliation. More accounts means more decisions. More slip between months. A worse audit trail. Start with 30. Add accounts only when a transaction doesn't fit anywhere.
Stripe is where the money comes in. If you don't connect it right to your bookkeeping system, you'll get a P&L that shows the wrong revenue, the wrong fees, and the wrong customer counts. This is the most common Month 1 mistake.
The wrong way: let your bookkeeping software pull the Stripe payouts from your bank feed. That gives you one deposit line every few days. It shows the net amount Stripe sends after fees and refunds. You don't see gross sales. You don't see fees as a separate line. You don't see refunds. Your revenue number is wrong from day one. The right way: connect Stripe direct to your bookkeeping system. Most modern tools have this. Or use a clearing-account setup with Maxio, Stripe Sigma exports, or a dedicated link. Each Stripe transaction should produce a clean entry. Gross sale to revenue (or deferred revenue). Fee to processing fees. Net to a Stripe clearing account that ties to payouts.
You sell a $1,200 annual subscription. Stripe takes $35 in fees. Here's what should hit your books on signing day. Debit Cash $1,165 (net Stripe payout). Debit Processing Fees $35 (gross fees). Credit Deferred Revenue $1,200 (the obligation to deliver 12 months of service). Then every month for the next 12 months: Debit Deferred Revenue $100. Credit Subscription Revenue $100. That's it. The signing entry sets up the liability. The monthly entry books revenue as you deliver. Memorize this one and you grasp 80% of SaaS revenue recognition.
In year one, with simple contracts and fewer than 50 customers, tracking deferred revenue monthly in a spreadsheet is fine. One row per contract: customer name, contract start date, contract end date, total contract value, monthly recognition amount, deferred revenue balance at each month-end. The total of all deferred revenue balances on your sheet should match the deferred revenue balance on your balance sheet at every month-end. When they don't match, something's wrong. Once you cross 100 contracts, the spreadsheet becomes the bottleneck. You move up to a tool that handles it natively. For more on the mechanics, see Stripe revenue recognition for SaaS.
If you use freelancers, agencies, or independent contractors, you'll owe them 1099-NEC forms in January. The threshold is $600 per contractor per year. That's the full annual amount paid to one person. Not per payment. Pay a freelance designer $300 in March and $400 in November. You owe them a 1099. Most founders mess this up because they don't track from day one.
The pattern: founder pays a contractor through Stripe, Wise, PayPal, or a direct ACH from their bank. The payment goes into a generic "Contractors" or "Consulting" expense bucket. No W-9 was collected. No record of the contractor's legal name, address, or TIN. January arrives. The founder has to email 12 contractors and beg for W-9s. The 1099 filing deadline is January 31. Half the contractors don't respond. The other half are confused. The founder either files late (penalty) or doesn't file (bigger penalty if audited).
Three things per contractor. A signed W-9 collected before you pay them (the legal standard). Every payment logged against that contractor by date and amount. The running annual total per contractor visible to you at any time. Modern bookkeeping software handles this on its own. So do dedicated tools like Gusto, Justworks, Deel, or Bill. Manual tracking works at 1 to 3 contractors. At 5 or more, move up to a tool. Note: payments via credit card or third-party platforms (like Upwork) get reported by the platform on a 1099-K. Not by you on a 1099-NEC. ACH and check payments are on you.
Rule of thumb: 5 or more active contractors. Or any contractor with ongoing payments rather than one-off projects. Gusto handles US contractors well. Deel handles international contractors well. Bill handles AP workflows with approvals. The cost is $10 to $40 per contractor per month. A lot less than the cost of a botched 1099 season. You can also handle this inside your bookkeeping system if it has 1099 tracking built in.
ASC 606 is the US accounting rule for how SaaS companies should recognize revenue. It has five steps, dozens of edge cases, and entire books written about it. You don't need to use all of it in year one. You do need to know the basic shape. So your books aren't actively wrong. And so your year-three audit doesn't find issues that should've been handled in year one.
You need to know: revenue is recorded as you deliver service. Not when cash is collected. For most SaaS subscriptions, that means monthly straight-line recognition over the contract term. Monthly subscriptions: record the full month in the month delivered. Annual prepays: divide by 12, record one-twelfth per month. Multi-year prepays: divide by total months, record one slice per month, split between current and non-current deferred revenue at each month-end. You need to do: post the monthly recognition journal entry, keep the deferred revenue roll-forward, log contract changes (upgrades, downgrades, cancellations with prorations) when they happen.
If you're under $5M ARR and not yet going through a formal audit, the bar is simple. Monthly recognition done the same way every month. Deferred revenue balance you can defend against your contract list. Contract changes logged with the entries that resulted. Processor fees split out from gross revenue. That's it. You don't need a 50-page ASC 606 memo. You don't need quarterly variable-consideration estimates. You don't need to capitalize and amortize every contract acquisition cost. Those matter if you take institutional money, prep for an audit, or approach an M&A event.
Three triggers. First, when you're prepping for a Series A or later round. Diligence will pick apart your recognition. Second, when you cross roughly $5M in ARR. The mess creeps in and the spreadsheet stops working. Third, when you have unusual contracts. Long-term deals with usage parts, bundled hardware plus software, milestones, performance obligations beyond plain-vanilla subscriptions. A SaaS-experienced CPA at year two is not the same as a generalist small-business CPA in year one. Different focus.
The reason any of this matters: someone is going to look at your year-one books in year two or year three. An investor. An acquirer. An auditor. By that point, you've already done the work. Or you haven't. Going back to clean up year-one books in year three is slow and costly. It can stall a fundraise.
Trial balance balances. Bank accounts tie out to the penny every month. Stripe and other processors tie out to gross and net. Deferred revenue balance on the balance sheet matches the sum of unearned amounts on the contract list. Revenue on the P&L matches the sum of monthly recognition entries posted. Processor fees split out as their own line. Contractor 1099s filed on time and traceable. COA hygiene: no duplicate accounts, no "Ask My Accountant" or "Uncategorized" buckets, every transaction in a real bucket.
Pre-audit checklist for end of year one. (1) Deferred revenue roll-forward built and balanced for all 12 months. (2) Journal entry notes for every recognition entry, with the formula or contract reference noted. (3) Contract files saved and findable, one per customer minimum, ideally one per contract. (4) COA scanned for duplicate or zero-balance accounts that should be cleaned up. (5) Processor-fee netting confirmed. No gross-up errors where fees got recognized as revenue. This isn't a full audit prep. It's the bar that makes a future audit survivable.
Two common paths. Mode 1 founders typically end year one on QBO with Maxio or a similar billing-and-recognition layer. They stay there through Series A. They move to a more specialized GL only if specific pain forces it. Multi-entity. Tricky revenue. International subsidiaries. Mode 2 founders end year one on a SaaS-native GL like Growthy. They never had to think about the move question. Which path is "right" depends on your future books. Closer to "more of the same" means Mode 1 holds. Closer to "much more tricky" means Mode 2 was worth it. Bobby is a CPA firm partner, not personally a CPA. The firm sees both paths work. The one that works best is the one you pick on purpose, not by inertia.
The honest year-one summary. Pick a GL on purpose. Set up a SaaS-flavored chart of accounts with about 30 active accounts, not 200. Connect Stripe properly. Track contractor payments and W-9s from dollar one. Post a monthly recognition entry. Keep a deferred revenue spreadsheet that ties to your books. Don't try to implement full ASC 606. Save your contract files. That's year one. Everything beyond that is year two's problem.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Get Started with Growthy. See saas bookkeeping.
Related: SaaS Accounting, Chart of Accounts, 1099 Filing, Stripe Bookkeeping.
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View author profileGrowthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
Practitioner comparison of 7 SaaS accounting options. QBO, Xero, Maxio, Chargebee, RecVue, Stripe Billing, and Growthy mapped to ARR stage and contract complexity.
Where deferred revenue lives on the SaaS balance sheet, the JE pattern on signing vs cash vs recognition, the monthly roll-forward, and what changes the balance in real-world contract churn.
SaaS chart of accounts template covering deferred revenue, capitalized commissions, COGS sub-accounts, and ASC 606/340-40/350-40 integration. 20-account starting point with $500K and $5M ARR additions.