Monthly Financial Reporting for Startups and SaaS in Chicago

Monthly financial reporting for a Chicago SaaS startup is a defined package delivered on a fixed schedule, not a one-off export, and knowing exactly what it contains explains why it is worth doing every month rather than scrambling at quarter end. In essence the package has three parts. The first is the set of financial statements, the profit and loss showing revenue and expenses for the month, the balance sheet showing what the company owns and owes including its deferred revenue and any lease-tax liability, and the cash flow statement showing where the money actually went. The second is a metrics summary built for a SaaS audience, carrying monthly recurring revenue, annual recurring revenue, net revenue retention, gross margin, monthly burn, and runway. The third is a short written commentary that explains what changed and why, so a founder can speak to the numbers rather than just present them.

The reason all three parts matter is that a board reads them together. The statements establish that the numbers are real and tie to reconciled books. The metrics translate those statements into the language investors think in, because a venture investor cares about ARR growth and net revenue retention more than about a raw revenue line. The commentary connects the two, pointing out that runway moved because a renewal slipped or that gross margin dipped because hosting scaled with usage. Without the commentary, a founder is left explaining surprises live in the meeting, which erodes confidence, and a board that is surprised twice tends to start asking for more control. For a Chicago company the package also surfaces the local tax layers, showing the Chicago lease tax collected as a liability rather than revenue and keeping the Illinois replacement tax in view so year-end does not blindside anyone. The value is that everything a board or an investor needs sits in one consistent document that arrives on time every month rather than being rebuilt from scratch under deadline pressure.

Here is a worked example of how the pieces fit. Suppose your Chicago SaaS company closes a month with $95,000 of recognized revenue, $150,000 of operating expense, and $1,100,000 of cash. The profit and loss shows a $55,000 operating loss, the cash flow reconciles that to a $150,000 burn once non-cash items and deferred revenue movement are considered, and the runway line reports roughly seven months. The metrics summary shows MRR of about $95,000, ARR near $1,140,000, and gross margin after processing and hosting. The commentary notes that burn rose because a new engineer started, which the board can weigh against the added capacity, and flags that a large renewal is due next month. That full picture, delivered days before the meeting rather than assembled inside it, is what monthly reporting produces and what lets a founder lead the conversation instead of reacting to it. A board that receives the same clean package month after month learns to trust the founder, and that trust is worth real money when terms are negotiated. We build it off reconciled books through our financial reconciliation work. The IRS accounting methods guidance and the Illinois Department of Revenue inform how the underlying revenue and taxes are treated.

Burn and runway are the two numbers a Chicago startup’s board asks about first, and monthly financial reporting is where they get calculated off real books rather than a founder’s mental estimate, which matters because getting them wrong drives the single most expensive decision a startup makes, when to raise. Burn is the net cash the company uses in a month. Gross burn is total cash out, and net burn subtracts any cash coming in from revenue, so net burn is the figure that actually depletes the bank. Runway is the cash on hand divided by net burn, expressed in months, and it answers the question every founder and investor lives with, how long until the money runs out. Reporting both gross and net burn matters, because a company can cut runway risk either by growing revenue or by trimming spend, and the two burn figures show which lever is moving.

The calculation sounds trivial, but it is only as good as the books beneath it, which is why reporting has to sit on reconciled accounts. Three common errors distort burn for a SaaS company. First, if cash raised through a SAFE or a round was booked as revenue, the company looks like it is burning less than it is, because financing inflows are masking operating losses. Second, if payment processor deposits were recorded net without splitting out fees, both revenue and expense are understated and the burn picture is muddy. Third, and specific to Chicago, if the roughly 9 percent lease tax collected from Chicago customers is sitting inside revenue rather than a liability, revenue is overstated and net burn looks artificially low. Reporting corrects all three by drawing on reconciled books where financing, fees, and taxes are already separated, and it also smooths out one-time items like an annual insurance payment so the trend reflects the true ongoing burn rather than a lumpy month.

