Governor-General Allowance Order 2013

The Order operationalises several interlocking concepts from the Governor‑General Act 1974; the Order itself defines a subset and relies on Act definitions for the remainder (notably those listed in the Note to s 4). Core concepts set out or used in the Order are:

• Scheme value (s 5): For the definition in subsection 2A(2) of the Act, the Order specifies that scheme value in relation to a member spouse is to be determined using the methods and factors in Schedule 1 as in force at the operative time. Schedule 1 supplies both the algebraic method for converting periodic allowances to present values and the numeric factors (Tables 1 and 2).

• Transfer amount: Referred to repeatedly (for example in ss 6-8 and 11). The Order assumes the existence of a transfer amount "that was payable at the operative time" and instructs increases to that amount using Treasury bond rates (ss 7, 11). The transfer amount is therefore a primary input to multiple calculations.

• Chief Justice’s salary (s 4): Several calculations divide by the Chief Justice’s salary and then multiply by the Chief Justice’s salary after rounding to 4 decimal places (see ss 6, 7 Step 5, 9 Step 13, 10 Step 13, 11 Step 8, 12 multiple steps, 13 Step 7). The Chief Justice’s salary is used as the monetary unit for expressing allowance rates and for a mandated rounding convention.

• Treasury bond rate (s 4): Defined as either the yield on 10‑year Treasury bonds issued on the last working day of the previous financial year (if such bonds were issued), or otherwise the RBA‑published 10‑year bond yield for that day. The Treasury bond rate is the interest input used to escalate transfer amounts over discrete periods (ss 7 Step 2B-2D; 11 Step 2B-2D).

• Operative time and payment split: The Order repeatedly considers the operative time and the possibility of one or more payment splits. The order instructs sequential application of reduction calculations if there has been more than one payment split (see the Notes to ss 9 and 10).

• Allowance valuation factors and scheme value factors (Schedule 1, Tables 1 and 2): The Schedule provides age‑ and gender‑specific factors (indexed allowance valuation factors and scheme value allowance valuation factors) to convert annual allowances into present values and vice versa. Table 1 and Table 2 are explicitly invoked at different steps.

• Rounding conventions: The Order specifies rounding to 2 decimal places for increases in transfer amount (steps that calculate monetary increases, e.g. ss 7 Step 2B-2D) and rounding to 4 decimal places where rates are produced as a fraction of the Chief Justice’s salary (e.g. ss 6 Step 4; 7 Step 5; many others). The rounding rule is always specified as "rounding up if the [next] decimal place is 5 or more."

The mathematical structure is consistently: identify an amount (transfer amount, retirement allowance rate, or allowance as payable), escalate or discount using Treasury bond rates and the relevant period, divide by an age‑ and gender‑adjusted factor (derived from Tables 1 or 2), normalise to a fraction of the Chief Justice’s salary with specified rounding, and then convert back into a monetary rate by multiplying by the Chief Justice’s salary. The Schedule supplies the numeric factors and an explicit method for handling unknown end dates (Schedule 1 Div 1.1), and cross‑references appear within Schedule 1 to ensure the same arithmetic structure is used across growth and payment phase valuations.

Primary parties affected:

• The Governor‑General (and former Governor‑Generals) whose retirement allowance, spouse allowance and associated interests are governed by the Governor‑General Act 1974. The Order changes calculation method and therefore the numeric amount of entitlements derived from that Act (s 5; Schedule 1).

• Member spouse and non‑member spouse: The Order prescribes calculation methods for associate immediate allowances (s 6) and associate deferred allowances (s 7), including special treatment where a non‑member spouse dies before payment (s 8). The Order also prescribes reductions to spouse and associate allowances where operative time, payment splits, or death occur (ss 9-13).

• The Commonwealth executive and administrators (Department of Finance or other officials charged with paying allowances): They are responsible for obtaining the transfer amount, Treasury bond rates, Chief Justice’s salary at relevant times, and for executing the stepwise arithmetic in ss 6-13 and the Schedule. The Order explicitly directs them to use RBA published yields or actual Treasury bond yields (s 4), and to use the Tables in Schedule 1.

