New on FinoLib · Volume III: Finance Encyclopedia
I have just published a new article on FinoLib, my free finance education library: Straight-Through Processing (STP) Rate and Matching Tolerance. It is part of Volume III: Finance Encyclopedia. Below is a summary of the topic in plain, expert language, so you can follow the idea even before you open the full article.
The idea in plain words
The STP rate measures how many items match automatically, without anyone touching them. But it depends on how generous the tolerance is, so it measures throughput, not accuracy. Set tolerances on amounts only, cap what they absorb in total, and watch warning indicators such as aged breaks and forced matches. And remember that CLS is payment-versus-payment settlement, not a central counterparty.
Key points
■Identifiers and quantities match exactly; tolerances apply only to amount fields.
■In the worked example, a $5 tolerance beats a $50 one while a break costs less than $10 to investigate.
■A $1 per-item tolerance with no aggregate cap can hide $2,475,000 a year of systematic leakage.
■Maker-checker approval should apply to every manual or forced match.
A closer look
The single most-watched reconciliation KPI is the Straight-Through Processing (STP) rate: the percentage of items that match automatically between the two data sources without any manual intervention. A tolerance is a pre-set acceptable variance (for instance, $1 per item, or 0.01% of the transaction value) below which a difference is accepted automatically instead of being raised as a break, so that people do not spend their day on rounding. Tolerances belong on amount fields only. Identifiers (the security, the account, the counterparty, the settlement date) and quantities match exactly or not at all, because a share that is “nearly” there is not there.
Two-way matching compares exactly two data sources (an internal record against a custodian’s, for instance). Three-way matching adds a third, independent source, such as a counterparty confirmation or an affirmed trade from a central matching service. The gain is attribution: when two sources agree and the third differs, the odd one out is usually wrong.
A worked example
Worked Example — Compare the Scenarios: Where Should the Tolerance Sit?
Take the 50,000 items above: at zero tolerance 48,500 match and 1,500 differ, the 97% STP rate. Illustrative assumptions: 800 differ by under $1 (rounding); 400 by $1 to $5, of which 300 are self-clearing timing items and 100 come from a misconfigured fee that undercharges clients $3.20 each; 200 by $5 to $50, half noise and half one-off errors averaging $20, recoverable if found; 100 by more than $50, worked under every policy. Each break routed to a person costs c = $8 (10 minutes at a $48 loaded hourly cost).
Under the hood
Under the Hood: What a Matching Engine Actually Does
Reconciliation platforms (Volume I names SmartStream’s TLM, for Transaction Lifecycle Management, Broadridge, Gresham and Trintech) load both feeds, normalize formats and match in passes, strictest first: exact keys (security, account, quantity, dates), then tolerances on amounts, then shape mismatches such as one-to-many (one custodian cash movement settling 40 client trades in bulk). Whatever no rule pairs becomes a break in an exception queue. People may then match items manually or force-match them, which is where control weakens, so mature functions apply maker-checker to every manual or forced match: one person proposes, a second independent person approves, and the system records both.
Decision rule
Put a band of differences inside tolerance only if investigating it costs more per break than the real errors it contains per break. In the worked example the $5-to-$50 band holds $2,000 of real errors across 200 breaks, $10 a break, so it is worth working while a break costs less than $10.
The costliest mistake
A per-item tolerance with no aggregate cap. A feed error shaves $0.99 off 10,000 items a day under a $1 tolerance: every item matches, the STP rate looks perfect and no break is raised. Leakage = 10,000 × $0.99 = $9,900 a day; over 250 business days, 9,900 × 250 = $2,475,000 a year, visible only to the “value accepted within tolerance” KRI. Avoid it by capping what a tolerance may absorb per account per day and raising a break, with maker-checker on any override, when the cap is hit.
Recap
The STP rate measures automatic matching and rises whenever tolerances loosen, so it must be read alongside the tolerance policy and KRIs such as aged breaks, forced matches, value accepted within tolerance and reconciliations not performed. Tolerances belong on amounts only, with an aggregate cap, and should sit where investigation cost per break equals the real error it finds. CLS is payment-versus-payment FX settlement, not a central counterparty.
What the full article covers
The full article includes worked examples, a look under the hood at the mechanics, a clear decision rule, the one mistake that costs people the most, a recap, a reveal-on-click quiz and the official sources behind every figure.
Volume III: Finance Encyclopedia
Read the full article on FinoLib
The complete article, Straight-Through Processing (STP) Rate and Matching Tolerance, with every worked example, diagram, quiz and source, is free to read in Volume III, Finance Encyclopedia on finolib.com.
Explore the Finance Education Series: Vol. II — Capital Markets · Vol. I — Global Economy · Vol. III — Finance Encyclopedia · Vol. IV — Finance Careers · Vol. V — Personal Finance