Creating a BPMN Model Step by Step: Invoice Approval in Practice

Disorganized paper-based invoice handling on the left; on the right, a tidy workstation with a schematic diagram of a possible digital process.

Key takeaway: A good invoice approval BPMN model shows who does what, under what conditions the case moves forward, and what happens when exceptions arise. In this example, we build a model from the business requirement, covering invoice receipt through to approval or closure. We will not execute a process here: the goal is consistent operational logic that can be reviewed and agreed with business stakeholders.

Within the BPMN 2.0 in Practice topic, this BPMN invoice approval example connects knowledge of the notation with actual modeling. The most important question is not how to position the shapes, but how to make responsibilities and decision rules clear.

Practical focus: This series is not a complete BPMN 2.0 reference manual—the official notation set is far broader, and here we focus on the most essential elements and practical workflows used in everyday operations.

1. The Business Requirement and Process Boundaries

Let us start with this requirement: “An incoming supplier invoice may only be passed on for payment once its data has been verified, delivery or performance has been confirmed, and the required management approval has been obtained.” This is not yet a process description. We need to clarify the entry condition, participants, decision threshold and possible outcomes.

In our example, the process starts when the invoice is received. Payment execution belongs to a separate process. Management approval depends on a value threshold; the specific amount is determined by the organization’s policy, not chosen by the modeler.

Modeling questionRule applied in this example
What triggers the process?Receipt of the supplier invoice.
Who performs the checks?Finance and the business representative responsible for confirming delivery or performance.
When is a management decision required?Above the value threshold specified in the policy.
What happens when information is incomplete?A request for missing information is initiated, with a defined response deadline.
What is the successful outcome?The approved invoice is passed to the payment process.
What other closure outcomes are possible?Closure due to duplication, rejection or failure to provide the missing information.

Document the assumptions as well: for example, one process instance handles one invoice, and the currency used for comparison against the value threshold is predefined. Without these assumptions, the same diagram can be interpreted in different ways.

An unlabeled schematic data graphic showing a one-to-one mapping of invoices to process instances, with columns aligned to a common baseline.

2. Defining Participants and BPMN Elements

We represent the company’s process in a single pool, with three lanes within it: finance, the business representative confirming delivery or performance, and the management approver. A lane organizes responsibilities; it does not, by itself, represent a task or a permission setting. The supplier is a separate pool whose internal operations do not need to be detailed.

  • Event: indicates that something happens. Here, receipt of the invoice can be a message start event, while closure of the approved case can be an end event.
  • Activity: represents work to be performed, such as “Check invoice data.” Name the action explicitly.
  • Gateway: controls the branching or merging of paths. It does not perform checks or grant approval itself.
  • Lane: shows which role is responsible for a given activity.

Within the company pool, including between lanes, connections use sequence flow connects the steps. Communication between the supplier and the company is represented by message flow. Sequence flow cannot cross from one pool to another.

3. Building the invoice approval model in ten steps

  1. Place the start event. Connect the message flow from the supplier to the “Invoice received” message start event. This also makes the trigger visible.
  2. Register the invoice. Include the “Register invoice” task in the finance lane. The invoice identifier will also be needed later for reconciliation.
  3. Check for duplicates. The “Check for duplicates” task is followed by an exclusive gateway. Finance checks whether the same supplier invoice appears in another, previously registered case. A duplicate invoice follows a separate closure path, while a new invoice proceeds.
  4. Check formal completeness. After “Check invoice data”, the “Data complete?” decision opens two paths. If information is missing, we request it; if the data is complete, we proceed to substantive checks.
  5. Determine whether management approval is required. Record whether a management decision is required based on the amount threshold rule. Clarify whether to use the net or gross amount and how to handle an amount equal to the threshold.
  6. Start the independent checks. Use a parallel gateway to separate the financial check from the business verification of delivery or service completion. Our example assumes these can be performed without each other’s results.
  7. Wait for both results. Each task should record a positive or negative result, and the branches should then converge at a parallel join gateway. An exclusive gateway then checks whether both checks passed.
  8. Handle threshold-based approval. After successful checks, management approval is either required or skipped according to the predefined rule. After the management task, a separate decision point evaluates the approval outcome.
  9. Merge the rejection paths. A failed check or management rejection should lead to “Record reason for rejection”, followed by notification of the supplier. An exclusive merge can connect the mutually exclusive branches to a shared task.
  10. Name the end states. The successful path should include a “Forward for payment” task, followed by an “Approved and forwarded” end event. Give each remaining outcome its own descriptive name.