Secondary and external effects:

• The judiciary (Chief Justice): The Chief Justice’s salary is used as the unit in many calculations, so changes to judicial remuneration will mechanically change the numeric allowances when the Order’s steps refer to the Chief Justice’s salary at the operative time or when allowances become payable (see s 4 definition, and steps referencing "Chief Justice’s salary when the allowance becomes payable", e.g. s 7 Steps 5-6).

• Financial market data providers and the Reserve Bank of Australia: The calculation of increases to transfer amounts is tied to the Treasury bond rate as published by the RBA for specific days (s 4). Administrators must obtain reliable RBA data or bond yields for specific dates.

• Tax and superannuation administrators indirectly: Section 13 applies a specific calculation for Governors‑General first appointed between 20 August 1996 and 1 July 2005 when a "superannuation surcharge applies". That clause affects a cohort who were appointed in the specified period and therefore may alter net payment calculations or interaction with superannuation arrangements (s 13(1)-(3)).

Who pays and who decides:

• Payment ultimately flows from the Commonwealth (the Order sets method for determining statutory allowances payable under the Act). The Order was made by the Minister for Finance and Deregulation under the Governor‑General Act 1974 (cover and s 3), thereby delegating the arithmetic methodology to an instrument rather than embedding detailed numeric factors in primary legislation.

Who must act:

• Administrators must implement procedural steps (identify operative time, calculate increases using Treasury bond rates, apply Tables 1 and 2, enforce rounding) and must repeat step sequences where multiple payment splits occur (notes to ss 9-11).

Who bears the cost:

• The Order does not create a new cost centre; it sets the formulae for Commonwealth liabilities under the Act. Any increase in payable amounts produced by the prescribed calculations will be borne by the Commonwealth budget lines that fund those statutory allowances. Operational costs of compliance fall on the administering department.

Duties imposed by the Order are procedural and arithmetic. The Order does not create offences; it prescribes how to calculate amounts that are rights under the Governor‑General Act 1974.

Primary duties for administrators:

• Determine inputs precisely: administrators must identify the transfer amount payable at the operative time (numerous provisions: ss 6, 7, 8, 11, 12, 13), the dates when allowances become payable (ss 7, 8, 11), the Chief Justice’s salary at operative times or dates of payment (see s 4 definition and repeated references), and the relevant Treasury bond rates (s 4).

• Apply staged escalation or discount calculations: For deferred allowances and for operative‑time reductions, administrators must increase the transfer amount for discrete segments (first period, full financial year(s), final period) using the Treasury bond rate and daily counts (ss 7 Step 2B-2D; 11 Step 2B-2D). That requires precise date arithmetic.

• Use the Schedule factors and formulae: For valuation conversions between annual rates and present values, the Order mandates use of allowance valuation factors and scheme value factors in Schedule 1 (ss 5; Schedule 1 Divs 1.2-1.4). The conversion method is algebraic: divide the annual rate by the age‑ and gender‑specific factor, and use the allowance valuation factor appropriate to the allowance type.

• Follow rounding conventions: Monetary increases are rounded to 2 decimal places (rounding up on a 5 in the third decimal), and the fraction of the Chief Justice’s salary (the intermediate rate) is rounded to 4 decimal places (rounding up on 5 in the fifth decimal). Administrators must apply these rounding rules at the precise steps dictated (e.g. ss 7 Steps 2B-2D for 2 decimal rounding; ss 6 Step 4, 7 Step 5 for 4 decimal rounding).

• Where there are multiple payment splits, steps must be repeated in chronological order (Notes to ss 9 and 10).

Rights created or given effect to by the Order:

• Entitlements under the Act (associate immediate allowance, associate deferred allowance, retirement allowance, spouse allowance, and scheme value) continue to exist, but their numeric realisation is fixed by the Order’s methods. The Order does not change eligibility criteria; it prescribes how to compute the amounts once eligibility and operative events are determined under the Act.

