Here’s a passing thought. How does our software know what is, and what is not, a valid TFN? If we incorrectly type a TFN, the software we use tells us it's invalid. The problem is easily fixed by correctly re-entering the numbers. But what makes a number invalid? Especially when you consider that its validity or otherwise is not dependant on matching those numbers with someone’s name and/or birthday and/or address and so on.
These identifiers are used to cross-check a person’s identity of course, but the initial validity of a TFN is known via another factor — the “TFN algorithm”.
This verification algorithm is embedded in each unique TFN and is also known as a check digit algorithm. As with a lot of these things, this best explained using an example. However you need to keep a number in mind, which in this case is the number 11.
To make the algorithm work, a fixed weighting is applied to each number of the TFN. In order from the left, these weightings are 1, 4, 3, 7, 5, 8, 6, 9, 10.
Let’s take the following TFN as an example — 123 456 782. Now multiply each digit by the weightings, in order. So that’s 1 x 1 = 1, 2 x 4 = 8, 3 x 3 = 9, 4 x 7 = 28, 5 x 5 = 25, 6 x 8 = 48, 7 x 6 = 42, 8 x 9 = 72 and 2 x 10 = 20.
Now, add those results together. 1 + 8 + 9 + 28 + 25 + 48 + 42 + 72 + 20 = 253. Now, remember that number you were keeping in mind? If the total you arrived at is a multiple of 11, you’ve got yourself a true TFN.
To check for yourself, try the above with your own TFN.
The check digit algorithm used to be kept secret and was kept in the ATO’s vault for decades, but in more modern times the algorithm has had to be shared with many external entities such as software developers, who are generally required to sign a confidentiality agreement. See here: https://softwaredevelopers.ato...