Bookkeeping for Startups and SaaS in Chicago

Bookkeeping for a Chicago SaaS startup differs from ordinary bookkeeping in several ways, and the differences are large enough that a bookkeeper who treats a SaaS company like a retail shop will produce books that mislead the founders and fall apart under investor scrutiny. The single biggest difference is revenue recognition, which for a subscription business is governed by the principle in ASC 606 that revenue is recognized as the service is delivered rather than when the cash is collected. A company that sells a physical product records the sale when it ships the product, but a SaaS company that collects a year of subscription upfront has not earned a year of revenue, it has taken on an obligation to provide a year of service, and the accounting has to reflect that.

Practically, this means an annual subscription paid in advance is booked as deferred revenue, a liability, and then recognized into income month by month as the service is delivered. Ordinary bookkeeping that records the full payment as revenue when it hits the bank overstates the company’s revenue early in the subscription and understates the liability it owes, which distorts every metric derived from those numbers. Because SaaS companies live and die by monthly recurring revenue and annual recurring revenue, and because those metrics are only meaningful if the underlying recognition is correct, getting deferred revenue right is the foundation of SaaS bookkeeping.

The second difference is the financing instruments. Startups raise money through SAFEs and convertible notes that ordinary bookkeeping has no natural home for. The cash from a SAFE is not revenue and usually not taxable on receipt, but it changes the balance sheet, and recording it as income would badly misstate both earnings and taxes. A bookkeeper who does not understand these instruments creates a mess that has to be cleaned up at the next financing round.

The third difference is the metrics the books have to support. A venture-backed company reports burn and runway to its board and investors, and those figures depend on accurate, current books. An understated or miscategorized expense makes burn look smaller and runway longer, and a founder who trusts a wrong runway plans the next raise too late. Ordinary bookkeeping aimed at producing a year-end tax return is not built to deliver the monthly precision a startup needs.

Here is a concrete example. Suppose a Chicago SaaS company sells a $24,000 annual plan and collects the whole amount in January. Correct SaaS bookkeeping records $2,000 of revenue each month and carries the remainder as deferred revenue, so by June the company shows $12,000 recognized and $12,000 still owed as service. Ordinary bookkeeping might record $24,000 of revenue in January and nothing afterward, making the company look far stronger in the first quarter than it is and setting up a diligence problem later. We keep the books the way a SaaS company actually needs them and build the reporting on top through our monthly financial reporting service. The recordkeeping expectations sit with the IRS recordkeeping guidance, and the accounting-method framework is in IRS Publication 538.

Deferred revenue matters so much in SaaS startup bookkeeping because it is the difference between books that tell the truth about a subscription business and books that flatter it, and because the error it prevents is exactly the kind that a sophisticated investor or acquirer will find during diligence. Deferred revenue is the liability a company records when it has been paid for a service it has not yet delivered. For a SaaS company that collects subscriptions in advance, especially annual plans, deferred revenue is often one of the largest items on the balance sheet, and how it is handled shapes the entire financial picture.

The underlying principle, expressed in ASC 606, is that revenue is recognized as the performance obligation is satisfied, which for a subscription means as the service is provided over the subscription term. When a customer pays for a year upfront, the company has an obligation to deliver twelve months of service, so it recognizes the payment as revenue gradually, one month at a time, and carries the unearned portion as deferred revenue until it is delivered. This matches revenue to the period in which it is actually earned, which is the whole point of accrual accounting.

If a bookkeeper instead records the full upfront payment as revenue immediately, several things go wrong at once. Revenue is overstated in the month of collection and understated in every later month of the subscription. The balance sheet omits the deferred-revenue liability, so the company looks like it owes less service than it does. And the recurring-revenue metrics that SaaS investors scrutinize become unreliable, because they are being computed off distorted figures. A company that shows a big revenue spike whenever it lands an annual contract, followed by dead months, is displaying the signature of broken revenue recognition.

The consequences land hardest at fundraising or acquisition. When investors or a buyer conduct diligence, their finance people expect to see clean deferred-revenue accounting, and they will recompute the metrics themselves. If they find that revenue was recognized on collection rather than delivery, they lose confidence in the numbers, the diligence slows while the books are corrected, and the founders negotiate from a weakened position. Clean deferred revenue, by contrast, signals financial maturity and lets the diligence move quickly.