Discretion and decision points:

• The Order leaves no discretion about formulas: it instructs precise steps and sourced inputs. However, administrators must exercise judgement in identifying certain factual matters required by the Act and the Order: operative time, when an associate deferred allowance "becomes payable", the dates for payment splits, and whether Treasury bonds with a 10‑year term were issued on the last working day of the prior financial year (s 4).

• The Minister who made the Order has the statutory authority to do so under the Governor‑General Act 1974 (s 3), but the Order itself commits administrators to fixed methods.

Recordkeeping and evidential duties (implicit):

• The repeated references to specific dates, RBA yields, and the Chief Justice’s salary imply a duty to record date‑stamped data and calculation steps so that the prescribed rounding and sequencing can be audited or reproduced.

The Order does not enact offences or monetary penalties. It is an instrument that prescribes calculation methods and factors to be applied under the Governor‑General Act 1974. The text contains no penal provisions, enforcement powers or administrative sanctions. Instead, the Order functions as a technical implement to determine the monetary amounts payable under the Act.

Practical enforcement mechanisms and likely loci of compliance:

• Administrative control: Compliance will be enforced administratively by the department or agency responsible for paying allowances under the Act. Those administrators must apply the Order’s prescribed arithmetic (ss 5-13, Schedule 1) when determining payments. The instrument binds those making the calculations; incorrect application likely becomes a matter of administrative rectification under the Act or departmental procedure.

• Auditability and documentation: The Order’s many cross‑references, date‑specific inputs (Chief Justice’s salary and RBA yields), and explicit rounding steps produce an audit trail requirement. While the Order does not itself require recordkeeping, applying it in practice will require retaining source data (dates, RBA yields, salary figures) and stepwise calculations to justify amounts.

• Interaction with the Governor‑General Act 1974: Any formal enforcement (penalties, remedies) for wrong payment or misapplication of the law would be anchored in the primary statute, not the Order. The Order repeatedly directs administrators to treat amounts "as if" certain steps had occurred (for example s 8(2) treating increases as if an associate deferred allowance had become payable at date of death), but it does not provide enforcement sanctions.

Risks and implementation issues relevant to enforcement:

• Input errors: The Order passes enforcement pressure to ensure accurate sourcing of inputs (RBA yields and Chief Justice’s salary) and correct date arithmetic. Errors in those inputs will directly affect payable amounts and the administrative process for correction.

• Rounding effects: Because the Order mandates rounding at multiple intermediate steps, small numerical differences can accumulate; enforcement or correction disputes may necessitate precise reproduction of rounding steps.

• Multiple payment splits: The Order requires sequential repetition where there have been multiple payment splits (notes to ss 9-10). Administrative failure to sequence correctly may produce incorrect amounts, but the Order lacks its own penalty apparatus; resolution would fall to statutory or administrative remedies under the Act or Comptroller/Finance procedures.

In short, this instrument is not a punitive instrument; it is a technical directive for computation. Any formal enforcement of incorrect calculation or payment will rely on the machinery of the Governor‑General Act 1974 and the administrative processes of the paying department.

Primary statutory interaction:

• Governor‑General Act 1974: The Order is made under that Act (s 3) and repeatedly implements or gives content to provisions of that Act. The Order explicitly references subsections and concepts from the Act that it quantifies: subsection 2A(2) definitions (mentioned in s 4 Note), subsection 4AB (associate immediate allowance, s 6), subsection 4AC (associate deferred allowance, ss 7-8), subsection 4AE (reductions after operative time, ss 9-10), subsection 4AF (operative time during growth phase, s 11), and subsection 4AG (reduction of standard allowance payable at operative time, s 12), and the definition of scheme value (s 5). The Order does not change eligibility or substantive rights; it translates statutory references into numerical methodology.

• Salaries and determinations of judicial pay: The Order uses the “Chief Justice’s salary” as the monetary unit for converting between rates and fractions (s 4 and numerous steps). Therefore, changes to judicial remuneration as set under the judicial remuneration regime will alter the numerical expression of allowances when the Order requires use of that salary at a given date.

