Superannuation (CSS) (Surcharge Commutation Amount - Conversion Factors) Determination No. 1

The Schedule rests on a few narrow, explicit concepts stated in the text. First, conversion factors. Each table is headed as providing “PENSION CONVERSION FACTORS” and each row maps a whole number age to a single numeric conversion factor. The Schedule uses the same label for both tables but separates them by pension type: “INDEXED PENSIONS” (Table 1) and “NON‑INDEXED PENSIONS” (Table 2). The Schedule itself does not define “indexed” or “non‑indexed”; those classifications must be established by the Act or by other provisions of the statute implementing subsection 146D(2).

Second, the age metric. Both tables use the exact phrase “AGE AT LAST BIRTHDAY” as the independent variable. That phrase fixes the age measure to completed years. The Schedule therefore embeds an operational rule about which integer age applies for a given individual: the age to be used is the last birthday reached, not a rounded or projected age, and not an age measured to decimal precision.

Third, the scope of the numeric domain. Each table covers the integer ages 15 through 70 inclusive. Table 1 lists conversion factors for ages 15 to 70 for indexed pensions, beginning at 24.1 for age 15 and declining to 13.4 for age 70. Table 2 lists conversion factors for ages 15 to 70 for non‑indexed pensions, beginning at 14.6 for age 15 and declining to 10.4 for age 70. The Schedule thereby constrains the explicit statutory factors to this band of ages.

Fourth, the statutory provenance. The Schedule is captioned “CONVERSION FACTORS REQUIRED UNDER SUBSECTION 146D(2) OF THE ACT”. That phrase identifies the Schedule as the numerical content required by a specific subsection. The Schedule therefore functions as the statutory annex that supplies required numeric parameters, rather than as an explanatory schedule or a guideline.

There are several implicit consequences embedded in these explicit concepts. The two tables produce systematically different factor magnitudes for the same integer ages, with factors in Table 1 (indexed) consistently larger than those in Table 2 (non‑indexed) for every listed age. The difference in magnitude narrows with increasing age, as the tables show steeper initial gaps and smaller gaps at older ages. The Schedule does not state units attached to the numbers, or rules for interpolation between integer ages, or treatment for ages outside the 15-70 range. Any such application must look to the Act, subsidiary instruments, or administrative guidance for the missing operational detail.

Directly, the Schedule affects any person or entity required by the Act to use the conversion factors that are “required under subsection 146D(2)”. The Schedule itself does not name the types of decision‑makers or payers who must apply the factors, but by supplying the legislated numeric factors it binds the statutory calculation that the subsection governs to these numbers. The practical actors who will be affected therefore include administrators, actuarial officers, trustees, employers, or government agencies who carry out calculations under the relevant subsection.

The Schedule also affects pension recipients and prospective beneficiaries insofar as the conversion factors are inputs to statutory calculations that determine entitlements, offsets, capitalised values, or other quantifications of pension‑related rights under the Act. For any given integer age between 15 and 70, the choice between Table 1 and Table 2 produces materially different conversion factors (for example, at age 65 Table 1 gives 15.3 while Table 2 gives 11.5). That numeric difference will affect the numerical outcomes of whatever statutory formula uses the factors, and therefore affects the economic position of persons whose age and pension classification fall within the tables’ domain.

Administrators who must implement the statutory calculation are affected by the Schedule’s procedural details. The explicit “AGE AT LAST BIRTHDAY” instruction sets a clear age determination rule that affects operational steps such as data validation, recordkeeping and the timing of calculations. Because the Schedule enumerates factors only for ages 15 through 70, persons outside that age band fall into a residual category that the Schedule does not address; those cases will require decision‑makers to consult the Act or seek instructions from the statutory decisionmaker about how to proceed in the absence of a listed factor.

The Schedule will also affect intermediaries such as accountants, lawyers and actuaries who advise on pension calculations under the Act. They will need to ensure the correct table is chosen for “indexed” versus “non‑indexed” pensions and that the age used is the age at last birthday. The Schedule contains no enforcement instructions or administrative processes; any compliance burden, dispute procedures, or practical application details will come from the Act itself or from administrative guidance that interprets subsection 146D(2).

