Fails-to-deliver, often shortened to FTDs, are settlement failures: a trade has been executed, but the seller does not deliver the securities by the required settlement date. This is a core market-structure concept because it sits at the point where trading, borrowing, clearing, custody, and regulation all meet. Not every fails-to-deliver event is abusive or manipulative, but persistent or unexplained fails can matter for liquidity, compliance, and risk control.

1. Term Overview

• Official Term: Fails-to-deliver
• Common Synonyms: FTDs, fail to deliver, delivery fail, settlement fail, short delivery
• Alternate Spellings / Variants: Fails-to-deliver, fails to deliver, fail-to-deliver, fail to deliver
• Domain / Subdomain: Markets / Market Structure and Trading
• One-line definition: A fails-to-deliver occurs when the seller in a securities trade does not deliver the securities to the buyer by the settlement deadline.
• Plain-English definition: The trade happened, but the shares or bonds did not show up on time.
• Why this term matters: It helps explain settlement problems, short-selling controls, liquidity stress, operational breakdowns, and some forms of regulatory surveillance.

2. Core Meaning

What it is

A fails-to-deliver is a post-trade settlement problem. After a trade is matched, the market expects two things to happen on settlement date:

1. cash moves from buyer to seller, and
2. securities move from seller to buyer.

If the security does not arrive on time, that is a fail-to-deliver from the seller’s side. On the buyer’s side, the mirror image is often called a fail-to-receive.

Why it exists

Modern securities markets are fast and mostly electronic, but settlement still depends on many moving parts:

• correct trade matching
• available inventory
• stock borrow availability for short sales
• proper settlement instructions
• clearing and custody systems
• corporate action adjustments
• netting at clearing agencies

A failure in any of these can lead to an FTD.

What problem it solves

The term itself does not solve a problem. Rather, it gives markets a standard way to identify, record, measure, and manage unsettled delivery obligations. Without that category, firms could not monitor operational risk, regulators could not track chronic settlement issues, and market participants could not separate routine exceptions from serious problems.

Who uses it

• broker-dealers
• clearing firms
• custodians
• prime brokers
• market makers
• hedge funds
• regulators and exchanges
• issuers and investor-relations teams
• market-structure analysts and researchers

Where it appears in practice

Fails-to-deliver appear most often in:

• listed equities
• OTC equities
• ETFs
• corporate bonds
• sovereign bonds
• repo and securities financing markets
• securities lending operations
• cross-border custody and depository settlement

3. Detailed Definition

Formal definition

A fails-to-deliver is the non-delivery of securities by the seller or delivering participant by the contractual or regulatory settlement date for a completed trade.

Technical definition

Technically, an FTD is an open delivery obligation that remains unresolved after the settlement deadline in a clearing, depository, or bilateral settlement system. In centrally cleared markets, the number often reflects a net unsettled position rather than a raw count of every failed trade.

Operational definition

From an operations standpoint, an FTD means:

• the trade executed,
• settlement instructions were due,
• all or part of the security quantity was not delivered,
• the position remains open until closed out, borrowed, bought in, or otherwise resolved.

Context-specific definitions

U.S. equity market context

In U.S. equity markets, the term is commonly used in the context of clearing-agency settlement, Regulation SHO, short-selling controls, and public discussion of threshold securities and settlement discipline.

Fixed-income and repo context

In bond and repo markets, a fail usually means the securities side of the transaction did not settle on the agreed date. These fails may be common in stressed or special collateral markets and are often handled through fail charges, bilateral controls, or market conventions.

India market context

In India, the underlying concept exists, but retail users often hear terms such as short delivery, auction, or close-out rather than “fails-to-deliver” in the U.S. sense. The economics are similar: the seller did not deliver the securities on time.

OTC context

In OTC markets, the same concept applies, but the mechanics may be more bilateral and more dependent on custodian instructions, counterparty agreements, and depository procedures.

4. Etymology / Origin / Historical Background

Origin of the term

The word fail comes from old settlement jargon. In the era of physical certificates, a trade could “fail” because the paper certificate did not arrive, did not match, or had transfer defects.

Historical development

Fails-to-deliver existed long before electronic trading. Key stages in their development include:

