Skip to Main Content
Reckon Product Ideas
Make a difference by sharing your ideas with the Reckon product development team. Your votes will directly influence the product roadmap and help guide our products future direction.

Please note all new ideas remain hidden from public view until reviewed by our team.


Announcement: September 2023

We are currently well underway building our next-gen user interfaces, starting with Payroll web and mobile (released), Invoices mobile (released) and soon, advanced Payroll, Reckon Mate enhancements, and Time web.

Where appropriate we'll add features from the Product Ideas Portal to both old and new interfaces, or, where new is replacing old, we'll add to the new range only.

Thank you for your patience - whilst we understand building new interfaces and products takes longer than adding a feature, we are certain the new designs will ultimately provide a better experience for all our customers.

Regards,
The Reckon Product Team


Status Planning to do
Workspace Reckon One
Categories Basics (core)
Created by Guest
Created on Jun 19, 2020

Be able to edit items when not registered for GST

My business is small and as such is not (and not required to be) registered for GST. If the registered for GST option in reckon one is set to 'no' items in reckon one cannot be edited due to the following error: "Tax is set as included but no purchase tax code selected"

  • Attach files
  • Admin
    Jason Hollis
    Reply
    |
    Jun 23, 2020

    Hi John, we have been able to reproduce. It is quite possible one of your chart of account items or product service items has a tax code.

    Please go to your settings and turn GST registration ON so you can track tax. Check your chart of accounts and remove any DEFAULT tax codes. Then check your items and remove any tax codes. Turn tax tracking off.

    This should resolve the issue. We'll look into ensuring a user cant get into this state.

    Please let us know how you got on.

  • Admin
    Jason Hollis
    Reply
    |
    Jun 23, 2020

    Hi John. Sounds like a bug. I'll check with the team to ensure it's been logged.