This article describes which fields of a Confirmation are mandatory in any case (covering outgoing PDF-to-Confirm).
Mandatory fields for any Confirmation
The following table lists all fields that are considered mandatory for any Confirmation processed in Confirmation Hub.
Note: The provisioned enumerations (values) of the two fields "Commodity" and "TransactionType" determine the type of validation applied by Confirmation Hub.
| Technical Field | Field name | Description |
| DocumentID | Document Identifier | As per recommendation. Typically includes the Trade ID. |
| DocumentUsage | Document usage | Defines the usage of the Confirmation such as test or live. |
| SenderID | Sender identifier | Sender if the Confirmation |
| ReceiverID | Receiver identifier | Receiver of the Confirmation |
| ReceiverRole | Receiver role | Typically "Trader" and possibly "Broker" |
| DocumentVersion | Document version | Version of document |
| Commodity | Commodity | Multiple commodities are supported. Determines the type of validation applied thereafter. |
| TransactionType | Transaction type (product) | Multiple transaction types / products are supported. Determines the type of validation applied thereafter. |
| BuyerParty | Buyer party | Buyer side |
| SellerParty | Seller party | Seller side |
| Agreement | Agreement | Reference to the bilateral agreement effective between buyer and seller |
| Currency | Currency | Multiple currencies are supported |
| Total Volume | Total volume | Total volume of trade |
| TotalVolumeUnit | Total volume unit | Multiple volume units are supported |
| TradeDate | Trade date | The date the trade is executed |
| TradeID | Trade Identifier | ID of trade in source system such as E/CTRM |