CashTransfer

By definition, to specify a cash transfer, we need to say how much we want to transfer, who is the payer (correspondent) and who is the receiver (beneficiary). Those terms are used in the settlement instruction and allow us to define the direction of the movement.

Nested view
Tree view

Field	Type	Description	Print form title	FFSM title	Properties	Conditions
suppress	xsd:boolean	Indicate if this transfer should be suppressed. Absence of this flag means that the transfer should not be suppressed.	Suppress.		0-1, ncf	This is not used in messages to the repository.
@id	xsd:ID				1-1, ncf
transferAmount	Money	The money to transfer.	Transfer amount.		1-1, mre
payerPartyReference	PartyReference	A reference to the party responsible for making the payments defined by this structure.	Payer.	Party code.	0-1, mre, mfr
payerAccountReference	AccountReference	A reference to the account of the payer party (specified by payerPartyReference) responsible for making the payments defined by this structure.	Payer's account.	Party's client.	0-1, ncf	At the first stage this element is not used in the repository messages.
receiverPartyReference	PartyReference	A reference to the party that receives the payments corresponding to this structure.	Receiver.	Party code.	0-1, mre, mfr
receiverAccountReference	AccountReference	A reference to the account of the receiver party (specified by receiverPartyReference) that receives the payments corresponding to this structure.	Receiver's account.	Party's client.	0-1, ncf	At the first stage this element is not used in the repository messages.
attributions	Attributions	For accounting, reporting or regulatory reasons, the transfer may have to be explained in a series of individual amounts. It may be possible for example to break down a transfer amount into constituents (gross, tax, net) or into individual amounts (interest, penalty) that would be netted at the transfer level. The attributions structure allows participants to explain their transfer amounts for better traceability. This is strictly optional.	Transfer attributions.		0-1

Collapse All | Expand All

CashTransfer

transferAmount(Money)

	The money to transfer.

currency(Currency)

	The currency in which an amount is denominated.
	Code of currency of denomination.

amount(decimal)

	The monetary quantity in currency units. For the purposes of reporting to the repository, an amount is specified with 7 decimal places. For example, 350.1234567. The value of 350.45 would be represented as 350.4500000.

payerPartyReference(PartyReference)

	A reference to the party responsible for making the payments defined by this structure.
	Party code.

receiverPartyReference(PartyReference)

	A reference to the party that receives the payments corresponding to this structure.
	Party code.

attributions(Attributions)

For accounting, reporting or regulatory reasons, the transfer may have to be explained in a series of individual amounts. It may be possible for example to break down a transfer amount into constituents (gross, tax, net) or into individual amounts (interest, penalty) that would be netted at the transfer level. The attributions structure allows participants to explain their transfer amounts for better traceability. This is strictly optional.

settlementCurrency(Currency)

The currency that is used for all the attributions expressed with settlementAmount. The reason for this is to avoid repeating the currency (for example using FpML:Money) for every attribution amount in the structure. We therefore assume that attributions are expressed in a maximum of three currencies, which we specify here. The settlementCurrency is assumed to be the settlement currency of the trade in general cases.

baseCurrency(Currency)

	The currency that is used for all the attributions expressed with baseAmount. The baseCurrency is usually USD within the firm, but it is in fact driven by the accounting engine expectations.

underlyingCurrency(Currency)

	The currency that is used for all the attributions expressed with underlyingAmount. Underlying currency is the currency of issuance for the underlying instrument. So if you need to express attributions on a Repo settling in EUR but with GBP instruments, you would specify underlyingCurrency to be GBP.

attribution(Attribution)

	The attributions go here. There is no limit on the number of attributions.

type(AttributionType)

	The attribution type. The cash settlement amount specified in the enclosing transfer will be broken down into several subcomponents (like a PandL explain), and the type of the breakdown is defined here. Typical values are in a scheme.

settlementAmount(decimal)

An amount expressed in the settlement currency that was indicated in the enclosing Attributions structure. This is done to avoid repeating the currency for every amount when we know that attributions are expressed in a consistent way, with the same currencies.

baseAmount(decimal)

An amount expressed in the base currency defined in the enclosing Attributions structure (see baseCurrency). If this optional field is present, baseCurrency must be defined in the enclosing structure.

underlyingAmount(decimal)

An amount expressed in the currency of an underlyer (see underlyingCurrency). If this field is present then the underlyingCurrency field in the enclosing structure must be defined.