Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Interpreting the Positions Reconciliation Report

Whenever there is a net position discrepancy, the first value is the position in PropReports and the second is the position at the external entity being compared. For example, here is a sample discrepancy report versus the Sterling platform:

	ABC123
                AAPL 0 3,000
	ABC456
                IBM -100 -200

The above indicates that account ABC123 was flat AAPL whereas Sterling was long 3,000 shares. Account ABC456 is short 100 shares IBM whereas Sterling shows the account short 200.

(lightbulb) For examples of frequent and infrequent position discrepancies, as well as steps to fix them, please visit the Handling Position Discrepancies Page. 

Interpreting the Executions Reconciliation Report

When you set up an Execution reconciliation, PropReports will compare internally stored fills against another source such as your clearing firm.  Running the reconciliation daily allows you to double-check that imported trading activity is correct and up-to-date. Below is an example of an execution discrepancy caused by a canceled or busted trade on the external side:

ABC123 (123)
	XYZ
		Internal:
			B 4,300 @ 10.543 ABC001
			B 200 @ 10.541 ABC002
			==========
                        B 4,500 @ 10.542 (TOTAL)
 
		External:
			B 4,300 @ 10.543 ABC001
			B 200 @ 10.541 ABC002 CXLD
			==========
                        B 4,300 @ 10.543 (TOTAL)


		Difference:
                        B 200 @ 10.541

Please note the execution discrepancy report is displayed in the following order:

SideQty PriceOrder NumberFill Status
B200@10.541ABC002CXLD

Internal: Refers to the fills PropReports is reporting
External: Refers to the fills the source you are reconciling against is reporting
Difference: What trades would need to be posted in PropReports in order for that execution to reconcile 

(lightbulb) For examples of frequent and infrequent discrepancies, as well as steps to fix them, please visit the Handling Execution Discrepancies Page.

 

  • No labels