WorkflowInvestment Operations & Middle Office

Learn · one field

Place of settlement (PSET), and why Europe now wants it early

The place of settlement is the central securities depository where a trade's securities and cash finally change hands, and a mismatch in it is a fail that could have been prevented on trade date. From 7 December 2026 EU allocations must carry it; this guide explains PSET and PSAF, how to find the right one, and how Standard Settlement Instruction Management checks it.

Updated · 12 min read

See one case, screen by screen →
Watch with transcript →

The place of settlement, PSET for short, is the location where a trade finally settles: the central securities depository (CSD) in whose books the securities pass from seller to buyer and the cash from buyer to seller. ESMA defines it as "the location where the final transfer of securities or funds will take place" (ESMA consultation paper, February 2025). It matters because many securities can settle in more than one place, especially exchange-traded funds and international bonds, and if the two sides of a trade instruct different places, their instructions cannot match. From 7 December 2026, Delegated Regulation (EU) 2026/1536 requires professional clients' written allocations to include "the place of settlement ('PSET')", so the question has to be answered on trade date, before any instruction is sent (Delegated Regulation (EU) 2026/1536). In a standing settlement instruction, the place of settlement is one of the lines that, once wrong, is wrong on every trade; Botminds' Standard Settlement Instruction Management checks it on every change, alongside the account format by market, sanctions lists and the counterparty's own published data.

Examples use fictional counterparties from the solution's sample data. The rules and ESMA's analysis are linked where they appear.

One cross-border ETF trade, two outcomes: the place of settlement agreed at allocation, or discovered at matching

PSET agreed on trade datePSET left to each side
Allocation, trade date

PSET agreed on trade date: The asset manager’s allocation names the CSD where its custodian holds the ETF; the broker accepts it.

PSET left to each side: The allocation names accounts but no place of settlement; each side assumes its usual CSD.

Instructions

PSET agreed on trade date: Both custodians instruct at the same CSD.

PSET left to each side: The fund’s custodian instructs where the fund’s ETF position sits; the broker instructs at the CSD of the venue it traded on.

Matching

PSET agreed on trade date: Matched; eligible for overnight settlement.

PSET left to each side: Each CSD holds one instruction with no counterpart. Nothing matches.

Fix

PSET agreed on trade date: None needed.

PSET left to each side: Find the mismatch, agree one place, cancel and re-instruct, or realign the position across CSDs, which takes time a T+1 cycle does not have.

Result

PSET agreed on trade date: Settles on the intended date.

PSET left to each side: Late matching or a fail, and a cash penalty in the EU on the side found to have failed.

Our illustration. ESMA's 2024 T+1 report notes that for ETFs a broker must check, for each transaction, the content of the SSIs to find the place of settlement before sending instructions; respondents to ESMA's 2024 penalty consultation listed a place-of-settlement mismatch among the reasons instructions do not match.Source: ESMA T+1 report, 2024; ESMA penalty advice, 2024

What is the place of settlement (PSET)?

It is the CSD where a specific trade settles. ESMA's 2025 consultation put it in one paragraph: the place of settlement "refers to the location where the final transfer of securities or funds will take place. This is the place where the ownership of securities is officially transferred from the seller to the buyer, and where funds are moved from the buyer to the seller. The PSET is typically specified in the settlement instructions" (ESMA, paragraph 145).

The term comes from the messaging standards. ESMA explains that "'PSET' is the ISO15022 label" of the message element that, in the ISO 20022 messages used by TARGET2-Securities, is called the receiving or delivering depository, and that "This field is already a mandatory matching field in T2S". In practice it is usually filled with the identifier code of the CSD. Two caveats matter: the place of settlement is a property of a trade between two parties, not of a security, and ESMA notes that it "may change along the settlement chain in the case of netting", for example when a central counterparty nets many trades into one settlement.

How is place of settlement different from place of safekeeping?

The place of safekeeping, PSAF, is where the securities are held; the place of settlement is where this trade will move them. ESMA describes PSAF as the field that "identifies the location where the financial instruments are/will be safekept", typically the account or system where a custodian keeps them (ESMA, paragraph 155). For most domestic trades the two are the same CSD. They diverge when a fund holds a security in one CSD and trades it with a broker who settles in another, and that gap is what turns a matched trade into a realignment.

Place of settlement and the three things it is often confused with

TermWhat it identifiesWhere it livesWho decides it
Place of settlement (PSET)The CSD where this trade’s securities and cash finally moveAllocation, confirmation and settlement instruction; standing instruction per marketAgreed by the two parties, constrained by where the security can settle
Place of safekeeping (PSAF)Where the securities are or will be heldCustody statements and some instructionsThe account owner and its custodian
Custodian or settlement agentThe bank that holds the account and acts at the CSDStanding settlement instruction, with its BICThe account owner
Participant code at the CSDThe account or member identifier inside the CSDStanding instruction; matching field for delivering and receiving participantsThe CSD assigns it; the owner communicates it
Definitions of PSET and PSAF follow ESMA's consultation paper of 13 February 2025, paragraphs 145 and 155; the participant identifiers are matching fields under Article 5(3) of Delegated Regulation (EU) 2018/1229. The rest is our summary.