• Reserve Bank of Australia publications and Commonwealth bond issuance: The Treasury bond rate definition (s 4) ties the Order to RBA published yields or to the actual annual rate of return on Treasury bonds with a 10‑year term if such bonds were issued on a specific day. The Order therefore imports external monetary market data into its operation and is sensitive to how RBA provides yield data.

• Superannuation and surcharge regimes: Section 13 applies a special method where “a Governor‑General who was first appointed between 20 August 1996 to 1 July 2005” and “if superannuation surcharge applies.” The Order therefore expects application of external superannuation or surcharge rules (which are not reprinted in the Order). Administrators must determine whether a superannuation surcharge applies under the relevant revenue or superannuation law and then apply s 13’s arithmetic.

Cross‑reference and dependence structure:

• The Order cross‑references multiple provisions of the Act and relies on Act definitions. For example, s 5 imports the Schedule into the Act’s definition of scheme value; Schedule 1 in turn cross‑references section 7 (ATA calculation) for one of its factors (Schedule 1 Div 1.2 item 2 refers to ATA from s 7, adjusted to the relevant date).

• The Order instructs administrators to "disregard subsection 4(4) of the Act" in some intermediate steps (for example s 9 Steps 1-3 repeatedly instruct identification "disregarding subsection 4(4) of the Act"). That means the Order prescribes whether to treat certain statutory constraints or offsets as being ignored in intermediate arithmetic. The ultimate treatment of those statutory provisions is therefore split between the primary Act and this Order’s computational direction.

Potential operational conflicts or dependencies:

• Timing and data publication: Because the calculation of increases depends on Treasury bond rates for specific financial years and the Chief Justice’s salary at specific times, there is a dependency on the timing and availability of those data sources. If RBA yields or salary determinations are delayed, administrators are given no alternative in the Order beyond the specified definitions (s 4), and must determine the proper date to use.

• Differences in factor tables: The Order supplies two tables (Schedule 1 Part 2 Table 1 and Table 2) with different numeric values and labels (indexed age allowance factors, widow/widower/associate factors, scheme value allowance valuation factors). Administrators must choose the correct table and column per the Order’s explicit instruction in each step (for example s 9 Step 4 uses Table 2; s 6 Step 2 uses Table 1).

• Interaction with Act provisions not reproduced here: Because the Order relies on, and instructs how to treat, specific Act subsections (for example 4(4)), administrators must apply both instruments together. The Order does not displace or amend the primary legislation; it gives numerical content to statutory formulae.

In sum, the Order is a technical, subordinate instrument that operationally depends on other legal and factual inputs: the Act for substantive rights and definitions, judicial remuneration determinations for conversion units, RBA or Treasury bond yields for escalation, and superannuation/surcharge law for cohort‑specific rules. Administering the Order requires coordination across those sources.

The instrument text as provided contains a single creation entry and no subsequent amendments. Documented timeline and metadata in the Order:

• Made: The instrument is dated 12 March 2013 and is signed by the Minister for Finance and Deregulation (cover).

• Commencement: The Order commenced on 15 March 2013 (s 2).

• Authority: The instrument expressly states it is made under the Governor‑General Act 1974 (s 3).

There are no amendment clauses, expiry provisions, transitional provisions beyond those embedded in calculation steps, or subsequent amending instruments included in the text. The Schedule contains definitions and numeric tables as of the instrument's making; the Order instructs that scheme value is determined "using the methods and factors set out in Schedule 1 as in force at the operative time" (s 5). That formulation implies the possibility of future amendment to Schedule 1 (i.e. tables or methods could be varied later and those variations would apply at future operative times), but the Order itself records no history of such amendments. Administrators implementing the instrument must therefore check whether Schedule 1 or the Order has been subsequently amended or replaced when applying it at any operative time beyond the instrument's commencement date.

