RightRev

RightRev handles the accounting detail between a contract and the revenue posted to the ledger. Teams configure recognition for each performance obligation, meaning a promised good or service within the contract. Revenue can be recognized at a particular event or spread over a period. Amendments, cancellations, renewals and expansions trigger the relevant reallocations.

From a contract to a revenue schedule

Rules can use bookings, billing, delivery, completed milestones or other defined events. For a contract combining a subscription and an implementation service, the obligations can therefore follow different recognition rules.

The standalone selling price tools calculate and test how revenue is allocated across a bundle. The simulator lets a team examine allocation outcomes before deploying changes. Revenue waterfalls show planned and recognized amounts over time, and variance analysis helps explain differences. Revenue can be deferred or released automatically or manually, with detailed or summarized journal entries sent to the accounting system daily or periodically.

Connecting and buying RightRev

The standalone application accepts contract data from other systems through application programming interfaces, or APIs. The Salesforce-native application runs the revenue workflow within Salesforce. The public integration documentation describes authenticated access and structured responses for developers connecting the service.

RightRev quotes prices using three factors: use-case complexity, advanced features and revenue processed. Bring the contract patterns and required source systems into the discussion, including how amendments and usage events reach the revenue process. A simple subscription and a contract with minimum commitments, overages and changing bundles put different demands on that setup.