semt.017 Securities Transaction Posting Report

When semt.017 is used

The account servicer sends the semt.017 to the account owner or its agent for one safekeeping account (or a set of sub-accounts) and the period in StmtGnlDtls/StmtPrd, given as from and to dates or date-times. It is sent daily, intraday or at another agreed frequency, as a complete or delta report, and on a settlement-date (SETT) or trade-date (TRAD) basis in StmtBsis.

Each instrument with movements is one FinInstrmDtls block: the instrument identification, an optional price, the opening balance (OpngBal, first or intermediate), the closing balance (ClsgBal, final or intermediate) and one Tx per movement. Opening balance plus receipts minus deliveries must equal the closing balance.

Each Tx starts with its references. AcctOwnrTxId, the account owner’s instruction reference, is mandatory in every transaction; for movements the owner did not instruct, such as corporate action credits, NONREF is commonly used. Next come the servicer’s reference (AcctSvcrTxId), the market infrastructure reference (MktInfrstrctrTxId), the trade reference, the common reference and the corporate action event reference (CorpActnEvtId).

TxDtls describes the movement: the activity (TxActvty: SETT, CORP, CLAI, COLL or BOLE), the settlement transaction type (for example TRAD) or corporate action event type (for example BONU), the direction (SctiesMvmntTp: RECE or DELI), the payment type (Pmt: APMT or FREE), the posted quantity (PstngQty), the cash posted with its credit/debit sign (PstngAmt), the dates, the effective settlement date (FctvSttlmDt, mandatory), the delivering and receiving settlement parties, and RvslInd for a reversal.

For the holdings themselves, see semt.002; for instructions not yet settled, semt.018 or the per-instruction status advice sese.024; for a single settlement confirmation, sese.025. See the guide to reading a custody statement.

Versions in common use

semt.017 key elements

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

Rules worth knowing

• Every transaction must carry AcctOwnrTxId, as the MT536 requires 20C::RELA in each transaction.
• The Document has no message identification element; the message reference travels in the Business Application Header (BizMsgIdr).
• Amounts and quantities use a dot as decimal mark and are never negative: the direction comes from SctiesMvmntTp, CdtDbt and ShrtLngInd.

semt.017 XML example

The same statement as in the MT536 example: movements of 22 October 2026 on account ZAG-SAFE-0001 of FUNDGB2LXXX. A purchase of 50,000 AEZAGT000016 settled against payment (opening 100,000, closing 150,000) and a bonus issue credited 5,000 AEZAGT000024 (opening 45,000, closing 50,000).

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:semt.017.001.12">
  <SctiesTxPstngRpt>
    <Pgntn>
      <PgNb>1</PgNb>
      <LastPgInd>true</LastPgInd>
    </Pgntn>
    <StmtGnlDtls>
      <RptNb>
        <Shrt>112</Shrt>
      </RptNb>
      <StmtId>ZT536S2610220001</StmtId>
      <StmtPrd>
        <FrDtToDt>
          <FrDt>2026-10-22</FrDt>
          <ToDt>2026-10-22</ToDt>
        </FrDtToDt>
      </StmtPrd>
      <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>
    <SfkpgAcct>
      <Id>ZAG-SAFE-0001</Id>
    </SfkpgAcct>
    <FinInstrmDtls>
      <FinInstrmId>
        <ISIN>AEZAGT000016</ISIN>
        <Desc>ZAG TEST HOLDINGS PJSC ORD</Desc>
      </FinInstrmId>
      <OpngBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <OpngBal>
          <Frst>
            <Qty>
              <Unit>100000</Unit>
            </Qty>
          </Frst>
        </OpngBal>
      </OpngBal>
      <ClsgBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <ClsgBal>
          <Fnl>
            <Qty>
              <Unit>150000</Unit>
            </Qty>
          </Fnl>
        </ClsgBal>
      </ClsgBal>
      <Tx>
        <AcctOwnrTxId>ZTBUY20261020A01</AcctOwnrTxId>
        <AcctSvcrTxId>CUST7781234</AcctSvcrTxId>
        <TxDtls>
          <TxActvty>
            <Cd>SETT</Cd>
          </TxActvty>
          <SttlmTxOrCorpActnEvtTp>
            <SctiesTxTp>
              <Cd>TRAD</Cd>
            </SctiesTxTp>
          </SttlmTxOrCorpActnEvtTp>
          <SctiesMvmntTp>RECE</SctiesMvmntTp>
          <Pmt>APMT</Pmt>
          <PstngQty>
            <Qty>
              <Unit>50000</Unit>
            </Qty>
          </PstngQty>
          <PstngAmt>
            <Amt Ccy="AED">620000</Amt>
            <CdtDbt>DBIT</CdtDbt>
          </PstngAmt>
          <TradDt>
            <Dt>
              <Dt>2026-10-20</Dt>
            </Dt>
          </TradDt>
          <FctvSttlmDt>
            <Dt>2026-10-22</Dt>
          </FctvSttlmDt>
          <SttlmDt>
            <Dt>
              <Dt>2026-10-22</Dt>
            </Dt>
          </SttlmDt>
          <DlvrgSttlmPties>
            <Dpstry>
              <Id>
                <AnyBIC>CSDXAEADXXX</AnyBIC>
              </Id>
            </Dpstry>
            <Pty1>
              <Id>
                <AnyBIC>BRKRAEADXXX</AnyBIC>
              </Id>
            </Pty1>
          </DlvrgSttlmPties>
        </TxDtls>
      </Tx>
    </FinInstrmDtls>
    <FinInstrmDtls>
      <FinInstrmId>
        <ISIN>AEZAGT000024</ISIN>
        <Desc>ZAG TEST CEMENT PJSC ORD</Desc>
      </FinInstrmId>
      <OpngBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <OpngBal>
          <Frst>
            <Qty>
              <Unit>45000</Unit>
            </Qty>
          </Frst>
        </OpngBal>
      </OpngBal>
      <ClsgBal>
        <ShrtLngInd>LONG</ShrtLngInd>
        <ClsgBal>
          <Fnl>
            <Qty>
              <Unit>50000</Unit>
            </Qty>
          </Fnl>
        </ClsgBal>
      </ClsgBal>
      <Tx>
        <AcctOwnrTxId>NONREF</AcctOwnrTxId>
        <CorpActnEvtId>ZTCA2026BONU07</CorpActnEvtId>
        <TxDtls>
          <TxActvty>
            <Cd>CORP</Cd>
          </TxActvty>
          <SttlmTxOrCorpActnEvtTp>
            <CorpActnEvtTp>
              <Cd>BONU</Cd>
            </CorpActnEvtTp>
          </SttlmTxOrCorpActnEvtTp>
          <SctiesMvmntTp>RECE</SctiesMvmntTp>
          <Pmt>FREE</Pmt>
          <PstngQty>
            <Qty>
              <Unit>5000</Unit>
            </Qty>
          </PstngQty>
          <FctvSttlmDt>
            <Dt>2026-10-22</Dt>
          </FctvSttlmDt>
        </TxDtls>
      </Tx>
    </FinInstrmDtls>
  </SctiesTxPstngRpt>
