1. Introduction to the Technique
Process mapping (or flowcharting) is a visual audit tool used to document and understand how a business process flows from start to finish. It highlights the steps involved, the people responsible, decision points, and documents or systems used. Internal auditors like Auren at ACME Corp use process maps to identify control points, inefficiencies, redundancies, and risks that may not be obvious in written procedures. It’s especially useful for complex or high-risk processes like procurement, payroll, or production.

2. Suggested Template or Format
To apply process mapping effectively, use the following structure:

• Start/End symbols (oval): Define the beginning and end of the process.

• Activities (rectangles): Show each task or action taken.

• Decision points (diamonds): Indicate where choices are made.

• Connectors (arrows): Indicate the direction and sequence of flow.

• Swimlanes (optional): Divide the process by role or department.

Audit process maps can be hand-drawn during walkthroughs or created using tools like Lucidchart, Visio, or even PowerPoint.

3. Practical Example: Mapping ACME’s Purchase-to-Pay Process
At ACME Corp, CEO Liora has asked internal auditor Auren to assess the effectiveness of the purchase-to-pay (P2P) process, as delays and overpayments have been reported. Auren begins by creating a process map.

• He sets up a walkthrough with Project Manager Aven, the Procurement Officer, the Receiving Clerk, and Accounts Payable.

• As the team describes their roles, Auren maps out each step:

  1. Aven initiates a purchase request (PR) →

  2. Procurement generates a purchase order (PO) →

  3. Vendor ships goods →

  4. Receiving logs goods received →

  5. Accounts Payable matches invoice with PO and receiving report →

  6. Payment is approved and processed.

Auren notices that:

• There is no automated 3-way match; AP manually compares documents.

• PRs and POs are sometimes created after the goods arrive (“backdated”).

• The receiving clerk logs receipts on paper, which introduces delays.

Using the process map, Auren highlights bottlenecks, control weaknesses, and decision points where risks can arise. He recommends introducing automated workflows and digital receipt logs, and presents the map to Liora and Aven for discussion.

Process mapping helped Auren visualize the actual workflow, detect non-compliance with policy, and communicate findings clearly. The visual format made it easier for management to understand problems and agree on changes.

In auditing, a well-structured process map isn’t just a picture—it’s a diagnostic tool that can reveal where the process truly lives, where it breaks, and where it can be improved.