• Physical certificate era: non-delivery often meant literal paper problems.
• Dematerialization and book-entry settlement: physical delivery risks fell, but system, inventory, and instruction failures remained.
• Central clearing and netting: fails became more standardized and easier to measure at the aggregate level.
• Growth of short selling and securities lending: borrow availability became more important in managing delivery risk.
• Post-2000s regulatory focus: regulators gave more attention to persistent fails, especially where short selling and market integrity were involved.
• Shorter settlement cycles: moves from longer cycles to T+2 and then T+1 increased pressure to get allocations, borrows, and instructions correct earlier.

How usage has changed over time

Historically, a “fail” was mainly a back-office problem. Today, fails-to-deliver are also part of:

• compliance conversations
• market-structure debates
• short-selling controversies
• liquidity analysis
• public narratives around “naked shorting”

Important milestones

Relevant milestones include:

• broad dematerialization of securities
• expansion of CCP and netting systems
• U.S. Regulation SHO framework for short-sale-related settlement discipline
• post-crisis emphasis on settlement efficiency
• adoption of shorter settlement cycles in major markets
• rising public attention to FTD data in heavily discussed stocks

5. Conceptual Breakdown

5.1 Trade date vs settlement date

Meaning: Trade date is when the trade is agreed. Settlement date is when cash and securities are due to exchange.

Role: FTDs exist because trading and settlement are not the same moment.

Interaction: A shorter settlement cycle leaves less time to find borrow, fix allocations, or correct instructions.

Practical importance: Many beginners think execution means the process is finished. It is not.

5.2 Delivery obligation

Meaning: The seller owes securities delivery.

Role: This is the legal and operational core of the transaction.

Interaction: Delivery depends on inventory, custody chain, lending arrangements, and matching instructions.

Practical importance: If the obligation is not met, the trade is economically incomplete even if the price was agreed.

5.3 Fail-to-deliver vs fail-to-receive

Meaning: One party fails to deliver; the other experiences a fail-to-receive.

Role: These are two sides of the same settlement break.

Interaction: The seller’s FTD is the buyer’s missing receipt.

Practical importance: Confusing the two leads to bad analysis of responsibility and exposure.

5.4 Causes of an FTD

Meaning: Reasons the delivery did not happen.

Role: Root cause determines whether the issue is routine, risky, or potentially abusive.

Common causes: – administrative errors – late or broken allocations – missing or incorrect settlement instructions – unavailable securities inventory – hard-to-borrow names – borrowing failure after a short sale – corporate actions such as splits, mergers, symbol changes, or CUSIP changes – restricted or unfree shares – custody chain delays – cross-border depository mismatches – market stress or exceptional volume

Practical importance: Cause matters more than headline quantity.

5.5 Measurement dimensions

Meaning: How market participants quantify a fail.

Common dimensions: – failed quantity – failed market value – days outstanding – fail as a percentage of trade size – fail relative to average daily volume – fail relative to free float or shares outstanding – persistence over consecutive settlement days

Practical importance: A 50,000-share fail can be trivial in a mega-cap and serious in a micro-cap.

5.6 Resolution mechanisms

Meaning: Ways to cure the fail.

Common mechanisms: – deliver from inventory – borrow securities – purchase securities to close out – auction or close-out process – bilateral remediation – cash penalties or fail charges in some markets – buy-in procedures where applicable

Practical importance: The right remedy depends on jurisdiction, asset class, and rulebook.

5.7 Market implications

Meaning: Why FTDs matter beyond back-office operations.

Effects can include: – increased operational risk – counterparty friction – liquidity distortion concerns – compliance problems – reputational issues – regulatory attention – confusion among investors if public data is misunderstood

6. Related Terms and Distinctions

