Education · Free
STP Labels and Execution Reality
Separate automated order processing from legal roles and execution quality using fictional timestamps, quotes and clearly defined transaction states.
Image credit
Illustrative synchronized timeline. Receipt, routing, filling and confirmation are separate events.
FavAcademy · Original FavAcademy educational illustration; public use authorized
Public summary
An automated order path can still contain credit checks, routing decisions, rejections and reconciliation. A fictional millisecond timeline distinguishes processing stages from legal roles and explains what an STP label leaves unresolved.
Treat STP as a description of processing
Straight-through processing refers to moving information through an operational workflow with less manual intervention. In retail FX marketing, STP is sometimes presented as though it answered every question about an order. It does not tell you, without further documentation, who becomes your counterparty, which price is executable, or what happens when a message is rejected. Those are separate properties of a transaction.
An automated workflow can support different commercial arrangements. A firm can use software to validate an order, apply limits and choose a route while still acting as principal to the customer. Alternatively, documentation may describe an agency arrangement with different obligations. Rather than treating automation as proof of either role, distinguish the message-processing claim from the contractual claim. This is an interpretation framework, not a ranking of provider labels.
Read the fictional timeline as separate events
Imagine an order reaches a system at 10:00:00.000 UTC. A route is selected at 10:00:00.040, a fill arrives at 10:00:00.115, and the customer confirmation is produced at 10:00:00.180. The first interval is 40 milliseconds, the second is 75, and the final interval is 65. Total elapsed time in this invented example is 180 milliseconds.
The illustration uses a timeline rather than a single fast arrow because each event means something different. Receipt is not necessarily acceptance; routing is not a fill; and producing a confirmation is not proof of settlement or final reconciliation. All four timestamps are assumed to share an accurately synchronized clock for the arithmetic. A real comparison needs to establish clock origin and precision before treating an apparent delay as a measured processing interval.
Keep the legal role outside the speed claim
Suppose a fictional policy says that customer contracts are made with Dealer X, while an execution page says orders are processed automatically. Those sentences can coexist without contradiction: one identifies a contracting party and the other describes a workflow. If the customer assumes the second sentence makes a separate venue their direct counterparty, that assumption needs evidence from the actual agreement.
The CFTC’s U.S. consumer guidance warns that an electronic forex interface may connect customers to a dealer rather than an exchange. Its point is relevant when interpreting an impressive-looking platform, but its jurisdictional context matters. A global reader should verify the entity, product and governing terms available to them. Neither a familiar software brand nor the absence of manual handling establishes a universal legal or financial protection.
Identify decisions inside the automated path
Automation still implements choices. A workflow can check account limits, order parameters, quoted quantity and the availability of a route. It can reject an order, accept a partial quantity or return a new price under its documented rules. Calling these steps automatic does not make them neutral by definition; it means rules are executed by a system rather than a person handling each request.
In wholesale FX, the Global FX Committee’s Code discusses standards of good practice while explicitly stating that the Code is not a replacement for regulation. That distinction is useful here: technology, conduct expectations and legal duties are related but separate. A claim about a fast system needs to be read alongside the actual order-handling policy. Do not assume a guarantee simply because the explanation contains several technical acronyms.
Compare equivalent prices before discussing quality
Take two fictional contemporaneous quotes: platform A displays 1.3210 bid and 1.3212 ask, while platform B displays 1.3211 bid and 1.3213 ask. Both show a two-pip spread when one pip is 0.0001. The ask on B is one pip above A’s ask. This numerical comparison does not yet establish which price could actually have been executed for a particular order.
The benchmark must identify the same instrument, side, amount, time and relevant order conditions. A display price for a small quantity is not automatically executable for a larger one. Nor does a rapidly delivered confirmation prove that its price was the best available under an unspecified comparison. Processing speed and price quality should remain distinct observations; otherwise a single attractive timestamp can conceal the absence of a meaningful benchmark.
Leave room for failed and corrected messages
A realistic workflow includes more states than successful receipt and fill. Lost acknowledgments, duplicate messages and later corrections require identification and reconciliation. An order that has no visible confirmation should not simply be assumed absent, and a retry should not be assumed harmless. The customer’s documented procedures for unresolved order status matter precisely when the normal automatic sequence breaks down.
NFA guidance for relevant U.S. forex dealer members addresses slippage settings, customer notice and certain price adjustments. This does not prove that every provider follows the same process. It does demonstrate why the exception rules deserve close reading. The useful question is what a confirmation and its status mean under the applicable policy, rather than whether an advertisement uses the word straight-through.
Conclude at the level of the evidence
Our timeline establishes a hypothetical 180-millisecond path between four defined events. It does not establish a typical latency, a superior execution arrangement or a guarantee about future orders. Our quote comparison establishes displayed differences under stated units; it does not establish a tradable opportunity. Keeping those conclusions narrow prevents operational terminology from becoming an unsupported promise about performance or safety.
A clear STP description should therefore be understood as one part of a larger explanation. Processing stages describe how information travels; agreements establish roles and obligations; execution records allow limited comparisons; and exception policies explain uncertainty. When one of those pieces is missing, retain the gap instead of treating an automated diagram as a substitute. The result is a more accurate reading of the claim, with fewer assumptions attached to the technology.
Continue learning with B-Book Execution: Questions Worth Asking and A-Book Execution: What External Hedging Changes.
Risk disclosure
The timestamps and quotes are fictional. An STP description alone does not establish legal roles, executable prices or protection.