semt.015 — Intra-Position Movement Status Advice

The status of an intra-position movement request. Issued by the custodian / CSD in response to a semt.014 (Instruction), it signals whether the request is accepted, rejected, or pending — a visibility step before final confirmation by semt.013.

Purpose and place in the flow

semt.015 acts as intermediate step between the request (semt.014) and the confirmation (semt.013). Possible statuses in PrcgSts/Sts/Cd:

• RECE — Received, the request is received by the CSD.
• ACPT — Accepted, ready for execution.
• PEND — Pending, awaiting a condition (business day, validation, etc.).
• REJT — Rejected, refusal with detailed reason.
• MTCH — Matched (rarely used in intra-position, but valid for consistency with settlement).

On real-time markets (T2S, Euroclear ESES), the full cycle (semt.014 → semt.015 → semt.013) is typically < 5 minutes. On batch markets (some emerging CSDs), the cycle can spread over a day.

XML structure

• Id — unique status advice identifier.
• TxIdDtls — custodian (AcctOwnrTxId) and CSD (AcctSvcrTxId) identifiers.
• PrcgSts — Processing Status: status + reason.
• FinInstrmId — ISIN.
• AcctOwnr / SfkpgAcct — owner and account.
• IntraPosDtls — movement details (BalFr, BalTo, quantity).

Key fields

• PrcgSts/Sts/Cd — status (RECE, ACPT, PEND, REJT, MTCH).
• PrcgSts/Rsn/Cd — reason (NEXT = await next business day, INSF = insufficient balance, REGL = regulatory hold).
• PrcgSts/Rsn/AddtlRsnInf — narrative.

XML example

Euroclear Belgium notifies BNP Paribas that the 20 May intra-position movement request (AVAI → BLCK swing on 80k€ OAT 2032) is pending the start of next business day:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:semt.015.001.07">
  <IntraPosMvmntStsAdvc>
    <Id>IPMS-20260520-EOCX-001</Id>
    <TxIdDtls>
      <AcctOwnrTxId>BNPP-INTPOS-20260520-001</AcctOwnrTxId>
      <AcctSvcrTxId>EOCXBEBB-IP-7894561</AcctSvcrTxId>
    </TxIdDtls>
    <PrcgSts>
      <Sts>
        <Cd>PEND</Cd>
      </Sts>
      <Rsn>
        <Cd>NEXT</Cd>
        <AddtlRsnInf>AWAITING NEXT BUSINESS DAY FOR BLOCKING ACTIVATION — CSA-2024-001</AddtlRsnInf>
      </Rsn>
    </PrcgSts>
    <FinInstrmId>
      <ISIN>FR0014007T87</ISIN>
    </FinInstrmId>
    <AcctOwnr>
      <Id><AnyBIC><AnyBIC>BNPAFRPP</AnyBIC></AnyBIC></Id>
    </AcctOwnr>
    <SfkpgAcct><Id>BNPPSAFEKEEP-EUR-001</Id></SfkpgAcct>
    <IntraPosDtls>
      <SttlmQty>
        <Qty><FaceAmt Ccy="EUR">80000.00</FaceAmt></Qty>
      </SttlmQty>
      <BalFr><Cd>AVAI</Cd></BalFr>
      <BalTo><Cd>BLCK</Cd></BalTo>
    </IntraPosDtls>
  </IntraPosMvmntStsAdvc>
</Document>

• PrcgSts/Sts/Cd = PEND — Pending.
• PrcgSts/Rsn/Cd = NEXT — reason: rollover to next business day.
• BalFr/BalTo — carry-over from semt.014.
• AcctOwnrTxId and AcctSvcrTxId — both references for bilateral matching.

Common pitfalls

• No RECE — on modern markets, an explicit RECE is not mandatory before an ACPT. On batch markets, it's typically issued to materialise receipt.
• REJT without Rsn — a reject with no reason prevents correction. Always document via Cd + AddtlRsnInf.
• Prolonged PEND — a PEND exceeding 24h without transition to ACPT or REJT warrants escalation. Explicit follow-up.
• Inapplicable MTCH — intra-position has no bilateral matching (one account involved). MTCH status is rare and typically signals incorrect usage.
• Ledger not updated before ACPT — the custodian must not start booking the movement as effective before an explicit ACPT status.

Related messages

• semt.014 — Intra-Position Movement Instruction (the request).
• semt.013 — Intra-Position Movement Confirmation (the execution).
• MT508 — SWIFT FIN equivalent.