Here is a worked example. Suppose your Chicago SaaS company has $1,200,000 in the bank at month end. Its true operating cash out was $210,000, and it collected $60,000 of subscription cash, so net burn is $150,000. Runway is $1,200,000 divided by $150,000, which is eight months. That eight-month figure tells the founder to start raising now, because a venture round routinely takes three to five months to close and you never want to be negotiating with two months of cash left. Now suppose the books had wrongly counted a $90,000 SAFE inflow as revenue that month. Net burn would appear to be only $60,000, runway would look like twenty months, and the founder would wait, then be caught short with a round half-closed and the bank nearly empty. The difference between those two readings is the difference between raising from strength and raising in a panic at a discount, and a discounted round taken under duress can cost a founder several points of ownership they never get back. We calculate burn and runway monthly off reconciled numbers and frame them for the raise through investment coordination. The IRS starting a business center and the Illinois Department of Revenue cover how the inflows and taxes behind these figures are treated.

Monthly financial reporting for a SaaS startup depends on ASC 606 revenue because every metric a board reads, MRR, ARR, gross margin, and net burn, is built on the revenue number, and if that number is measured on cash instead of on earned revenue, every metric above it is wrong. ASC 606 is the revenue recognition standard, and its rule for subscriptions is that you recognize revenue as you deliver the service over the contract term, not when the customer pays. For a company that sells annual plans and collects the year up front, cash and revenue diverge sharply, and the reporting has to follow revenue, not cash, or the entire picture distorts and every downstream metric inherits the error.

The reason this is not academic is that SaaS metrics are defined in terms of recurring revenue. Monthly recurring revenue is meant to be the steady, normalized subscription revenue for a month, which is exactly what ASC 606 produces when an annual contract is spread across its twelve months. If instead MRR is calculated off cash collected, then a single large annual prepayment lands as a huge spike in one month and nothing in the following months, making the revenue trend look wildly volatile and the growth story unreadable. An investor who sees MRR jump and then collapse will not trust it, and rightly so, because it signals either bad accounting or churn that is being hidden. Beyond MRR, gross margin depends on matching the revenue earned in a period against the cost of delivering it in that same period, which only works when revenue is recognized as earned, and net revenue retention is meaningless unless each customer’s recurring revenue is measured consistently period to period.

Here is a worked example. Suppose your Chicago SaaS company signs a $24,000 annual contract in March and collects the full amount up front. Under ASC 606, March revenue from that deal is $2,000, and the remaining $22,000 sits in deferred revenue and is recognized at $2,000 a month through the following February. Reported correctly, MRR from this customer is a steady $2,000. Reported on cash, March would show $24,000 of revenue from this one deal and the next eleven months would show zero, so the reporting would display a $24,000 spike and then an apparent loss of that revenue, which is not what happened at all. Multiply that across many annual deals closing in different months and cash-based reporting becomes noise that no investor can read, while ASC 606 reporting produces a smooth, believable line that reflects the real business. That believable line is exactly what lets a founder claim a growth rate an investor will accept without a fight, and it keeps the company from the embarrassment of restating revenue mid-diligence when the cash-based numbers fall apart under a closer look. We report all SaaS metrics off ASC 606 revenue drawn from reconciled books, and we tie the reporting to the monthly close in our bookkeeping service. The IRS accounting methods guidance and the Illinois Department of Revenue address how the recognized revenue is ultimately reported for tax.

Monthly financial reporting for a Chicago company has to show the Chicago lease transaction tax and the Illinois replacement tax explicitly, because a report that leaves them out overstates margin and understates burn, and a board that later discovers the omission loses confidence in the whole package. These two taxes are exactly the items a reporting template built for a no-tax state or a generic business misses, so surfacing them correctly is a large part of what makes local reporting worth having rather than a generic dashboard that could describe any company anywhere.

