ZagTrader

camt: Cash Management

camt.102 Create Standing Order

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

camt.102 is the ISO 20022 CreateStandingOrder message in the Cash Management business area (camt). The latest version is camt.102.001.03, and 3 versions are in the repository.

Message
CreateStandingOrder
Latest version
camt.102.001.03
Submitting organisation
Swift
MT equivalent
None listed

In use: published in the current ISO 20022 catalogue.

What camt.102 is for

The CreateStandingOrder message is sent by a member to the transaction administrator.

It is used to create a permanent order for the transfer of funds between two accounts belonging to the same member and being held at the transaction administrator.

Based on the criteria defined in the CreateStandingOrder message, the transaction administrator will execute or reject the requested creation and respond with a Receipt message as a reply to the request.

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

camt.102 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

VersionRegistration statusPublished in
camt.102.001.03latestRegisteredLatest version set
camt.102.001.02RegisteredPrevious version set
camt.102.001.01RegisteredArchive

camt.102 message structure

The building blocks of camt.102.001.03 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

  • Document [1..1]
    • CretStgOrdr CreateStandingOrder [1..1]
      • MsgHdr Message Header [1..1]MessageHeader1

        Common business identification for the message.

        • MsgId Message Identification [1..1]Max35Text

          Point to point reference, as assigned by the sender, to unambiguously identify the message.

        • CreDtTm Creation Date Time [0..1]ISODateTime

          Date and time at which the message was created.

      • StgOrdrId Standing Order Identification [1..1]StandingOrderIdentification8

        Identifies the standing order.

        • Id Identification [0..1]Max35Text

          Unique and unambiguous identification for a standing order, as assigned by the account servicer or the account owner.

        • Acct Account [1..1]CashAccount40

          Business relationship between two entities; one entity is the account owner, the other entity is the account servicer.

          • Id Identification [0..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • AcctOwnr Account Owner [0..1]BranchAndFinancialInstitutionIdentification8

          Party that legally owns the account.

          • FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
          • BrnchId Branch Identification [0..1]BranchData5
      • ValSet Value Set [1..1]StandingOrder10

        Set of values for the standing order.

        • Amt Amount [0..1]Amount2Choice (choice)

          Amount of money and currency to be transferred when a payment instruction is created as a result of a standing order.

          • AmtWthtCcy Amount Without Currency [1..1]ImpliedCurrencyAndAmount
          • AmtWthCcy Amount With Currency [1..1]ActiveCurrencyAndAmount
        • Cdtr Creditor [0..1]BranchAndFinancialInstitutionIdentification8

          Party to which an amount of money is due.

          • FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
          • BrnchId Branch Identification [0..1]BranchData5
        • CdtrAcct Creditor Account [0..1]CashAccount40

          Cash account credited from a standing order mechanism.

          • Id Identification [0..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • Dbtr Debtor [0..1]BranchAndFinancialInstitutionIdentification8

          Party that owes an amount of money to the (ultimate) creditor.

          • FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
          • BrnchId Branch Identification [0..1]BranchData5
        • DbtrAcct Debtor Account [0..1]CashAccount40

          Cash account debited from a standing order mechanism.

          • Id Identification [0..1]AccountIdentification4Choice (choice)
          • Tp Type [0..1]CashAccountType2Choice (choice)
          • Ccy Currency [0..1]ActiveOrHistoricCurrencyCode
          • Nm Name [0..1]Max70Text
          • Prxy Proxy [0..1]ProxyAccountIdentification1
        • ExctnTp Execution Type [0..1]ExecutionType1Choice (choice)

          Defines whether the standing order is executed through a time-based or an event-based trigger.

          • Tm Time [1..1]ISOTime
          • Evt Event [1..1]EventType1Choice (choice)
        • Frqcy Frequency [0..1]Frequency2Code

          Regularity with which payment instructions are to be created and processed as a result of the standing order, such as daily, weekly, or monthly.

        • VldtyPrd Validity Period [0..1]DatePeriod2Choice (choice)

          Dates during which the standing order is in effect.

          • FrDt From Date [1..1]ISODate
          • ToDt To Date [1..1]ISODate
          • FrToDt From To Date [1..1]DatePeriod2
        • ZeroSweepInd Zero Sweep Indicator [0..1]TrueFalseIndicator

          Indicates whether the standing order is defined as a zero sweeping order.

      • SplmtryData Supplementary Data [0..*]SupplementaryData1

        Additional information that cannot be captured in the structured elements and/or any other specific block.

        • PlcAndNm Place And Name [0..1]Max350Text

          Unambiguous reference to the location where the supplementary data must be inserted in the message instance.

        • Envlp Envelope [1..1]SupplementaryDataEnvelope1

          Technical element wrapping the supplementary data.

Have a camt.102 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

External code sets used in camt.102

These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.

camt.102 questions

What is the latest version of camt.102?
The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.102.001.03.
What is the root element of camt.102?
The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.102.001.03, and its message element is CretStgOrdr (CreateStandingOrder).
Is there an MT equivalent of camt.102?
No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.