format / Audience / Date / Classification
/ File Ref: / [G043]
Invalid TFN VALUES in SuperSTream messages
Purpose
The purpose of this document is to address the problem of invalid or incorrect TFNs being provided in SuperStream Member Registration Request (MRR) and Contribution Transaction Request (CTR) messages.
Background
The member TFN is a key item in the processing of a member registration and also in correctly allocating a contribution to the member’s account.
If the TFN provided in a CTR or MRR message is not a properly-formed TFN, or is not the correct TFN for the member, then a manual workflow action is likely to be triggered during processing by the receiving fund and this delays the processing of the registration or contribution transaction for the member.
ISSUE
This is essentially an employer related data integrity issue and the intent of the document is to highlight the steps that should be undertaken by employers and employer solution providers to minimise the risk of incorrect or invalid TFNs being populated into MRR or CTR messages.
RECOMMENDED GUIDANCE
In creating MRRs and CTRS the following principles must be adhered to by the employer and employer sending solution:
a)If an employer has the employee’s TFN then the TFN must be provided in a SuperStream message where specified.
b)All TFNs allocated to individuals are 9 digits. Eight digit TFNs must not be used for individuals.
c)A leading zero (or any other digit) must not be added to an eight digit TFN to imitate a 9 digit individual TFN.
d)Individual’s TFNs supplied in SuperStream messages must not contain embedded spaces.
e)TFN exemption codes used for other reporting must not be used in a SuperStream message. SuperStream requires the actual TFN allocated to the individual.
f)The basic checksum algorithm test must be applied to all TFNs before they are included in a SuperStream message.
g)SuperStream messages have an indicator to declare that TFN has not been provided (Identifiers.TaxFileNumberNotProvided.Indicator). Where the employer has made reasonable attempts to obtain the employee’s TFN but has been unable to do so, an alternative identifier must be used in the message and the indicator must be used to specifythat a TFN has not been provided for that employee.
Note:The use of EmployerTICKis recommended to verify that the TFN provided to the employer is in fact the employee’s TFN. In November 2015 EmployerTICK will be extended to provide a corrected TFN back to the employer whenever possible.
RELease NoTE
This guidance note supersedes G037 and has the same title.
The only change from that guidance note is the addition of point c) above to formally document the guidance for a specific issue encountered in some production messages.
1