SaaS Revenue Reporting

The SaaS Monthly Close Revenue Pack

A complete monthly close for a SaaS company should produce four revenue-related deliverables. Each serves a distinct audience — your GL, your auditors, and your operating team.

1. Revenue Recognition Schedule

The contract-level schedule showing each deal, its term, and the monthly revenue allocation. This is your primary working paper and the source of truth for the GL posting.

Generate yours with our free calculator.

2. Deferred Revenue Rollforward

The period-over-period movement of your balance sheet liability:

Opening balance + new bookings - recognised revenue = closing balance

Build one with our waterfall tool.

3. Journal Entry Summary

The monthly journal entries typically include:

• Dr Deferred Revenue / Cr Revenue — the monthly recognition journal
• Dr Accounts Receivable / Cr Deferred Revenue — when new invoices are raised
• Dr Revenue / Cr Deferred Revenue — if adjustments or corrections are needed

4. Revenue Waterfall (MRR/ARR)

While not a GAAP requirement, the MRR waterfall is essential for operating analysis:

• Opening MRR
• (+) New business
• (+) Expansion (upsells)
• (-) Contraction (downgrades)
• (-) Churn
• = Closing MRR

In practice: Most SaaS finance teams produce these four deliverables within 3-5 business days of month-end. If any single deliverable takes more than a few hours, that is a signal the underlying data or process needs automation.

Board Revenue Slides That Add Value

Board decks should bridge the gap between GAAP revenue and operating metrics. Directors want to understand not just what happened, but why.

Key slides to include:

• Revenue vs. plan — recognised revenue compared to budget/forecast
• Bookings vs. revenue — showing the timing difference between signing and recognition
• Deferred revenue trend — quarter-over-quarter showing growth in future revenue
• Net revenue retention — the expansion vs. churn picture for existing customers

Watch for: Presenting MRR/ARR alongside GAAP revenue without clearly labelling the difference. Board members who are not accountants may conflate the two, leading to incorrect conclusions about growth or runway.

Audit-Ready Documentation Checklist

When auditors arrive, they will request documentation in a specific order. Having these ready upfront saves weeks of back-and-forth:

1. Revenue recognition policy memo (documented methodology)
2. Complete revenue schedule with contract-level detail
3. Deferred revenue rollforward reconciled to the GL
4. Sample contracts for testing
5. Documentation of significant judgments (SSP estimates, variable consideration constraints)
6. Reconciliation of ARR/MRR to GAAP revenue

Having clean, automated schedules significantly reduces audit time and the risk of management letter comments.

In practice: Create a shared folder (or audit room) before the auditors arrive. Pre-populate it with the six items above. Auditors who can self-serve on documentation rarely expand their sample size.

Revenue Reporting Errors That Trigger Restatements

1. Recognising revenue at invoicing — revenue should follow delivery, not billing
2. Inconsistent treatment across contracts — apply the same methodology to similar contracts
3. Not tracking contract modifications — upgrades and downgrades need journal adjustments
4. Spreadsheet formula drift — as contract volumes grow, manual schedules become error-prone

In practice: Even a single month of incorrectly recognised revenue can cascade into prior-period adjustments during an audit. Catching these errors early — ideally through an automated reconciliation check at month-end — is far cheaper than correcting them retroactively.