Finally, because the Schedule fixes numbers rather than describing a method for updating them, parties who prefer or require alternative parametrisations (for instance for internal modelling) must treat these numbers as the statutory baseline whenever the Act calls for the conversion factors required under s 146D(2), and must account for deviations if they use different figures for other purposes.

The Schedule itself contains no prescriptive duties or rights in the form of operative language, beyond specifying the numbers that are “required under subsection 146D(2) of the Act”. The Schedule therefore functions as the numerical annex to a statutory provision that presumably assigns rights, liabilities or calculation rules. The Schedule imposes the following de facto obligations by its form and labelling.

First, an obligation to use the specified factors where the Act requires the conversion factors under subsection 146D(2). The Schedule supplies two labelled tables, and the natural reading of the text is that the conversion factor applied must be the number listed against the person’s “AGE AT LAST BIRTHDAY” and the appropriate pension type, indexed or non‑indexed. The Schedule thereby constrains the numerical input for any statutory formula that references the conversion factors required by s 146D(2).

Second, an obligation to use the age measure “AGE AT LAST BIRTHDAY”. This phrase is in the column heading for both tables. That wording supplies an operational rule: the integer age to be used for mapping to the conversion factor is a person’s completed years of life as at their last birthday. This creates a duty on administering bodies to determine and record that specific age when selecting the factor, rather than using alternative conventions such as age in years and months or nearest whole year.

Third, a duty to distinguish pension type. Table 1 is titled for indexed pensions, Table 2 for non‑indexed pensions. The presence of two separate tables implies the duty to select the correct table based on whether the pension in question is indexed or non‑indexed under the Act or relevant scheme rules. The Schedule does not define those terms; the operative definitions will reside in the Act. The duty therefore requires administrators to map a pension to the statutory classification before selecting the factor.

The Schedule does not itself create expressed rights such as entitlements to a specific amount payable, nor does it state appeal or review rights. Any rights flowing from use of the conversion factors derive from the underlying Act and from the calculation that uses these numbers. The Schedule does not supply rounding or interpolation rules, so an implementing duty remains to address how to handle ages outside 15-70, fractional ages, or absent definitions. Where the Act is silent on these operational points, implementing agencies or decision‑makers will be required to adopt administrative conventions or seek clarification, because the Schedule supplies only the raw numeric inputs.

In short, the Schedule imposes numeric constraints that implementing bodies must apply in calculations called for by subsection 146D(2). It establishes operational choices to be made before application: determining the person’s age at last birthday, classifying the pension as indexed or non‑indexed, and selecting the corresponding factor. The Schedule itself does not set out ancillary procedural duties such as timing, notification, or recordkeeping; those duties, where they exist, appear in the Act or in administrative instruments.

The Schedule contains no provisions concerning penalties, sanctions, or enforcement mechanisms. It is a numerical schedule labelled as required under subsection 146D(2) of the Act, and it supplies numeric factors only. Neither table references offences, civil penalties, enforcement agencies, time limits for correction, or audit procedures. Consequently, any penal or enforcement regime that applies to failures to use, or misapplication of, these conversion factors must be found in the operative text of the Act or in other related legislative or regulatory instruments, not in this Schedule.

Because the Schedule does not specify enforcement, practical compliance and dispute resolution will depend on the architecture of the Act. Implementing agencies will be the likely enforcement agents if the Act vests them with compliance powers. For example, a government department or tribunal referenced elsewhere in the Act would decide whether a wrongly applied conversion factor gives rise to an administrative correction, a civil liability, or an offence, but the Schedule does not itself make those connections.

The Schedule’s lack of enforcement language creates several operational risks that implementers should control for administratively. The tables are precise numeric inputs, so inadvertent transcription errors, mis‑selection of the table for indexed versus non‑indexed pensions, or use of an incorrect age measure (for example, age in years and months rather than age at last birthday) can materially alter calculation outputs. Because the Schedule does not instruct on rounding, interpolation, or out‑of‑range ages, implementers must adopt documented conventions and internal controls to reduce the chance of disputes arising from inconsistent application.