A BPMN 2.0 invoice approval diagram with a Supplier pool and Finance, Performance Verifier and Manager lanes: duplicate and data checks, requests for missing information with an event-based gateway (missing information received or deadline expired), parallel financial checks and performance verification with a synchronizing join, managerial approval based on a value threshold, and a shared rejection branch with reason recording and supplier notification.

The invoice, confirmation of delivery or service completion, and decision rationale can also be represented as data objects. These show the information used or created; they do not replace control flow connections.

A single limestone bridge with a fine red line along its walkway; the supporting structure and the path evoke the distinct roles of data and control.

4. Exception paths: which gateway should you use, and when?

Exclusive gateway: only one path continues

An exclusive gateway makes a selection based on existing data. Examples include “Data complete?” and “Management approval required?”. Outgoing conditions should be clear, mutually exclusive and cover all possible cases. The approver’s decision must first be made in a task.

Parallel gateway: every branch starts

A parallel split does not evaluate conditions. In our example, both checks run, and both return to the join gateway. If one branch exited immediately with a negative result while the other reached the join, the model could become blocked. Immediate interruption must be designed separately.

Event-based gateway: the next event determines the path

After sending a request for missing information, we wait for two possible events: the supplier’s response arrives, or the deadline expires. After the event-based gateway, we place an intermediate message catch event and an intermediate timer event. Whichever occurs first determines which branch continues.

If a response arrives, we update the data and return to the formal check. If the deadline expires, this example proceeds to a notification and the “Closed without missing information supplied” end state. Handling late responses and limiting repeated requests for missing information should be clarified in a separate business rule.

A finance employee checks supplementary documents received for an invoice while a colleague points to the desk calendar.

5. Checklist: ten common modeling mistakes

Review the first version together with a finance team member and an approver. The following list identifies modeling errors; it does not replace technical execution testing.

  1. The start condition is not precisely named.
  2. The task name does not indicate what work needs to be done.
  3. Clear responsibilities cannot be assigned to the lanes.
  4. Message flow connects lanes within the company.
  5. Sequence flow crosses a pool boundary.
  6. The conditions for exclusive branches overlap.
  7. One of the decision outcomes has no continuation.
  8. The parallel join waits for a branch that cannot arrive.
  9. The wait for missing information has no time limit.
  10. The end events do not indicate the outcome of the case.

Try walking through a low-value invoice, one requiring managerial approval, one with missing information, a duplicate and a rejected invoice. In every case, it should be possible to answer: who is working on it now, what are we waiting for, and how can the case end?

6. How does this relate to the broader topic of BPMN?

Five specialist topics complement this example. They help you progress from understanding the notation to preparing for implementation:

  • BPMN 2.0 elements explained with examples: correct use of events, activities, gateways and lanes.
  • Exclusive, parallel and event-based gateways: when should you use each? Distinguishing between data-based decisions, concurrent work and waiting for events.
  • The 10 most common BPMN modeling mistakes: a detailed review of the checkpoints above.
  • BPMN vs. flowcharts vs. UML activity diagrams: choosing the right representation. BPMN is particularly useful for illustrating message exchanges between participants and event handling.
  • How does a BPMN diagram become an executable process? Defining the data model, task assignments, permissions, integrations and technical tests.

A correct diagram is not automatically an executable process. The current model documents a business agreement; the next step is to verify the settings required for execution and the elements supported by the target system.

A process outline with swimlanes on a dark technical blueprint, separated by a gap from a technical preparation area, with red verification marks.

7. Summary and next steps

A usable invoice approval model shows not only the normal path, but also how missing information is supplied, how rejection is handled and how waiting ends. Its quality depends primarily on clear rules, defined responsibilities and consistent paths.

Would you like to review your own invoice approval process in this way? Consult xFLOWer experts: start with your current operations and a few real exception cases, then use these to define the requirements for the model and subsequent digitalization.

This article is part of our comprehensive guide: BPMN 2.0 in Practice: A Complete Guide from Modeling to a Working Process

xFLOWer.ai

Design the process behind this article – for free!

AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.

Contact us

Let's talk about your processes

Tell us briefly which process you'd like to automate – we'll get back to you within 1 business day.