Start with the Chicago Personal Property Lease Transaction Tax, which runs at roughly 9 percent and can apply both to the SaaS tools the company buys and to the product it sells to Chicago customers. In the report, these show up in two different places. Lease tax the company pays on its own inbound software is a real operating cost and belongs in expenses, where it correctly lowers gross margin and raises burn, so the founder sees the true cost of the tool stack rather than an understated one. Lease tax the company collects from its Chicago customers is not revenue at all, it is money held on behalf of the city, so it belongs on the balance sheet as a liability until it is remitted, never in the revenue line. If that collected tax were reported as revenue, the top line and margin would both be overstated, and the company would be carrying an unshown debt to the city that grows every month until it surfaces, usually at the worst possible time during a raise.

The Illinois replacement tax works differently but also belongs in the picture. Illinois levies it on the entity, roughly 2.5 percent on a C corporation and 1.5 percent on pass-throughs, on top of the flat 4.95 percent income tax. A pre-profit startup may owe little in a given month, but the obligation and the state filing still belong in the forward-looking view so year-end is not a surprise, and a company approaching profitability needs to see it coming. Here is a worked example. Suppose your Chicago SaaS company collects $54,000 of lease tax over a year on Chicago subscriptions and pays $6,000 of lease tax on its own software tools. Reported correctly, the $54,000 never touches revenue and sits as a liability that clears as it is remitted, while the $6,000 shows as expense, trimming reported gross margin by that amount so the founder is not surprised by thinner margins later. A report that buried the $54,000 in revenue would overstate annual revenue by that sum and hide the payable entirely, a discrepancy an investor’s advisors would find and question, and one that can stall a deal while the founder scrambles to quantify the back-tax exposure. We keep both taxes visible in the monthly numbers and coordinate the compliance through client accounting services. The city documents the lease tax at the Chicago Department of Finance and the state taxes at the Illinois Department of Revenue.

Monthly financial reporting is one of the most direct things a Chicago startup can do to make its next fundraise faster and cleaner, because the numbers a company reports every month are the same numbers an investor will demand in diligence, and having them already produced, consistent, and reconciled turns a raise from a scramble into a handoff. A venture round has two phases where financials matter, the pitch, where the metrics have to tell a growth story, and diligence, where a buyer’s advisors test whether those metrics are real. Monthly reporting serves both, and a company that has been reporting all along walks into each phase already prepared rather than assembling a data room from a cold start.

In the pitch, an investor wants to see ARR, its growth rate, net revenue retention, gross margin, burn, and runway. A company that has reported these every month can show a clean twelve-month trend line, which is far more persuasive than a snapshot assembled the week before, because a trend proves consistency and a snapshot invites suspicion that the numbers were arranged to flatter. In diligence, the investor’s team reconciles the metrics to the underlying financials and the financials to the source data. This is where companies that reported loosely get punished, because the advisors find that MRR was calculated on cash, or that the Chicago lease tax was sitting in revenue, or that deferred revenue does not tie to contracts, and each discovery slows the deal and gives the investor a reason to negotiate the price down. A company with reconciled monthly reporting sails through because the numbers already tie, and its founder spends diligence answering strategic questions rather than fixing accounting.

Here is a worked example. Suppose two Chicago SaaS startups each raise a Series A at roughly $1,500,000 of ARR. The first has reported monthly for two years, so its data room shows a consistent ARR trend, net revenue retention above 100 percent, a clean burn and runway history, and revenue recognized under ASC 606 that ties to contracts. Diligence takes a few weeks and the terms hold. The second reported ad hoc, and its advisors find MRR inflated by cash-based recognition and an unrecorded lease-tax liability, so diligence drags for months, the valuation gets trimmed, and the founder spends the period defending numbers instead of building the company. The reporting discipline is the difference between those outcomes. Because runway is finite, the weeks saved in diligence are weeks of cash preserved, and the clean numbers protect the valuation the founder worked to earn. In a competitive market where a term sheet can be pulled if diligence surfaces surprises, that clean package is often what keeps the round alive at all, and it lets a founder run a tight process with several investors rather than clinging to the only one still at the table. We produce the monthly package that makes this possible and frame it for investors through investment coordination. The IRS starting a business center and the Illinois Department of Revenue cover the tax treatment behind the reported figures.