Where disputes occur about the use of the conversion factors , for example, about which table applied, whether an employee’s pension was correctly classified as indexed, or how to treat an age not listed in the tables , the Schedule itself provides no dispute mechanism. The Schedule therefore increases reliance on the Act’s enforcement and dispute framework. Any party seeking to challenge a calculation that used the Schedule would need to ground their argument in the Act’s substantive and procedural provisions and in any administrative guidance that explains how subsection 146D(2) is to be applied.

In sum, the Schedule prescribes numeric inputs but does not prescribe enforcement. Penalties, remedies and supervisory oversight must be sourced from the Act’s other provisions or from delegated instruments, and implementers should document internal controls to mitigate the operational enforcement gap left by the Schedule’s silence on these matters.

The Schedule explicitly ties itself to subsection 146D(2) of “the Act” by stating that the conversion factors are “REQUIRED UNDER SUBSECTION 146D(2) OF THE ACT”. That linkage is the sole statutory cross‑reference contained in the Schedule. Therefore the Schedule’s immediate legal interaction is with the provisions of the Act that invoke or rely on the conversion factors required under s 146D(2). Any statutory formula, entitlement rule, or administrative process in the Act that calls for “the conversion factors required under subsection 146D(2)” will now reference the numbers in this Schedule.

Beyond that explicit cross‑reference, the Schedule is silent about interactions with other legislation, regulatory standards, tax law, superannuation law, actuarial standards, or financial reporting rules. Any practical intersection between the Schedule and other laws will arise via the broader statutory or regulatory environment in which the Act operates. For instance, if the Act uses these factors to compute capitalised values for pension offsets or means tests, those computed amounts may in turn affect taxable income, social security entitlements, or liabilities under other statutory regimes. The Schedule does not itself state those linkages.

Two structural interaction points should be noted explicitly because they follow from the Schedule’s format. First, the classification split between “INDEXED PENSIONS” and “NON‑INDEXED PENSIONS” will interact with any legal definitions of indexing in the Act or in other laws. Whether a pension qualifies as “indexed” for the purposes of Table 1 will be determined by the definition of indexed pension in the Act or by guidance from the relevant authority. The Schedule does not define the terms, so the classification interaction depends on other legal texts.

Second, the phrase “AGE AT LAST BIRTHDAY” interacts with any other legal provisions that specify alternative age metrics. Where other statutes or administrative rules use a different age measure for related calculations, implementers must ensure consistency or document differences. For example, if a different statutory provision uses age last birthday for some calculations but exact age for others, practical inconsistencies may arise; the Schedule’s explicit age rule governs only the conversion factors it supplies.

Finally, because the Schedule sets fixed numeric values without a built‑in updating mechanism, its interaction with laws that expect periodic adjustment will depend on the Act’s provisions for revision. If the Act or delegated legislation provides procedures for amending schedules or indexing statutory tables, those mechanisms will determine how this Schedule interacts dynamically with other laws over time. The Schedule itself contains no updating clause, indexation provision, or cross‑references to external indices.

The Schedule as provided contains no amendment history, marginal notes, or versioning statements within its text. It contains the heading “SCHEDULE SCHEDULE” and the label “CONVERSION FACTORS REQUIRED UNDER SUBSECTION 146D(2) OF THE ACT” and then sets out TABLE 1 and TABLE 2 with their numeric entries. There are no annotations, effective dates, commencement dates, or notes indicating prior values or prior amendments.

Because the Schedule lacks an internal amendment history, anyone seeking to determine when these specific numbers took effect, what earlier numbers they replaced, or how often they have been altered must consult the Act itself, the parliamentary bills or instruments that inserted the Schedule, or relevant legislative history materials not included in this Schedule. The Schedule gives no indication whether the numbers are intended to be temporary, periodically reviewed, or fixed unless the Act provides those governance rules elsewhere.

