Create Engagement from Annual Plan

Convert an approved annual plan item into a detailed audit engagement.

Use this form to define the engagement header information based on an approved annual audit plan item. The planning workspace will be available after this step.

Origin: Annual Audit Plan Object Type: Process

Linked Annual Plan Item

Plan Year

2026

AAP Item Code

AAP-2026-012

Auditable Process

FIN – Order to Cash

Object Type

Process

Risk Rating / Priority

High Priority A

Planned Period

Q2 2026

Planned Effort

30 man-days

This information is read-only and comes from the approved Annual Audit Plan.

Engagement Information

Engagement Title*

Engagement Type

Object Type

Process

Engagement Code

Process Owner

Primary Unit / Function

Audited Processes in This Engagement

Use this list to include multiple related processes or locations under a single engagement (for example, the same process across several branches).

Process Name	Unit / Owner	Priority / Risk
FIN – Order to Cash	Finance Operations – Head Office	High
FIN – Order to Cash (Branch Bandung 01)	Branch Bandung 01	Medium
FIN – Order to Cash (Branch Surabaya 02)	Branch Surabaya 02	Medium

In a real implementation, processes would be selected from the process catalog. This section allows you to model multi-object coverage under a single engagement.

Timing & Location

Planned Period (from AAP)

Target Fieldwork Start Date

Target Fieldwork End Date

Main Location

Team Assignment

Lead Auditor*

Team Members

Reviewer / Audit Manager

High-Level Objective & Scope

Objectives Refine or extend the objectives defined in the Annual Audit Plan. If this engagement covers multiple processes or locations, explain how they relate and how they will be covered under one project.

High-Level Scope Detailed planning will be done in the Planning workspace.

Governance & History

This engagement is based on an approved Annual Audit Plan item.

Approval trail for the AAP item is maintained in the Annual Plan module.
Any future changes to engagement status (e.g., cancellation, significant scope change) should be logged in the engagement history page.

Fields marked with * are required.