Why do PSET mismatches fail trades?

Because a CSD can match only instructions it holds, and two instructions sent to two different CSDs never meet. The EU's matching fields name the delivering and receiving participants and, where CSDs share an infrastructure, the counterparty's CSD, but not the place of settlement itself. Respondents to ESMA's 2024 consultation on cash penalties said instructions still fail to match on non-economic data "such as place of settlement (although this information is not a mandatory matching criteria at trade level)" (ESMA, November 2024).

ESMA's own report on T+1 counted a wrong place of settlement in the instruction among the errors that a shorter cycle leaves no time to fix, and singled out ETFs, which are often listed on several venues and held in several CSDs, so that a broker must "check, for each transaction, the content of the SSIs (e.g. to check the place of settlement), prior to sending the SSIs to settlement" (ESMA T+1 report, November 2024). The EU T+1 industry task force told ESMA that "The industry has identified PSET mismatches as a common cause of settlement fails"; no regulator publishes how common.

Does the EU now require PSET in allocations?

Yes, from 7 December 2026. Delegated Regulation (EU) 2026/1536 adds "(p) the place of settlement ('PSET')" to the list of what a professional client's written allocation must specify, and its recital gives the reason: "to avoid late-stage adjustments which are particularly critical in the context of a shortened settlement cycle, the place of settlement should be communicated as early as possible in the settlement process" (Delegated Regulation (EU) 2026/1536). The allocation rule is not among the provisions the regulation defers to 2027, so under its Article 2 it applies from the general date.

How the place of settlement went from optional to required on EU allocations

ESMA and the Commissionapplies from 7 Dec 2026
ConsideredNov 2024
Consultation: not requiredFeb 2025
Final report: requiredOct 2025
Adopted; applies 7 DecJul 2026
  • ConsideredNov 2024
  • Consultation: not requiredFeb 2025
  • Final report: requiredOct 2025
  • Adopted; applies 7 DecJul 2026
Months to scale from November 2024 to December 2026. ESMA's T+1 report (18 November 2024) said it was considering whether the place of settlement should be a mandatory field; its consultation paper (13 February 2025) proposed not to require it in allocations; its final report (13 October 2025) included it; the Commission adopted Delegated Regulation (EU) 2026/1536 on 6 July 2026, published in the Official Journal on 14 October 2026.Source: ESMA final report, October 2025; Delegated Regulation (EU) 2026/1536

The turn came from the consultation. ESMA had proposed leaving PSET to industry best practice; the feedback "unanimously supported the critical role of PSET in improving settlement efficiency, in particular for cross-border settlement and for multi-listed securities (such as ETFs and bonds)", with "a slight majority in favour" of a legal requirement (ESMA final report, 13 October 2025). ESMA then added it to the allocation, while noting that it was not proposing to make PSET a matching field for settlement instructions. One thing it deliberately left out:

“ESMA has consciously left the term ‘place of settlement or PSET’ undefined to ensure that an industry-wide agreement can be reached in this area.”

ESMA, Final Report on amendments to the RTS on settlement discipline, 13 October 2025, paragraph 137

So the law requires the field and the industry supplies the meaning. Respondents pointed to the market practice of the Securities Market Practice Group; some suggested rules such as letting the buy side, which alone sees its custody structure, provide the PSET, or deriving it from the security's ISIN and the trading venue's market identifier code.

What does the UK T+1 plan say about PSET and PSAF?

It asks for a market practice first and its use second. Action SETT 09a says the UK taskforce and the investment, banking and markets associations "will agree, support and publish new market practice for the communication of Place of Settlement and Place of Safekeeping between the brokerage, custodian and buy-side communities", due by 31 December 2025; SETT 09b says the published practice "will be implemented and used systematically" by 31 December 2026 (UK Accelerated Settlement Technical Group, February 2025). Both are among the report's "highly recommended" actions rather than its critical ones.

ESMA's consultation records that the UK group also recommended that PSET be clarified at an earlier stage, when a client is onboarded. That is the SSI's job: if each standing instruction states the place of settlement per market, the allocation can carry it without anyone looking it up trade by trade. Collecting it at account opening is one of the five legs of counterparty onboarding.

How do you find the right place of settlement for a security?

Start from where your own position sits and where your counterparty settles, not from the security alone. A security issued into one CSD may be held through others linked to it, and a multi-listed ETF may settle where it traded or where the investor holds it. The right PSET for a trade is the one both sides can settle in without moving the position first.

