fpml:confirmationAgreed
The confirmationAgreed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester agrees with it.
Element information
Namespace: http://www.fpml.org/FpML-5/confirmation
Schema document: fpml-confirmation-processes-5-5.xsd
Type: fpml:ConfirmationAgreed
Properties: Global, Qualified
Content
- Sequence [1..1]
- fpml:header [1..1]
- fpml:validation [0..*] A list of validation sets the sender asserts the document is valid with respect to.
- fpml:parentCorrelationId [0..1] An optional identifier used to correlate between related processes
- fpml:correlationId [1..1] A qualified identifier used to correlate between messages
- fpml:sequenceNumber [0..1] A numeric value that can be used to order messages with the same correlation identifier from the same sender.
- fpml:onBehalfOf [0..1] Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Except for this case, there should be no more than two onABehalfOf references in a message.
- Choice [0..1]
- Sequence [1..1]
- fpml:originatingEvent [0..1]
- fpml:trade [1..1]
- fpml:amendment
- fpml:increase
- Sequence [1..1]
- fpml:terminatingEvent [0..1] This may be used to describe why a trade was terminated.
- fpml:termination [1..1]
- fpml:novation
- fpml:change
- fpml:optionExercise
- fpml:optionExpiry [1..*]
- fpml:deClear
- fpml:withdrawal
- fpml:additionalEventAbstract [1..1] The additionalEvent element is an extension/substitution point to customize FpML and add additional events.
from subst. group fpml:additionalEvent - Sequence [1..1]
- Sequence [0..1]
- fpml:party [1..*] A legal entity or a subdivision of a legal entity.Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.
- fpml:account [0..*] Optional account information used to precisely define the origination and destination of financial instruments.
from type fpml:ResponseMessagefrom group fpml:Validation.modelfrom group fpml:CorrelationAndOptionalSequence.modelfrom group fpml:Correlation.modelfrom group fpml:CorrelationId.modelfrom group fpml:Sequence.modelfrom group fpml:OnBehalfOf.modelfrom group fpml:Events.modelfrom group fpml:PartiesAndAccounts.model
Attributes
Name | Occ | Type | Description | Notes |
---|---|---|---|---|
fpmlVersion | [1..1] | Anonymous | Indicate which version of the FpML Schema an FpML message adheres to. | from group fpml:VersionAttributes.atts |
expectedBuild | [0..1] | xsd:positiveInteger | This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated. | from group fpml:VersionAttributes.atts |
actualBuild | [0..1] | xsd:positiveInteger | The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same. | Fixed value is "8". from group fpml:VersionAttributes.atts |
Sample instance
<confirmationAgreed fpmlVersion="5-5" xsi:schemaLocation="http://www.fpml.org/FpML-5/confirmation ../../fpml-main-5-5.xsd http://www.w3.org/2000/09/xmldsig# ../../xmldsig-core-schema.xsd"> <header> <messageId messageIdScheme="http://www.example.com/messageId">MS/2006/04/02/15-12</messageId> <inReplyTo messageIdScheme="http://www.example.com/messageId">MS/2006/04/02/15-10</inReplyTo> <sentBy>XYZBICXXX</sentBy> <sendTo>DEFBICXXX</sendTo> <creationTimestamp>2006-04-02T15:38:00+05:00</creationTimestamp> </header> <correlationId correlationIdScheme="http://www.example.com/conversationId">CS/2006/04/02/32-12</correlationId> <trade> <tradeHeader> <partyTradeIdentifier> <partyReference href="party1"/> <tradeId tradeIdScheme="http://www.xyzbank.com/cd-trade-id">xyz1234</tradeId> </partyTradeIdentifier> <partyTradeIdentifier> <partyReference href="party2"/> <tradeId tradeIdScheme="http://www.abcbank.com/cd-trade-id">abc1234</tradeId> </partyTradeIdentifier> <partyTradeInformation> <partyReference href="party1"/> <relatedParty> <partyReference href="party3"/> <role>ArrangingBroker</role> </relatedParty> </partyTradeInformation> <partyTradeInformation> <partyReference href="party2"/> <relatedParty> <partyReference href="party3"/> <role>ArrangingBroker</role> </relatedParty> </partyTradeInformation> <tradeDate>2002-12-03</tradeDate> </tradeHeader> <creditDefaultSwap> <generalTerms> <effectiveDate> <unadjustedDate>2002-12-04</unadjustedDate> </effectiveDate> <scheduledTerminationDate> <unadjustedDate>2007-09-06</unadjustedDate> </scheduledTerminationDate> <buyerPartyReference href="party1"/> <sellerPartyReference href="party2"/> <referenceInformation> <referenceEntity id="referenceEntity"> <entityName>Tenet Healthcare Corporation</entityName> <entityId entityIdScheme="http://www.fpml.org/spec/2003/entity-id-RED-1-0">8G836J</entityId> </referenceEntity> <referenceObligation> <bond> <instrumentId instrumentIdScheme="http://www.fpml.org/spec/2002/instrument-id-CUSIP-1-0">88033GAT7</instrumentId> <couponRate>0.06</couponRate> <maturity>2011-12-01</maturity> </bond> <primaryObligorReference href="referenceEntity"/> </referenceObligation> </referenceInformation> </generalTerms> <feeLeg> <periodicPayment> <paymentFrequency> <periodMultiplier>3</periodMultiplier> <period>M</period> </paymentFrequency> <firstPaymentDate>2003-03-06</firstPaymentDate> <rollConvention>6</rollConvention> <fixedAmountCalculation> <fixedRate>0.01</fixedRate> </fixedAmountCalculation> </periodicPayment> </feeLeg> <protectionTerms> <calculationAmount> <currency>USD</currency> <amount>5000000</amount> </calculationAmount> <creditEvents> <restructuring> <applicable>true</applicable> </restructuring> </creditEvents> </protectionTerms> </creditDefaultSwap> <documentation> <masterConfirmation> <masterConfirmationType>ISDA2003CreditNorthAmerican</masterConfirmationType> <masterConfirmationDate>2003-06-06</masterConfirmationDate> </masterConfirmation> </documentation> </trade> <party id="party1"> <partyId>XYZBICXXX</partyId> <partyName>XYZ Bank</partyName> </party> <party id="party2"> <partyId>ABCBICXXX</partyId> <partyName>ABC Bank</partyName> </party> <party id="party3"> <partyId>DEFBICXXX</partyId> <partyName>DEF Broker</partyName> </party> </confirmationAgreed>