Number |
Unique identification number of the engagement. |
Name |
Name of the engagement. |
Type |
Type of engagement. The choices are:
- None
- Internal Audit
- External Audit
- SOX Audit
- IT Audit
- Financial Audit
- Compliance Audit
- Certification Audit
- Regulatory Audit
- Operational Audit
- Continuous Audit
- Vendor Audit
- Customer Audit
- Store Audit
- Quality Audit
- Project Audit
Note: For information on the types of audits, see Audit types
|
Assigned to |
User assigned to the engagement. |
State |
- Scope
- Validate
- Fieldwork
- Awaiting Approval
- Follow Up
- Closed Complete
- Closed Incomplete
|
Percent complete |
Number that represents the percentage of the engagement
that is complete. |
Auditors |
Auditors assigned to the engagement. |
Approvers |
Approvers assigned to the engagement. |
Description |
General description of the engagement. |
Objectives |
Stated objectives of the engagement. |
Schedule |
Engagement planned start |
Estimated start date of the engagement. |
Engagement starts |
Choice to automatically determine the start date of the
engagement. The choices are: |
Engagement actual start |
Actual date the engagement begins. |
Engagement planned end |
Estimated end date of the engagement. |
Engagement ends |
Choice to automatically determine the start date of the
engagement. The choices are: |
Engagement actual end |
Actual date the engagement ends. |
Fieldwork planned start |
Estimated start date of the fieldwork. |
Fieldwork planned end |
Planned end date that was originally set in the
engagement. Note: This field sets the value as one day plus
the planned start date for fieldwork by
default. |
Fieldwork planned duration |
Number of days and hours planned for fieldwork. The
duration and planned start date of fieldwork are used to
calculate the planned end date. If audit tasks are defined,
this field is populated with the longest planned duration
from the audit tasks. |
Fieldwork actual start |
Actual start date of the fieldwork. If audit tasks are
defined, this field is populated with the earliest actual
start date from the audit tasks. |
Fieldwork actual end |
Actual end date of the fieldwork. If audit tasks are
defined, this field is populated with the latest actual end
date from the audit tasks. |
Fieldwork actual duration |
Duration of fieldwork start date and end date. |
Results |
Result |
- Satisfactory
- Adequate
- Inadequate
|
Opinion |
Justification for the selected result. |
Report |
Knowledge base |
Knowledge base to use to select the template. |
Report template |
Template to be used to generate the knowledge base
article reporting the engagement results. |
KB article |
Recently generated knowledge base article containing the
engagement results. |
Activity |
Additional comments |
Customer-viewable comments. |
Work notes |
Comments that are viewable by the administrator and audit
manager. |
Plan
Details |
Parent plan |
Plan to associate the engagement with. |
Expenses
and Resources |
Budgeted expenses |
Budgeted expenses for the engagement. |
Planned expenses |
Estimated expenses for the engagement. If the cost plan
is defined, this field automatically displays the estimated
expenses. |
Remaining budgeted expenses |
Difference between Budgeted
expenses and Planned
expenses. This field gets automatically
populated. |
Actual expenses |
Actual expenses incurred. If timecards are defined, this
field gets automatically populated. |
Budgeted resources |
Budgeted resources, in hours, for the engagement. |
Planned resources |
Estimated resources, in hours, for the engagement. If
resource plans are defined, this field is automatically
populated. |
Actual resources |
Actual resources, in hours, for the engagement. If
timecards are defined, this field gets automatically
populated. |
Project
Details |
Project |
Automatically created engagement project. This field is
populated when you click Validate and
Plan. Note: This field also gets populated
when you click Enable Advanced
Planning on the engagement, in the
Validate or
Fieldwork state. It also gets
populated if it is already linked to a plan with
advanced planning capabilities if the user has the
required roles and the engagement is in the correct
state. |