[Unistats] RE: Quality issues on data submission to the Australian Taxation
Office
Ted Gallop
T.Gallop@curtin.edu.au
Thu, 20 Feb 2003 09:50:57 +0800
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2D882.82C93E10
Content-Type: text/plain;
charset="iso-8859-1"
John,
Thanks for looking into this.
I don't want to be 'difficult' on this matter, and I know tthe AVCC has
taken a positive role in trying to keep the communication lines open, but
there is a matter of principle involved.
The reason for people, including myself, overlooking the import of these
changes is quite simple.
When reading emails regarding validation changes one expects new validations
to validate against new specifications. It is my view that the 'official'
requirements for the collection are set down in the collection
specifications.
When changes to the requirements take place, one expects the data
specifications to be changed and the validations to follow that process.
This is not what happened in this case. The DEST requirements about what is
allowable in the address fields clearly conflict with the validations
imposed by DESTPAC! This is still the case today.
The ATO requirements are back-door changes to the specifications of the
student collection, that have not been implemented as changes to the
specifications. How many different avenues are there to be (and how many are
we expected to monitor) in repect of setting University data reporting
requirements?
Regards,
Ted Gallop
-----Original Message-----
From: John Mullarvey [mailto:tjm@avcc.edu.au]
Sent: Wednesday, 19 February 2003 6:25 pm
To: #AVCC - Snr.Uni.Administrators
Cc: #RA - DEST Data Coordinators
Subject: Quality issues on data submission to the Australian Taxation Office
Senior University Administrators
Cc DEST data co-ordinators
Given the comments I have received both formally and informally on the
Australian Taxation Office (ATO) data issues, I thought it timely to
elaborate on the AVCC stance and where it originally came from.
As you know the underpinning reason for the different address formats
required by the ATO was due to its strict internal requirements. This was
first discussed in 2000/2001, for implementation in 2002. The ATO's
integrated system architecture, put in place quite some time ago, does not
allow the alignment with DEST's format and therefore was not negotiable.
After extensive consultation with data collection co-ordinators, the final
specifications for the ATO changes, were sent to universities around August
2001 by DEST.
There is no fault re the data reporting specifications released to
universities by DEST, particularly re the various address formats. However,
the AVCC is fully aware that there has not been any validation implemented
in DESTPAC for the ATO address fields in 2002. (DESTPAC is the data
validation software provided by DEST for universities' data cleansing prior
to data submission to DEST). As a result, some format errors were detected
by the ATO in the second submission of 2002 HECS Due file. One of the
reasons for not having such validation requirements in place in DESTPAC 2002
was due to its implementation costs.
The AVCC was recently requested by the ATO to relay these data issues,
experienced in sub 2/2002, to universities to avert any future recurrence
(reason for doing so was stated in my previous email). DEST, at the request
of the ATO, also implemented the validation of these ATO address fields in
DESTPAC for 2003 submissions.
The AVCC, following representations from the ATO, agreed to circulate their
concerns to universities in advance of the 2003 submissions.
Finally, as you would appreciate, once the validations are implemented,
universities would not be able to submit their data files until all such
errors are cleared. It is therefore recommended that this should be taken
into account in planning your submission deadlines this year.
Cheers
john
-----Original Message-----
From: John Mullarvey [ mailto:tjm@avcc.edu.au <mailto:tjm@avcc.edu.au> ]
Sent: Wednesday, 12 February 2003 5:43 PM
To: #AVCC - Snr.Uni.Administrators
Cc: #RA - DEST Data Coordinators
Subject: Quality issues on data submission to the Australian Taxation Office
- FOR ACTION PLEASE
Importance: High
Senior University Administrators
Cc DEST Stats Coordinators
The Australian Taxation Office (ATO) has recently approached the AVCC
regarding the quality of the 2002's second data submission by universities.
This was followed up by a meeting recently held between the ATO and the
AVCC, to discuss issues pertaining to the ATO concern on the non-compliance
of the address field format in the 2nd submission of HECS Due file (part of
the changes introduced in 2002).
The errors outlined in the ATO summary report (see attached), while all
related to format errors in reporting institution address, students' postal
and permanent addresses and low in occurrence in relation to the total
number of student records, have significant impacts on ATO processing. The
tight deadlines of income tax account processing are difficult to
re-schedule as a result of data errors.
Loading of the HECS Due Files is part of a lengthy automated system process
spanning over 5 nights at the ATO. Just one errant record encountered is
enough to bring the process to a halt, not only delaying the HECS Load but
also impeding on other system processes integral to the maintenance of
taxation accounts. Because of the number of contending processes and
competing system priorities, rescheduling the HECS Load is a logistical
nightmare. In addition to the system impacts, manual work-arounds are
required to be implemented. Finding available staff to obviate these
problems presents its own understandable difficulties for the ATO.
The time-critical HECS Load for Semester one 2003 presents a potential for
even more serious implications if similar errors are encountered again. In
gearing up to deal with the receipt and upload of HECS data associated with
the forthcoming 2003 first submission by universities, the ATO is seeking
universities' co-operation to ensure that these problems do not recur in
2003. I urge you to work with the ATO to eliminate any potential problem
of this nature.
In assisting universities to isolate these problems and developing
solutions, the following ATO contact officers are available for
consultation:
Len Quinn Ph. 0262163606 E-Mail. Leonard.Quinn@ato.gov.au
Phil Cue Ph. 0262163724 E-Mail. Phil.Cue@ato.gov.au
Damien Hocart Ph. 0392153918 E-Mail. Damien.Hocart@ato.gov.au
Anything you can do to assist with these problems would be appreciated.
Cheers
john
<<HECS 2002 Sub2 Errors summary by University.xls>>
------_=_NextPart_001_01C2D882.82C93E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>FW: Quality issues on data submission to the Australian Taxation =
Office - FOR ACTION PLEASE</TITLE>
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C2D85D.A98159E0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>0</w:Zoom>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt =
72.0pt 90.0pt; mso-header-margin: 36.0pt; mso-footer-margin: 36.0pt; =
mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoBodyText {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 6pt; COLOR: black; FONT-FAMILY: =
Arial; mso-bidi-font-family: "Times New Roman"; mso-bidi-font-size: =
10.0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"
}
LI.MsoBodyText {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 6pt; COLOR: black; FONT-FAMILY: =
Arial; mso-bidi-font-family: "Times New Roman"; mso-bidi-font-size: =
10.0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"
}
DIV.MsoBodyText {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 6pt; COLOR: black; FONT-FAMILY: =
Arial; mso-bidi-font-family: "Times New Roman"; mso-bidi-font-size: =
10.0pt; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
SPAN.EmailStyle20 {
COLOR: navy; mso-bidi-font-family: Arial; mso-style-type: personal; =
mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; =
mso-hansi-font-family: Arial
}
SPAN.EmailStyle21 {
COLOR: #993366; mso-bidi-font-family: Arial; mso-style-type: personal; =
mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; =
mso-hansi-font-family: Arial
}
SPAN.EmailStyle22 {
COLOR: #003300; mso-bidi-font-family: Arial; mso-style-type: =
personal-reply; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: =
Arial; mso-hansi-font-family: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: 36.0pt" vLink=3Dblue =
link=3Dblue>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>John,</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff size=3D2>Thanks=20
for looking into this. </FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D978523101-20022003>I don't want to be 'difficult' on this =
matter,=20
and I know tthe AVCC has taken a positive role in trying to keep =
the=20
communication lines open, but there is a matter of principle=20
involved.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D978523101-20022003></SPAN><SPAN=20
class=3D978523101-20022003></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D978523101-20022003>The reason for people, including=20
myself, overlooking the import of these changes is quite simple.=20
</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff size=3D2>When=20
reading emails regarding validation changes one expects =
new validations to=20
validate against new specifications. It is my view that the =
'official'=20
requirements for the collection are set down in the collection =
specifications.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff size=3D2>When=20
changes to the requirements take place, one expects the data=20
specifications to be changed and the validations to follow that =
process.=20
This is not what happened in this case. The DEST requirements =
about what is=20
allowable in the address fields clearly conflict with the validations =
imposed=20
by DESTPAC! This is still the case today.</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D978523101-20022003>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
ATO requirements are back-door changes to the =
specifications of the=20
student collection, that have not been implemented as changes to the=20
specifications. How many different avenues are there to be (and how =
many are we=20
expected to monitor) in repect of setting University data reporting=20
requirements?</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff size=3D2>Ted=20
Gallop</FONT></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV></SPAN></DIV>
<DIV><SPAN class=3D978523101-20022003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> John Mullarvey=20
[mailto:tjm@avcc.edu.au]<BR><B>Sent:</B> Wednesday, 19 February 2003 =
6:25=20
pm<BR><B>To:</B> #AVCC - Snr.Uni.Administrators<BR><B>Cc:</B> #RA - =
DEST Data=20
Coordinators<BR><B>Subject:</B> Quality issues on data submission to =
the=20
Australian Taxation Office <BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">Senior University=20
Administrators<o:p></o:p></SPAN></SPAN></FONT></P>
<P class=3DMsoBodyText style=3D"TEXT-INDENT: 36pt"><FONT face=3DArial =
color=3Dblack=20
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">Cc<SPAN style=3D"mso-spacerun: =
yes"> =20
</SPAN>DEST data co-ordinators<o:p></o:p></SPAN></SPAN></FONT></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">Given the comments I=20
</SPAN></SPAN></FONT><FONT color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">have=20
</SPAN></FONT><SPAN lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: =
EN-AU">received both=20
formally and informally on the Australian Taxation Office (ATO) data=20
issues,<SPAN style=3D"mso-spacerun: yes"> </SPAN></SPAN><FONT=20
color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">I=20
thought it timely </SPAN></FONT><SPAN lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: EN-AU">to =
elaborate on=20
the AVCC stance and where it originally came =
from.<o:p></o:p></SPAN></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">As you know the underpinning =
reason for the=20
different address formats required by the ATO was due to its strict =
internal=20
requirements.<SPAN style=3D"mso-spacerun: yes"> </SPAN>This was =
first=20
discussed in 2000/2001, for implementation in 2002.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>The =
ATO</SPAN></SPAN></FONT><FONT=20
color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">’s</SPAN></FONT><SPAN=20
lang=3DEN-AU style=3D"mso-bidi-font-family: Arial; mso-ansi-language: =
EN-AU">=20
integrated system architecture, put in place quite some time ago, =
</SPAN><FONT=20
color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">does</SPAN></FONT><SPAN=20
lang=3DEN-AU style=3D"mso-bidi-font-family: Arial; mso-ansi-language: =
EN-AU"> not=20
allow the alignment with DEST’s format and therefore was not =
negotiable.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>After extensive=20
consult</SPAN><FONT color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">ation</SPAN></FONT><SPAN=20
lang=3DEN-AU style=3D"mso-bidi-font-family: Arial; mso-ansi-language: =
EN-AU"> with=20
data collection co-ordinators, the final specifications for the ATO =
changes,=20
were sent to universities around August 2001 by DEST.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">There is no fault re the data =
reporting=20
specifications released to universities by DEST, particularly re the =
various=20
address formats.<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>However, the=20
AVCC is fully aware that there has not been any validation =
implemented in=20
DESTPAC for the ATO address fields in 2002. (DESTPAC is the data =
validation=20
software provided by DEST for universities’ data cleansing =
prior to data=20
submission to DEST).<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>As a=20
result, some format errors were detected by the ATO in the second =
submission=20
of 2002 HECS Due file.<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>One=20
of the reasons for not having such validation =
</SPAN></SPAN></FONT><FONT=20
color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">requirements=20
</SPAN></FONT><SPAN lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: EN-AU">in =
place in=20
DESTPAC 2002 was due to its implementation costs. =
<o:p></o:p></SPAN></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">The AVCC was recently requested =
by the ATO=20
to relay these data issues, experienced in sub 2/2002, to =
universities to=20
avert any future recurrence (reason for doing so was stated in my =
previous=20
email).<SPAN style=3D"mso-spacerun: yes"> </SPAN>DEST, at the =
request of=20
the ATO, also implemented the validation of these ATO address fields =
in=20
DESTPAC for 2003 submissions.<SPAN=20
style=3D"mso-spacerun: yes"> =20
</SPAN><o:p></o:p></SPAN></SPAN></FONT></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3D#003300 =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; COLOR: #003300; mso-bidi-font-family: =
Arial; mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">T</SPAN></SPAN></FONT><SPAN =
lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: EN-AU">he =
AVCC,=20
</SPAN><FONT color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">following=20
representations from the </SPAN></FONT><SPAN lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: EN-AU">ATO,=20
</SPAN><FONT color=3D#003300><SPAN lang=3DEN-AU=20
style=3D"COLOR: #003300; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU">agreed=20
to circulate their concerns to universities in advance of the=20
</SPAN></FONT><SPAN lang=3DEN-AU=20
style=3D"mso-bidi-font-family: Arial; mso-ansi-language: EN-AU">2003=20
submissions.<SPAN style=3D"mso-spacerun: yes"> =20
</SPAN><o:p></o:p></SPAN></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: 10.0pt">Finally, as you would =
appreciate, once the=20
validations are implemented, universities would not be able to submit =
their=20
data files until all such errors are cleared.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>It is therefore =
recommended that=20
this should be taken into account in planning your submission =
deadlines this=20
year.<SPAN style=3D"mso-spacerun: yes"> =20
</SPAN><o:p></o:p></SPAN></SPAN></FONT></P>
<P class=3DMsoBodyText><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-AU=20
style=3D"FONT-SIZE: 11pt; mso-bidi-font-family: Arial; =
mso-ansi-language: EN-AU"><SPAN=20
style=3D"mso-bidi-font-size: =
10.0pt">Cheers<o:p></o:p></SPAN></SPAN></FONT></P>
<P class=3DMsoBodyText><SPAN class=3DEmailStyle22><FONT face=3DArial =
color=3D#003300=20
size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">john<o:p></o:p></SPAN></FONT></SPAN></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: black"><SPAN=20
style=3D"mso-spacerun: yes"> </SPAN></SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">-----Original=20
Message-----</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: =
black">=20
<BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">From: John Mullarvey [<A=20
href=3D"mailto:tjm@avcc.edu.au">mailto:tjm@avcc.edu.au</A>] =
</SPAN></FONT><FONT=20
color=3Dblack><SPAN style=3D"COLOR: black"><BR></SPAN></FONT><FONT =
color=3Dblack=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black">Sent: =
Wednesday, 12=20
February 2003 5:43 PM</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">To: #AVCC -=20
Snr.Uni.Administrators</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Cc: #RA - DEST Data=20
Coordinators</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: =
black">=20
<BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Subject: Quality issues on =
data=20
submission to the Australian Taxation Office - FOR ACTION=20
PLEASE</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: black"> =
<BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Importance: =
High</SPAN></FONT><FONT=20
color=3Dblack><SPAN style=3D"COLOR: black"> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3D"Times New Roman"=20
color=3Dblack size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: =
black"><![if !supportEmptyParas]><![endif]> </SPAN></FONT><FONT=20
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Senior University=20
Administrators</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: =
black">=20
<BR> </SPAN></FONT><FONT =
color=3Dblack=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black">Cc DEST Stats=20
Coordinators</SPAN></FONT><FONT color=3Dblack><SPAN style=3D"COLOR: =
black">=20
</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">The Australian Taxation =
Office (ATO) has=20
recently approached the AVCC regarding the quality of the 2002's =
second data=20
submission by universities. This was followed up by a =
meeting=20
recently held between the ATO and the AVCC, to discuss issues =
pertaining to=20
the ATO concern on the non-compliance of the address field =
format in the=20
2nd submission of HECS Due file (part of the changes introduced in=20
2002).</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">The errors outlined in the =
ATO summary=20
report (see attached), while all related to format errors in =
reporting=20
institution address, students' postal and permanent addresses and low =
in=20
occurrence in relation to the total number of student records, have=20
significant impacts on ATO processing. The tight =
deadlines of=20
income tax account processing are difficult to re-schedule as a =
result of data=20
errors. </SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Loading of the HECS Due Files =
is part of=20
a lengthy automated system process spanning over 5 nights at the =
ATO. =20
Just one errant record encountered is enough to bring the process to =
a halt,=20
not only delaying the HECS Load but also impeding on other system =
processes=20
integral to the maintenance of taxation accounts. Because of =
the number=20
of contending processes and competing system priorities, rescheduling =
the HECS=20
Load is a logistical nightmare. In addition to the system =
impacts,=20
manual work-arounds are required to be implemented. Finding =
available=20
staff to obviate these problems presents its own understandable =
difficulties=20
for the ATO. </SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">The time-critical HECS Load =
for Semester=20
one 2003 presents a potential for even more serious implications if =
similar=20
errors are encountered again. In gearing up to deal with the =
receipt and=20
upload of HECS data associated with the forthcoming 2003 first =
submission by=20
universities, the ATO is seeking universities' co-operation to ensure =
that=20
these problems do not recur in 2003. I urge you to work =
with the=20
ATO to eliminate any potential problem of this nature. =
</SPAN></FONT><FONT=20
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">In assisting universities to =
isolate=20
these problems and developing solutions, the following ATO contact =
officers=20
are available for consultation: </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Len=20
Quinn =20
Ph. 0262163606 =
E-Mail.=20
Leonard.Quinn@ato.gov.au</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"> <BR></SPAN></FONT><FONT color=3Dblack =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Phil=20
Cue =20
Ph. 0262163724 =
E-Mail.=20
Phil.Cue@ato.gov.au</SPAN></FONT><FONT color=3Dblack><SPAN =
style=3D"COLOR: black">=20
<BR></SPAN></FONT><FONT color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Damien Hocart Ph. =
0392153918 E-Mail.=20
Damien.Hocart@ato.gov.au =20
</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: black"><![if =
!supportEmptyParas]><![endif]> </SPAN></FONT><FONT=20
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Anything you can do to assist =
with these=20
problems would be appreciated.</SPAN></FONT><FONT color=3Dblack><SPAN =
style=3D"COLOR: black"> </SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">Cheers</SPAN></FONT><FONT=20
color=3Dblack><SPAN style=3D"COLOR: black"> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black">john</SPAN></FONT><FONT=20
color=3Dblack><SPAN style=3D"COLOR: black"> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black"> <<HECS 2002 Sub2 =
Errors=20
summary by University.xls>> </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: black"><![if =
!supportEmptyParas]><![endif]> </SPAN></FONT><FONT=20
color=3Dblack><SPAN=20
style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>
------_=_NextPart_001_01C2D882.82C93E10--