Straight-through processing (STP)

What is straight-through processing?

Straight-through processing, or STP, is the handling of a transaction from entry to result entirely by systems, with no manual step in between. The term grew up in finance, in securities settlement and payments, and has since spread to other transaction-heavy processes.

STP does not mean every transaction is accepted automatically. Systems validate the data, check the rules, and send anything that does not fit down an exception route. Only transactions that meet the conditions stay on the straight, automated path.

The payoff is less rekeying and fewer handovers, which can cut throughput time and data-entry errors, as long as the data and the checks are reliable.

How STP works

A transaction arrives in a machine-readable form, through a message, a file, an API, or a customer channel. The system checks the format, the mandatory fields, the references, and the business rules.

Systems then enrich or match the transaction against customer, account, or product data. Later steps handle authorisation, booking, confirmation, and any reporting. Each step returns a status. The unbroken automated route is the happy path; a missing account number, a sanctions hit, a price mismatch, or a technical error creates an exception and takes the transaction off it.

An audit trail records which checks and system steps ran, so a transaction that went through automatically can still be explained afterwards.

A payments example

A company sends a payment file to its bank. The bank validates the message format, the account details, the currency, and the available authorisations. Valid instructions carry on to further processing and confirmation.

A payment with missing beneficiary information leaves the STP path. Someone, a staff member or the customer, has to complete the data. Once corrected, the instruction can be resubmitted without repeating every earlier step by hand. Standard message formats and consistent reference data raise the share that goes straight through; free text and incomplete master data create more exceptions.

STP versus general automation

A process can contain automated steps and still not be straight-through. If every invoice has to be confirmed by a person after automatic extraction, the handling is automated but not full STP.

STP describes the path of a single transaction with no manual step. Process automation is broader: it also covers hybrid processes, human approvals, and work outside transaction handling. STP is closely related to RPA and intelligent process automation, which are among the tools used to reach it, but the term itself is about the unbroken path, not a specific technology.

Exceptions are part of the design

A high STP rate must not come from removing checks or waving through doubtful transactions. The exception path is what protects quality, compliance, and financial risk.

Classify exceptions by cause: missing data, invalid reference, business rule, external rejection, or technical failure. Give each category an owner and a fix. Avoid making staff rekey the same data across systems: show the original transaction, the failed check, and the possible correction in one place, and record who changed what and why.

Measuring STP

The STP rate is the share of transactions that reach the end point with no manual handling. Define the numerator, the denominator, and the end point precisely, or teams end up comparing different things under the same number.

Track volume, throughput time, wrongly automated cases, and time per exception alongside the rate. A rising STP rate with more corrections afterwards is not an improvement. Look at where the volume of exceptions comes from; the best fix is often at the source, in clearer input or better reference data.