Definition
A broader concept than workflow automation; automating an end-to-end business process, such as order-to-cash or hire-to-retire, across multiple systems and multiple people. Where workflow automation handles a single chain of steps, BPA covers the whole path a piece of work travels from start to finish.
What it looks like in practice
At a moving company, everything between a signed estimate and a cleared payment is treated as one process. The estimate is accepted online, which creates the job in dispatch, blocks a truck and crew on the calendar, and triggers a deposit request. The day before the move, the coordinator's checklist and the customer's confirmation both go out from the same record. When the crew closes the job on their tablet, final weight and hours flow into invoicing with nobody retyping them, and an unpaid balance moves to collections after a set number of days. Sales, dispatch, crew, and bookkeeping share one process instead of four.
Why it matters
BPA becomes relevant when the pain is no longer one task but an entire process that crosses people and software, everything from a signed order to a paid invoice. Done well, it removes the bottleneck where work waits on one specific person and cuts the errors that creep in whenever data gets retyped between systems. The catch is scope. Automating a process nobody has actually mapped just makes an existing mess run faster and harder to unpick, so the honest first step is writing down who does what today, in order, and fixing the obvious breaks before any software touches it.