semt.002 Securities Balance Custody Report

When semt.002 is used

The account servicer (a CSD, sub-custodian or global custodian) sends the semt.002 to the account owner or a party acting for it. It reports one safekeeping account, or a set of sub-accounts, as at the date and time in StmtGnlDtls/StmtDtTm. It is used for daily or intraday position reconciliation, as an answer to a statement request, and to show what is available to deliver.

Like the MT535 it states its frequency (Frqcy), whether it is complete or a delta (UpdTp with COMP or DELT) and its basis (StmtBsis with SETT settled, TRAD traded or CONT contractual positions). Unlike the MT535 it is a custody statement only: valuation statements have their own message, semt.003 (Securities Balance Accounting Report), so there is no statement-type indicator.

Each instrument is one BalForAcct block with the identifier in FinInstrmId, the total position in AggtBal, and optionally AvlblBal and NotAvlblBal. Every balance states its direction in a ShrtLngInd (LONG or SHOR) element instead of the MT sign. Sub-balances go in BalBrkdwn (for example AWAS, PEND, PENR, BLOK, PLED, LOAN, BLCA) and AddtlBalBrkdwn (classifications such as COLA, NOMI, UNRG), positions per place of safekeeping in BalAtSfkpgPlc, and lots in QtyBrkdwn.

When SubAcctInd is true, positions are reported per sub-account in SubAcctDtls, each with its own account and BalForSubAcct blocks, which corresponds to an MT535 with :17B::CONS//Y. Prices and values are optional: PricDtls gives the price and AcctBaseCcyAmts or InstrmCcyAmts the holding value in the account base currency or the instrument currency, with statement totals in AcctBaseCcyTtlAmts.

Movements between two statements are reported in semt.017, and pending instructions in semt.018. See the guide to reading a custody statement and reconciliation breaks, which apply equally to semt.002.

Versions in common use

semt.002 key elements

Paths are relative to Document/SctiesBalCtdyRpt. Occurrence is from the base message (semt.002.001.11); market practice such as CBPR+ or a CSD’s rules can make an optional element mandatory or forbid it.

Rules worth knowing

• The Document carries no message identification of its own: on Swift and in T2S the message reference travels in the Business Application Header (BizMsgIdr), which corresponds to MT field 20C::SEME.
• Every aggregate balance needs ShrtLngInd. Quantities are written as plain decimals with a dot (150000, 12.5), not with the MT comma.
• Choices must be filled with exactly one option: for example StmtDtTm takes either Dt or DtTm, and Frqcy, UpdTp and StmtBsis take either a code (Cd) or a proprietary value (Prtry).

semt.002 XML example

