Message PayManagementReport Scenario base

SYNOPSIS: PayManagementReport(35=EA) may be used to respond to the PayManagementRequest(35=DY) message. It provides the status of the request (e.g. accepted, disputed) and may provide additional information related to the request. PayManagementReport(35=EA) may also be sent unsolicited by the broker to a client. In which case the client may acknowledge and resolve disputes out-of-band or with a simple PayManagementReportAck(35=EB). PayManagementReport(35=EA) may also be sent unsolicited to report the progress status of the payment itself with PayReportTransType(2804)=2 (Status).
ELABORATION: It should be noted that this message, in the context of operational communication between investment managers and their brokers, is intended to agree and confirm on payment(s) to be made or received during the life of a contract.

ID	MsgType	Abbr	Flow
161	EA	PayMgmtRpt

Pedigree

Added	EP	Updated	EP	Deprecated	EP
FIX.5.0SP2	249

Responses

None

Members

PayManagementReport base members

ID	Name	Abbr	Presence	Description
1024	StandardHeader	BaseHeader	required	SYNOPSIS: The standard FIX message header ELABORATION:
2799	PayReportID	RptID	required	SYNOPSIS: Unique ID of the PayManagementReport(35=EA) message.
2812	PayRequestID	ReqID	optional	SYNOPSIS: Unique ID of the PayManagementRequest(35=DY) message.
2804	PayReportTransType	TxnTyp	required	SYNOPSIS: Identifies the message transaction type.
2803	PayReportRefID	RptRefID	optional	SYNOPSIS: Reference identifier of the PayManagementReport(35=EA). To be used with PayReportTransType(2804)=1 (Replace).
2805	ReplaceText	RplcTxt	optional	SYNOPSIS: Identifies the reason for amendment.
2802	EncodedReplaceTextLen	EncRplcTxtLen	optional	SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedReplaceText(2801) field.
2801	EncodedReplaceText	EncRplcTxt	optional	SYNOPSIS: Encoded (non-ASCII characters) representation of the ReplaceText(2805) field in the encoded format specified via the MessageEncoding(347) field. If used, the ASCII (English) representation should also be specified in the ReplaceText(2805) field.
2813	PayRequestStatus	ReqStat	optional	SYNOPSIS: Identifies status of the request being responded to.
2800	PayDisputeReason	DsptRsn	optional	SYNOPSIS: Used to provide the reason for disputing a request or report. See https://www.fixtrading.org/packages/PayDisputeReason for the list of applicable values.
1328	RejectText	RejTxt	optional	SYNOPSIS: Identifies the reason for rejection.
1664	EncodedRejectTextLen	EncRejTxtLen	optional	SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedRejectText(1665) field.
1665	EncodedRejectText	EncRejTxt	optional	SYNOPSIS: Encoded (non-ASCII characters) representation of the RejectText(1328) field in the encoded format specified via the MessageEncoding(347) field. If used, the ASCII (English) representation should also be specified in the RejectText(1328) field.
715	ClearingBusinessDate	BizDt	optional	SYNOPSIS: The business date for which the trade is expected to be cleared.
60	TransactTime	TxnTm	required	SYNOPSIS: Timestamp when the business transaction represented by the message occurred.
58	Text	Txt	optional	SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354	EncodedTextLen	EncTxtLen	optional	SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355	EncodedText	EncTxt	optional	SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
1003	Instrument	Instrmt	optional	SYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX. ELABORATION:
2209	RelatedTradeGrp	ReltdTrd	optional	SYNOPSIS: This component is used to identify trades that are related to each other for a business purpose, such as netting of forwards. This component should not be used in lieu of explicit FIX fields that denote specific semantic relationships, but rather should be used when no such fields exist. ELABORATION:
1012	Parties	Pty	optional	SYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource. ELABORATION:
2265	PostTradePayment	PostTrdPmt	required	SYNOPSIS: This component specifies the details of a payment between the parties involved. ELABORATION:
2139	SettlDetails	SettlDetails	optional	SYNOPSIS: ELABORATION:
1025	StandardTrailer	Trlr	required	SYNOPSIS: The standard FIX message trailer ELABORATION: