Enabling Revenue Cloud Connector

This Feature Console page provides an automated way to configure a standard setup between Revenue Management and Salesforce Revenue Cloud. When you enable the feature, fields are added to several Salesforce objects, then settings and templates are created so that you can recognize revenue and amortize costs against Salesforce orders. The integration creates settings and templates that allow you to run revenue recognition directly against your source objects (for example, to comply with ASC 605) or using revenue contracts (for example, to comply with ASC 606 and IFRS 15). See Metadata Changes when Enabling Revenue Cloud Connector for full details.

Enabling the feature also creates the Revenue Management on SF Revenue Cloud permission set which gives access to the fields that are created.

Notes:

Once this feature is enabled you cannot revert feature steps that add fields to objects, and create settings and templates. If you want to remove the feature for any reason, you must manually remove the fields, settings and templates that are created.

If the Actual vs Forecast feature is enabled in your org you must disable it (via the Revenue Management Settings custom setting) otherwise an error will be displayed when you attempt to perform feature step 1. This is because the settings records created by the Revenue Cloud Connector feature do not include mappings for forecasts and actual vs forecast.

You can only enable this feature if your user profile has:

• The Customize Application permission enabled.
• The Modify Metadata permission enabled.
• Read, Create, Edit, Delete permissions for the following Salesforce objects: Order, Order Item, Usage Summary, Invoice, Invoice Line, Credit Note, Credit Note Line, Product2, Revenue Treatment.
• Read, Create, Edit, Delete permissions for the following Revenue Management objects: Settings, Template, Revenue Recognition Transaction, Revenue Recognition Transaction Line, Performance Obligation Line Item.

To enable the Revenue Cloud Connector feature, work through the steps in the order shown on screen. Most of the steps are automatic but there are some steps that you must complete manually.

1. For each automatic step, click Perform. When each step has completed, its Status changes from "Not Done" to "Done".
   
   Note: When performing feature step 4, if you get the error message:
   "In field: excludeButtons, no such standard action:PrepareForBilling"
   you must manually add the fields listed in feature step 4 to the Order Product page layout. You will then be able to continue with feature step 5.
2. For feature step 19, follow the instructions in Configuring Salesforce Flows to Populate Template and GLA Fields on Source Records to have revenue recognition templates and GLAs assigned automatically to your source records. Click Mark as Done when you have completed the configuration.
3. For feature step 20, follow the instructions in Configuring a Salesforce Flow to Calculate SSP on Source Records if you intend recognizing revenue using revenue contracts. Click Mark as Done when you have completed the configuration.

When you have completed all the steps, use the Status slider in the Feature section to mark the feature as enabled.

If you intend recognizing revenue using revenue contracts, you must also enable the Create Setup for Using Revenue Contracts feature.

Next Steps

• Assign the Revenue Management on SF Revenue Cloud permission set to users needing to view and edit the fields that are created by this feature, and to users creating Salesforce flows to populate template, GLA, and SSP values. The fields are listed in Metadata Changes when Enabling Revenue Cloud Connector. Note that this permission set does not give access to the Salesforce objects. You must manage object access in your own permission sets.
• Ensure that users have the appropriate permissions before they attempt to run revenue recognition. A full list of permission sets is provided in the Revenue Management Technical Pack, available from the FinancialForce Community.
• Create recognition years and periods. For more information, see About Recognition Years and Periods.
• If you have not followed the instructions in Configuring Salesforce Flows to Populate Template and GLA Fields on Source Records you must manually populate the revenue recognition template and GLA fields on your source records: order items, invoice lines, credit note lines, and usage summaries (if used).
• Make sure that the Legal Entity field on orders will be populated. This is necessary for Revenue Management to group its transaction lines correctly so that all the lines on a revenue recognition transaction are for the same legal entity. You can do this manually, or automatically via a Salesforce flow or process builder. See the Salesforce Help for information about configuring flows and process builders. (This is in addition to populating the Legal Entity field on your order products which is required by Salesforce.)
• For advice about how to complete your Salesforce revenue recognition rules and revenue recognition treatments, see Completing Salesforce Revenue Recognition Rules and Treatments.