Year 2000 Preparations in the Australian Banking and Financial System Appendix 3 – Year 2000 Preparations in the Australian Banking and Financial System

Definition of Year 2000 Compliance

The standard definition of Year 2000 conformity prepared by British Standards Institute (DISC PD2000-1) is a useful benchmark definition. The definition below incorporates minor amendments by Standards Australia.

Year 2000 Conformity shall mean that neither performance nor functionality is affected by dates prior to, during or after the Year 2000

Rule 1

‘No value for current date will cause any interruption in operation’

This rule is sometimes referred to as General Integrity.

If this requirement is satisfied, roll-over between all significant time demarcations (e.g. days, months, years, centuries) will be performed correctly.

‘Current date’ refers to today's date as known to the equipment or software.

Rule 2

‘Date-based functionality must behave consistently for dates prior to, during and after Year 2000’

This rule is sometimes referred to as Date Integrity.

The rule means that all equipment and software must calculate, manipulate and represent dates correctly for the purpose for which they were intended.

The meaning of functionality includes both processes and the results of these processes.

If desired, a reference point for date values and calculations may be added by organisations: e.g. as defined by the Gregorian calendar.

No equipment or software shall use particular date values for special meanings: e.g. ‘99’ to signify ‘no end value’ or ‘end of file’, or ‘00’ to mean ‘not applicable’ or ‘beginning of file’.

Rule 3

‘In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or interfacing rules’

This rule is sometimes referred to as explicit/implicit century.

It covers two general approaches:

explicit representation of year in dates: e.g. by using four digits or by including a century indicator. In this case, a reference may be inserted[2] and it may be necessary to allow for exceptions where domain-specific standards (e.g. standards relating to Electronic Data Interchange, Automatic Teller Machines or Bankers Automated Clearing Service) should have precedence.

the use of inferencing rules: e.g. two-digit years with a greater value than 50 imply 19xx, those with a value equal to or less than 50 imply 20xx. Rules for century inferencing as a whole must apply to all contexts in which the date is used, although different inferencing rules may apply to different date sets.

Rule 4

‘Year 2000 must be recognised as a leap year in terms of handling both the 29th of February and day 366’

The Year 2000 is a leap year, whereas the years 1800 and 1900 were not. Hence for proper compliance there must be rollover from 28-02-2000 to 29-02-2000 (and subsequently to 01-03-2000), and from 28-02-1900 to 01-03-1900.

General Notes

For rules 1 and 2 in particular, organisations may wish to specify allowable ranges for values of current date and dates to be manipulated. The ranges may relate to the feasible life-span of equipment or products and/or the span of dates required to be represented by the organisation's business processes. Tests for specifically critical dates may also be added (eg for leap years, end of year, etc.). Organisations may wish to append additional material in support of local requirements.

Where the term century is used, clear distinction should be made between the ‘value’ denoting the century (e.g. 20th) and its representation in dates (e.g. 19xx): similarly, 21st and 20xx.

In order to encourage a uniform approach to date fields, organisations may wish to consider following the Commonwealth of Australia's convention for expressing the date field – CCYYMMDD.


e.g. 4-digit years as allowed by AS 3802-1989[1] [2]