Definition Type: ComplexType
Name: PartyTradeInformation
Namespace: http://www.fpml.org/FpML-5/transparency
Containing Schema: fpml-doc-5-9.xsd
Abstract
Documentation:
A type defining party-specific additional information that may be recorded against a trade.
Collapse XSD Schema Diagram:
Drilldown into isDisputed in schema fpml-doc-5-9_xsd Drilldown into isCommodityHedge in schema fpml-doc-5-9_xsd Drilldown into shortSale in schema fpml-doc-5-9_xsd Drilldown into tradingWaiver in schema fpml-doc-5-9_xsd Drilldown into otcClassification in schema fpml-doc-5-9_xsd Drilldown into isSecuritiesFinancing in schema fpml-doc-5-9_xsd Drilldown into TransactionClassification.model in schema fpml-doc-5-9_xsd Drilldown into compressedTrade in schema fpml-doc-5-9_xsd Drilldown into confirmationMethod in schema fpml-doc-5-9_xsd Drilldown into verificationMethod in schema fpml-doc-5-9_xsd Drilldown into executionVenueType in schema fpml-doc-5-9_xsd Drilldown into executionType in schema fpml-doc-5-9_xsd Drilldown into largeSizeTrade in schema fpml-doc-5-9_xsd Drilldown into pricingContext in schema fpml-doc-5-9_xsd Drilldown into offMarketPrice in schema fpml-doc-5-9_xsd Drilldown into nonStandardTerms in schema fpml-doc-5-9_xsd Drilldown into endUserExceptionReason in schema fpml-doc-5-9_xsd Drilldown into endUserException in schema fpml-doc-5-9_xsd Drilldown into reportingRegime in schema fpml-doc-5-9_xsd Drilldown into collateralPortfolio in schema fpml-doc-5-9_xsd Drilldown into collateralizationType in schema fpml-doc-5-9_xsd Drilldown into clearingStatus in schema fpml-doc-5-9_xsd Drilldown into intentToClear in schema fpml-doc-5-9_xsd Drilldown into allocationStatus in schema fpml-doc-5-9_xsd Drilldown into intentToAllocate in schema fpml-doc-5-9_xsd Drilldown into timestamps in schema fpml-doc-5-9_xsd Drilldown into executionDateTime in schema fpml-doc-5-9_xsd Drilldown into relatedParty in schema fpml-doc-5-9_xsd Drilldown into partyReference in schema fpml-shared-5-9_xsd Drilldown into PartyAndAccountReferences.model in schema fpml-shared-5-9_xsdXSD Diagram of PartyTradeInformation in schema fpml-doc-5-9_xsd (Financial products Markup Language (FpML®) - Transparency)
Collapse XSD Schema Code:
<xsd:complexType name="PartyTradeInformation">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">A type defining party-specific additional information that may be recorded against a trade.</xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:group ref="PartyAndAccountReferences.model" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Identifies that party that has ownership of this information. For shared trade information, this will reference the originator of the date (for example, an execution facility or clearinghouse).</xsd:documentation>
            </xsd:annotation>
        </xsd:group>
        <xsd:element name="relatedParty" type="RelatedParty" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="executionDateTime" type="ExecutionDateTime" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Trade execution date time, for example as provided by a central execution facility. Normally this refers to the original execution time of the trade, not the execution time of any post-trade events that may have affeted it. However, in the case of a post trade event that reports the new version of the trade (for example, the novation trade in an novation event, or the amended trade in an amendment event), the execution date time may contain the time that the newly created or modified trade was created or modified.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="timestamps" type="TradeProcessingTimestamps" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Allows timing information about a trade to be recorded.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="intentToAllocate" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether the trade is anticipated to be allocated.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="allocationStatus" type="AllocationReportingStatus" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="intentToClear" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether the trade is anticipated to be cleared via a derivative clearing organization</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="clearingStatus" type="ClearingStatusValue" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Describes the status with respect to clearing (e.g. AwaitingAcceptance, Pending, Accepted, Rejected, etc.)</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="collateralizationType" type="CollateralizationType" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether this party posts collateral. For Recordkeeping, the collateralization type refers to collateral that is posted by this firm, and One-Way is not meaningful. In other words, if the collateralization type is Full, this trade is fully collateralized by this party. For Transparency view, the options include Full, Partial, Uncollateralized, and One-Way.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="collateralPortfolio" type="PortfolioName" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Provides a name, code, or other identifier for the collateral portfolio to which this belongs.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="reportingRegime" type="ReportingRegime" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:sequence>
            <xsd:element name="endUserException" type="xsd:boolean">
                <xsd:annotation>
                    <xsd:documentation xml:lang="en">Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. wehter there is an exemption from clearing. For historical reasons this is called "end-user exception", but this may be used to indication any exception from normal clearing mandates caused by the type of the partiees or their relationship, such as inter-affiliate trades. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.</xsd:documentation>
                </xsd:annotation>
            </xsd:element>
            <xsd:element name="endUserExceptionReason" type="ClearingExceptionReason" minOccurs="0">
                <xsd:annotation>
                    <xsd:documentation xml:lang="en">Specifies a reason that the trade is exempted from a clearing requirement. This exemption may be an end-user exception, or another type such as in inter-affiliate trade.</xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:sequence>
        <xsd:element name="nonStandardTerms" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms. The flag indicates that the price for this trade is not to be construed as being indicative of the market for standardised trades with otherwise identical reportable terms.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="offMarketPrice" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="pricingContext" type="PricingContext" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Describes why the price of this trade does not reflect the current market price. For example, the trade may have been traded off-market as part of a termination or compression operation.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="largeSizeTrade" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting. Normally this will only be applicable for off-facility trades.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="executionType" type="ExecutionType" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Used to describe how the trade was executed, e.g. via voice or electronically.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="executionVenueType" type="ExecutionVenueType" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="verificationMethod" type="VerificationMethod" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation. This affect the timing of real-time reporting requirements. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="confirmationMethod" type="ConfirmationMethod" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation. This affects the process flow for confirmation messages. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="compressedTrade" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Specifies whether this trade is a result of compression activity.</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:group ref="TransactionClassification.model" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation>Provides classification of the transaction being reported</xsd:documentation>
            </xsd:annotation>
        </xsd:group>
        <xsd:element name="isDisputed" type="xsd:boolean" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">Used to report whether the trade is in dispute</xsd:documentation>
            </xsd:annotation>
        </xsd:element>
    </xsd:sequence>
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
partyReference nsA:partyReference (1) (1)
relatedParty nsA:relatedParty 0 unbounded
executionDateTime nsA:executionDateTime 0 (1)
timestamps nsA:timestamps 0 (1)
intentToAllocate nsA:intentToAllocate 0 (1)
allocationStatus nsA:allocationStatus 0 (1)
intentToClear nsA:intentToClear 0 (1)
clearingStatus nsA:clearingStatus 0 (1)
collateralizationType nsA:collateralizationType 0 (1)
collateralPortfolio nsA:collateralPortfolio 0 (1)
reportingRegime nsA:reportingRegime 0 unbounded
endUserException nsA:endUserException (1) (1)
endUserExceptionReason nsA:endUserExceptionReason 0 (1)
nonStandardTerms nsA:nonStandardTerms 0 (1)
offMarketPrice nsA:offMarketPrice 0 (1)
pricingContext nsA:pricingContext 0 unbounded
largeSizeTrade nsA:largeSizeTrade 0 (1)
executionType nsA:executionType 0 (1)
executionVenueType nsA:executionVenueType 0 (1)
verificationMethod nsA:verificationMethod 0 (1)
confirmationMethod nsA:confirmationMethod 0 (1)
compressedTrade nsA:compressedTrade 0 (1)
isSecuritiesFinancing nsA:isSecuritiesFinancing 0 (1)
otcClassification nsA:otcClassification 0 unbounded
tradingWaiver nsA:tradingWaiver 0 unbounded
shortSale nsA:shortSale 0 (1)
isCommodityHedge nsA:isCommodityHedge 0 (1)
isDisputed nsA:isDisputed 0 (1)
<xs:group> nsA:PartyAndAccountReferences.model 0 (1)
<xs:group> nsA:TransactionClassification.model 0 (1)
Collapse Derivation Tree:
Collapse References:
nsA:partyTradeInformation
Collapse Comments:
blog comments powered by Disqus