These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Audit Management
- Who it's for
- Multi-entity finance teams
Multi-entity finance teams
A finance assurance team working across subsidiaries often examines similar controls in different organizations. Audit Management links each finding to its organization and business unit. Engagements and risk workpapers carry their own organization references. The Audit Manager can inspect the entity context before discussing a finding with the team responsible for its response.
How Audit Management is set up for you
Directory preparation
Admin checks organization names and audited entity references before the team imports engagements. Similar names require a deliberate check so the correct entity receives the work.
Control context
Control descriptions and account classifications help Auditors identify the control under examination. Supporting workpaper lines connect a risk record to the control discussed in its memo.
Response ownership
The Control Owner reads the business unit and finding context before preparing corrective evidence. The Audit Manager checks the same references during release review.
A finance assurance team working across subsidiaries often examines similar controls in different organizations. Audit Management links each finding to its organization and business unit. Engagements and risk workpapers carry their own organization references. The Audit Manager can inspect the entity context before discussing a finding with the team responsible for its response.
Start with a recurring access control examined within a subsidiary. Prepare the organization directory, identify the audited entity and define the assessment period. Use the engagement memo to explain which local process the Auditor will examine. Keep supporting finance evidence in the agreed source system and set up access to it during the pilot.
Include a second organization with a similar business unit name in the rehearsal. Ask the Auditor to explain the references on a finding and show the engagement context used for the test. This exposes naming ambiguities before a larger import spreads them across the audit portfolio.
Review the resulting management response and follow-up evidence with the Audit Manager. Agree how organization scope will be configured for each participant, and test the evidence links using the reviewer's normal access. Follow [assessment and engagement preparation](/audit-management/processes/assessment-to-engagement) before expanding the operating cycle to other entities.
Features to start with
Roles on the team
- Admin
- Maintains access configuration and the organization directories used during audit setup.
- Auditor
- Prepares assessment scopes, engagement tests and findings with linked evidence.
- Audit Manager
- Reviews finding support and authorizes corrective response release within the agreed audit scope.
- Control Owner
- Maintains control descriptions and prepares corrective responses for review.
- Chief Audit Executive
- Reads assessment coverage, finding decisions and unresolved operation results across the agreed portfolio.
Set up Audit Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.