Here is a concrete example. Suppose a Chicago SaaS company signs ten customers to $12,000 annual plans in a single quarter and collects $120,000 upfront. Correct bookkeeping recognizes $10,000 of revenue per month across the year, roughly $30,000 for that quarter, and carries about $90,000 as deferred revenue at quarter-end. Booking the full $120,000 as quarterly revenue would overstate the quarter by $90,000 and leave a hole in the following quarters, a distortion any diligence team would catch. We maintain the deferred-revenue schedule so the reported revenue matches the accounting a buyer expects, feeding it into the reporting we produce through our monthly financial reporting service. The accounting-period and method rules are covered in IRS Publication 538, and the general recordkeeping standards sit with the IRS recordkeeping guidance.

Startup bookkeeping tracks burn and runway for a Chicago company by keeping the books accurate and current enough that the two most important cash figures a venture-backed company watches can be trusted, because burn and runway are only as reliable as the bookkeeping underneath them. Burn is the net amount of cash leaving the company each month, and runway is the cash on hand divided by that burn rate, expressed as the number of months before the company runs out of money and must either raise more or reach profitability. For a company living on money it raised rather than money it earns, these are the numbers that determine survival.

The reason bookkeeping quality is so central is that both figures are derived directly from the books. Burn is computed from the cash coming in against the cash going out, and if expenses are understated, miscategorized, or recorded late, the burn looks smaller than it actually is. A smaller apparent burn produces a longer apparent runway, and a founder who believes a runway that is too optimistic will delay the next fundraising, potentially starting the process with too little cash left to negotiate from strength or to survive if the raise takes longer than expected. Accurate, timely books are what keep this from happening.

There is also a forward-looking dimension. Good startup bookkeeping does not just report last month’s burn, it supports a forecast of future burn as the company hires, signs customers, and changes its spending. A company planning to add engineers needs to see how those salaries will change the burn and shorten the runway, so the hiring plan and the fundraising timeline can be aligned. This is why the books have to be maintained continuously rather than caught up at year-end, because a board and a founder need the burn and runway picture every month, not once a year.

The reporting side matters too. Investors expect regular updates, typically monthly or quarterly, that include the cash position, burn, and runway. If the books are current, producing that update is straightforward. If they are not, every board meeting triggers a scramble to reconstruct the numbers, which wastes time and erodes investor confidence. Clean books turn reporting into a routine rather than a crisis.

Here is a concrete example. Suppose a Chicago startup has $600,000 in the bank and is spending $50,000 a month net of any revenue. Accurate books show a twelve-month runway, which tells the founders they should begin raising within roughly six months so a round closes before the cash gets dangerously low. Now suppose sloppy books understated the burn at $40,000 a month by missing some recurring costs. The founders would calculate a fifteen-month runway, feel less urgency, and start raising too late, arriving at the market with only a few months of cash left. The difference between those two outcomes is entirely a matter of bookkeeping accuracy. We keep the books current so burn and runway are real, and we build the investor reporting through our monthly financial reporting service. The recordkeeping standards behind accurate books sit with the IRS recordkeeping guidance, and the accounting-method rules are in IRS Publication 538.

A Chicago startup should record SAFEs and convertible notes in its bookkeeping as the financing instruments they are, not as revenue or ordinary income, and getting this right when the money comes in prevents a painful cleanup at the next round, which is why startup bookkeeping treats these instruments with care. A SAFE, which stands for simple agreement for future equity, and a convertible note are both ways for a company to take investment early, before it is ready to set a formal valuation, and to convert that investment into stock later when a priced round establishes the price. They are common precisely because they let a startup raise quickly without negotiating a valuation prematurely.

The first principle is that the cash received is not revenue. When a startup takes $500,000 through a SAFE, that money is a financing inflow, not something the company earned by delivering a product or service, so it does not belong in the revenue line and generally is not taxable income on receipt. A bookkeeper who records it as revenue overstates the company’s earnings dramatically and misstates its tax position, creating a problem that is both an accounting error and a potential tax exposure. The SAFE proceeds instead belong on the balance sheet, reflecting that the company has taken in cash against a future obligation to issue equity.

