NEWS / FIXNOX

PSET and PSAF in FIX: How to Encode and Validate Settlement Locations

Industry News · 19 Nov 2026

PSET and PSAF in FIX: Catching Settlement Mismatches Before Instructions Are Sent

A trade can match on instrument, quantity, price and settlement date and still face a settlement break. If the investment manager and broker expect different settlement locations, the best time to find out is during allocation and confirmation, before settlement instructions go to the custodian or prime broker.

The FIX Trading Community's November 2026 draft recommended practices explain how to communicate Place of Settlement (PSET) and Place of Safekeeping (PSAF) using existing FIX fields. The draft makes an important distinction: PSET is supplied for matching, while PSAF is carried through the workflow as safekeeping information.

What PSET and PSAF tell you

PSET identifies the intended settlement location, typically a central securities depository (CSD) or international central securities depository (ICSD). PSAF identifies where the securities are held or are intended to be held. A safekeeping location is distinct from a securities account number at that location.

In a cross-CSD transaction, downstream settlement instructions can legitimately show different PSET values on opposite sides. Under the joint industry guidance from AFME, UK Finance and the Investment Association, downstream PSET identifies the counterparty's CSD or ICSD. A matching system therefore needs to compare values from the same perspective. Comparing raw PSET values from opposite-side instructions can flag a mismatch where none exists.

How to encode the locations in FIX

Use the applicable Parties component. The draft's allocation and confirmation examples use the settlement-party repeating group.

TagFIX fieldUsage
781NoSettlPartyIDsCount of all settlement-party entries in this group, including parties unrelated to PSET or PSAF.
782SettlPartyIDIdentifier of the location or institution.
783SettlPartyIDSourceIdentifier scheme agreed with the counterparty. B denotes a BIC, the draft's recommended scheme for PSET.
784SettlPartyRole10 for PSET. For PSAF, use 119 for a CSD, 120 for an ICSD, or 28 for a custodian acting as the safekeeping location.

When both locations are conveyed, send them as separate entries even if they share an identifier. Reserve role 10 for PSET. If the message contains multiple custodian entries, agree with the counterparty how to identify the one that represents PSAF. The same role values apply when an equivalent Parties component is used, but the tag numbers depend on the component.

The following illustrative TagValue fragment shows a PSET entry and a separate PSAF entry for an ICSD. The identifiers are placeholders and pipes represent SOH delimiters.

781=2|782=<settlement-location BIC>|783=B|784=10|
782=<safekeeping ICSD BIC>|783=B|784=120|

Where the fields go in the workflow

AllocationInstruction (35=J). In the draft's example, the settlement-party group sits within a delivery instruction (NoDlvyInst, tag 85) for an individual allocation (NoAllocs, tag 78). When a block is split across accounts, each allocation can carry its own settlement route. A single block-level default should not overwrite an account's intended location.

Confirmation (35=AK). The draft shows PSET in the settlement-party group within the confirmation's delivery instructions. This particular confirmation example does not include a separate PSAF entry. If the agreed confirmation profile carries PSAF, apply the same separate-entry and role rules. The example also carries a securities account number in SettlPartySubID (785), with SettlPartySubIDType (786) set to 10. That value of 10 is a sub-ID type, distinct from the PSET role in tag 784.

Matching and exception handling. Validate the identifier scheme and compare the received PSET with the expected location for that allocation and side. A valid BIC can still identify the wrong depository. Carry PSAF forward for downstream processing and flag missing or ambiguous values where the agreed workflow requires them. If PSET does not match, hold the affected allocation out of automatic instruction release, show operations the expected and received values, and revalidate after correction. The FIX fields carry the data; the counterparty profile determines the acknowledgement, correction and release behaviour.

A useful certification test is a block split across two accounts with different settlement routes. Put a valid but incorrect PSET on one allocation and verify that the system flags that allocation and prevents its automatic release. Then test a route where PSET and PSAF share a BIC: both role-qualified entries should survive the round trip.

Technical reference: FIX Trading Community, Place of Settlement and Place of Safekeeping, version 0.2 (draft), sections 6.1 and 7.1–7.3. Check the final publication and your counterparty's FIX profile before implementing.

← Back to news