Empty payee in Android app?

I've recently switched to new YNAB from YNAB4, and I'm surprised an annoying behaviour in Classic still exists in the new mobile app.

When I'm inputting a transaction, I can leave the "Payee" field empty without problems. But if geolocation comes in and autofills some nearby payee, app doesn't let me delete it, I must choose an existing payee (or create a new one). If I explicitly want an empty payee (for example because it's some trivial expense like a parking fee, in a place I won't come back), my only option is creating some kind of "No" payee, which is just an ugly hack.

Am I missing something? I sincerely thought it was a bug in Classic, so if all those years later everything is exactly the same and nobody is annoyed, perhaps it's me who's doing something wrong.

Thanks!

10replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Hi jesjimher ! 

    It looks like you're running into a bug we're actively investigating. Would you mind filling out a Bug Report, so we can gather more information? Thank you so much!

    Like
  • I've been experiencing this for as long as I can remember using the app. I have a 'Delete' payee which I routinely edit out on the desktop version. It's not the end of the world but it is annoying.

    Are you guys closer to a fix?

    Like
    • Hi Silver Pilot !

      Sorry for the trouble! We're working on making the mobile app as fully functional as the web app, but we don't have this option specifically pin-pointed. Would you mind submitting a Feature Request? That'll let our Product team know you'd like to see that option soon! :)

      Like
  • Is there any update to this?  I'd really love it if the Payee didn't autopopulate.  Can't delete it, either have to let it be, change it to an already made payee, or create a new one.  We have one-offs that really don't require a payee (more interested in category and account) and when we're entering something on the go, it's frustrating.

    Thanks for any update. :)

    Like
      • JoeDid
      • Remember: It is To Laugh
      • Purple_rain
      • 7 mths ago
      • Reported - view

      Beige Octopus I don't understand why anyone with this problem doesn't just create a "N/A" payee and used that consistently where no payee is needed, but you're required to enter one. Given that no payee tells you nothing, just using the same "N/A" payee does the same thing, and you have to create it only once.

      Like
      • malmomma
      • Beige_Octopus.8
      • 7 mths ago
      • Reported - view

      JoeDid  It was stated above by YNAB that there IS a bug.  I was asking for an update, not a workaround.  

      Like
      • JoeDid
      • Remember: It is To Laugh
      • Purple_rain
      • 7 mths ago
      • 1
      • Reported - view

      Beige Octopus Okay. Rather than light a candle -- even temporarily -- you'd rather curse the darkness. I get it.

      Like 1
    • Beige Octopus At the moment, it isn't possible to enter a transaction with no payee in the Android app, and you'll need to remove the payee in the web app. I don't have an update, but our team will continue to look into this!

      It sounds like you're seeing information populate with Geo Payees? You can turn that feature off on your Android device, and that may help here. The instructions to disable are near the bottom of that article. Give it try and let us know how it goes.

      Like
      • malmomma
      • Beige_Octopus.8
      • 7 mths ago
      • 1
      • Reported - view

      Nicole This was helpful!  I did have that turned on.  I just tested a few entries after turning it off and none of them autopopulated in either Payee or Category, just Account.  Before, they would populate with the same Payee and Category...  Thank you so much!  :)

      JoeDid Again, I wasn't asking for a workaround.  I didn't need one because I already had my own in place.  I was asking for an update on the bug mentioned in this thread.  Why stir up trouble where there is none?

      Like 1
      • JoeDid
      • Remember: It is To Laugh
      • Purple_rain
      • 7 mths ago
      • Reported - view

      Beige Octopus Yes, you've made your point. I'm sorry that what you saw as stirring up trouble was meant as a helpful workaround for a problem that was troubling you. I won't bother you again.

      Like
Like2 Follow
  • 2 Likes
  • 7 mths agoLast active
  • 10Replies
  • 96Views
  • 7 Following