Several regulatory jurisdictions require you to disclose historical transactions either directly in their standard disclosure form or as an annexure to the standard form. To streamline this process, we provide tools to automate the disclosure of historical transactions.

It's important to note that the transaction file is for document generation purposes only, and omitting transaction information will NOT result in Missing Data exceptions.

However, utilising the Transactions in Disclosure functionality will minimise the manual work required for disclosure in jurisdictions that require transaction-level data and facilitate the successful document generation of your results.

When you generate a disclosure form that requires transaction data, the system completes the following steps:

You can upload transaction data in a CSV file via the API endpoint or directly in the UI by navigating to Monitoring > Shareholding Disclosure > Other > Transactions. Once there, use the Import (.CSV) button to upload the appropriate file.

Our sample transaction file illustrates the file format and the fields required to pass validation. Please see the README for more information on the columns and the valid transaction types.

You cannot overwrite transactions by re-uploading them for previous NAV dates, as each transaction has a unique ID. You can only upload new transactions that have not been uploaded previously. Any re-uploading requires a new TransactionID to pass validation, resulting in double-counting.
​

To correct an erroneous transaction, cancel it by submitting an adjustment transaction. An adjustment transaction is the only method that allows you to re-use a TransactionID, but it must contain an equal and opposite value to the original transaction.

For example:
​Transaction ID 1: Buy 200
Transaction ID 1: Adjustment -200

The following rules require you to upload historical transactions to generate disclosures correctly: