Forum Discussion

AaronWood's avatar
AaronWood
Contributing User
5 years ago
Solved

2019 Individual Income Tax return lodgement error CMN.ATO.IITR.730001

Hi, We recently attempted to lodge a 2019 Individual Income Tax return with a Work Related Car expense claim. The software requires us to make a log book claim using schedule MVE 'Motor Vehicle...
  • MattN's avatar
    MattN
    5 years ago

    Hi AaronWood,

     

    for clients who had downloaded prior to and including the 3rd, there was an rounding issue with Cents per km calcuations on the D1 field - and was corrected with a hotfix (it's the reason why we had to delay the release (we had intended to get it out on the Tuesday of that week) - some clients had downloaded early.

     

    looking at the list of things our development team have identified and worked in since the 2019.0 release, it looks like it has been addressed for Logbook rounding as well - and should be in the 2019.0a release which is due out in the next few weeks.

     

     

MattN's avatar
MattN
MYOB Moderator

Hi AaronWood  and RPD 

 

can you please advise :

 

  • are you using the Cents per km method for calcuation; and
  • what date you downloaded tax 2019.0 / 5.4.32 release.

 

AaronWood's avatar
AaronWood
Contributing User
5 years ago

Hi MattN ,

We are only using the logbook method in the MVE schedule, which integrates to the logboook method section of schedule DS.

We have identified a work around.

Instead of putting the correct gross amounts in MVE and the correct busines use % into MVE we ended up manually calculating the business use amounts (gross amount x business use %) and populating the areas in the MVE schedule with these amounts and then we made the business use 100%. This meant that the automatic calculation in the DS schedule for the "Gross amount excl. depreciation" disclosure was a whole number and no longer contained cents in the figure (which it previously did). This meant that the two gross amounts disclosed in DS schedule (ie. "Gross Depreciation" and "Gross amount excl. depreciation") now correctly agreed to the total of the gross amounts shown in MVE.

We then attempted to lodge this manipulated return with the ATO and it was successfully lodged with them.

Clearly this is not the correct way in which to complete MVE and DS from the ATO's point of view, but we have taken the view that we have ended up with the correct result in the tax return.

We will amend and relodge the tax return once this problem has been fixed in a subsquent patch/update by MYOB.

We had our IT consultant download tax 2019.0 / 5.4.32 release on either Thursday 4th July or Tuesday 9th of July. Will this make a difference?

Thanks for your assistance Matt.

Regards
Aaron Wood

  • MattN's avatar
    MattN
    MYOB Moderator
    5 years ago

    Hi AaronWood,

     

    for clients who had downloaded prior to and including the 3rd, there was an rounding issue with Cents per km calcuations on the D1 field - and was corrected with a hotfix (it's the reason why we had to delay the release (we had intended to get it out on the Tuesday of that week) - some clients had downloaded early.

     

    looking at the list of things our development team have identified and worked in since the 2019.0 release, it looks like it has been addressed for Logbook rounding as well - and should be in the 2019.0a release which is due out in the next few weeks.

     

     

    • Kevo88's avatar
      Kevo88
      User
      5 years ago

      Have downloaded the 2019.0a MYOB AE Tax.

       

      Still having issues with D1

       

      The motor vehicle schedule (MVE) allocated to D1 appears to be showing no cents. The new DDCTNS schedule includes cents which orginal (MVE) schedule does not.

       

      Current work around it adjusting (MVE) schedule to match the rounding error in DDCTN schedule. Boss managed to lodge 2 returns today.

      • AaronWood's avatar
        AaronWood
        Contributing User
        5 years ago

        Hi Kevo88 

        Thanks for the information regarding the work around for the error still in 2019.a

        Cheers

    • AaronWood's avatar
      AaronWood
      Contributing User
      5 years ago

      Hi MattN 

      Great to hear MYOB will be fixing this in the 2019.0a release.

      Thanks for your time addressing this issue.

      Regards
      Aaron Wood