</Document>

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

The purchase shows a DBIT posting amount: cash left the client’s account against the securities received. The bonus credit has no posting amount because it is free of payment.

semt.017 and its MT equivalent

semt.017 is the ISO 20022 counterpart of the MT536. The structure is the same; the MX makes the cash direction explicit and adds structured parties, LEIs and fields for distributed-ledger holdings.

Category 5 messages were not part of the November 2025 payments deadline, so MT536 remains in use on FIN alongside semt.017. See ISO 20022 migration in securities versus payments.

Common errors and rejects

1. Opening plus movements does not equal closing

   Check for intermediate balances on continuation pages, reversals (RvslInd) that must be netted against the original, and delta statements that leave out movements already reported.

   How to fix it

2. Movement with NONREF cannot be matched

   The owner did not instruct it. Use TxActvty and CorpActnEvtId or AcctSvcrTxId to identify a corporate action, market claim or collateral movement.

3. Cash booked with the wrong sign

   The amount is always positive; CdtDbt gives the direction. A loader that ignores it books every purchase as a cash credit.

4. Schema error after a release

   T2S and custodians move to new versions on their release dates (for example semt.017.001.12 to .14 in T2S R2026.NOV). A parser bound to one namespace rejects the new version until updated.

5. Trade-date statement used to explain settled positions

   With StmtBsis TRAD the statement lists trades by trade date, including unsettled ones. Use a SETT-basis statement to explain the change between two settled semt.002 statements.

Related messages

• MT536Statement of Transactions
• semt.002Securities Balance Custody Report
• MT535Statement of Holdings
• MT537Statement of Pending Transactions
• sese.024Securities Settlement Transaction Status Advice
• sese.025Securities Settlement Transaction Confirmation
• MT544Receive Free Confirmation
• MT545Receive Against Payment Confirmation
• MT546Deliver Free Confirmation
• MT547Deliver Against Payment Confirmation

• 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.

Codes used in semt.017

• TRAD
• BONU

semt.017 questions

What is semt.017?

The ISO 20022 Securities Transaction Posting Report: a statement of every securities movement booked on an account during a period, per instrument, with opening and closing balances. It is the counterpart of the MT536.

What is the difference between semt.017 and sese.025?

sese.025 confirms one settled instruction as soon as it settles. semt.017 lists all movements of a period, including ones the owner did not instruct.

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

semt.002 is a snapshot of holdings at a point in time; semt.017 explains how holdings changed during a period.

Which semt.017 version does T2S use?

semt.017.001.12 from the June 2026 release, and semt.017.001.14 from release R2026.NOV. Confirm the go-live date with your CSD.

What does NONREF mean in AcctOwnrTxId?

That there is no instruction from the account owner behind the movement, for example a corporate action credit. The element is mandatory, so a placeholder is sent.