Last month, the purchasing manager at a mid-sized textile company faced a familiar problem: a single raw material order required sign-off from three different managers, and those approvals were taking anywhere from five to ten business days. By the time the paperwork cleared, the supplier had either changed the price or run out of stock. The company was losing money and production time simply because of a slow internal process. This is precisely where business process management — BPM — becomes relevant. But in a crisis, trying to fix everything at once is a mistake that strains both the budget and the organization. Choosing the right starting point determines whether the project delivers real value or becomes another stalled initiative.
BPM is a management approach for defining, analyzing, and systematically improving the workflows inside an organization. Software tools support this approach, but BPM is fundamentally not a technology project — it is a process design and change management effort. In difficult economic conditions, companies start paying more attention to BPM because cash pressure and cost constraints make the cost of inefficient processes impossible to ignore. Yet the question of where to start is rarely examined carefully enough. Project teams often gravitate toward the most complex or most complained-about process, when the right criterion in a crisis is different: which process can produce a measurable cash impact in the shortest time?
The answer to that question almost always points to three areas: purchase approval workflows, invoice processing, and collections management. These three areas are operationally and financially linked — a delay in one directly affects the others. Slow purchase approvals lead to supplier price changes or emergency order premiums. Errors and delays in invoice processing damage supplier relationships and stretch accounting close cycles. Weak collections discipline cuts directly into cash flow; the older a receivable gets, the harder it is to collect.
Redesigning the purchase approval process with BPM is among the fastest ways to produce visible results. Clarifying approval steps and authority limits, assigning workflow rules to determine who approves which spending threshold, and making e-mail-routed approval requests trackable — these are improvements that can be implemented even without specialized software. When a BPM tool is added, approval cycle times become measurable: which step is causing delays, which approver is holding things up, and how long each stage actually takes. That visibility gives managers the information they need to act.
Invoice processing offers improvement opportunities on both the supplier and customer sides of the business. For most small and mid-sized companies, the flow from receiving a supplier invoice to recording it in the accounting system and getting it approved for payment still runs largely on paper and e-mail. Mapping this flow with a BPM approach — defining who is responsible for each step and how long it should take — surfaces the bottlenecks. When a workflow tool works alongside the existing accounting software, invoice approval cycles shorten, payment errors decrease, and supplier relationships stabilize. In a crisis, maintaining supplier trust translates into long-term cost advantages that are hard to quantify but very real.
Collections management has the most direct effect on cash flow of the three areas. Tracking customer receivables, deciding who follows up on overdue invoices and how often, and determining at what point an escalation goes to senior management — in most small businesses, these decisions are left to individual initiative rather than written rules. Formalizing the collections process through BPM means setting follow-up schedules for each customer segment, assigning clear ownership, and making aging receivables visible to the right people at the right time. Practitioners who have worked through this kind of restructuring consistently report that the main benefit is not any single recovered invoice but the predictability that comes from a defined process.
A few practical criteria matter when starting a BPM project in a crisis environment. Keep the scope narrow: one process, one clearly defined problem, one measurable target. Trying to improve three processes simultaneously exhausts both the project team and the end users. Second, check what workflow features the existing ERP or accounting software already provides — in many cases, unused modules can be activated before any additional tool is purchased. Third, involve the process owners from the beginning. The most common reason BPM projects fail is not technical; it is organizational resistance. Speed matters in a crisis, but cutting corners on the process design creates larger problems downstream. A BPM initiative that starts from the right process, stays narrow in scope, and sets measurable targets delivers both short-term cash impact and a foundation for gradually improving process maturity across the organization.
This article was originally written in Turkish by Gökhan MERCANOĞLU on February 18, 2008 and has been automatically translated into English and other languages using machine translation.