Friday, February 3, 2017

Unique Message Identifiers (UMIDs)

Every message stored in Alliance Access can be uniquely identified based on information contained within parts of the header and text.
A Unique Message Identifier (UMID) consists of a User Unique Message Identifier (UUMID) plus a suffix, which makes it unique in the scope of Alliance Access. A UUMID, which is unique from the point of view of a single Alliance Access user, consists of the following:
I/O + Correspondent + ID (type of message) + Reference
where Reference is either TRN or MUR (MUR can be empty). However, note that the UUMID will not always be unique to a user, for example, if the user puts the same Reference twice in a single message.
The following table lists the information contained in the UMID:
Message identifier
This is a single-character direction indicator. "I" means an input message, that is, a message input to the network specified within the message, from Alliance Access. "O" - means an output message, that is, a message output from a network to Alliance Access.
This is 11 alphanumeric characters long and is the full BIC address of the sender or receiver of the message. If no specific branch code is given, then the last 3 characters of the BIC address default to "XXX". For messages with a direction indicator of "I", the BIC address identifies the receiver of the message. Where the direction indicator is "O", it identifies the sender of the message.
For SWIFT format, this is always a 3-character number and refers to the message type, for example, "100" for a customer transfer.
This is either the Transaction Reference Number (TRN) as given in field 20 of the message, or the Message User Reference (MUR) extracted from the User Header block of the message, in SWIFT format. This reference may be up to 16 characters in length. The exact form of reference used - TRN or MUR - is determined during the installation of SWIFT Message Syntax Tables into Alliance Access.
The suffix is a system-generated value that can help uniquely identify a message. The first part is the creation date of the message in YYMMDD format, a six-digit number. The second part consists of a 1-to-10 digit number that the system generates. The second part is generated only if a message is already present in the message file that has the same values for I/O, Correspondent, MT, and Reference. This number is incremental and unique for all messages.


  1. This comment has been removed by the author.

  2. Would you happen to know anything about PDE trailers added due to duplicate UUMID[s] and perhaps how to disable them from bring added in the first instance?