ERP Consultant for SaaS

The SaaS quote-to-cash process, step by step

Unlike service firms, a SaaS company sells a product that is billed again and again under changing terms. The core process map, in words, is:

Lead -> trial or demo -> opportunity -> quote with plan, seats, add-ons and discounts -> signed order or self-serve checkout -> subscription created -> provisioning -> recurring invoice and usage charges -> payment and dunning -> amendments: upgrades, downgrades, seat changes -> renewal or cancellation.

Self-serve and sales-led customers often follow different paths into the same subscription records. Self-serve sign-ups may start in a payment platform, while enterprise deals start in CRM with custom terms. Both have to land in one consistent billing and accounting model.

When I map this flow, I follow one customer of each type, plus a mid-term upgrade and a cancellation, through every system. That usually reveals the real problems: amendments that never reach CRM, discounts applied by hand, or usage data that arrives after invoices are issued. I document the flow in process maps that finance, sales and product can all read.

Pain points SaaS finance teams run into

SaaS businesses tend to hit the same set of problems as they grow:

• CRM and billing disagree. Contract value in CRM does not match what billing charges, because amendments are made in one system only.
• Usage billed by spreadsheet. Product usage is exported, adjusted and uploaded each month, which delays invoices and causes disputes.
• Deferred revenue tracked outside the system. Annual prepayments are invoiced at once, and the release of revenue over the term is calculated manually.
• Several recurring revenue numbers. Sales, finance and investors each see a different figure because definitions were never agreed.
• Failed payments handled ad hoc. Dunning and retry rules are inconsistent, and involuntary churn is not measured.
• Multi-currency and tax complexity. Selling worldwide adds currencies, sales tax or VAT rules and entity structures that simple accounting tools handle poorly.

Most of these come from unclear ownership of data. Once each system has a defined role, the right platform choice becomes much clearer. For the CRM link specifically, see ERP and CRM integration.

Revenue recognition concepts, in system terms

Revenue recognition is where SaaS finance systems are most often under-designed. I do not set accounting policy: your accountants or auditors decide how standards such as ASC 606 or IFRS 15 apply to your contracts. What I do is make sure the system can record and report whatever they decide. The concepts the system has to support usually include:

• Billing is not revenue. An annual invoice raised upfront is typically recorded as deferred revenue and released over the service period.
• Contracts with several elements. A deal may combine a subscription, onboarding services and support. Your accountants may treat these separately, so the system needs to hold them as distinct lines.
• Contract changes. Upgrades, downgrades and cancellations mid-term change future revenue schedules and must update them automatically.
• Usage-based charges. Variable fees are often recognized as usage occurs, which requires reliable usage data by period.
• Audit trail. Every schedule should trace back to a contract, invoice and policy.

I write these needs into the requirements so platforms are tested on real scenarios, not just on whether they mention revenue recognition in a brochure.

Recommended modules and finance stack for SaaS

A SaaS finance stack is often a combination rather than a single ERP. The components that matter are:

• CRM: opportunities, quotes, contract terms and renewals for sales-led deals.
• Subscription billing: plans, seats, add-ons, proration, usage rating, invoicing, payment collection and dunning.
• Accounting or ERP: general ledger, receivables, deferred revenue, multi-currency, multi-entity and tax.
• Revenue schedules: either inside the billing tool, inside the ERP or in a dedicated revenue module.
• Purchasing and expenses: cloud hosting, software vendors and contractor costs, often a large share of spend.
• Reporting: recurring revenue, churn, expansion, retention and cash runway from agreed definitions.

The key decision is where subscription logic lives: inside the ERP, or in a specialist billing platform feeding the ERP. Early-stage companies often do well with a billing tool plus accounting. Larger or multi-entity companies may need a stronger ERP behind it. I assess this in an ERP evaluation grounded in your pricing model and growth plans. Firms with recurring managed contracts face similar choices, as covered on the IT services page.

Implementation checklist, migration and growth data

Before building, I make sure a SaaS company has agreed and documented:

1. The full price book: plans, tiers, seats, add-ons, discounts, trials and usage meters.
2. Proration, upgrade, downgrade and cancellation rules.
3. Which system owns customers, contracts, subscriptions, usage and invoices.
4. Accounting policies from your accountants, translated into system requirements.
5. Recurring revenue, churn and retention definitions signed off by finance and leadership.
6. Dunning steps and how failed payments affect access.
7. Tax handling by country or state, confirmed with your tax advisors.

Migration means moving active subscriptions with their exact terms, renewal dates, prepaid balances and deferred revenue positions. I recommend a parallel billing run, where old and new systems produce the same month's invoices for comparison, before cutover. The data migration plan defines the reconciliation checks.

Clean billing data also improves growth decisions. When CRM and billing agree, acquisition channels can be judged on retained revenue rather than sign-ups, which links directly to SaaS SEO and paid acquisition. The CRM and lead generation case study shows that link in a services context. Contact me to map your quote-to-cash flow.