Process Mapping Template: An Invoice Workflow with Decisions and Exceptions
A process map shows how work moves from a defined starting event to a defined outcome, including decisions, handoffs and exceptions. A useful template makes the current process discussable before anyone redesigns or automates it.
A process map shows how work moves from a defined starting event to a defined outcome, including decisions, handoffs and exceptions. A useful template makes the current process discussable before anyone redesigns or automates it.
Download the editable invoice step register (CSV), the editable Mermaid diagram source or the blank step template (CSV). The diagram source is a text file for a compatible Mermaid editor; the article's image and table remain readable without that software.
Completed Example: Invoice Receipt to Approval
This illustrative workflow starts when accounts payable receives an invoice and ends when its approval or rejection is recorded. Payment execution is deliberately outside the boundary. The map includes a correction loop because incomplete invoices do not simply disappear from the real process.
| ID | Responsible role | Step or decision | Next state |
|---|---|---|---|
| S1 | Supplier | Submit invoice and required references. | S2: received. |
| S2 | Accounts payable | Check required fields and purchase-order match. | Complete: S4. Incomplete: S3. |
| S3 | Supplier | Correct the stated issue and resubmit. | Return to S2; retain the original receipt record. |
| S4 | Authorized approver | Approve or reject with a reason under the applicable policy. | Either outcome: S5. |
| S5 | Accounts payable | Record outcome and notify the appropriate party. | End: approved or rejected; payment is a separate process. |
A nonresponse at S4 is not approval. An overdue item stays open and follows the documented escalation route. If the invoice is disputed rather than incomplete, define a separate exception with an owner; do not force every possible problem through the same correction arrow.
Set the Boundary and Choose the Right Map
Write a start event, an end event and the unit of work. For this example, the unit is one invoice, not one supplier or one payment batch. State what is excluded. This prevents the workshop from expanding into every purchasing and finance activity.
A simple flowchart emphasizes sequence and decisions. A swimlane map adds responsibility boundaries. A high-level supplier/input/process/output/customer view helps agree scope before detailed mapping. A value-stream analysis adds measures such as processing and waiting time. Choose the view that answers the current question rather than combining every notation into one unreadable chart.
A Gantt chart addresses scheduling and dependencies over time. It is not a replacement for the decision paths in an operating workflow. The invoice can loop through correction repeatedly; that behavior needs a process model even if a project plan separately schedules improvements.
Use a Small, Consistent Symbol Set
ASQ's flowchart guidance describes common symbols and the importance of defining scope and walking through the result. For this template, use a rounded start/end marker, rectangles for activities, a diamond for a decision and labeled arrows for direction. Role labels identify who performs the step.
Name activities with a verb and object, such as “Check purchase-order reference.” Name decisions as answerable questions, such as “Required information complete?” Label outgoing branches. An unlabeled diamond makes the reader infer the condition and can hide a missing path.
The supplied Mermaid source uses role groups and explicit yes/no branches. Its visual arrangement can vary by renderer; the step IDs and transition table are the stable specification. The accessible preview summarizes the same role handoffs rather than pretending that proximity on a diagram creates authority.
Map What Happens, Including Workarounds
- Ask the people performing the work to walk through a recent normal case.
- Record handoffs, waiting states, system entries and decision conditions.
- Walk through an incomplete, rejected and overdue case.
- Compare the diagram with records or screens rather than relying only on the written policy.
- Mark uncertainties and disagreements for verification instead of silently choosing one account.
Separate the current-state map from a proposed future-state map. Combining them can make an unimplemented improvement look like an existing control. Give each version a date, owner and scope. Retain unresolved questions beside the relevant step.
Capture the detail needed to explain a meaningful handoff or failure. Avoid recording every keystroke unless the task is specifically an interface procedure. A high-level map can link to a detailed sub-process for exceptions without making the main flow unusable.
Validate the Map with Three Walkthroughs
| Case | Expected path | Defect to detect |
|---|---|---|
| Complete invoice approved | S1, S2, S4, S5. | Missing record of who approved. |
| Invoice corrected then rejected | S1, S2, S3, S2, S4, S5. | Lost original receipt time or missing rejection reason. |
| Approver unavailable | S4 remains open; defined delegation or escalation applies. | Automatic approval implied by silence or an unowned waiting state. |
Check every branch for a destination, every activity for an owner and every end state for an observable record. A map can be visually tidy while leaving a failed case stranded. Ask a colleague who was not in the workshop to trace the examples from the diagram and table.
Use the Map to Select the Next Analysis
The map identifies where to collect evidence; it does not prove which step is slowest or most expensive. Add timestamps and queue observations when the next question is a bottleneck. Add a decision-rights record when the problem is disputed authority. Add a data-ownership contract when systems disagree about the invoice state.
Do not automate the flow until exception ownership and approval conditions are clear. Faster routing can amplify an unclear process. The completed template should leave the team with one agreed description of how work moves, which paths remain uncertain and what evidence is needed to improve it.