Related Term	Relationship to Main Term	Key Difference	Common Confusion
Fail-to-receive (FTR)	Mirror image of FTD	FTD is seller-side non-delivery; FTR is buyer-side non-receipt	People treat them as different events when they are often two sides of the same break
Short selling	Can lead to FTD if delivery cannot be made	A short sale is a trading strategy; an FTD is a settlement outcome	Not all short sales fail
Naked short selling	Often discussed with FTDs	Naked shorting means selling short without proper borrow/locate discipline; an FTD may result, but not every FTD proves naked shorting	Many assume every FTD equals naked shorting
Threshold security	Regulatory category related to persistent fails	A threshold security is defined by specific regulatory criteria; an FTD is a settlement event	Threshold status is not proof of manipulation
Securities lending	Common tool to avoid or cure FTDs	Lending supplies shares; FTD reflects missing delivery	People confuse borrow availability with completed delivery
Buy-in	Remedy for unresolved settlement	Buy-in is an action taken to obtain securities; FTD is the problem prompting it	A fail does not automatically trigger immediate buy-in everywhere
Close-out	Compliance or operational resolution step	Close-out addresses an open fail; the fail itself is the unresolved obligation	Close-out timing varies by rule and market
Short interest	Related but separate data series	Short interest measures open short positions; FTD measures settlement non-delivery	High short interest and high FTD are not the same thing
Settlement cycle (T+1, T+2)	Time framework in which FTD occurs	Settlement cycle defines deadline; FTD means missing that deadline	Faster settlement reduces time to fix issues but does not eliminate fails
Clearing and settlement netting	Often shapes reported FTD quantity	Reported fail may reflect net obligations, not every individual trade	Raw trading activity and net fail data are not one-to-one
Stock borrow fee / rebate	Signal related to delivery stress	Borrow cost reflects scarcity; FTD reflects non-delivery	Expensive borrow does not guarantee a fail
Short delivery / shortage auction	Local-market remediation term	Often used in some markets instead of the U.S.-style FTD language	Same economic issue, different market vocabulary

7. Where It Is Used

Stock market

This is the most visible setting. Fails-to-deliver matter in:

• cash equity settlement
• short-sale execution and borrow management
• ETF market making
• corporate action periods
• micro-cap and hard-to-borrow names

Fixed-income markets

Fails also occur in:

• government bond settlement
• corporate bond settlement
• repo transactions
• special collateral markets

In these markets, the term “fail” may be more operational and less politicized than in equity discussions.

Policy and regulation

Regulators track settlement efficiency because chronic fails can indicate:

• weak controls
• liquidity stress
• abusive trading behavior
• counterparty risk
• reduced confidence in market integrity

Business operations

Inside broker-dealers, custodians, banks, and clearing firms, FTDs are part of:

• exception management
• reconciliation
• break resolution
• client reporting
• capital and liquidity planning
• control testing

Banking and securities finance

Banks, prime brokers, and securities lending desks care about FTDs because they affect:

• collateral movement
• stock loan demand
• hard-to-borrow inventory
• client financing risk
• fail penalties and exposure

Valuation and investing

FTDs are not a standard valuation metric, but investors and researchers use them as a market-quality and market-friction signal, especially when studying:

• liquidity stress
• crowded shorts
• special situations
• corporate events
• market manipulation allegations

Reporting and disclosures

Public-company reporting rarely centers on FTDs, but financial intermediaries may include settlement-risk language, and regulators or clearing systems may publish aggregated fail information depending on jurisdiction.

Analytics and research

Researchers study FTDs in relation to:

• short selling
• price efficiency
• market quality
• volatility
• settlement discipline
• regulatory changes

Accounting

FTD is not a mainstream standalone accounting term. However, unsettled trades, receivables, payables, control breaks, and reserve or disclosure impacts may be relevant in internal accounting and operations control.

8. Use Cases

8.1 Broker-dealer settlement exception management

• Who is using it: Broker-dealer operations team
• Objective: Resolve trades that did not settle on time
• How the term is applied: FTDs are logged, aged, categorized by cause, and assigned for action
• Expected outcome: Faster resolution, fewer aged fails, better client service
• Risks / limitations: Misclassification can hide root causes; repeated manual fixes can mask poor process design

8.2 Short-sale compliance monitoring

• Who is using it: Prime broker, compliance team, market maker
• Objective: Detect and reduce delivery failures connected to short selling
• How the term is applied: Firms compare open fails with locate records, borrow availability, and close-out obligations
• Expected outcome: Lower regulatory risk and better settlement discipline
• Risks / limitations: Not every fail is a compliance breach; overreacting can hurt liquidity provision

8.3 Market surveillance

• Who is using it: Exchange surveillance unit or regulator
• Objective: Identify persistent, unusual, or unexplained settlement failures
• How the term is applied: FTD trends are screened against volume, float, borrow stress, and corporate events
• Expected outcome: Better detection of abusive patterns or weak controls
• Risks / limitations: Public or aggregate data can create false positives if context is ignored

8.4 Issuer monitoring of unusual settlement activity

• Who is using it: Listed company, legal counsel, investor-relations adviser
• Objective: Understand whether unusual trading and settlement behavior needs escalation
• How the term is applied: Issuer reviews whether fail patterns are persistent, event-driven, or potentially harmful to market perception
• Expected outcome: Better communication and fact-based escalation
• Risks / limitations: Issuers often lack full trade-level visibility and may overinterpret incomplete data

