What is business process automation? (And where it stalls)
Business process automation covers a whole process rather than a task: an invoice arriving through to payment sent, or a new hire through to first-day access. That scope is the point. Deloitte found process fragmentation, not technology, was the top barrier to scaling automation, cited by 32% of organizations.
What counts as a "process"
A process at this scope starts at an intake and ends at an outcome. Procure-to-pay runs from a purchase request to a paid invoice. Order-to-cash runs from a customer order to collected cash. Employee onboarding runs from a signed offer to a person with a laptop, a payroll record, and system access. Each one crosses several systems and at least two departments, and each one has a handoff where the work sits in somebody's queue.
That is the line between business process automation and automating a task. A bot that reads an invoice automates a step. BPA owns the route the invoice takes, who approves it, what happens when the amount fails to match the purchase order, and where a person gets pulled back in.
Where it bites
Deloitte surveyed 530 leaders and found 67% had started a robotic process automation program while only 4% ran more than 50 bots. The top barrier was process fragmentation at 32%, ahead of unclear vision and IT readiness at 17% each. In the 2022 follow-up, 62% named integration difficulty and 52% said they could not change the underlying process. Average payback stretched from 16 months to 22.
Read that as a scoping verdict, not a technology one. Automating steps inside a broken process buys a faster broken process. If a process has one owner and one system, a task-level tool is enough and cheaper. Commit to BPA when the process crosses departments, when the delay lives in the handoffs rather than the steps, and when someone senior has the authority to redraw how work is routed.
Last updated: Sep 5, 2026