No revocation or replacement of prior instruments is recorded in the text provided. The Order does not incorporate any automatic indexation or formula for changing the Tables themselves; the escaling of transfer amounts is tied to external Treasury bond rates, but the core valuation Tables 1 and 2 are static numeric schedules embedded in the instrument until changed by further legislative or regulatory action.

Where a later audit or legal query examines amounts payable under the Act for periods after 15 March 2013, administrators must verify they used the version of Schedule 1 "as in force at the operative time" (s 5), which may require checking consolidated or current instrument registers kept by the responsible department or the Commonwealth's Federal Register of Legislation.

The Order as provided contains no citations to case law and contains no record of litigation. The instrument itself does not reference any judicial decisions, and there are no notes of judicial consideration attached.

What this means for practitioners:

• There is no litigation history recorded in the text to guide interpretation of ambiguous steps or rounding practices. Any disputed interpretation would therefore need to be resolved by applying standard principles of statutory interpretation to the Order together with the relevant sections of the Governor‑General Act 1974.

• The Order's arithmetic specificity and multiple rounding points suggest that numerical disputes are likely to be technical and fact‑based (e.g. whether the correct RBA yield for a given day was used, whether the correct Chief Justice salary figure at a particular date was applied, whether the sequence of payment splits was applied in chronological order). Resolution of such disputes would rest on documentary evidence of the inputs and calculation steps.

• Because the Order contains no penalties or enforcement provisions, disputes about incorrect payments will primarily be administrative or civil in nature and will implicate the remedies available under the Governor‑General Act 1974 or general administrative law, but the Order provides no guidance on remedies.

If litigation arises concerning amounts computed under this Order, a court or tribunal will likely be asked to review whether administrators followed the stepwise methods, used the correct external inputs (RBA yields, bond issues, Chief Justice salary), respected rounding directions, and sequenced payment split calculations correctly. Because the Order supplies precise arithmetic, judicial review would likely focus on factual compliance and the proper application of the instrument’s steps rather than the policy rationale behind the rates or tables.

Several practical traps for administrators, advisers and those advising beneficiaries are embedded in the Order’s mechanics. The following items are concrete, source‑grounded risks or complexities that can cause calculation error or unintended outcomes.

1. Multiple rounding stages produce non‑linear effects

• The Order specifies rounding to 2 decimal places for increases in transfer amounts (ss 7 Step 2B-2D; 11 Step 2B-2D) and 4 decimal places for fractions of the Chief Justice’s salary that represent rates (e.g. s 6 Step 4; s 7 Step 5). Because rounding is applied at intermediate steps, small input differences or different sequencing can yield materially different final amounts. The Order mandates which rounding point to apply and when.

2. The Chief Justice’s salary is the monetary unit and must be sourced for specific dates

• Multiple steps divide by the Chief Justice’s salary at a specified time and then multiply by it after rounding (e.g. ss 6 Step 4-5, 7 Step 5-6, 9 Step 13). Administrators must ensure they use the correct salary figure for the exact date the Order specifies (operative time, when the allowance becomes payable, when the Governor‑General died, etc.). There is no alternative unit in the Order. Changes in judicial remuneration between operative time and payment date will alter results.

3. Treasury bond rate sourcing logic creates a data dependency

• The Treasury bond rate is defined to be the yield on 10‑year Treasury bonds issued on the last working day of the prior financial year if such bonds were issued on that day; otherwise it is the RBA‑published 10‑year yield for that day (s 4). Administrators must correctly determine whether bonds were issued on that day; if they were, they must use the actual annual return on those bonds rather than the RBA published yield. That choice can materially change the escalation calculation.

4. Date counting and period segmentation are precise

• For escalating the transfer amount (ss 7 and 11), the Order breaks the time between operative time and when an allowance becomes payable into a first period, zero or more full financial years (second period), and a final period. Administrators must compute the shorter of two periods for the first period, then identify any full financial years, and then handle the residual final period. Errors in date segmentation will yield incorrect increases.

5. Payment splits must be handled sequentially

