About Grouped Transactions

When you submit records on the Recognize Revenue page, the resulting revenue recognition transactions are created by group if both of the following are true:

1. The RM Grouped Transactions feature is enabled in your org. For information about how to enable this feature using Feature Console, see Revenue Management Grouped Transactions
2. You have applied grouping to your source data on the Recognize Revenue page. For information about how to do this, see Grouping your Source Data.

For example, let's assume your source data includes records for Company A, Company B, and Company C. When you submit records from all three companies:

• If you have grouped your source data by company, separate transactions are created for Company A, Company B, and Company C. The Grouped By field on each transaction indicates the company that the transaction relates to.
• If you have not grouped your source data, the resulting transactions contain details for all three companies. The Grouped By field on the transaction is blank in these circumstances.

If you apply multiple grouping criteria, the resulting transactions are grouped by the first criteria only. For example, if you group by region, company, and then account, the resulting transactions are grouped by region only.

Transactions are always created asynchronously when grouping is applied.

Notes:

When you recognize revenue or cost against source records via the Recognize All process, transactions are grouped according to the Grouped By field mapping defined on a primary source object's settings record. If you have multiple settings records for the same primary source object, this Grouped By field must be mapped to the same field in all of them.

When you recognize revenue or cost against recognition schedules, transactions are grouped according to the Company field mapping defined on a primary source object's settings record.