ASIC FIX Implementation
The aim of the FundApps implementation process is to set up your environment to allow day-to-day use of ASIC FIX. Below we provide some useful information for the three main steps of the implementation.
Every step of the way, the FundApps client services team (firstname.lastname@example.org) will be available to help you in this process.
1. Accessing your environment
The user setup will be done via our Customer Success team, you will need to provide a list with:
- Type of access (write/read)
Users who have access to the Regulatory Connectivity service will be able to upload short positions files and send filings to ASIC (write access) or review the data previously uploaded (read access).
If there is a requirement to set up single sign-on via SAML in your organization, our SSO article documents the process.
Shareholding Disclosure users
All Admin/Manager/Reviewer users will be able to see the new Regulatory Connectivity module at the top banner of the screen, however, only Admin/Managers will be able to Upload/Send Filings to ASIC.
Please find more information about setting up new users and user roles.
2. Setting up the short positions file
The file should be provided in .csv format. For a successful upload, the file must include the following 4 fields:
- Seller ID,
- Stock Code,
- Short Quantity,
- Position Date.
Can be any of the following and consistent across all filings:
- ASIC Identifier,
- Australian Business Number (ABN),
- Australian Company Number (ACN),
- Australian Registered Body Number (ARBN),
- SWIFT Bank Identifier Code (BIC).
If an ABN is provided, it must relate to the entity's ACN or ARBN.
If a BIC is provided, then the full SWIFT BIC code should be provided, including any applicable branch code. I.e., a SWIFT BIC code for a branch office should always be 11 characters.
Most ASX listed company codes have 3 characters which represents the company and all securities issued by that company.
The short position provided as a whole number of shares, always greater or equal to zero.
Required date format MM/DD/YYYY or YYYY-MM-DD.
Uploading a position file
Our system will accept any of the combinations below:
- short positions for one Position Date and one Seller ID,
- short positions for multiple Position Dates and one Seller ID,
- short positions for one Position Date and multiple Seller ID’s,
- short positions for multiple Positions Date and multiple Seller ID’s.
We support up to 1000 rows per SellerID, if your position reflects more than this, please contact us via email@example.com.
This sample file contains dummy data to reflect one of the examples above.