8.5 Hedge fund or analyst liquidity assessment

• Who is using it: Portfolio manager or market-structure analyst
• Objective: Judge whether a security is operationally hard to trade or borrow
• How the term is applied: FTDs are combined with short interest, borrow fees, utilization, and volume
• Expected outcome: Better execution planning and risk sizing
• Risks / limitations: FTDs are backward-looking and often reported with delay

8.6 Fixed-income settlement management

• Who is using it: Bond trader, repo desk, treasury operations team
• Objective: Manage failed deliveries that disrupt financing or collateral chains
• How the term is applied: Open fails are tracked by counterparty, security, value date, and penalty or fail-charge exposure
• Expected outcome: Better collateral mobility and lower settlement friction
• Risks / limitations: Market-wide collateral scarcity can produce fails even with strong internal controls

9. Real-World Scenarios

A. Beginner scenario

• Background: A retail investor buys shares in a thinly traded stock.
• Problem: The investor sees the position in the brokerage account but reads online about fails-to-deliver and worries the purchase was “fake.”
• Application of the term: The broker explains that an FTD is a settlement issue at the market plumbing level, not proof that the customer’s trade was invented.
• Decision taken: The investor checks whether the issue is temporary, whether the broker has credited the account, and whether any corporate action is underway.
• Result: The position settles after the seller’s delivery issue is cured.
• Lesson learned: A visible account position and an underlying settlement fail can coexist for a short time.

B. Business scenario

• Background: A broker-dealer handles a large number of client trades through several custodians.
• Problem: After a symbol and CUSIP change from a corporate action, settlement exceptions spike.
• Application of the term: Operations identifies many of the breaks as FTDs caused by outdated settlement instructions and mismatched security identifiers.
• Decision taken: The firm updates reference data, contacts counterparties, and introduces a same-day control for future corporate events.
• Result: Fails drop sharply in the next settlement cycle.
• Lesson learned: Many FTDs are process problems, not trading abuse.

C. Investor / market scenario

• Background: An analyst studies a small-cap stock with rising social media interest.
• Problem: Public commentary claims high fails-to-deliver prove illegal shorting and guarantee a squeeze.
• Application of the term: The analyst compares fail data with trading volume, borrow fee, short interest, recent warrant exercises, and a pending reverse split.
• Decision taken: The analyst concludes the fails deserve monitoring but do not, by themselves, prove manipulation.
• Result: The stock remains volatile, but the original claim was overstated.
• Lesson learned: FTD data must be interpreted with market context.

D. Policy / government / regulatory scenario

• Background: A regulator sees persistent delivery failures in a specific security over multiple settlement periods.
• Problem: The regulator must determine whether this is operational stress, abusive short selling, or a corporate-action disruption.
• Application of the term: Surveillance teams review member-level fail patterns, locate and borrow records, corporate-event timelines, and concentration among participants.
• Decision taken: The regulator escalates the matter for targeted inquiry instead of assuming misconduct from the fail data alone.
• Result: The investigation identifies a combination of borrow scarcity and weak controls at specific firms.
• Lesson learned: Persistent FTDs are a signal for investigation, not a verdict by themselves.

E. Advanced professional scenario

• Background: An ETF market maker must hedge and deliver basket components around a major index rebalance.
• Problem: One component becomes operationally difficult due to borrow scarcity and delayed custody movement.
• Application of the term: The market maker tracks expected fails-to-deliver, secures substitute borrow where possible, and reprices liquidity to reflect settlement risk.
• Decision taken: The desk reduces quote size, increases spread, and pre-arranges securities lending.
• Result: Most delivery obligations are met, and remaining fails are resolved quickly.
• Lesson learned: In professional trading, FTD awareness directly affects pricing, quoting, and risk appetite.

10. Worked Examples

10.1 Simple conceptual example

A seller agrees to sell 1,000 shares of Company X. Settlement date arrives, but only 900 shares are delivered.

• Shares due: 1,000
• Shares delivered: 900
• Fails-to-deliver: 100 shares

This is the cleanest form of the idea.

10.2 Practical business example

A custodian receives a sell instruction for shares that have just undergone a stock split and symbol change. The old identifier is used in the settlement instruction, so the depository rejects the delivery.

• Trade executed correctly
• Security identifier mismatch prevents settlement
• The seller misses delivery on settlement date
• The trade becomes an FTD until corrected

This example shows that FTDs can arise from operations, not only trading strategy.