Absent further text in this Schedule, the only concrete statement about origin is the caption that they are “REQUIRED UNDER SUBSECTION 146D(2)”. That indicates the numbers are provided to give statutory content to that subsection, but it does not supply a timeline. Practitioners must therefore check the Act’s commencement and amendment provisions and the parliamentary instruments that enacted or modified subsection 146D(2) to establish the dates of effect and the amendment pathway.

If an implementing body or regulated party needs to track changes to these factors over time, the Schedule itself will not suffice. They must rely on legislative histories, amendment instruments, or consolidated versions of the Act that record insertions to the Schedule. The Schedule does not include a mechanism for future amendment such as automatic indexation, so statutory amendment or delegated‑legislation procedures will be required to change the numbers.

The Schedule contains no case law citations, dispute records, or references to litigation. It sets out only the numeric conversion factors and the note that they are required under subsection 146D(2) of the Act. The text does not mention prior legal challenges, appellate decisions, tribunal determinations, or interpretive rulings related to these factors.

Because there is no litigation history in the Schedule itself, any analysis of how courts or tribunals have treated the conversion factors, the label “AGE AT LAST BIRTHDAY”, or the indexed/non‑indexed distinction must be based on external case law, which is not included in the supplied text. Practitioners wishing to know whether disputes have arisen about the application of these conversion factors or about the treatment of persons whose ages fall outside the table will need to consult judicial databases and the relevant tribunal records.

In the absence of recorded litigation, the Schedule should be read as a piece of numeric legislation that supplies precise inputs and that could be treated by courts or tribunals as definitive for purposes of statutory calculation where the underlying Act calls for the conversion factors required under subsection 146D(2). However, the Schedule does not itself indicate whether courts have accepted or criticised specific uses of the numbers, or whether there have been disputes over interpretation such as how to treat ages outside the table, rounding, or the pension classification. Those matters remain to be determined by reference to external authorities if any exist.

The Schedule is narrowly drafted and contains several points that can cause practical surprise if implementers assume more than the text provides. Below are concrete items drawn from the Schedule’s text that warrant attention.

1. Age metric is explicit and constraining. Both tables use the column heading “AGE AT LAST BIRTHDAY”. That phrase is the operative age rule. Using age measured in years and months, or tiling to nearest year, would depart from the Schedule. Implementers must ensure systems and data fields support calculation of age at last birthday and record that value. Failure to do so will lead to inconsistent application of the table.

2. Two distinct tables, classification required. The Schedule supplies separate factors for “INDEXED PENSIONS” and “NON‑INDEXED PENSIONS”. The Schedule does not define those terms. Implementers must therefore determine from the Act or from subsidiary rules whether a given pension is indexed. Selecting the wrong table will produce materially different outcomes (for example, at age 65, Table 1 gives 15.3 and Table 2 gives 11.5).

3. No units or formula specified. The Schedule lists numeric conversion factors but does not state the units, the signification of a unit change, or how the numbers are to be applied in arithmetic formulas. The Schedule therefore must be read alongside the Act’s operative formulae that invoke the conversion factors. Do not infer the meaning of a numeric entry without checking the Act.

4. Limited age range. Both tables cover ages 15 through 70 only. The Schedule is silent about persons younger than 15 or older than 70. For those outside the table range the Act must be consulted to determine the correct approach; absent such guidance, administrators must obtain direction rather than extrapolate without authority.

5. Decimal precision present, rounding unspecified. The factors are given to one decimal place (for example 23.7, 14.6). The Schedule does not set a rule for rounding when intermediate calculations require different precision. Implementers should record the exact table value used and any rounding convention adopted, because the Schedule does not itself supply a rounding rule.

6. System and transcription risk. The Schedule’s numeric grid invites data entry error. The presence of two side‑by‑side age columns in the printed format increases the risk of selecting the wrong cell. Implementers should ensure automated data extraction uses the correct column mapping and that manual processes have verification steps.

7. No update mechanism included. The Schedule contains fixed numbers and no indexing or revision formula. If the underlying economic context for the conversion factors requires periodic review, that process must be supported by the Act or by separate amendment instruments. Relying on the Schedule alone will not permit automatic updating.

