2 Issues with STP and Accounts hosted - Version Number and Business Phone with +61

Peter van Dijk
Peter van Dijk Member Posts: 1
edited October 2019 in Accounts Hosted
Dear Reckon,

2 minor issues we have come across with the STP JSON file generated from Accounts Hosted Payroll.

A fix would lie somewhere between Accounts Hosted, the STP app or the STP file specification

1. Our BusinessPhone field included in the STP export has a "+612" in it – we send our invoices to overseas customers and this field is printed on our invoices, statements, etc. IE this is part of our company configuration and then used by a number of templates.

We have to manually edit each JSON file and replace "+612" with "02" - not a big deal ... but another manual step.

It may make sense to cleanse the phone numbers in the STP App?

2. The current version of Accounts Hosted (2019 r2) generates the following version in the JSON file

    "Version":  "v2",

This is not accepted by the Reckon STP app and it generates a "Product Key Invalid" error.

Amending the JSON file entry to

    "Version":  "v1",

fixes this.

This would appear to be a problem with Accounts Hosted (2019 r2) or the STP App.

Once again not a big issue, but surely it defeats the purpose of STP to manually edit the JSON files to make it work.

Regards Peter

Comments

  • Rav
    Rav Administrator, Reckon Staff Posts: 15,305 Community Manager Community Manager
    edited October 2019
    Hi Peter,
    Thanks for your post. Just before I jump into this I just want to clarify, when you say STP app in your post above, do you mean the GovConnect service in our Portal? OR do you mean the smartphone-only micro-business STP app

    For point 1, usually I'd recommend adjusting the phone number in the Company Information section in the software itself ie. Reckon Accounts Hosted as we don't really recommend tinkering with the JSON file once its been created. On the flipside however, I can totally understand how this can be a hurdle particularly when it comes to overseas based customers as you've mentioned.
    I'm not overly across the specifics but from what I understand there are a multitude of data integrity checks that are performed on the JSON both at the GovConnect level and then of course at the ATO end to ensure it conforms to a certain standard and all required data fields & parameters are intact.

    In regard to point 2, this is something that I'm a bit more concerned about. Changing the 'v' or version number in the JSON shouldn't be required and to be honest, it shouldn't be working in this manner either. Do you edit this parameter each and every time you attempt to upload a submission recently? Just to triple check you're definitely using Reckon Accounts Hosted 2019 R2?


    ℹ️ Stay up to date with important news & announcements for your Reckon software! Click HERE for more info.