--- title: Roll up expenses and resources in an engagement description: Any audit project has associated costs, budgets, and resources. Roll ups of these costs, budgets, and resources enable the audit manager to view the entire costs and resources in a consolidated manner. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/audit-management/audit-engagement-project-integration.html release: australia product: Audit Management classification: audit-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Audit Management overview, Audit Management, Governance, Risk, and Compliance] --- # Roll up expenses and resources in an engagement Any audit project has associated costs, budgets, and resources. Roll ups of these costs, budgets, and resources enable the audit manager to view the entire costs and resources in a consolidated manner. Starting with the new release, a new plugin called Advanced Audit has been introduced in the Audit Management application. When you activate the Advanced Audit plugin and install the Project Portfolio Management application, you can utilize the project management capabilities to automatically create engagement projects. When an audit plan is created, the audit manager must be able to view the complete expenses and the resources involved in the engagement. Activating the Advanced Audit plugin enables the rollup of the expenses and resources cost of all engagements for a consolidated view. You can also use the advanced planning capabilities to automatically roll up the expenses and resources of each individual engagement to the parent plan of the engagements. ## Project budget rollup After an engagement project is automatically created, if the user has the it\_portfolio\_manager role, the user can create a project budget. When a budget is created, the budget cost gets copied over to the **Budgeted expenses** field of the engagement from the engagement project. When you use the advanced planning capabilities to automatically create a plan, the values in the expenses and the resources field are rolled up. These values come from the associated engagements and the engagement projects. To allocate a project budget, see [Allocate budget to a project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-business-management/allocate-budget-to-project.md). If you allocate a project budget, then the data from the budget cost field gets copied over to the engagement. For example, an engagement has a budget expense of $100. If you create a project budget for the engagement project and enter the budget cost as $200, the engagement budget expense is overwritten with $200. ## Actual expenses and resources rollup If actual effort is updated on an engagement project, then that value gets copied over to actual resources on the engagement. The **Actual resources** and **Actual expenses** both are copied over from the **Actual effort**and **Actual cost** fields. ## Resource plan rollup With Project Portfolio Management, you can add resource plans and cost plans to an engagement. To learn how to create an engagement with advanced planning, see [Create an engagement with advanced planning](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/audit-management/creating-an-engagement-with-advance-planning.md) After you create a resource plan and it is in the **Allocated** state, all the confirmed and allocated hours are summed up in the planned resources. When a resource plan is created, you cannot manually enter hours in the **Planned resources** field on the engagement form. The values get automatically rolled up. To manually enter hours in the **Planned resources** field, delete the resource plan. ## Cost plan rollup You can create an independent cost plan that is not created as a result of a resource plan. In this case, you cannot manually enter values in the **Planned expenses** field on the engagement form. You can still edit the **Planned resources** field.