How StepFive works

From deal to revenue.
With the detail intact.

Your Salesforce Revenue Cloud deal already carries its prices, periods and source records. StepFive connects that detail to SSP, allocation and recognition, with Revenue Cloud Billing evidence alongside it.

ASC 606 and IFRS 15

The five steps, mapped to the engine

Where a judgment has to be recorded, such as a control-transfer date or how a change is treated, the engine waits until a person records it.

  1. 01Identify the contractKeyed from the Revenue Cloud order, its assets and contract.
  2. 02Identify obligationsDistinct goods and services, with your accounting judgments.
  3. 03Determine the priceThe order's own priced amount, read where it lives.
  4. 04Allocate the priceRelative standalone selling price, exact to the cent.
  5. 05Recognize revenueReviewed runs, balanced journals, a second approver.

Built for Salesforce Revenue Cloud

The records behind the revenue.

The connection reaches into the selling, asset and billing record families. Those relationships keep the source of an amount available as your team reviews recognition.

Quote and order detail.

SSP evidence belongs with the quote and order lines. Native detail lines keep effective dates and prices available for source review.

ProductsQuotesQuote linesQuote line detailsOrdersOrder productsOrder product details

Asset history.

Assets, their actions and state periods connect the sold line to the installed product and its lifecycle context.

AssetsAsset actionsAsset action sourcesAsset state periods

Billing context.

Schedules, billing periods and invoice evidence connect the commercial source to billing dates and amounts.

Billing schedulesBilling schedule groupsBilling period itemsInvoices and invoice lines

Usage evidence.

Usage summaries and liable summaries provide the consumption and rated billing-period context for the usage workflow.

Usage summariesLiable summaries

See the related lifecycle and billing context

StepFive's source readers also use quote and order actions, order product groups and relationships, asset contract relationships, credit memo lines, and billing milestone plans and items. These records provide context for reviewed source mappings and accounting treatments.

Bring a ramp, a detail-priced line or a lifecycle change to the walkthrough. We will confirm its source mapping and the accounting treatment your team needs.

SSP at the source

Price the deal.
Keep the accounting basis.

StepFive resolves standalone selling price within native Revenue Cloud pricing, then carries the SSP evidence on quote and order lines.

The quote-to-order journey preserves the policy, basis, resolved amounts, status and explanation. Your team can inspect those values before revenue allocation begins.

Choose the basis.

Set SSP as an amount or a percentage of list price. Use your configured policy to resolve a fixed value or evaluate a range.

Keep the outcome with the line.

Review the policy result and supporting SSP values alongside the agreed commercial price. Native repricing refreshes the evidence.

Step 4 · Allocate

One order. Every cent accounted for.

The robot, software and support each receive a share of the USD 146,760.00 order, based on their recorded standalone selling prices. The engine keeps the allocation tied to the transaction price, including the final cents.

ObligationExtended SSP (USD)Allocated (USD)Recognition schedule
AlphaX 500 Robot ×1 (one-time)150,000.00117,133.13One amount on the attested control-transfer date, 2027-01-15
RoboControl Cloud – Standard ×10 (annual term)32,990.0025,761.4812 × 2,146.79 over 2027
RoboCare Premium Support ×1 (annual term)4,950.003,865.3911 × 322.11, then 322.18, over 2027
Total187,940.00146,760.00

Revenue Cloud Billing · Usage products

The usage charge has a source.

Revenue Cloud Billing's liable summaries hold the rated consumption charge and its usage period. StepFive's usage capture connects selected summaries to the sold obligation and keeps the source snapshot with the recognition evidence.

Your accounting team sets the usage treatment and reviews what is ready to recognize. Confirm your consumption, commitment and source-readiness requirements during the walkthrough.

Follow the usage period.

Usage amounts retain the period they belong to, so the recognition workflow can review the charge in context.

Return to the liable summary.

The source snapshot gives reviewers a path back to the rated amount and the originating Salesforce record.

Data flow

From Revenue Cloud order to posted journal

Follow the source package through review, activation, recognition and journal posting. A second person reviews the source package, schedules and journals.

Illustrative workflow using a USD 146,760.00 Robotics Inc. order: source checks, independent approval, allocation, recognition and balanced journals.
Illustrative workflow using a USD 146,760.00 Robotics Inc. order: source checks, independent approval, allocation, recognition and balanced journals.
See the review and approval sequence
#StepWho
01Stage a legal entity and date window, and declare the control totals.Preparer
02Dispose each named exception with a written reason. A one-time item also needs an attested control-transfer date.Preparer
03Seal. The declared totals are checked against the staged rows and the native billed total.Preparer
04Approve. Approval is tied to the exact decisions reviewed, against a fresh read of Revenue Cloud.Second person
05Activate. The evidence is re-checked, then the contract groups are admitted in batches.Preparer
06Reconcile. The admitted result is compared with both control totals.Preparer
07Activate schedules. Each Draft recognition schedule is activated.Second person
08Calculate a recognition run for an entity and period, then review it.Preparer
09Commit the reviewed run to balanced Draft journals.Preparer
10Approve the journals.Second person
11Post the approved journals to ledger entries.Preparer

Architecture

A revenue subledger in your Salesforce org

StepFive works from Revenue Cloud records and stores revenue contracts, obligations, schedules and journals in Salesforce.

Source

Revenue Cloud and Billing

Quote and order detail, assets, billing schedules and usage summaries supply the source context.

Calculate

StepFive

Source packages and control totals feed reviewed contracts, SSP allocation and recognition schedules.

Review

Your team

People review recognition runs and independently approve journals before posting.

AI sits above the deterministic engine to explain results, investigate supported discrepancies and prepare calculations for review.

Explore the AI workflow

The Cloud Update

Walk through it with us.

Bring a deal. Bring a revenue question. See how StepFive connects AI assistance, deterministic calculations and the Salesforce Revenue Cloud and Revenue Cloud Billing records behind them.

StepFive is built for ASC 606 and IFRS 15 revenue recognition. Accounting judgments stay with your team.

Product screens and illustrations use sample data. Availability and implementation scope are confirmed during your walkthrough.

Salesforce, Revenue Cloud and Revenue Cloud Billing are trademarks of Salesforce, Inc. StepFive is an independent product of The Cloud Update and is not sponsored or endorsed by Salesforce, Inc.