A SaaS customer pays $12,000 upfront in January for a 12-month subscription. Under ASC 606 (the US revenue recognition standard) and its international equivalent IFRS 15, the company cannot report the full $12,000 as revenue in January. Revenue is recognized as the company delivers the service over the 12-month period: $1,000 per month from January through December.
This is not just accounting policy. It affects how investors read the income statement, how the audit is conducted, and how Salesforce Revenue Cloud must be configured to support compliant reporting. Revenue Cloud ships with four recognition methods that map to the common patterns in B2B subscription and product businesses.
The compliance backdrop
ASC 606 (US GAAP) and IFRS 15 (international) require revenue to be recognized when performance obligations are satisfied. The standards define 5 steps for analyzing a contract:
- Identify the contract with the customer.
- Identify the performance obligations in the contract.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognize revenue when (or as) performance obligations are satisfied.
For Revenue Cloud purposes, step 5 is where the four methods come in. The other 4 steps drive how the Quote, Order, and Contract are structured.
Auditors will read the Revenue Schedule records and confirm they match the contract terms and the recognition method documented in the accounting policy. The Salesforce configuration becomes part of the audit trail.
Method 1: Ratable over service period
The most common method for SaaS subscriptions. Recognize revenue evenly across the service period.
Example: $12,000 annual subscription, 12-month service period.
- Revenue per month: $1,000
- Schedule: 12 monthly entries from service start through service end
When to use:
- Subscription products where service is delivered continuously.
- Maintenance and support contracts.
- Recurring service relationships.
Configuration in Revenue Cloud: Set the product's Revenue Recognition method to Ratable. Salesforce auto-generates a Revenue Schedule with monthly entries (or whatever frequency the product specifies).
Audit considerations: The auditor will sample Revenue Schedule entries and confirm they sum to the contracted amount and span the correct period. Off-by-one errors at start or end produce immediate audit findings.
Method 2: On invoice (point-in-time)
Recognize revenue at the moment the invoice is posted. Used when the performance obligation is satisfied at a discrete event (no ongoing service).
Example: $5,000 setup fee invoiced in March, no ongoing service component.
- Revenue in March: $5,000
- Schedule: single entry at invoice date
When to use:
- One-time professional services delivered up front.
- Setup or onboarding fees.
- Hardware sales (with caveats; see method 3).
Configuration in Revenue Cloud: Set Revenue Recognition method to On Invoice. The Revenue Schedule has one entry tied to the invoice date.
Audit considerations: The auditor will confirm that the performance obligation was actually satisfied at the time of invoicing. If the setup work is actually delivered over weeks, On Invoice is wrong; use Ratable across the delivery window.
Method 3: On activation or delivery
Recognize revenue at the moment of activation or shipment, which may differ from the invoice date.
Example: Hardware shipped to the customer in February, invoiced in January (with payment terms).
- Revenue in February (shipment date): full amount
- Schedule: single entry at activation date
When to use:
- Hardware sales where the performance obligation is transfer of physical goods.
- License keys delivered as discrete events.
- Implementations marked complete at a specific date.
Configuration in Revenue Cloud: Set Revenue Recognition method to On Activation. The Revenue Schedule reads the activation date from the Order Product. The invoice date is separate.
Audit considerations: The activation date must be auditable. The Order Product needs explicit activation tracking (date, who confirmed, what was activated). Verbal confirmation from sales is not enough.
Method 4: On milestone
Recognize revenue as discrete milestones are completed. Used for project work where deliverables are phased.
Example: $300,000 implementation project with 3 phases: Discovery ($90K, month 2), Build ($150K, month 4), Deploy ($60K, month 6).
- Month 2: recognize $90,000 (Discovery complete)
- Month 4: recognize $150,000 (Build complete)
- Month 6: recognize $60,000 (Deploy complete)
When to use:
- Multi-phase implementation projects.
- Long-cycle professional services with milestone-based deliverables.
- Custom development with phased acceptance.
Configuration in Revenue Cloud: Set Revenue Recognition method to On Milestone. The product or Order Product specifies the milestone schedule, with allocations per milestone. Revenue is recognized as each milestone is marked complete.
Audit considerations: The milestone completion criteria must be documented in the contract and verifiable. The auditor will confirm that revenue was recognized only after the milestone deliverables were accepted by the customer. Marking a milestone complete without customer acceptance is a finding.
Picking the right method per product
The decision per product:
| Product type | Method |
|---|---|
| SaaS subscription | Ratable |
| Maintenance / Support | Ratable |
| Professional services delivered upfront | On Invoice |
| Setup / Onboarding fee | On Invoice (if delivered immediately) or Ratable (if over time) |
| Hardware | On Activation |
| License keys | On Activation |
| Phased implementation projects | On Milestone |
| Hybrid (subscription + services) | Mixed: subscription Ratable, services per their nature |
The matrix encodes accounting policy. Documented once, applied consistently across all products in the catalog.
Common revenue recognition mistakes
Five patterns Sapota has seen in audits:
- Ratable used for everything. All products configured Ratable for simplicity, including one-time setup fees that should be On Invoice. Causes minor timing errors that compound at audit.
- On Invoice for ongoing services. A 12-month support contract configured as On Invoice (because it is "one charge"). Full $12,000 recognized at invoice. Customer asks for refund mid-year and revenue cannot easily be reversed. Restatement risk.
- On Activation without an activation date field. The method is set but no activation date is tracked. Revenue schedule cannot determine when to recognize. Schedule remains empty until manually populated. Audit risk.
- Milestone amounts that do not sum to contract value. Phase 1 $90K, Phase 2 $150K, Phase 3 $60K, contract is $310K. Discrepancy means $10K is unaccounted for. Find and resolve during contract creation.
- No reconciliation to GL. Revenue Schedule entries do not match GL journal entries. Source of truth is unclear. Audit becomes a reconstruction exercise.
Revenue Schedule integration with the GL
The Revenue Schedule is the source of period-by-period revenue. The general ledger (NetSuite, SAP, Oracle Financials) needs this data for monthly close.
Two integration patterns:
Salesforce as the source of truth. Revenue Schedule entries are exported to the GL each period. The GL posts journal entries based on the export. Salesforce is authoritative.
GL as the source of truth. Revenue Schedule is generated in Salesforce as a draft, exported to the GL, reviewed and adjusted by accounting, then the GL posts the final entries. Salesforce is informational.
Most implementations use pattern 1 with accounting oversight. The integration must support reconciliation: a way to verify that GL entries match Revenue Schedule entries for any given period.
What good revenue recognition looks like
A Salesforce Revenue Cloud revenue recognition setup that satisfies audit:
- Recognition method configured per product type, documented in the accounting policy.
- Revenue Schedule generated automatically on Order activation.
- Activation dates and milestone completion tracked with audit-ready evidence.
- GL integration with reconciliation reporting per period.
- Quarterly policy review to catch product additions that need method assignment.
Revenue recognition is one of the most audit-visible parts of Revenue Cloud. Sapota's Salesforce team treats it as a finance-led workstream during implementation, with explicit auditor walkthroughs to validate the configuration before go-live.
Configuring revenue recognition in Salesforce Revenue Cloud? Sapota's Salesforce team holds the Revenue Cloud Consultant credential and handles ASC 606 and IFRS 15 implementation on production engagements. Get in touch ->
See our full platform services for the stack we cover.
