How Should SaaS Founders Reconcile Monthly Bookings to Revenue for the Board?
Show bookings, billings, deferred revenue, ASC 606 recognized revenue, and cash collections as separate, reconciled figures. B2B SaaS companies processing payments can easily conflate them when license fees and transaction-based charges fall in different months.
- Signed contracts establish commitments, but actual transaction volume may differ from the forecast.
- Invoices can precede delivery, so billings may increase deferred revenue before you recognize revenue.
- Collections can lag invoices, affecting cash planning without changing revenue already earned.
The monthly board view needs five separate, reconciled metrics
| Metric | What it shows | What it cannot tell the board |
|---|---|---|
| Bookings | Signed commitments plus separately labeled estimates of future transaction volume. | Actual payments volume or revenue earned. |
| Billings | Invoices issued, net of billing adjustments. | Whether customers paid or the company earned the invoiced amount. |
| Deferred revenue | Advance amounts owed as future service, shown as opening and closing contract liability balances. | All future contracted revenue; usage billed after delivery does not create deferred revenue. |
| ASC 606 recognized revenue | Revenue earned as contractual performance obligations are satisfied. | When customers will pay. |
| Cash collections | Payments received from customers, including collection of receivables. | Whether the cash relates to revenue earned this month. |
Read each row alongside its monthly forecast and prior-period balance. The sections below explain why the figures diverge and what a founder should do when they do.
Bookings show signed commitments, not revenue earned
Bookings record signed orders and expansion commitments. For B2B SaaS companies processing payments, a hybrid contract may fix a license fee and a transaction rate without fixing how many transactions customers will process. Show estimated transaction value separately from contracted amounts so the board can see which part of the bookings forecast depends on usage.
A contractually binding minimum makes part of the forecast more predictable. Keep that minimum separate from actual processed volume and recognized revenue. The contract terms determine what the customer owes, while the revenue schedule determines when the company earns it.
Build base, upside, and downside scenarios to forecast transaction-based revenue, including customer mix. Each month, compare signed deals and processed volume with the forecast assumptions. Repeated missed signings may call for a review of sales capacity. If signings hold but usage falls, check seasonality and customer mix before changing spend.
Billings show what customers were charged, not what they paid or what you earned
Billings capture invoices issued during the month, including credits and other billing adjustments. A signed order may start later or ramp over time, so its booking need not appear in billings right away.
For B2B SaaS companies processing payments, license fees may be invoiced in advance while transaction-based charges are invoiced after usage. An advance invoice can therefore precede revenue recognition because the company has not yet satisfied the related obligation under ASC 606.
Billings tell the board what customers have been charged, not what customers have paid or what the company has earned. When you compare months, separate license and transaction-based invoices. Usage seasonality and shifts in customer mix can change the total even when contract commitments remain steady.
Deferred revenue is the service you still owe after payment arrives or becomes due
Deferred revenue records what you still owe a customer after payment arrives or becomes due, but before you satisfy the related performance obligation under ASC 606. An upfront invoice for future license access may create a contract liability. An invoice for usage already delivered in arrears does not create deferred revenue merely because the customer has yet to pay.
Prepaid usage can also create a contract liability. You reduce that balance as you fulfill the obligations covered by the prepayment, following the contract's ASC 606 treatment. Transactions occurring on a customer's account do not, by themselves, create deferred revenue.
For the board, show opening and closing contract liability balances alongside billings and recognized revenue. A rising balance may reflect advance billing rather than increased demand. Compare the balance with bookings to check which commitments remain undelivered, but do not treat it as the full contracted backlog.
ASC 606 recognized revenue is the figure the board should use for growth and margin
The board should use the controller's ASC 606 revenue schedule for growth and margin analysis. ASC 606 recognizes revenue when a company satisfies its obligations to customers, rather than when a customer signs, receives an invoice, or pays. The controller should reconcile the schedule to the monthly close and show license and transaction-based revenue separately.
For B2B SaaS companies processing payments, contract terms determine how license and usage or transaction fees are recognized. Variable consideration, credits, refunds, and contract modifications can change the amount or timing of recognized revenue, so it may differ from billings and collections in a given month. Compare recognized revenue by stream with its direct costs to assess unit economics. Then compare revenue from acquired accounts with sales spending and the original forecast. Blended growth can conceal a shift toward customers whose transaction volume or margins fall short of plan.
Cash collections show liquidity, not earned revenue
Cash collections show what reaches your bank account from receivables and fees on processed transactions. They answer a runway question that recognized revenue cannot. Processor settlement timing and fees can further separate recorded charges from usable cash.
For B2B SaaS companies processing payments, license fees and transaction-based charges may arrive on different schedules. Usage volatility and seasonality shift transaction receipts, while customer mix affects when invoices come due. An enterprise contract with annual contract value above $100,000 may have Net 30 or Net 60 terms. Collections can then lag invoicing and recognized revenue, so fast growth can increase the cash needed to fund operations.
Compare receivables aging and actual collection dates with the cash forecast. If payment lags, revise runway, cash buffers, or growth spending without mistaking late cash for weaker demand or lower margins. A revenue-based loan may cover a timing gap, but its cost and repayments can constrain future cash. Compare it with borrowing against receivables, negotiating payment terms, and moderating spend before choosing financing.
The controller reconciles the close and the strategic finance leader acts on it
B2B SaaS companies processing payments need a strong team of senior controller and strategic finance talent. The controller reconciles billing records, Stripe activity, and financial accounts. Every dollar of billings, deferred revenue, cash collections, and accounts receivable needs an accounted-for place in the close, with discrepancies identified before the finance leader uses the numbers to forecast.
The strategic finance leader turns that reconciled close into revenue and cash forecasts, then prioritizes capital for accounts with the strongest growth potential. Growth should not outrun the cash available to support it. This is the approach at Bridges, which pairs controller services with strategic finance.
At Bridges, we want founders to understand the health of their revenue, not just celebrate a rising number. For companies billing in arrears, growth can require spending on sales and delivery well before customers pay. If working capital is already strained, chasing that growth without a collections forecast can leave the company short of cash.
A reconciled board view separates timing delays from weaker demand
A reconciled monthly board view helps you separate timing delays from weaker demand or deteriorating margins. If collections lag while recognized revenue holds, revisit cash buffers and spending. If signed orders keep missing the forecast, review sales capacity. If transaction margins weaken, examine pricing and customer mix.
