SaaS · Finance

SaaS Financial Operations — A Field Guide

Financial operations is the unglamorous machinery that turns subscriptions into trustworthy numbers — billing, revenue recognition, reconciliation, and collections done right.

John Kihiu12 min read

Financial operations — FinOps in the finance sense — is the day-to-day machinery of running a SaaS business's money: billing customers correctly, recognising revenue properly, reconciling the systems, and collecting what you are owed. It is unglamorous and easy to neglect, and neglecting it produces numbers no one can trust and revenue that quietly leaks. Getting it right is what makes every metric downstream reliable.

Billing and revenue recognition

Two related but distinct things. Billing is charging the customer — the right amount, at the right time, handling upgrades, downgrades, proration, and failed payments. Revenue recognition is accounting for that revenue when it is earned, not when it is billed: an annual plan paid upfront is recognised across the twelve months it covers, not all in month one. Conflating billing with recognition is the classic SaaS accounting error, and it distorts your reported performance.

Reconcile the systems

Your billing system, your accounting records, and your bank must agree, and they drift apart without active reconciliation — a failed charge here, a manual adjustment there, a mis-synced refund. Regularly reconcile what the billing system says you charged against what actually hit the bank, and investigate the differences. Unreconciled billing is where revenue leaks unnoticed and where your metrics quietly become fiction.

Dunning and collections

A meaningful share of SaaS churn is involuntary — payments that fail because a card expired or was declined, not because the customer chose to leave. A dunning process recovers that revenue: retry failed payments on a smart schedule, notify customers to update their card, and escalate before cancelling. Recovering failed payments is some of the cheapest revenue you will ever find, because the customer already wanted to keep paying.

Involuntary churn is recoverable churn

Before optimising acquisition, plug the leak of customers lost to failed payments they never intended. A solid dunning flow — retries, reminders, card-update prompts — routinely recovers a real fraction of would-be churn. It is money you have already earned quietly walking out the door over a technicality.

SaaS financial operations is correct billing separated from proper revenue recognition, regular reconciliation so the billing system and the bank agree, metrics computed from that clean data, and dunning to recover involuntary churn. It is not glamorous work, but it is what makes the difference between a business whose numbers you can trust and one whose reported revenue is a hopeful approximation.

John Kihiu
Acumatica ERP Developer · Laravel Engineer

Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.