SaaS startup bookkeeping: MRR you can trust, deferred revenue done right

Cash, billings, and revenue are three different numbers

A SaaS company has three layers of "how much did we make": cash that reached the bank, what customers were billed, and revenue actually earned — the current month's slice of every active contract. Bank-feed bookkeeping collapses all three into one, which is why so many startups discover at their first financing that their revenue was never real.

We run QuickBooks Online or Xero as the ledger, with billing data flowing from Stripe through a controlled connector or mapped import — a raw Stripe feed dumped into the ledger is where most startup books go wrong. Dashboards like ChartMogul or Baremetrics are excellent for MRR analytics, but the ledger is what an investor's diligence team will actually tie out.

Deferred revenue: the schedule behind every annual plan

Annual prepay is great for cash and dangerous for books: the money arrives at once but is earned over twelve months, so the unearned balance is a liability, not income. We maintain a deferred revenue schedule by contract and roll it every month, with upgrades, downgrades, and churn adjusting the remaining term.

Deferred revenue is one of the first schedules a financing or acquisition diligence asks for. Built monthly it is a report; improvised at term-sheet time it is a discount to your valuation.

Stripe payout reconciliation, not payout booking

A Stripe payout is a batch: charges minus refunds, disputes, and fees, settled on a lag. Booking payouts as revenue understates your topline, hides processing cost, and misses the money still in transit at month-end. We reconcile every payout to its underlying balance transactions — gross charges to revenue, fees to expense, refunds to contra revenue, disputes and reserves to their own accounts — and carry the in-transit balance as a receivable at the close.

USD subscriptions add the FX layer: revenue converts at proper monthly rates and the gain or loss on conversion is booked separately, so growth in CAD terms is not just currency drift.

SR&ED-ready books: tag it when it happens

A SR&ED claim is won or lost on contemporaneous records, and the books carry half of that burden. We tag developer salaries and contractor invoices by person and by project as they are posted, so the eligible salary base for the T661 is a report you pull, not a year-old reconstruction. Most CCPC claims use the proxy method, which computes overhead from eligible salaries — one more reason payroll must be clean and consistently coded.

For a pre-revenue CCPC the enhanced refundable federal credit is real cash flow, and CRA reviewers increasingly ask how claimed time was tracked. Books that already split eligible work from routine development answer that question before it is asked.

Burn and runway your board can trust

Burn only means something on accrual books. A month with a big annual prepay looks spectacular in cash and ordinary in accrual — the board should see both, labelled honestly: gross burn, net burn, and runway from the actual cost base. Because deferred revenue is tracked, nobody mistakes collected-but-unearned cash for margin.

We close by mid-month with a founder-ready package: MRR movement reconciled to the ledger, deferred revenue roll-forward, burn and runway, and clean GST/HST treatment of Canadian versus zero-rated US revenue. When US customers trigger state sales tax questions or a Delaware flip enters the conversation, our cross-border tax guide for SaaS startups covers that ground, and our bookkeeping services page shows how the monthly close runs.

Source: CRA — SR&ED tax incentive program.