10.3 Numerical example

A broker sells 100,000 shares of a stock at $18.60. By settlement date, only 92,500 shares are delivered.

Step 1: Calculate failed quantity

Failed quantity = shares due – shares delivered

Failed quantity = 100,000 – 92,500 = 7,500 shares

Step 2: Calculate failed market value

FTD value = failed quantity × reference price

FTD value = 7,500 × $18.60 = $139,500

Step 3: Calculate trade-level fail rate

Fail rate = failed quantity / shares due

Fail rate = 7,500 / 100,000 = 7.5%

Step 4: Compare to liquidity

Assume average daily volume is 500,000 shares.

Liquidity-relative fail rate = failed quantity / average daily volume

Liquidity-relative fail rate = 7,500 / 500,000 = 1.5%

Interpretation

• 7.5% of this specific trade failed
• but the fail equals only 1.5% of a normal day’s trading volume
• this could still be manageable in a liquid stock, but it would be more serious in a thinly traded name

10.4 Advanced example: netting effect

A clearing participant has the following same-security obligations on settlement date:

• Gross buys: 380,000 shares
• Gross sells: 400,000 shares

After netting, the participant must deliver:

Net delivery obligation = 400,000 – 380,000 = 20,000 shares

The participant can source only 5,000 shares through inventory and borrowing.

FTD quantity = 20,000 – 5,000 = 15,000 shares

Why this matters

The market may observe a 15,000-share fail at the clearing level, but that does not mean only one 15,000-share trade failed. The number can be the result of many gross trades that netted down.

11. Formula / Model / Methodology

There is no single universal “fails-to-deliver formula” used across all markets. Instead, professionals use a set of practical metrics.

11.1 FTD quantity

Formula:
FTD quantity = securities due – securities delivered on time

Variables: – securities due = amount the seller had to deliver – securities delivered on time = amount actually delivered by settlement deadline

Interpretation: The basic size of the fail.

Sample calculation:
10,000 due – 8,400 delivered = 1,600 failed

Common mistakes: – forgetting partial delivery – using executed volume instead of contractual delivery obligation – ignoring netting

Limitations: Reported market-level figures may be net, not trade-by-trade.

11.2 FTD market value

Formula:
FTD value = FTD quantity × reference price

Variables: – FTD quantity = failed shares or units – reference price = trade price, settlement price, or end-of-day price depending purpose

Interpretation: Converts the fail into money terms.

Sample calculation:
1,600 shares × $22.50 = $36,000

Common mistakes: – mixing prices from different dates without saying so – assuming all firms use the same reference price

Limitations: Value changes with price; share count may be more stable for comparison.

11.3 Trade-level fail rate

Formula:
Fail rate = FTD quantity / securities due

Variables: – FTD quantity = quantity failed – securities due = original obligation

Interpretation: What portion of the specific trade or obligation failed.

Sample calculation:
1,600 / 10,000 = 16%

Common mistakes: – comparing trade-level fail rate with market-wide fail rate – ignoring partial settlements over time

Limitations: Good for single trades, less useful for market-wide analysis.

11.4 Liquidity-relative fail rate

Formula:
Fail burden = FTD quantity / average daily volume

Variables: – FTD quantity = failed quantity – average daily volume = typical daily traded volume over a chosen window

Interpretation: Shows how large the fail is relative to normal trading liquidity.

Sample calculation:
1,600 / 80,000 = 2% of ADV

Common mistakes: – using abnormal event-day volume as the denominator – comparing illiquid and liquid stocks without context

Limitations: ADV can swing sharply in volatile names.

11.5 Float-relative fail rate

Formula:
Float-based fail rate = FTD quantity / free float

Variables: – free float = shares actually available for public trading

Interpretation: Useful for evaluating crowding in small or tightly held names.

Sample calculation:
1,600 / 4,000,000 = 0.04% of float

Common mistakes: – using shares outstanding when float is the more relevant number – using stale float data

Limitations: Float data may be estimated, delayed, or affected by lockups and insider holdings.

11.6 Persistence and aging

Formula:
Aging days = number of settlement days the fail remains unresolved

Alternative metric:
Share-days failed = sum of open failed quantity across days

Example:
Day 1: 7,500 shares open
Day 2: 6,000 shares open
Day 3: 4,000 shares open
Day 4: 0 shares open

Share-days failed = 7,500 + 6,000 + 4,000 = 17,500 share-days

Interpretation: Persistent fails are usually more important than one-day fails.