8. Potential mismatch with other age rules. If other statutory provisions use different age conventions for related calculations, inconsistency may arise. The Schedule’s explicit “AGE AT LAST BIRTHDAY” rule applies only to selecting the conversion factor; it does not override other provisions that expressly use different age measures.

9. Interpretation gap for hybrid pensions. The Schedule divides pensions into two discrete types, but real‑world pension instruments may have hybrid features or partial indexation. The Schedule offers no guidance for split or partially indexed pensions. Implementers must find authoritative guidance in the Act or seek administrative clarification.

10. Absence of enforcement and appellate guidance. Because the Schedule contains no enforcement provisions or litigation history, procedural disputes about correct application will need to be resolved under the Act’s broader dispute resolution framework. Documentation of how the Schedule was applied will therefore be important if a calculation is contested.

These concrete gotchas arise directly from the Schedule’s content and omissions, and they identify where practitioners must look beyond the Schedule to the Act, to administrative guidance, or to legislative amendment instruments.

The Schedule’s content is straightforward to operationalise provided implementers observe the explicit constraints and fill in the operational gaps with authoritative rules. Below are practical, source‑grounded steps to ensure compliance with the Schedule as it stands.

1. Establish the statutory trigger. Confirm that the calculation you are performing is one for which the Act requires “the conversion factors required under subsection 146D(2)”. The Schedule is explicitly tied to that subsection, so compliance requires that the Act’s conditions for applying s 146D(2) are met.

2. Classify the pension. Determine from the Act whether the pension in question is an “indexed pension” or a “non‑indexed pension” as those terms are used by the Act. The Schedule has two separate tables, so correct classification is the primary gatekeeper to selecting the correct factor.

3. Determine age at last birthday. For the person whose factor is being applied, calculate the completed years of age as “AGE AT LAST BIRTHDAY” and map that integer to the corresponding table row. Use a single, auditable method for computing age last birthday (for example by date of birth and date of calculation) and log that method to avoid disputes.

4. Confirm age falls within 15-70. The Schedule lists ages 15 through 70 inclusive. If the person’s age is outside that band, do not select a number from the table. Instead, consult the Act for guidance about out‑of‑range ages or seek an administrative ruling. Document any instructions received and any interim approach taken pending authoritative guidance.

5. Use the exact decimal values. The Schedule supplies figures to one decimal place. Record and apply the table value exactly as printed unless the Act or authoritative guidance authorises rounding. Log the value used and the table selected in the calculation record.

6. Document table selection and calculation steps. For auditability and dispute resolution, record which table (Table 1 or Table 2) was used, the age at last birthday applied, the numeric conversion factor drawn from the schedule, and any upstream determinations (such as how a pension was classified as indexed or non‑indexed). This documentation addresses the Schedule’s lack of procedural text.

7. Develop internal controls for transcription and system mapping. If the tables are implemented in software, ensure that database fields map correctly to the table entries and validate the mapping with independent checks. For manual processes, establish a two‑person check for table selection and entry.

8. Resolve hybrid or ambiguous cases before calculation. If a pension’s indexing status is unclear, obtain a written determination under the Act or from the responsible administrator before selecting a factor. The Schedule gives no guidance for partial or conditional indexation, so authoritative classification must precede use.

9. Seek guidance for rounding and interpolation only where authorised. The Schedule does not permit interpolation between integer ages nor supply rounding conventions. Use such techniques only if the Act or authorised guidance expressly permits them. Otherwise, rely on the integer age mapping provided.

10. Monitor legislative instruments for amendments. Because the Schedule contains no internal update mechanism, ensure you have a process to check for legislative amendments or replacement schedules. Any change to subsection 146D(2) or to the Schedule itself will affect which numbers are the statutory inputs.

Following these steps will align practical application to the Schedule’s explicit terms: use the conversion factor required under s 146D(2), map by age at last birthday, and choose the correct indexed or non‑indexed table. The Schedule does not resolve peripheral operational questions; those must be addressed by reference to the Act, to delegated legislation, or to authoritative administrative guidance and documented in the calculation record.