The WRE MST will be Reporting Party (RP) context in the 4 wre.0003 2017.lodge 19.07.2018 N/A Closed INC000033383826 WRE Message Structure Table (MST) updated to document that has Min Occurs of zero (0), which the Reporting (RP) does not align with the WRE context has a Min Occurs validation rule VR.ATO.GEN.000209 of one (1). advising 'The number of Reporting party contexts must equal 1'. When VR.ATO.IITR.200034 is Code has been updated 5 iitr.0005.2018.lodge 19.07.2018 5.07.2018 Closed INC000033722882 triggered by an IITR lodgment and so that when the request does not include any VR.ATO.IITR.200034 is Super Lump Sum related elements triggered the (i.e. when SLSSeqNum Context is CMN.ATO.IITR.201034 NULL), a message is returned when SLSSeqNum is returned instead of Context is NULL. CMN.ATO.IITR.201034 message text. When an IITR request is Code will be updated to 6 iitr.0005.2018.lodge 19.07.2018 10.07.2018 Closed INC000033688344 submitted with only one correctly process IITR INC000033698737 SLSSeqNum context supplied, lodgments when only one INC000033722504 interactive error SLSSeqNum context is CMN.ATO.GEN.EM0002 is being provided. incorrectly returned with error code 91902. When an IITR lodge request is A new SBR channel 7 iitr.0005.2018.lodge 16.08.2018 29.09.2018 Resolved INC000032790997 submitted where SLS payment validation rule will be details are reported but not all fields introduced, which aligns have been completed, the lodgment with the current is rejected with interactive error interactive error, to reject message CMN.ATO.IITR.EM0032. an IITR lodge request when all SLS payment fields have not been provided, instead of passing onto the backend systems.
4 Reporting Party (RP) context in the WRE Message Structure Table (MST) has Min Occurs of zero (0), which does not align with the WRE validation rule VR.ATO.GEN.000209 advising 'The number of Reporting party contexts must equal 1'. wre.0003 2017.lodge INC000033383826 The WRE MST will be updated to document that the Reporting (RP) context has a Min Occurs of one (1). 19.07.2018 N/A Closed 5 When VR.ATO.IITR.200034 is triggered by an IITR lodgment and the request does not include any Super Lump Sum related elements (i.e. when SLSSeqNum Context is NULL), a is returned instead of CMN.ATO.IITR.201034 message text. iitr.0005.2018.lodge INC000033722882 Code has been updated so that when VR.ATO.IITR.200034 is triggered the CMN.ATO.IITR.201034 message is returned when SLSSeqNum Context is NULL. 19.07.2018 5.07.2018 Closed 6 When an IITR request is submitted with only one SLSSeqNum context supplied, interactive error CMN.ATO.GEN.EM0002 is being incorrectly returned with error code 91902. iitr.0005.2018.lodge INC000033688344 INC000033698737 INC000033722504 Code will be updated to correctly process IITR lodgments when only one SLSSeqNum context is provided. 19.07.2018 10.07.2018 Closed 7 When an IITR lodge request is submitted where SLS payment details are reported but not all fields have been completed, the lodgment is rejected with interactive error message CMN.ATO.IITR.EM0032. iitr.0005.2018.lodge INC000032790997 A new SBR channel validation rule will be introduced, which aligns with the current interactive error, to reject an IITR lodge request when all SLS payment fields have not been provided, instead of passing onto the backend systems. 16.08.2018 29.09.2018 Resolved
ATO-IITR-2018-Package-v1.7-Contents.docx