3 results found

1. on multi coded contacts be able to exclude suppliers

   on multi coded contacts be able to exclude suppliers

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Archived  ·  0 comments  ·  Cleanup  ·  Delete…  ·  Admin →

2. Multi-Coded Contacts Transaction Dismiss

   I have noticed that in the multi-coded contacts that when an item has been dismissed for a contact all future items are dismissed in the same way as such I am having to review both the dismissed section and suggested every time I review to ensure that everything has been correctly coded. For example contact Jo blogs who is normally a supplier of material which we code as such then also charges us for some machinery which we capitalise and dismiss - this is fine. The following week perhaps we have accidently coded the materials purchase to IT costs, this will be dismissed already due to the fact that we have dismissed Jo blogs as a multi coded contact. So effectively the one transaction was fine to dismiss but that doesnt mean I dont want to ignore all future issues..

   The solution that I would ideally want is the ability to dismiss the individual transaction in my example instead of dismissing Jo as an individual that has multi-coded transactions I would want to dismiss the transaction that was capitalised.. Therefore any future miscoding's will again be flagged if again I am okay with the different coding I can dismiss that transaction but I want this to be flagged each time otherwise I am going to have to review the dismissed section every time..

   I don't think this should replace the current way it works but having the ability to do both of these will be big for me and my team. I would use the transactional dismiss more then a contact however there is use cases for the contact as well i.e. places like Amazon I would keep here but as I say I think a transactional dismiss would be superior.

   Another option which would also work but would not be as good would just be the ability to add a note to contacts or transactions within the Dext Precision platform so when I am reviewing the dismissed items I can see why my team have done that instead of having to check for myself.

   I have noticed that in the multi-coded contacts that when an item has been dismissed for a contact all future items are dismissed in the same way as such I am having to review both the dismissed section and suggested every time I review to ensure that everything has been correctly coded. For example contact Jo blogs who is normally a supplier of material which we code as such then also charges us for some machinery which we capitalise and dismiss - this is fine. The following week perhaps we have accidently coded the materials purchase to IT costs, this… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Archived  ·  0 comments  ·  Cleanup  ·  Delete…  ·  Admin →

3. Receipt bank integration

   Feature request....
   The set contact default is kind of useful however the problem is most people are not entering invoices directly in to Xero therefore the default does not auto populate. Why not also link in with Receipt Bank therefore setting supplier / contact defaults there - this would ensure that the data comes in to the system correct / clean

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Archived  ·  0 comments  ·  Cleanup  ·  Delete…  ·  Admin →