Process mapping and BPMN: drawing the payment flow so everyone agrees

Process mapping in payments starts with the as-is process, which is what actually happens today, not what the procedure manual says happens. The analyst maps the as-is by observing the operations team, by reading the incident log, and by tracing a real payment from initiation to settlement. The as-is will always contain workarounds, manual steps, and delays that the manual does not mention, and those are the most important findings, because they are the reason the straight-through processing rate is low. A map that shows only the ideal process is a fiction. BPMN, the Business Process Model and Notation, is the standard for drawing the process. A BPMN diagram has pools for the participants, lanes for the roles, tasks for the work, gateways for the decisions, and events for the start, the end, and the messages. For a payment, the pools are the customer, the bank, the clearing system, and the beneficiary bank. The lanes are the channel, the payment hub, the screening engine, and the operations team. The gateways are the decisions: is the payment valid, is it screened clear, is there sufficient balance, is it within the cut-off. Each gateway must have a path for yes and a path for no, because the no path is the exception. The payment flow as a process has a beginning, a middle, and an end, and the map must show all three. The beginning is initiation: the customer authenticates, enters the payment, and submits it. The middle is processing: validation, screening, routing, enrichment, and the message. The end is settlement and status: the clearing system settles, the beneficiary is credited, the status is reported, and the ledger is reconciled. A map that ends at the message has missed the settlement, the status, and the reconciliation, and the product built from it will fail. Exception paths in BPMN are drawn as separate flows, not as footnotes. When a payment is rejected, the flow goes to a reject handling task, which notifies the customer, records the reason code, and returns the funds. When a payment is returned, the flow goes to a return handling task, which matches the return to the original payment, updates the ledger, and notifies the customer. When a payment is recalled, the flow goes to a recall handling task, which sends the camt.056, waits for the camt.029, and updates the status. Each exception path must have an owner, a deadline, and a measurable outcome. The to-be process is the redesign, and it must be justified by the as-is findings. If the as-is shows that 20 percent of payments need manual intervention because the screening rules are too broad, the to-be must narrow the rules or add a pre-screening step. If the as-is shows that exceptions take three days because the operations team has no status information, the to-be must give them the status. The to-be must be drawn in the same notation as the as-is, so the difference is visible, and the difference must be quantified: the STP rate will rise from 75 percent to 95 percent, or the exception time will fall from three days to four hours. Process mapping is a workshop activity, not a solo activity. The analyst draws the draft, the operations team corrects it, the compliance team adds the controls, and the technology team adds the systems. The map is not finished until every team agrees it is correct, because a map that one team disagrees with will not be followed. The workshop must be facilitated, not lectured, and the analyst must ask the questions that reveal the workarounds, not the questions that confirm the manual. For a business analyst, the process map is judged by whether it can be used to build the product and to train the operations team. The acceptance criteria must include a test where a new operations analyst follows the map to process a payment and an exception, without asking for help. Last reviewed 7 November 2026. Further reading: the Object Management Group, BPMN 2.0 specification; the International Institute of Business Analysis, A Guide to the Business Analysis Body of Knowledge; the EPC SEPA process flows; the SWIFT payment process documentation.