• Notes to ss 9 and 10 insist that if there has been more than one payment split, steps 1 to 11 (or 12) must be repeated in the order that the splits happened from earliest to latest. Failure to sequence repeats correctly will give wrong reductions.

6. Cross‑references to the Act require correct legal interpretation

• The Order repeatedly instructs administrators to “disregard subsection 4(4) of the Act” in certain interim steps or to treat amounts “disregarding subsection 4(4) of the Act” (ss 9-12). Administrators must understand subsection 4(4) of the Governor‑General Act 1974 to know when it is to be disregarded for purposes of the intermediate arithmetic and when it applies to the ultimate entitlement. This requires applying the Order together with the primary Act.

7. Cohort‑specific rule for superannuation surcharge

• Section 13 applies only to Governors‑General first appointed between 20 August 1996 and 1 July 2005 where a "superannuation surcharge applies". Determining whether the surcharge applies requires applying external tax/superannuation law. There is no explanation in the Order of how to determine surcharge status; administrators must consult relevant tax or superannuation statutes and records.

8. Schedule 1 contains a non‑trivial “end date” rule for unknown term end

• Schedule 1 Div 1.1 defines “end date” for valuation when the date a Governor‑General will cease to hold office is unknown. The rule depends on whether the officeholder has held office for less than 5 years, or 5 years or more, and sets different end dates (5 years after commencement or 6 months after the date the value is calculated). This has valuation consequences and requires precise assessment of tenure as at the valuation date.

9. Some formulae appear as embedded images

• The Order’s text sometimes presents formulae as images (for example the "Calculate an amount using the formula" lines followed by an image). Administrators need to ensure they are using the exact algebraic expressions embedded in the instrument rather than approximations. Any transcription error from image to spreadsheet will produce calculational divergence.

10. Interplay of member spouse age in whole years and months

• Many steps require the member spouse’s or non‑member spouse’s age in whole years and the number of whole months not included in those years (the variable m). Ambiguities may arise if age is not computed consistently (which day counts to use). The Order’s repeated use of "age in whole years" and "number of whole months" obliges administrators to settle a precise convention and document it.

11. Multiple valuation tables with similar labels

• Schedule 1 provides several factor columns with close labels (indexed age allowance factor, widower/associate indexed age allowance, indexed age allowance factor for widow/associate, scheme value allowance valuation factors). Administrators must map the correct Table and column to each step; mistakes in table selection will yield incorrect results.

12. No penalties in the Order for miscalculation

• The Order contains no sanctions or remediation procedures. Any correction of errors or disputes will be handled under the Governor‑General Act 1974 or by administrative processes. Practitioners should record steps to expedite dispute resolution.

Administrators and advisers should document inputs, date arithmetic, table lookups and rounding at each step, and be prepared to reproduce a full calculation chain to meet audit or beneficiary queries.

This section sets out a practical compliance checklist and recommended administrative controls, grounded in the specific requirements of the Order (ss 2-13 and Schedule 1). The Order prescribes deterministic arithmetic steps and specific data inputs; compliance is therefore procedural and record‑driven.

1. Establish governance and responsibility

• Assign a single responsible officer or team charged with computing Governor‑General Scheme calculations and maintaining authoritative records. The Order creates little interpretive discretion; the responsible officer must ensure technical correctness and retention of source data.

2. Record key dates and events

• For each case, record the operative time, the date(s) when an associate deferred allowance becomes payable, dates of any payment splits, date of death (if relevant), and the date that the value is being calculated. These dates determine segmentation into first, second and final periods for transfer amount escalations (ss 7 Step 2B-2D; 11 Step 2B-2D) and influence end date determination under Schedule 1 Div 1.1.

3. Source and archive input data