Common mistakes: – focusing only on one snapshot date – not distinguishing new fails from old unresolved fails

Limitations: High persistence can result from legitimate complex events, not only abuse.

12. Algorithms / Analytical Patterns / Decision Logic

12.1 Settlement exception triage logic

What it is: A workflow used by operations teams to classify and resolve open fails.

Why it matters: Fast triage reduces aging, penalties, and client complaints.

When to use it: Daily post-settlement exception management.

Typical logic: 1. Confirm trade details and settlement date. 2. Identify whether fail is full or partial. 3. Check inventory and securities lending availability. 4. Verify counterparty and custodian instructions. 5. Review corporate actions or identifier changes. 6. Assign root cause code. 7. Resolve through delivery, borrow, purchase, or escalation.

Limitations: Strong process still cannot eliminate market-wide inventory shortages.

12.2 Surveillance screen for persistent fails

What it is: A rules-based monitoring approach used by compliance or regulators.

Why it matters: Helps distinguish routine noise from patterns worth investigating.

When to use it: Ongoing market surveillance.

Common screen inputs: – consecutive settlement days with open fails – fail quantity relative to ADV or float – borrow fee and utilization – concentration by participant – absence of explanatory corporate events – repeated threshold-like behavior where relevant

Limitations: False positives are common around splits, mergers, index events, and new issuance.

12.3 Event-adjusted interpretation framework

What it is: A decision framework that asks whether the fail occurred around a known operationally disruptive event.

Why it matters: Many dramatic-looking fail spikes are event-related.

When to use it: Whenever public FTD data is being interpreted.

Key questions: – Was there a split, reverse split, merger, spin-off, or CUSIP change? – Was there unusual options activity or ETF basket rebalancing? – Was the security hard-to-borrow? – Did volume and volatility spike abnormally?

Limitations: Not all events are public or easy to map precisely.

12.4 Investor due-diligence logic

What it is: A practical screen to avoid overreacting to FTD headlines.

Why it matters: Retail commentary often turns one data point into a conspiracy theory.

When to use it: Before making trading decisions based on FTD chatter.

Suggested sequence: 1. Check whether fails are persistent or one-off. 2. Compare fails with volume, float, and short interest. 3. Review borrow conditions. 4. Look for corporate actions or settlement calendar effects. 5. Distinguish evidence from speculation.

Limitations: Public data is often delayed and aggregated.

13. Regulatory / Government / Policy Context

13. Regulatory / Government / Policy Context

United States

In the U.S., fails-to-deliver are closely associated with:

• SEC short-sale and settlement rules, especially Regulation SHO
• broker-dealer compliance and supervisory controls
• clearing-agency settlement processes
• public debate around threshold securities and persistent fails

Important points:

• The U.S. uses a short settlement cycle, which raises the importance of timely borrowing, allocation, and instruction matching.
• Regulation SHO includes locate and close-out concepts designed to reduce certain types of delivery failure.
• Persistent fails may contribute to a security being identified under threshold-security criteria.
• Public FTD data is useful but can be misunderstood because it is delayed, aggregated, and often netted.

Caution: Exact regulatory timings and technical thresholds should always be checked in the current SEC, FINRA, and clearing-agency rule text.

India

In India, the same economic issue appears through exchange and clearing-corporation settlement processes, but the market vocabulary often emphasizes:

• short delivery
• shortages
• auction settlement
• close-out procedures

Important points:

• Exchange and clearing-corporation mechanisms typically resolve non-delivery through auction or close-out frameworks.
• The issue is operationally similar to an FTD even if local terminology differs.
• Segment-specific rules can differ, so current exchange circulars and clearing-corporation procedures should be verified.

European Union

In the EU, settlement discipline is strongly shaped by central securities depository rules and related market-infrastructure regulation.

Important points:

• The policy focus includes settlement efficiency, matching discipline, and penalties for failed settlement.
• Cash penalties have been an important part of the EU settlement-discipline approach.
• The mandatory buy-in framework has evolved over time and should be checked against the latest EU legal position and local implementation.

United Kingdom

The UK approach is similar in principle but not identical to the EU framework after Brexit.

Important points:

• Market participants should review the current UK settlement-discipline, depository, and custody arrangements.
• CREST and local market practices matter operationally.
• Firms should not assume EU and UK treatment is identical.

International / global usage

Across markets globally:

