Supported operation families
Review the Revenue Workbench operation families supported by the Revenue task library and their typical automation uses.
The Revenue task library provides out-of-the-box tasks for Revenue Workbench operations. The available task list can vary by tenant configuration and release.
The following operation families describe the published Revenue Workbench capabilities that these tasks are intended to automate.
| Operation family | Examples of Revenue operations | Typical automation use case |
|---|---|---|
| Revenue contract and line retrieval | Retrieve or query revenue contract, performance obligation, and transaction-line information. | Find contracts that meet an exception or operational condition before taking action. |
| Hold management | Apply or release revenue and transfer holds at supported Revenue levels. | Pause processing for exceptions, or release a hold after review or approval. |
| Revenue release and deferral | Release or defer revenue for eligible performance obligations or lines. | Automate controlled recognition or deferral after a business event. |
| Allocation and contract actions | Run allocation-related actions, open or close contracts, reallocate, switch allocation, or unfreeze eligible contracts. | Coordinate follow-up processing after a contract change or exception resolution. |
| Performance obligation and line updates | Update supported performance obligation attributes or revenue contract line data. | Apply controlled corrections or data updates based on validated business rules. |
| Forecast and analysis support | Generate forecasts or retrieve revenue-related information used by downstream steps. | Start a forecast process and notify an accounting or operations team. |
| File and job processing | Upload supported Revenue data files and retrieve upload or job status. | Orchestrate an inbound file process and branch on completion or error. |
| General ledger and journal operations | Retrieve supported GL batch information or create supported manual journal entries. | Automate downstream accounting operations with appropriate controls. |
| Generic Data Query task | Create and run data queries for Revenue directly inside Workflow. Note: Supported only when Workflow Type = Batch Processing. | Automate the process of fetching data from Revenue contracts, Revenue Contract lines, Revenue Contract Bills, Revenue Schedules, Revenue Staging Transactions, Revenue Bundle Configurations, Revenue Contract Performance Obligations, Revenue Contract Batches, and so on with other Revenue objects that are available for the Data Query. |
| Generic Object Query Task | Declaratively fetch data from Revenue Objects inside Workflow without an SQL query. | Automate the process of iteratively fetching conditional-based Revenue Data from Revenue contracts, Revenue Contract lines, Revenue Contract Bills, Revenue Schedules, Revenue Staging Transactions, Revenue Bundle Configurations, Revenue Contract Performance Obligations, Revenue Contract Batches, and so on with other Revenue objects that are available for the Data Query. |
| Generic Call Out | Call and automate any Revenue API. | Automate different Revenue use-cases such as Transfer Accounting data, File Upload Data ingestion, Revenue Reporting, Revenue Manual Journal Entries, Revenue Jobs and Programs. |
The task library is authoritative for the supported operation, required inputs, optional inputs, output payload, and error behavior.
If an operation is not available in the Revenue task list, use the documented Revenue UI, Revenue APIs, or another supported integration method instead.