• Chief Justice’s salary: obtain the precise annual rate applicable at the dates specified in the Order (operative time, date allowance becomes payable, date of death, etc.). Record official documents that set the salary for that date, as the Order requires division and multiplication by that figure at various steps (e.g. s 6 Step 4-5).
• Treasury bond rate: follow s 4: on each relevant calculation date, determine whether Treasury bonds with a 10‑year term were issued on the last working day of the prior financial year. If yes, obtain the annual rate of return on those bonds for that day; if not, obtain the RBA‑published 10‑year bond yield for that day. Archive the RBA source and any Treasury bond issue data used.
• Transfer amount and allowance rates: extract the transfer amount that was payable at the operative time, and any retirement or spouse allowance rates as directed in the Order. Where the Order instructs to "identify the annual rate ... disregarding subsection 4(4) of the Act", document the calculation and the source of the disregarded item.

4. Implement the arithmetic and tables exactly

• Implement the formulae as printed (pay attention where formulae are presented as images). Use Schedule 1 Tables 1 and 2 for allowance valuation factors (Schedule 1 Div 1.4 and Part 2). Ensure correct selection of the table column for the relevant party (male/female, retirement allowance vs spouse/associate allowance, scheme value factor vs allowance valuation factor).

5. Apply date segmentation rules precisely

• For escalation of transfer amounts, compute first period as the shorter of: (a) period between operative time and end of the financial year of operative time, and (b) period between operative time and when the deferred allowance becomes payable (ss 7 Step 2B; 11 Step 2B). Then identify any complete financial years (second period) and any residual final period. Compute increases for each segment using the Treasury bond rate and the day counts as specified.

6. Apply rounding rules at the prescribed points

• Monetary increases in transfer amounts are rounded to 2 decimal places with specified tie treatment (round up on 5 in the third decimal) (ss 7 Step 2B-2D; 11 Step 2B-2D). Rates expressed as fractions of the Chief Justice’s salary must be rounded to 4 decimal places (round up on 5 in fifth decimal) (for example s 6 Step 4; s 7 Step 5). Make sure rounding is coded into spreadsheets or calculation templates at the correct intermediate steps.

7. Handle multiple payment splits sequentially

• If there is more than one payment split, repeat the prescribed steps in chronological order (notes to ss 9 and 10). Maintain a ledger of splits and the resulting recalculations. Ensure that earlier splits are applied and deducted before computing the impact of later splits.

8. Special rules and cohort checks

• Apply s 13’s special method for Governors‑General first appointed between 20 August 1996 and 1 July 2005 if a superannuation surcharge applies. That requires a separate determination of surcharge status under tax or superannuation law; document the legal basis for the surcharge determination before applying s 13 arithmetic.

9. Audit trail and documentation

• For each calculation, retain: the transfer amount and its provenance; the RBA or Treasury bond data used; the Chief Justice salary documents; the table lookups; intermediate calculation spreadsheets showing the segmentation and rounding at each step; and sign‑offs by the responsible officer. The Order’s precision will require that calculations be fully reproducible.

10. Quality assurance and peer review

• Subject every computation to independent peer review by a second qualified officer to detect table selection, date segmentation, input sourcing, or rounding errors. Because the Order lacks a penalty mechanism but creates obligations under the Act, internal controls are the principal risk mitigation.

11. Reconcile and communicate

• When communicating calculated amounts to beneficiaries or budgets, indicate the date used for the Chief Justice’s salary and the RBA/Treasury bond rate. If amounts change because later data correct earlier inputs, maintain a versioned record of prior calculations and the reason for any adjustment.

12. Legal coordination

• Coordinate with legal counsel when an input requires interpretation of the Governor‑General Act 1974 (for example whether subsection 4(4) applies and should be disregarded at an intermediate step), or when a superannuation surcharge determination is necessary. The Order’s arithmetic depends on the correct legal classification of certain amounts.

Practical technologies and templates:

• Use locked spreadsheets or calculation modules that implement the Order’s step sequence and rounding precisely. Embed table lookups for Schedule 1 Tables 1 and 2, and code the date segmentation logic for periods. Keep templates version controlled and signed off by legal and finance.

By following the above checklist and documenting every step and input source, administrators will comply with the Order’s procedural requirements and be able to reproduce calculations for audit or query.