AlphaX 500 Robot
117,133.13
StepFive
All five steps. Built for Revenue Cloud.
Revenue recognition built for Salesforce Revenue Cloud and Revenue Cloud Billing
It follows the five-step model of ASC 606 and IFRS 15, from the Revenue Cloud order to the posted journal.
Before StepFive
You know how month end feels.
- Export the orders.
- Export the billing.
- Rebuild every contract in a spreadsheet.
- Tie it back by hand.
- Then check it again.
We built StepFive so recognition starts from the Revenue Cloud records you already trust.
ASC 606 · IFRS 15
All five steps, in your org.
- 01Identify the contractKeyed from the Revenue Cloud order, its assets and contract.
- 02Identify obligationsDistinct goods and services, with your accounting judgments.
- 03Determine the priceThe order's own priced amount, read where it lives.
- 04Allocate the priceRelative standalone selling price, exact to the cent.
- 05Recognize revenueReviewed runs, balanced journals, a second approver.
Built for Revenue Cloud
It runs inside your Salesforce org.
StepFive turns your Revenue Cloud orders into revenue contracts your team reviews and approves.
OrdersOrder productsAssetsAsset actionsBilling schedules
Take an order for a robot, ten software seats and premium support, worth USD 146,760.00. StepFive allocates it on standalone selling price:
RoboControl Cloud · 10 seats
25,761.48
RoboCare Premium Support
3,865.39
Transaction price · USD146,760.00
Tie-out
The totals have to tie.
StepFive matches the sold and billed totals to Revenue Cloud and Revenue Cloud Billing before recognition starts.
If a total is off by a cent, StepFive stops and names it.
Recognition runs
Review the period before anything posts.
Calculate the run, review it contract by contract, and create the journals when you are ready.
Revenue contracts
Each contract gets its own page.
See where each revenue contract stands, and how it got there.
Revenue contract
Robotics Inc. · AlphaX 500 order
ActivePeriod June 2027
Recognized
USD129,477.63
Posted journals
Awaiting posting
USD2,468.90
The June run
Due
USD0.00
Covered by runs
Planned
USD14,813.47
July to December
Billed
USD133,380.00
Revenue Cloud Billing
Obligations
AlphaX 500 Robot ×1117,133.13 of 117,133.13 · 100%
RoboControl Cloud – Standard ×1012,880.74 of 25,761.48 · 50%
RoboCare Premium Support ×11,932.66 of 3,865.39 · 50%
Waterfall · by quarter · USD
| Quarter | Recognized | Billed | Status |
|---|---|---|---|
| Q1 2027 | 124,539.83 | 126,690.00 | Posted |
| Q2 2027 | 7,406.70 | 6,690.00 | 2,468.90 awaiting |
| Q3 2027 | 7,406.70 | 6,690.00 | Planned |
| Q4 2027 | 7,406.77 | 6,690.00 | Planned |
Contract position · USD
Billed through June133,380.00
Recognized through June131,946.53
Contract liability at June 30, 20271,433.47
Controls
Ties to Revenue Cloud BillingPass
Unexplained0.00
Plan equals remainingPass
Every due month has a runPass
June journalsAwaiting posting
Progress by obligation
Each performance obligation shows what is recognized, awaiting posting, due and planned.
Month, quarter or year
The waterfall lays out revenue by period, at the grain you choose.
Billed and recognized
What Revenue Cloud Billing billed sits beside what was recognized, period by period.
Contract asset or liability
The position at each period end, with the arithmetic behind it.
Controls
Review reconciled totals and investigate amounts that do not tie.
Source records
Each obligation traces back to the Revenue Cloud records it came from.
AI
AI explains. Your team stays in control.
Ask about a revenue contract or a recognition run in plain language. Review source lineage and discrepancies using figures calculated by the StepFive engine.
Explains
AI
The assistant explains contract figures and discrepancies, and can prepare a deterministic calculation for review. It does not commit, approve or post revenue.
Calculates
StepFive
Every allocation, schedule and journal is calculated by rules from your Revenue Cloud records. The same records give the same answer, every time.
Approves
Your team
Your team reviews prepared calculations before committing them. A separate approver reviews journals; posting stays with people.
Revenue is never a guess.
Migration
Bring your open contracts with you.
Contracts still in flight in your current system move into the same org as your Revenue Cloud deals.
Revenue you already recognized comes across as an opening baseline, so none of it posts twice.
By design
Numbers you can check.
To the cent
Every allocation adds back exactly to the transaction price.
Tied out
Compare declared totals with native Revenue Cloud records before activation.
2 people
The person who approves a journal can never be the one who prepared it.
In your org
Recognition begins with the Revenue Cloud records your team works from.
The Cloud Update
Walk through it with us.
StepFive is for revenue teams who work from Revenue Cloud records every day. Bring your questions about your orders, ramps, amendments and billing schedules.