What is straight-through processing?
Straight-through processing is a transaction completing from end to end without a person touching it. The term comes from banking operations, where the proportion achieving it is a standing measure. Its complement, the exception rate, is where the operational cost actually lies.
Also called: STP
Why the exception rate is the number worth negotiating
Every banking operations head can state their straight-through rate, which makes it the most useful language available for an automation business case. The trap is that the headline rate says nothing about the work it excludes. A process completing most cases automatically can still occupy the same team it always did, because the remainder are the hard ones and they arrive without context. A proposal committing to a rate without also committing to how exceptions are handled is incomplete.
- The rate is already understood by the people who approve the investment.
- Exceptions consume disproportionate effort per case, so the residue matters.
- A high rate on easy volume can leave the team's workload unchanged.
- Measuring the rate per transaction type exposes where automation stopped.
How straight-through processing works
- The transaction types in scope are defined, with their volumes stated.
- Completion is defined precisely, including what counts as a person touching it.
- Automated handling covers the validation and the enrichment each type requires.
- Cases failing any check are routed to an exception queue with the reason attached.
- The rate is calculated per type rather than across the whole volume.
- Exception reasons are examined so that recurring causes are engineered out.
How straight-through processing is evaluated
The rate is reported per transaction type, because an aggregate figure hides the types that never completed. Examine the following across a full period:
- straight-through rate per transaction type
- exception rate with the reason behind each
- manual effort per exception against per automated case
- proportion of exceptions recurring from the same cause
- rate stability across the month and at peak
Limitations, risks and common failure modes
- The aggregate rate is quoted while one transaction type completes nothing.
- A case touched briefly for approval is counted as fully automatic.
- Exceptions are absorbed by the team without any reason being recorded.
- The rate improves because difficult volume was quietly excluded from scope.
- Nobody measures the effort per exception, so the business case stays unexamined.