Multiple versions of a form is often loaded for a single return, and to better provide context around this, the nuj naming convention is applied.
On upload, files are renamed based on the information in the "EntityDetails" tab as well as which "SRF_" tabs exist in the file.
Provided that you have permission to upload data for the fund, and the details in the file uniquely identifies a form, the file is then automatically renamed to the following format:
Format | Example |
[Form number]&"_"&[Fund name]&"_"&[Form version]&"_"&[Date]&"_"&[Document version] | SRF605_0_ABC_AD_20250630_1 |
[Document version] provides a numerical way to identify the sequence of data loaded for a return (later versions has a higher number). Only the latest version of data for a return is used for visualisation for the nuj Connect Reporting module.
e.g. For fund ABC, the return for SRF605.0 for reporting end date (20250630) has the latest file version of SRF605_0_ABC_AD_20250630_2.xlsx which include products ABC1 and ABC2
Hannah uploaded a new file to make changes to the return and was renamed to SRF605_0_ABC_AD_20250630_3.xlsx which include products ABC2, ABC4 and ABC5
In this scenario v3 will fully replace v2 as the data for the return and only products listed in Hannah's update will be seen for that return. (Fund ABC / SRF605.0 / 20250630)
Field Descriptions
Name | Format | Example | Description |
Form number | SRF+Number<000_0> | SRF605_0 | SFR605.0 |
Fund Name | Fund Name<3> | ABC | ABC Superannuation Fund |
Form Version | char<2> | AD | Valid values: |
Date | YYYYMMDD | 20250630 | To reflect the Reporting Date of the form. |
Document Version | number<1> | 1 | To cater for multiple submissions of same return. |