The same statement as in the MT535 example: ZagTrader Test Bank (ZAGTAEADXXX), as custodian, reports account ZAG-SAFE-0001 of the asset manager FUNDGB2LXXX as at 22 October 2026 18:00 (Dubai time). Three instruments: 150,000 shares with 10,000 earmarked for a pending delivery, 50,000 shares, and a sukuk held in face amount. Values add up to AED 3,290,000.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:semt.002.001.11">
  <SctiesBalCtdyRpt>
    <Pgntn>
      <PgNb>1</PgNb>
      <LastPgInd>true</LastPgInd>
    </Pgntn>
    <StmtGnlDtls>
      <RptNb>
        <Shrt>112</Shrt>
      </RptNb>
      <StmtId>ZT535S2610220001</StmtId>
      <StmtDtTm>
        <DtTm>2026-10-22T18:00:00+04:00</DtTm>
      </StmtDtTm>
      <Frqcy>
        <Cd>DAIL</Cd>
      </Frqcy>
      <UpdTp>
        <Cd>COMP</Cd>
      </UpdTp>
      <StmtBsis>
        <Cd>SETT</Cd>
      </StmtBsis>
      <ActvtyInd>true</ActvtyInd>
      <SubAcctInd>false</SubAcctInd>
    </StmtGnlDtls>
    <AcctOwnr>
      <Id>
        <AnyBIC>FUNDGB2LXXX</AnyBIC>
      </Id>
    </AcctOwnr>
    <AcctSvcr>
      <Id>
        <AnyBIC>ZAGTAEADXXX</AnyBIC>
      </Id>
    </AcctSvcr>
    <SfkpgAcct>
      <Id>ZAG-SAFE-0001</Id>
    </SfkpgAcct>
    <BalForAcct>
      <FinInstrmId>
        <ISIN>AEZAGT000016</ISIN>
        <Desc>ZAG TEST HOLDINGS PJSC ORD</Desc>
      </FinInstrmId>
      <AggtBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <Qty>
          <Qty>
            <Qty>
              <Unit>150000</Unit>
            </Qty>
          </Qty>
        </Qty>
      </AggtBal>
      <AvlblBal>
        <Qty>
          <Qty>
            <Unit>140000</Unit>
          </Qty>
        </Qty>
      </AvlblBal>
      <NotAvlblBal>
        <Qty>
          <Unit>10000</Unit>
        </Qty>
      </NotAvlblBal>
      <PricDtls>
        <Tp>
          <Cd>MRKT</Cd>
        </Tp>
        <Val>
          <Amt Ccy="AED">12.5</Amt>
        </Val>
        <ValTp>
          <Yldd>false</Yldd>
        </ValTp>
        <QtnDt>
          <Dt>2026-10-22</Dt>
        </QtnDt>
      </PricDtls>
      <AcctBaseCcyAmts>
        <HldgVal>
          <Amt Ccy="AED">1875000</Amt>
        </HldgVal>
      </AcctBaseCcyAmts>
      <BalBrkdwn>
        <SubBalTp>
          <Cd>AWAS</Cd>
        </SubBalTp>
        <Qty>
          <Qty>
            <Qty>
              <Unit>140000</Unit>
            </Qty>
          </Qty>
        </Qty>
      </BalBrkdwn>
      <BalBrkdwn>
        <SubBalTp>
          <Cd>PEND</Cd>
        </SubBalTp>
        <Qty>
          <Qty>
            <Qty>
              <Unit>10000</Unit>
            </Qty>
          </Qty>
        </Qty>
      </BalBrkdwn>
    </BalForAcct>
    <BalForAcct>
      <FinInstrmId>
        <ISIN>AEZAGT000024</ISIN>
        <Desc>ZAG TEST CEMENT PJSC ORD</Desc>
      </FinInstrmId>
      <AggtBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <Qty>
          <Qty>
            <Qty>
              <Unit>50000</Unit>
            </Qty>
          </Qty>
        </Qty>
      </AggtBal>
      <AvlblBal>
        <Qty>
          <Qty>
            <Unit>50000</Unit>
          </Qty>
        </Qty>
      </AvlblBal>
      <PricDtls>
        <Tp>
          <Cd>MRKT</Cd>
        </Tp>
        <Val>
          <Amt Ccy="AED">8.4</Amt>
        </Val>
        <ValTp>
          <Yldd>false</Yldd>
        </ValTp>
        <QtnDt>
          <Dt>2026-10-22</Dt>
        </QtnDt>
      </PricDtls>
      <AcctBaseCcyAmts>
        <HldgVal>
          <Amt Ccy="AED">420000</Amt>
        </HldgVal>
      </AcctBaseCcyAmts>
    </BalForAcct>
    <BalForAcct>
      <FinInstrmId>
        <ISIN>AEZAGT000032</ISIN>
        <Desc>ZAG TEST SUKUK 5.25 2031</Desc>
      </FinInstrmId>
      <FinInstrmAttrbts>
        <DnmtnCcy>AED</DnmtnCcy>
        <MtrtyDt>2031-04-15</MtrtyDt>
        <IntrstRate>5.25</IntrstRate>
      </FinInstrmAttrbts>
      <AggtBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <Qty>
          <Qty>
            <Qty>
              <FaceAmt>1000000</FaceAmt>
            </Qty>
          </Qty>
        </Qty>
      </AggtBal>
      <PricDtls>
        <Tp>
          <Cd>MRKT</Cd>
        </Tp>
        <Val>
          <Rate>99.5</Rate>
        </Val>
        <ValTp>
          <Yldd>false</Yldd>
        </ValTp>
        <QtnDt>
          <Dt>2026-10-22</Dt>
        </QtnDt>
      </PricDtls>
      <AcctBaseCcyAmts>
        <HldgVal>
          <Amt Ccy="AED">995000</Amt>
        </HldgVal>
      </AcctBaseCcyAmts>
    </BalForAcct>
    <AcctBaseCcyTtlAmts>
      <TtlHldgsValOfStmt>
        <Amt Ccy="AED">3290000</Amt>
      </TtlHldgsValOfStmt>
    </AcctBaseCcyTtlAmts>
  </SctiesBalCtdyRpt>
