Create payee

Hey

What is the best way to handle this? Are there any plans to add payee creation soon? It makes it rather difficult to use the API to create transactions when we cannot create payees. 

13replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Scott Robertson It's on the list!  "payee_name" will be able to be passed to the writable transaction endpoints to resolve an existing payee (by name) or create a new one if it does not exist.  ETA: mid-next week.

    Reply Like 1
  • Awesome!

    By the sounds of things, i should just wait until next week before starting any more threads ha... 

    Reply Like
  • Brady at YNAB one more question...

    If i supply a payee_name without a category_id, would the API autofill the category in any way?

    Reply Like
    • Scott Robertson That's a good idea to allow setting the category (if not specified) by the payee.  We store "category autofill" setting for each payee, based on previous categorization so I think this would be feasible.  I'll add it to our list. I can't promise but it seems fairly straightforward to implement and would be helpful.

      Reply Like
      • Scott Robertson
      • syncforynab.com Founder
      • scottrobertson
      • 1 yr ago
      • Reported - view

      Brady at YNAB perfect. Those 2 things together would allow me to get rid of this messy logic, and would make things much more consistent! https://github.com/scottrobertson/fintech-to-ynab/blob/master/app/services/ynab_transaction_creator.rb#L43-L48

      Reply Like
    • Scott Robertson Oh yeah, that would certainly reduce the need for that logic!  By the way, I like your project!  The new possibilities being opened up by PSD2 are really neat and it's fun to see projects like your's starting to take advantage of it.

      Reply Like
      • Scott Robertson
      • syncforynab.com Founder
      • scottrobertson
      • 1 yr ago
      • Reported - view

      Brady at YNAB Thank you :) Really looking forward to all the PSD2 stuff, which is why i am super excited about the bulk endpoint! Gonna integrate teller.io next once we have the duplicate detection working in a bit nicer/more reliable way which opens things up to a huge amount more banks.

      Reply Like
      • Scott Robertson
      • syncforynab.com Founder
      • scottrobertson
      • 1 yr ago
      • Reported - view

      Brady at YNAB Will this also handle cases when people have renamed Payees? I assume like Direct Import's do?

      Reply Like
    • Scott Robertson Initially no - the payee_name specified would be used to create or use an existing payee by that name.  We have "payee rename rules" for Direct Import which allows for imported payees being renamed in YNAB to be remembered and used going forward.  To use these through the API, we'd need to implement it.  I'll add it to the request list.

      Reply Like
      • Scott Robertson
      • syncforynab.com Founder
      • scottrobertson
      • 1 yr ago
      • 1
      • Reported - view

      Brady at YNAB Awesome thanks. That would keep things much more consistent across the app. Even if it was an option we had to pass into the API call to allow/or disallow auto renaming.

      Sorry for making the list longer and longer :D 

      Reply Like 1
    • Brady Bit late to the API beta, but enjoying playing around with it! Thanks for all your hard work. This payee renaming functionality in the API is exactly what I'm looking for – any follow-up about whether it is being implemented?

      Reply Like
    • Thomas Kilgour Thanks for the feedback!  It hasn't been implemented yet but it's still on the list.  It would certainly be a handy thing to have in the API.  I can't give you a definitive answer on if/when it will be implemented but I think it's likely we'll get it added in the not-too-distant future.

      Reply Like 2
    • Scott Robertson and Thomas Kilgour  A followup on this: payee rename rules support has been implemented!

      Reply Like 1
Like1 Follow
  • Status Added to feature requests
  • 1 Likes
  • 1 yr agoLast active
  • 13Replies
  • 1221Views
  • 5 Following