• the core concept remains the same: securities were not delivered on time
• public transparency varies widely
• some markets emphasize auctions and close-outs
• others emphasize penalties, buy-ins, or bilateral remediation
• fixed-income markets may have their own conventions, especially for sovereign debt and repo

Taxation angle

There is no simple universal “FTD tax rule.” However, failed settlement can affect:

• record-date entitlement issues
• dividend and substitute-payment mechanics
• withholding tax processing
• corporate action timing

These effects are highly jurisdiction-specific and should be verified with current tax and custody guidance.

Public policy impact

Settlement discipline matters for public policy because it affects:

• confidence in market integrity
• investor protection
• operational resilience
• systemic risk
• fairness of short-selling rules
• smooth functioning of securities financing markets

14. Stakeholder Perspective

Student

A student should view fails-to-deliver as part of post-trade market plumbing. It connects trading, clearing, settlement, securities lending, and regulation.

Business owner / issuer

An issuer cares when persistent FTD discussion affects market perception, shareholder confidence, or concerns about abusive trading. But an issuer should avoid jumping from raw fail data to legal conclusions.

Accountant or finance controller

This term is not central to external accounting theory, but it matters for:

• unsettled trade reconciliation
• control failures
• operational loss review
• entitlement and corporate-action reconciliation

Investor

An investor should treat FTDs as a signal, not a verdict. The right question is not “Are there FTDs?” but “Why are they happening, how persistent are they, and what other evidence exists?”

Banker / lender / securities-finance desk

Banks and lending desks care because FTDs affect:

• stock loan demand
• collateral movement
• settlement exposure
• financing spreads
• client service and compliance risk

Analyst

An analyst uses FTDs to study:

• settlement frictions
• liquidity quality
• borrow stress
• event-driven distortions
• potential market-structure vulnerabilities

Policymaker / regulator

Regulators see FTDs as a surveillance input. Persistent fails can justify review, but sound policy requires separating operational frictions from abusive conduct.

15. Benefits, Importance, and Strategic Value

A fails-to-deliver is not a “benefit” by itself. The benefit comes from understanding, measuring, and controlling it.

Why it is important

• shows whether the market’s settlement system is working smoothly
• highlights weaknesses in inventory, borrowing, and operations
• helps regulators monitor market integrity
• helps traders understand execution quality beyond price alone

Value to decision-making

FTD analysis helps firms decide:

• whether to pre-borrow or reduce trade size
• when to escalate a settlement break
• whether a security is operationally difficult
• whether a fail pattern is noise or a real warning sign

Impact on planning

• earlier allocation deadlines
• stronger corporate-action preparation
• better custodial coordination
• improved borrow sourcing in hard-to-borrow names

Impact on performance

Chronic fails can reduce performance through:

• missed settlement efficiency targets
• higher penalties or financing costs
• wider spreads
• reduced trading capacity
• client dissatisfaction

Impact on compliance

Good FTD control supports:

• short-sale compliance
• supervisory procedures
• books-and-records integrity
• timely close-out actions where required

Impact on risk management

FTDs matter for:

• operational risk
• counterparty risk
• market conduct risk
• reputational risk
• liquidity and funding risk in securities finance chains

16. Risks, Limitations, and Criticisms

Common weaknesses

• raw FTD data is often delayed
• aggregate figures may be netted
• root causes are not visible from headline numbers alone
• one-day spikes can look dramatic but be harmless

Practical limitations

• public data often lacks participant-level detail
• cross-border settlement chains are hard to analyze from outside
• different markets use different labels and remedies
• not all asset classes disclose fails the same way

Misuse cases

• claiming every FTD proves naked shorting
• using FTD spikes as guaranteed squeeze signals
• comparing fail counts across stocks without adjusting for volume or float
• ignoring corporate actions and custody events

Misleading interpretations

A high FTD number may reflect:

• a corporate-action disruption
• temporary settlement mismatches
• netting artifacts
• increased trading volume
• genuine inventory scarcity

Edge cases

• ETF creation/redemption timing
• option exercises and assignments
• ADR conversion timing
• reverse splits and CUSIP changes
• sovereign-bond collateral squeezes

Criticisms by experts and practitioners

Experts often criticize public FTD debates for being too simplistic. Common expert criticisms include:

• confusing settlement data with proof of intent
• treating netted data as trade-level evidence
• ignoring market-making and corporate-action mechanics
• overstating causal links between FTDs and long-term price suppression

17. Common Mistakes and Misconceptions

1. Wrong belief: Every FTD is illegal

