SECTIONSUsing Usage Summary as a Source Object
When you enable the Revenue Cloud Connector feature, metadata is created that allows the Usage Summary object to be used as a source object but it is not configured to be included in revenue recognition. This is because the blng__TotalRevenue__c field on Usage Summary does not sum revenue from individual usage records, so it does not provide the Total Revenue amount needed for revenue recognition. As a workaround, the integration configures usage-based revenue to be recognized against invoice lines.
If you want to recognize usage-based revenue against usage summaries instead of against invoice lines, you must do either of the following to overcome the issue with the blng__TotalRevenue__c field:
- Establish a way of populating the blng__TotalRevenue__c field correctly on your usage summary source records.
- Map a different field that does calculate total revenue correctly, to Total Revenue in the settings records for the Usage Summary object.
When you have overcome the Total Revenue issue, you must make the following changes:
- On the Invoice Line object, modify the formula of the Include in Revenue Recognition field so that usage-based revenue is not included.
- On the Usage Summary object, modify the formula of the Include in Revenue Recognition field so that usage-based revenue is included.
For details of the recognition settings and templates that are created for Usage Summary, and the fields that Revenue Management adds to the Usage Summary object, see Metadata Changes when Enabling Revenue Cloud Connector.