![\"Invoice](\"https:\/\/bpmn.visual-paradigm.com\/wp-content\/uploads\/sites\/8\/2026\/09\/img_6a963f83eff33.png\" "\\"Invoice")
<\/p>\n<\/p>\n
In the world of Business Process Model and Notation (BPMN), efficiency is key. When modeling real-world accounting scenarios, you rarely encounter processes that are strictly linear. Often, a single logical step in a high-level diagram actually represents a complex, repetitive cycle of actions. This tutorial explores a classic example of this: the Invoice Reconciliation Process<\/strong>, specifically focusing on how to model a Looped Task<\/strong> using Multi-Instance logic.<\/p>\n Imagine an accounts payable department. An accountant receives an invoice and a corresponding Purchase Order (PO). Their job is to ensure that what the vendor billed matches exactly what was ordered and received.<\/p>\n If the Purchase Order contains 50 distinct line items, the accountant cannot simply “check” the document once. They must iterate through the list, verifying Item 1, then Item 2, and so on, until Item 50 is complete. This is a perfect candidate for a Looped Task<\/strong>.<\/p>\n Let’s break down the diagram shown in the example into its constituent parts to understand the flow from start to finish.<\/p>\n The process begins with a green circle labeled Invoice Received<\/strong>. In BPMN, this is the Start Event. It signifies that the trigger has occurred\u2014the physical or digital document has arrived in the system, and the workflow can now proceed.<\/p>\n The first step is a standard task: Review Invoice & PO<\/strong>. This is an atomic action. It is a single, indivisible step where the user performs a high-level check to ensure the documents are legible and belong to the correct order. Once this is done, the process flows linearly to the next stage.<\/p>\n This is the core of our architecture. The task is labeled Match Line Items<\/strong>, but it features a specific icon: a circle with two arrows forming a loop at the bottom.<\/p>\n The diagram provides a detailed view of what happens inside the loop. This is where the magic of BPMN iteration occurs.<\/p>\n Notice the stack of documents icon in the expanded view. This represents the Collection<\/strong>\u2014the list of data (the 50 items) that the process needs to iterate over. The process engine reads this collection, takes the first item, and passes it to the task.<\/p>\n Inside the loop, the specific action is defined as Match Item<\/strong>. This is a granular sub-task. While the high-level view says “Match Line Items,” the detailed view reveals the engine is actually executing “Match Item” 50 times.<\/p>\n The notation 50x (Multi-Instance Loop)<\/strong> explicitly defines the cardinality of the loop. This configuration ensures that:<\/p>\n Once the loop completes its execution (having matched all 50 items), the process flow exits the loop and proceeds to the final task: Process Payment & Close<\/strong>. Finally, the process hits the End Event, marked by a green double circle, indicating the Reconciliation Complete<\/strong> status.<\/p>\n When building your own BPMN diagrams, remember the distinction between simple tasks and looped tasks:<\/p>\n By correctly applying Multi-Instance loops, you ensure your diagrams remain readable regardless of the complexity of the underlying business rules, telling a clear story of the business narrative.<\/p>\n","protected":false},"excerpt":{"rendered":" Learn to model efficient Invoice Reconciliation loops in BPMN using Multi-Instance logic to handle repetitive line-item verification without breaking workflow standards.<\/p>\n","protected":false},"author":1,"featured_media":9023,"template":"","meta":{"_yoast_wpseo_title":"Mastering BPMN Loops: The Invoice Reconciliation Process Explained","_yoast_wpseo_metadesc":"Learn to model efficient Invoice Reconciliation loops in BPMN using Multi-Instance logic to handle repetitive line-item verification without breaking workflow standards.","inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"source_url":"https:\/\/bpmn.visual-paradigm.com\/mastering-bpmn-activities-a-practical-guide-to-modeling-tasks-and-sub-processes-in-visual-paradigm\/","source_h1_title":"Mastering BPMN Activities: A Practical Guide to Modeling Tasks and Sub-Processes in Visual Paradigm**","fifu_image_url":"","fifu_image_alt":"","_fifu_image_alt":"","fifu_alt":"","_fifu_alt":"","fifu_image_title":"","_fifu_image_title":"","fifu_input_alt":"","vp_image_hash":"925ce0848f171fa112b871f6cf88bad6f84a839fa9bb565ae60d5df5d620ccb1"},"asset-category":[20],"class_list":["post-9022","gallery","type-gallery","status-publish","has-post-thumbnail","hentry","asset-category-bpmn"],"source_url":"https:\/\/bpmn.visual-paradigm.com\/mastering-bpmn-activities-a-practical-guide-to-modeling-tasks-and-sub-processes-in-visual-paradigm\/","source_h1_title":"Mastering BPMN Activities: A Practical Guide to Modeling Tasks and Sub-Processes in Visual Paradigm**","fifu_image_url":"","fifu_image_alt":"","vp_image_hash":"925ce0848f171fa112b871f6cf88bad6f84a839fa9bb565ae60d5df5d620ccb1","yoast_head":"\nUnderstanding the Scenario<\/h2>\n
Deconstructing the Process Flow<\/h2>\n
1. The Start Event<\/h3>\n
2. The Initial Review (Standard Task)<\/h3>\n
3. The Looped Task: “Match Line Items”<\/h3>\n
\n
Deep Dive: Multi-Instance Logic<\/h2>\n
The Collection<\/h3>\n
The Iteration<\/h3>\n
\n
Conclusion: The Final Task<\/h2>\n
Key Takeaways for Modelers<\/h2>\n
\n