ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

setr.004 — Subscription Bulk Order Cancellation Request

Subscription order cancellation. Request from the investor or distributor to the transfer agent to cancel — fully or partially — one or several orders previously sent, within the still-open window (before the NAV cut-off).

Purpose and place in the flow

setr.004 asks the transfer agent to cancel a subscription order previously sent via setr.001 or setr.010. The TA checks whether the order is still cancellable: if the cancellation arrives before NAV cut-off, the order is withdrawn and never executed; after cut-off, the order has already been priced and the cancellation is refused (a reversal would then go through different flows).

The cancellation request can be partial (amount/quantity reduction) or total (full withdrawal). For a cancellation after cut-off but before settlement, some TAs accept a "late cancellation" but it is exceptional and chargeable.

XML structure

  • MsgId — Unique cancellation request identifier.
  • PoolRef — Pool reference for bulk cancellations.
  • PrvsRef — Reference to the previous message (the original setr.001/010).
  • OrdrRef — Reference of the order to cancel.
  • CxlByOrdrDtls (Cancellation by Order Details) — details of the order(s) to cancel.
  • CpyDtls — Copy of the original message identifier for traceability.

Key fields

ElementNameUsage
MsgId/IdMessage IDUnique cancellation identifier on the sender side.
PrvsRef/RefPrevious Message ReferenceMsgId of the original setr.001.
OrdrRef/RefOrder ReferenceOrdrRef of the order to cancel.
CxlByOrdrDtls/MstrRefMaster ReferenceLot master reference.
CpyDtls/OrgnlMsgIdOriginal Message IDCopy of the original message ID (traceability).

XML example

Cancellation of order ACME-SBSC-2026-187 (EUR 12,500 on Amundi Funds Global Equity) previously sent via setr.001 on 15 May 2026 at 09:30. The cancellation is sent at 10:45, before the 12:00 NAV cut-off — cancellation is eligible:

xml setr-004-cancellation-request.xml
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:setr.004.001.04">
  <SbcptBlkOrdrCxlReq>
    <MsgId>
      <Id>ACME-CXL-20260515-001</Id>
      <CreDtTm>2026-05-15T10:45:00+02:00</CreDtTm>
    </MsgId>
    <PoolRef>
      <Ref>POOL-2026-05-15</Ref>
    </PoolRef>
    <PrvsRef>
      <Ref>ACME-SBSC-20260515-001</Ref>
    </PrvsRef>
    <OrdrRef>
      <Ref>ACME-SBSC-2026-187</Ref>
    </OrdrRef>
    <CxlByOrdrDtls>
      <MstrRef>MAST-2026-05-15-ACME</MstrRef>
      <OrdrRef>
        <Ref>ACME-SBSC-2026-187</Ref>
      </OrdrRef>
    </CxlByOrdrDtls>
    <CpyDtls>
      <OrgnlMsgId>ACME-SBSC-20260515-001</OrgnlMsgId>
    </CpyDtls>
  </SbcptBlkOrdrCxlReq>
</Document>

Common pitfalls

  • Cancellation after cut-off — a setr.004 sent after NAV cut-off cannot be handled as a simple cancellation. Request a "trade reversal" with the TA if needed.
  • Wrong OrdrRef — the reference must be strictly identical to the original setr.001. An error breaks reconciliation.
  • Ambiguous partial cancellation — for a partial cancellation, state the new amount/quantity through a complementary setr.001 amendment, or use the amendment flow instead of a cancellation.
  • PrvsRef vs OrgnlMsgId — common confusion. PrvsRef = previous message reference. OrgnlMsgId = original message ID (the originating setr.001).
  • Cancellation without setr.005 received — cancellation is only confirmed by setr.005. Until received, consider the order still active.
  • setr.001 — Subscription Order, the message being cancelled.
  • setr.005 — Subscription Bulk Order Cancellation Status Report (acceptance/refusal).
  • setr.010 — Subscription Bulk Order (bulk variant).
  • setr.012 — Subscription Bulk Order Confirmation (to be updated if cancellation accepted).
  • setr.011 — Subscription Order Confirmation Cancellation (if the order was already confirmed).