This topic includes details about Position reporting scenarios related to the submission of the new Part 17 FIXML Position message.

Contents

Position Report Identification

The following fields uniquely identify a Position Report:

• Reporting Firm ID + Report Date + Account ID + Unique Contract Identifier (UIC)

Submitting More Than One New Position Report

The following outcome applies when more than one “New” message (FIXML/Batch/PosRpt@Actn=1) is submitted for the same daily position.

• The subsequent “New” submission will overwrite the previously submitted message.

• If less position information is present in the subsequent message, then a quantity of 0 will be implied.

Example 1: Submitting More Than One New Position Report

In all of the following Examples, the report will be submitted for:

Reporting Firm ID: ABCD

Report Date: 01/12/2025

Account ID: a123b456

UIC: 3UQXZP2E66IT

In this example a New message is sent that includes:

• Long Position = 10

• Short Position = 25

• EFPs Bought = 100

• EFPs Sold = 250

For this New message submission the reporting record shows the following for the message processing:

A subsequent New message is then sent and includes:

• Long Position = 5

• Short Position = 25

For this subsequent New message submission the reporting record shows:

Modifying Position Report After Submitting a New Message

The following outcome applies when a “Modify” message (FIXML/Batch/PosRpt@Actn=2) is submitted after a “New” message (FIXML/Batch/PosRpt@Actn=1) for the same daily position.

Example 2: Modifying a Position Report After a New Message Submission

In this example a New message is sent that includes:

• Long Position = 10

• Short Position = 25

• EFPs Bought = 100

• EFPs Sold = 250

For this New message submission the reporting record shows the following for the message processing:

A subsequent Modify message is then sent and includes:

• Long Position = 5

• Short Position = 25

For this Modify message submission the reporting record shows:

Changing Position Report Before Submitting a New Message

“Change” message submissions are rejected when sent before a new message.

Example 3: Changing a Position Report Before a New Message Submission

In this example a Change message is sent that includes:

• Long Position = 10

• Short Position = 25

• EFPs Bought = 100

• EFPs Sold = 250

For this Change message submission the reporting record is blank because the message submission is rejected.

Deleting a Position Report

To delete a Position Report, CME Group recommends submitting a “Delete” message (FIXML/Batch/PosRpt@Actn=3) on the previously submitted report entry.

• CME Group systems will use the following fields to identify the previously submitted report entry to delete, no other fields will be validated to process the “Delete”: 

  • Reporting Firm ID + Report Date + Account ID + Unique Instrument Code (UIC)

• It is possible to delete a specific position for a reported entry by setting that position to 0 in the Change message but this method should not be used to delete all positions of a report entry.

Example 4: Deleting a Position Report

In this example a Delete message is sent that includes no data.

For a Delete message submission received before New, the reporting record is blank.

Position Report Rejection Scenarios

• A Change submission is rejected when the Change is received before New message on the same daily position.

• A Delete submission is rejected when the Delete is received before New message.

• The Position Report is rejected when submitted with a Holiday Date.