SAFEs and convertible notes differ from each other in ways the books should capture. A convertible note is structured as debt, often carrying an interest rate and a maturity date, so it is recorded as a liability and any accrued interest is tracked. A SAFE is not debt and has no interest or maturity in its standard form, so its treatment differs, though it still sits on the balance sheet rather than in income. Both typically include terms such as valuation caps and discounts that determine how much stock the investor receives when the instrument converts, and those terms have consequences that surface at conversion.

The payoff for recording these correctly comes at the priced round. When a company raises a formal round, the outstanding SAFEs and notes convert into shares according to their terms, and the cap table and the books have to reflect the conversion accurately. If the instruments were recorded loosely, or dumped into the wrong accounts, the financing opens with an accounting cleanup that slows the deal and signals disorganization to the new investors. Clean records let the conversion happen smoothly.

Here is a concrete example. Suppose a Chicago startup raises $500,000 on a SAFE with a valuation cap. Correct bookkeeping records the $500,000 as a financing inflow on the balance sheet, not as revenue, and carries the SAFE until it converts. If instead the company had booked the $500,000 as income, its profit-and-loss statement would show half a million dollars of earnings that do not exist, distorting its metrics and potentially triggering a tax problem. We record SAFEs, convertible notes, and the eventual conversions correctly so the books and the cap table agree when a priced round tests them, coordinating the structure with our entity formation and structuring service. The general recordkeeping standards sit with the IRS recordkeeping guidance, and the accounting-method framework is in IRS Publication 538.

The Chicago software lease tax shows up in a SaaS startup’s bookkeeping as a real liability that ordinary bookkeeping would miss entirely, and recognizing it is one of the clearest reasons a Chicago SaaS company needs a bookkeeper who understands both software and the city’s tax rules. The tax in question is the Personal Property Lease Transaction Tax, which Chicago imposes at a rate around 9 percent and applies to nonpossessory computer leases, a category the city interprets to include cloud software and software-as-a-service used by customers in Chicago. The theory is that subscribing to SaaS is effectively leasing the provider’s computers and software, and the city taxes that lease.

There are two sides to how this touches the books. On the buy side, a Chicago company that subscribes to third-party SaaS tools for its own operations can owe the lease tax on those subscriptions. If the vendor charges the tax, it flows through as part of the cost. If the vendor does not charge it, the company may have a duty to self-assess the tax and remit it to the city, which means the books have to accrue a liability for tax owed even though no vendor invoiced it. A bookkeeper unaware of the rule would simply record the subscription cost and miss the accrued tax obligation entirely.

On the sell side, the exposure is larger and more important to record correctly. A SaaS company that provides its product to customers located in Chicago may be required to collect the lease tax from those customers and remit it to the city, much like a sales tax. When that is the case, the tax collected is not the company’s revenue, it is money held on behalf of the city, so the books have to carry it as a liability owed to Chicago rather than folding it into income. Recording collected tax as revenue would overstate earnings and hide the remittance obligation.

Alongside the lease tax, the Illinois layers also belong on the books. Any pass-through owners face the flat 4.95 percent Illinois income tax on income that flows to them, and the entity itself may owe the personal property replacement tax. These are separate from the Chicago lease tax but part of the same picture of what the company truly owes, and books that ignore them present an incomplete financial position.

Here is a concrete example. Suppose a Chicago SaaS company sells $600,000 of annual subscriptions to customers located in Chicago and, after analysis, those subscriptions are subject to the lease transaction tax. At roughly 9 percent, that is about $54,000 a year that should be collected from customers and remitted to the city, and the books should carry that collected tax as a liability, not as revenue. If the company never recorded the obligation, it would be accumulating a back-tax exposure that surfaces as a nasty surprise during diligence for a funding round. We record the lease-tax liability and the Illinois layers correctly so the books reflect the company’s true obligations, tying the compliance to our tax compliance service. The city publishes the rules through the Chicago Department of Finance, and the Illinois taxes sit with the Illinois Department of Revenue.