Finding and holding the right place of settlement, market by market

  1. Know where each fund’s position is held

    Your custodian’s statements of holdings should show the place of safekeeping for each line; ask for it where they do not.

  2. Record a place of settlement in every standing instruction, per market

    Store the CSD, normally by its identifier code, not just the custodian. One counterparty may need different PSETs for different markets.

  3. Agree it with the counterparty when the relationship starts

    The UK group recommended clarifying PSET at onboarding; a broker that settles some ETFs in another CSD should say so then.

  4. Send it on the allocation

    Required in the EU from 7 December 2026; good practice everywhere a security settles in more than one place.

  5. Watch multi-listed securities and new venues

    A new listing or venue can change where a counterparty settles a security you already trade.

  6. Treat a PSET change in an SSI as a change to verify

    A new place of settlement moves where your trades settle, so it is confirmed with the counterparty like an account change.

Our checklist, drawing on ESMA's consultation paper and final report (2025), the UK Technical Group's SETT 09 actions, and Delegated Regulation (EU) 2026/1536.

Where PSET lives in a standing settlement instruction

In a securities SSI it is the depository line, sometimes labelled "place of settlement", sometimes "depository" with a participant code beside it. Fictional Kawabe Securities' Japanese equities SSI in the solution's sample names JASDEC as the depository and participant 41270; when Kawabe moved its settlement agent to a new bank, the depository and participant did not change, and the solution showed them as unchanged rather than leaving the approver to infer it.

A Japanese equities SSI in Standard Settlement Instruction Management: the agent changes, the place of settlement does not

Dossier for Kawabe Securities' JPY equities instruction SSI-06630. The What changes panel lists seven fields: settlement agent changed from Sakuragawa Trust Bank to Minato Custody Bank, agent BIC changed from SKGWJPJT to MNTCJPJT, safekeeping account changed from 0042-118305 to 0081-447120; beneficiary unchanged; depository JASDEC participant 41270 marked same; bank country Japan same; effective 26 October 2026 at 00:01 Tokyo. The counterparty's own authenticated record agrees. Checks include the BIC MNTCJPJT exists and the safekeeping account format for Japan, both passed.
Fictional sample data. The depository line is the place of settlement for these trades; showing it as unchanged tells the approver that trades will still settle at the same CSD, only through a different agent.

Place of settlement also ages. A standing instruction set up years ago for a market the firm rarely trades may name a depository arrangement the counterparty has since changed, and it fails the first trade that uses it. That is one reason the sample firm's quarterly review targets instructions unused for twelve months.

A quarterly review of dormant instructions, market by market

Recertification for the fourth quarter of 2026: 1,286 instructions due, because they were not used for 12 months, used in a failed trade, or high risk; the campaign closes 15 December. The Recertification agent proposes 688 to confirm because they match the counterparty's own record, 431 to retire because they are dormant and no longer in the counterparty's record, and 167 to call back because there is no record to compare or a failed trade. A table lists instructions by counterparty, asset and currency, such as fixed income in EUR, FX in JPY, collateral in AUD, with last used date, the number of funds, the proposal and the reason. A team lead other than the confirmer checks a 5% sample.
Fictional sample data in Standard Settlement Instruction Management. Each proposal compares the instruction with the counterparty's own published data; a person confirms, retires or calls back.

How Standard Settlement Instruction Management checks place of settlement

The Checker agent tests every new or changed instruction on its own, apart from the fraud score: BIC, IBAN and routing codes, the account format for the market, the place of settlement, sanctions and watch lists, and whether the template is complete. A change that moves the place of settlement is treated as a change to verify with the counterparty on the number on file, like an account change, and goes live at an agreed time in the SSI master, order management, the custodians and payments, so that allocations built from it carry the new PSET from the same moment. From the SSI to the CSD instruction shows where the allocation goes next. To see it on your own instructions, start from Standard Settlement Instruction Management.

Questions people ask

Is there a place of settlement PSET list?

No regulator publishes a single list of PSET codes. In practice the place of settlement is identified by the CSD's identifier code, and CSDs and custodians publish their own market guides. Because ESMA left the term undefined in EU law, the industry's market practice, not a register, decides how the field is filled.

Can the place of settlement change along the chain?

Yes. ESMA notes that the place of settlement, and the place of safekeeping, may change along the settlement chain where trades are netted, for example by a central counterparty. A client's allocation and the broker's final instruction to the CSD may then name different places, which is why the place agreed bilaterally is the one to record.

Is PSET a matching field?

It is a mandatory matching field in TARGET2-Securities, ESMA says, but EU law does not list it among the matching fields CSDs must require, and ESMA's 2025 final report did not propose adding it there. From December 2026 the EU requires it in the allocation instead, so the parties agree it before instructing.

What is the place of settlement for US securities?

For most US equities and corporate and municipal bonds it is DTC, which the SEC describes as the depository that settles most US securities transactions (SEC, 2023). US Treasuries settle elsewhere. The question becomes live mainly for foreign securities and cross-border holdings.

Why does PSET matter more for ETFs?

An ETF is often listed on several exchanges and held in several CSDs, so the same ISIN can settle in more than one place and the two sides may assume different ones. ESMA's 2024 report found that a broker has to check the place of settlement in the SSI for each ETF trade before instructing.

Standard Settlement Instruction Management.
See it on your own files.

An agentic solution from Botminds. Keeps counterparty settlement instructions current and fraud-checked for settlement operations Book a demo, or explore how it works.