</Document>

Document only, without a Business Application Header. All BICs, ISINs and names are made up; the ISINs carry valid check digits.

The nested Qty/Qty/Qty in AggtBal is not a typo: the outer level chooses between a quantity and a proprietary balance, the middle level between a single quantity and original-and-current face, the inner level between units, face amount and amortised value.

The share price is an amount (Val/Amt), the sukuk price a percentage rate (Val/Rate), as 90B ACTU and 90A PRCT in the MT535.

semt.002 and its MT equivalent

semt.002 is the counterpart of the custody form of the MT535 (:22F::STTY//CUST). The accounting form (STTY//ACCT) maps to semt.003. Most MT535 fields have a direct element, and the MX adds structured identifiers such as LEIs, explicit long/short indicators and holding values in two currencies.

Category 5 messages were not part of the November 2025 payments deadline, so custodians still send MT535 on FIN alongside semt.002. See ISO 20022 migration in securities versus payments.

Common errors and rejects

1. Positions do not reconcile

   The same checks as for the MT535 apply: compare the statement basis (StmtBsis) with your books, check the statement time, collect every page up to LastPgInd true, and treat a DELT statement as changes only.

   How to fix it

2. Schema error after a T2S or custodian release

   A version change alters the namespace (for example semt.002.001.11 to semt.002.001.12). Parsers that check the namespace strictly reject the new version until they are updated. Track your servicer’s release calendar.

3. Short positions read as long

   The quantity itself is never negative: the direction is in ShrtLngInd. A loader that ignores it will report short positions as holdings.

4. Valuation statement expected, custody report received

   semt.002 has no statement type: valuations with book values are sent as semt.003. Ask your custodian which of the two it sends, and do not expect prices on every line of a semt.002.

5. Sub-account positions missing

   When SubAcctInd is true the positions sit under SubAcctDtls/BalForSubAcct, not under BalForAcct. A loader that reads only BalForAcct sees an empty statement.

Related messages

• MT535Statement of Holdings
• semt.017Securities Transaction Posting Report
• MT536Statement of Transactions
• MT537Statement of Pending Transactions
• sese.024Securities Settlement Transaction Status Advice
• sese.025Securities Settlement Transaction Confirmation
• MT564Corporate Action Notification

• MT535 reconciliation breaks
• Header, account, holdings, balances, prices, transactions and pending items, and how to reconcile them.
• Securities messages stay on ISO 15022 alongside ISO 20022 after the November 2025 payments switch; the MT to MX map.

semt.002 questions

What is semt.002?

The ISO 20022 Securities Balance Custody Report: a statement of the securities a custodian or CSD holds for a client on one account at a given time. It is the counterpart of the custody MT535.

What is the difference between semt.002 and semt.003?

semt.002 is the custody statement for position reconciliation. semt.003 is the accounting statement with valuations. The MT535 does both, switched by :22F::STTY.

What is the difference between semt.002 and semt.017?

semt.002 gives the holdings at a point in time. semt.017 gives the movements booked during a period, with opening and closing balances per instrument.

Which semt.002 version does T2S use?

From the June 2026 release T2S uses semt.002.001.11; release R2026.NOV moves it to semt.002.001.12. Check your CSD’s documentation for its exact go-live dates.

Where is the message reference in a semt.002?

Not in the Document. The Business Application Header carries it in BizMsgIdr; StmtGnlDtls/StmtId identifies the statement itself.