• Why it is wrong: Many fails are operational or temporary.
• Correct understanding: Some are routine settlement exceptions; legality depends on facts, rules, and behavior.
• Memory tip: Fail does not automatically mean foul.

2. Wrong belief: Every FTD proves naked short selling

• Why it is wrong: Long sales, custody errors, and corporate actions can also create fails.
• Correct understanding: Naked shorting may cause some fails, but FTD and naked shorting are not identical.
• Memory tip: Same symptom, different causes.

3. Wrong belief: FTDs and short interest are the same

• Why it is wrong: Short interest measures open short positions; FTD measures failed settlement.
• Correct understanding: A stock can have high short interest and low fails, or vice versa.
• Memory tip: Short interest is position; FTD is settlement.

4. Wrong belief: One day of high FTD means manipulation

• Why it is wrong: Temporary spikes happen around market events.
• Correct understanding: Persistence, scale, and context matter more than a single print.
• Memory tip: Pattern beats snapshot.

5. Wrong belief: T+1 should eliminate all fails

• Why it is wrong: Faster settlement reduces time, but it does not remove inventory or instruction problems.
• Correct understanding: Shorter cycles can reduce some risks while increasing operational pressure.
• Memory tip: Faster is not flawless.

6. Wrong belief: If I can see shares in my account, there cannot be an FTD

• Why it is wrong: Retail account display and street-name settlement plumbing are not always the same thing.
• Correct understanding: Brokers may credit positions while back-end settlement is still being completed.
• Memory tip: Front-end view is not back-end settlement.

7. Wrong belief: High FTDs guarantee a short squeeze

• Why it is wrong: FTDs do not automatically force immediate buying in every situation.
• Correct understanding: Resolution timing depends on rules, market structure, and sourcing ability.
• Memory tip: A fail is pressure, not prophecy.

8. Wrong belief: Only stocks have fails-to-deliver

• Why it is wrong: Bonds, repo, ETFs, and other instruments can also fail to settle.
• Correct understanding: Any market with deferred settlement can have delivery fails.
• Memory tip: If it settles later, it can fail later.

9. Wrong belief: Public FTD data is real-time

• Why it is wrong: Public dissemination is usually delayed.
• Correct understanding: Public data is useful for analysis, not live settlement management.
• Memory tip: Public fail data is history, not a live wire.

10. Wrong belief: Bigger number always means bigger risk

• Why it is wrong: Scale must be compared with volume, float, and persistence.
• Correct understanding: Context determines significance.
• Memory tip: Always normalize.

18. Signals, Indicators, and Red Flags

Positive signals

• low level of aged fails
• quick resolution after settlement date
• stable instruction match rates
• normal borrow cost and availability
• no repeat fail pattern after corporate events
• low fail burden relative to volume and float

Negative signals

• persistent open fails over multiple settlement days
• repeated spikes without clear operational explanation
• rising fail burden relative to ADV or float
• very high borrow fees and borrow scarcity
• recurring issues in the same desk, counterparty, or security
• repeated appearance in persistent-fail regulatory screens where applicable

Warning signs to monitor

• aging buckets growing longer
• concentration of fails in illiquid or low-float names
• rising manual overrides in settlement operations
• corporate actions with poor reference-data updates
• unresolved allocations late in the day
• mismatch between borrow records and delivery outcomes

Metrics to monitor

• FTD quantity
• FTD market value
• fail rate by trade
• fail burden versus ADV
• fail burden versus float
• days outstanding
• share-days failed
• borrow fee
• utilization
• instruction match rate
• counterparty concentration of fails

What good vs bad looks like

Metric	Good	Bad
Aging	Resolved quickly	Stays open for multiple settlement cycles
Size vs ADV	Small share of typical volume	Large share of daily volume
Borrow conditions	Borrow available at normal cost	Borrow scarce and expensive
Root cause profile	Mostly explainable operational exceptions	Repeated unexplained patterns
Concentration	Diffuse and occasional	Concentrated in names, desks, or counterparties

19. Best Practices

Learning

• understand the full trade lifecycle from execution to settlement
• learn the difference between trade data, short-interest data, and fail data
• study local market vocabulary, because not every market uses “FTD” as the main term

Implementation

• use pre-settlement checks for inventory, borrow, and allocations
• automate reference-data updates for splits, mergers, and symbol changes
• establish root-cause codes for every fail
• escalate aged fails quickly

Measurement

• track both quantity and persistence