Skip to Content

Release Notes

A steady stream of YNAB improvements for your reading pleasure. Grab some tea. Curl up with a Snuggy® and enjoy.

YNAB Is Always Improving
YNAB Is Always Improving

Web Release Notes: July 21st, 2020

We made a few behind-the-scenes fixes today, and one in-front-of-the-scenes fix:

  • Fixed some problems, including a crash, that could happen after creating a goal in a future month.

Web Release Notes: July 16th, 2020

Good morning! We’ve got a few YNAB fixes and improvements coming in hot with today’s release:

  • Links from our Help tool (blue “?” icon in the bottom right corner) were not working properly in Safari, but now they are!
  • We’ve disabled browser autocomplete recommendations on inputs that already have dropdown lists.
  • In some cases when you cancelled your request to sign on with Apple, you would get an unfriendly error instead of being taken back to where you were. We fixed that.

Web Release Notes: July 15th, 2020

This release fixes a couple of small issues preventing some users from syncing changes from our mobile (iOS / Android) apps. Don’t know about our mobile apps? Learn more.

Web Release Notes: July 14th, 2020

For today’s release, we’re continuing to make improvements to the Direct Import process by adding more helpful messaging and alerts and really tightening up the flow there. 

Along with those Direct Import improvements, we also made a fix to the new goals that we added a few months ago. The Needed for Spending: Weekly goal had a bug where if you selected “Every Friday” or “Every Saturday” due specifically in December 2020, the goal was prompting users to budget for 5 weeks rather than 4. All fixed now!

API News

“Continue with Apple” was not working as it should when authorizing one of our API Applications. Once you logged in with Apple we were not properly returning you back to the screen to authorize the app. Now we will!

Web Release Notes: July 9th, 2020

Earlier this year, we pushed out a release that was the culmination of several months of work for a team here at YNAB that works on Direct Import (AKA the ability for YNAB to connect to your bank and magically pull in transactions). We switched Direct Import providers to a company called Plaid  (a provider that connects many popular financial apps to banks) with the overall goal of making your connection to YNAB more stable. 

In today’s release, we pushed out a bunch of back-end fixes to make your bank connection (via Plaid) more stable and reliable! Also with today’s release:

  • When hovering over your available balance on a category with a goal, we show something called a “tooltip” to give you some helpful information. Well, we were not showing a tooltip for Needed for Spending (By Date) goals that have a repeat scheduled. Now we do!
  • When removing a split , we were not updating the “Amount remaining to assign” totals right away but now we do.
  • We corrected a minor issue with goals behaving inconsistently when created in future months.

Web Release Notes: July 7th, 2020

Happy week after the 4th of July! We released a big (BIG!) revision to goals a couple of weeks back. Well, we uncovered a few issues as you all got in and got your goals on. Like where, in some rare cases, future goals could tell you to budget the wrong amount in the current month, which is especially not helpful. In today’s release, we fixed a few other issues to go alongside our extensive goals fixes:

  • As some of you are aware, we use Ember for our front-end JavaScript framework for YNAB. In this release, we’ve upgraded Ember to version 3.9 which contains various security fixes, reduces file size and improves the performance roughly by 6% on the Budget and by 32% on the Register. Those are performance updates that will make YNAB smoother and faster!
  • We fixed a bug that was making it so that users weren’t able to set goals during the getting started steps in YNAB.
  • We fixed an issue where users weren’t able to close the Budget calendar picker. SIDE NOTE: Being constantly reminded that the date won’t go away is the most 2020 thing ever.
  • And, as always, some under the hood work where we don’t need to bother you all with the details.

API News

  • The API now allows split transactions to be categorized to the Inflow: To be Budgeted category

Web Release Notes: July 2nd, 2020

This morning we’re dropping (like it’s hot…which it is, because it’s Summer) a veritable plethora of layout fixes to make your life better. Have a gander (not the bird, but the “look at a thing” version of that word):

  • We fixed an issue where you couldn’t scroll all the way to the right on the Income v Expense report to see your totals…which, hey…if not seeing your expenses made them actually go away, how cool would that be? Turns out, that’s not the case.
  • We fixed an issue where, if you had a really long category name, the inspector would get cut off. I can’t be the only one who has an “Emergency Fun Socks Only For Extreme Emergencies” category.
  • We also fixed a few display issues when resizing your browser to smaller sizes.

Web Release Notes: June 30th, 2020

Oh, hey. Nothing to see here. But maybe instead of seeing it, you just feel this update as it involved a lot of behind-the-scenes polish…which, can I just give a shout out to proper nouns right now? Because it was behind-the-scenes polish, and maybe not behind-the-scenes Polish. Although, that would be cool too as Poland is a pretty rad country.

Web Release Notes: June 26th, 2020

Should we deploy on a Friday two weeks in a row? No. Did we deploy on a Friday two weeks in a row? Yes. We needed to fix some subtle goal issues so you can happily budget over the weekend!

Web Release Notes: June 25th, 2020

In today’s release, we focused on the inner beauty of the YNAB app and thought we didn’t have much to report, until we remembered the incredibly noteworthy update to all things goals last week and we FORGOT TO TALK ABOUT IT! So, let’s talk about it.

You’ve heard of #lifegoals and maybe even #squadgoals, but what about #goalgoals?! Last week, YNAB fulfilled everyone’s #goalgoals by taking goals in YNAB to the next level. When setting goals in YNAB you’ll now have quite a few more options to help you accomplish all of your #moneygoals.

Of particular sparkly-ness:

  • You can now set a target day of the month for Monthly goals.
  • You can set Weekly goals and specify by day.
  • You can repeat goals every “n” months/years. And “n” in this case stands for number..I think…or maybe just months that start with “n”…November? Napril? Hmm….

Read more about the updates to goals.

Web Release Notes: June 23rd, 2020

You know sometimes when you’re tapping out a text and you’re trying to write “Brian” and it auto-corrects to “Brain”—and then you backspace and type out “Brian” again and it auto-corrects to “Brain”? And then you do it all a third time and throw your phone out the window because, well, just because?

We were doing something kinda like that if you imported a file with memos, undid it, and then tried to import it again. We would autocorrect to use the previous memos. Now, when importing, you get a clean slate. No more Brian>Brain swaparooski.

Also, we heard quarantine was sending people into a home improvement tizzy and we caught the bug and gave the account setup screen a little interior redesign. When you have no accounts in your budget (ha! Remember that precious moment?), you see a cute little piggy traipsing along with a bank instead of a scrawly not-on-brand-anymore treasure hunt map.

Screen Shot 2020-06-17 at 2 09 57 PM

Screen Shot 2020-06-17 at 2 00 57 PM

And one last update to wrap up our productive set:
If you usually operate in USD, and then you opened up your budget and saw 35.43$ you might cringe a little, right? Well, we were doing that to the good people of Poland and a kind Pole informed us that their currency doesn’t look quite right without a space before the currency symbol, so we fixed that:

In other wonderful news, we’ll leave you with this: the official currency of Poland is called “the zloty.”

Web Release Notes: June 19th, 2020

Should we deploy on a Friday? No. Did we deploy on a Friday? Yes. We didn’t want a display issue with our referral program link in Safari lingering around all weekend.

Web Release Notes: June 18, 2020

Update: We pushed out a second release today fixing an issue with Safari where items in the sidebar were not practicing social distancing and getting scrunched up.

In today’s release, we fixed a bug where the tops and bottoms of some letters and emojis in your category names were getting cut off. We wanted to let you know that this was a bug and not a time paradox scenario where the emojis were getting cut off because you had traveled back in time and messed something up where your parents didn’t fall in love, thus making it so that your “Internet School” emoji was getting cut off…”erased from existence!”

Nothing to see here. Just dreaming of purchasing Canada!

If you’re like me, you’re always looking out for those kinds of scenarios and checking past weather events for lightning storms just in case you need to generate the 1.21 gigawatts needed to make the flux capacitor work to time travel back to the present, should you find yourself stranded in the past. To be clear, this is not one of those situations.

Web Release Notes: June 16, 2020

Apropos of nothing everything, I just wanted to say that Atomic Habits, a book by James Clear, kind of rules. And by “kind of rules” I mean it’s inspiring and I love it and want to marry it. In Atomic Habits, Mr. Clear shares the story of the hapless British Cycling team that had been a joke in the cycling world (deemed to have suffered from “100 years of mediocrity”…ouch) until they hired Dave Brailsford as their Performance Director.

Brailsford was relentless in finding small areas where the team could make incremental 1% changes. The team redesigned bike seats, tested and improved racing suit fabrics and rubbed alcohol on the bike handlebars…seemingly trivial stuff in the overall scheme of things. But the “aggregation of these marginal gains” eventually led to huge improvements where, in the 2008 Olympics, the British Cycling team won “60% of all medals available.” Blimey!…might be a thing they remarked about the results?

Speaking of “marginal gains,” in today’s release we:

  • Fixed the literal margins (spacing) and the hover state of transaction flags.
  • Did some work on the details of the deselect checkboxes for categories and subcategories (tightening the margins and what not…you know…the digital equivalent of putting alcohol on the bike handlebars).
  • Added a link to the documentation as to why your credit card payment category is red. Maybe not “your” credit card payment category, but if it is “your” credit card payment category, we want you to know why.

Web Release Notes: June 11, 2020

In today’s release, we fixed the vertical centering on the buttons throughout the app…we’re prefectionists perfectioniss perfectionists:

Dance, buttons, dance!!!
Look at you go, you crazy button!
Front and center(ed)…horizontally…and now vertically

Some of you are going to read this and say, “buttons? That’s not a big deal!” And hey, I get it. It’s a nice, little bit of polish…and we love you for doing this, Kyle…but I want to be super clear that we just pushed out a ton of other changes as well. You’ll see them soon. I guess we could say that these features are “pending?”

Release #2 on June 11, 2020:

We identified and fixed a performance issue when importing direct transactions that caused our database to do more work than needed.

Web Release Notes: June 9, 2020

Today’s release contains some infrastructural changes and some behind-the-scenes optimization and bug-fixing…which, when you think about bug-fixing…if you fix a bug, does that mean it’s still there, but it’s just fixed? Like, if I fix a leaky faucet, the faucet is still there, but the leak is gone….but bugs? I don’t know if we want to just fix them. We probably need to eliminate them. I’ll discuss this with the team and make sure the bugs aren’t still there, even after they’re fixed. I hope that doesn’t weird anyone out to think that there are possibly fixed bugs running around in YNAB.

Web Release Notes: June 4, 2020

We really do put a ton of effort and resources into making sure that you can connect with your bank and give dollars jobs like it was…your job. We recently switched direct import providers (i.e. the service we use to connect YNAB to your bank to pull in transactions) and we hope and anticipate this will be a big improvement. However, there is no perfect way to have direct import work perfectly all the time, just like there is no perfect way to perfectly use the word “perfectly” perfectly multiple times in a sentence. So, in today’s release, we shipped an improvement to how we let you know about connections that don’t go…perfectly.

We’re now showing a “delayed” status for accounts / connections that go for some time without refreshing successfully. This can happen if the institution is having temporary issues or delaying our attempts to refresh the connection, or if it gets stuck somewhere in the process. The good news is that it usually fixes itself after a bit, but it serves as an alert to let you know things aren’t as good as they should be, and that the issues should be resolved momentarily. If you see a “delayed” status, we recommend waiting a couple of days before contacting Support. Read more about delayed connections.

Web Release Notes: June 2, 2020

Today’s release is chock-full (which…I always thought was either “chocked full” or “chalked full”) of all sorts of YNAB-y goodness. But before I get into that, I should probably let you know about my hypothesis on where “chock-full” comes from. I spent the last minute Googling it and I’m like 99% sure a “chock” was maybe like a place in a ship. So, one day, a boat captain was pulling into port and the longshoreman person was like “aye, how much wheat do you have in there, guv’na” and the captain turns to the person in a moment of brilliance and says “aye, the boat ‘tis chock-full.” 

Speaking of boats…look what we’ve shipped today!

  • Avast! A various assortment of Budget table and Edit menu fixes:
    • If you manually added spaces to your category names they will now appear in the budget table like they used to… maybe you’re now trying to socially distance the letters in your category names?
    • The budget table will now adjust column sizes to fit better on smaller and larger screens.
    • If you have a lot of categories, the Edit > Categorize menu used to adjust too much causing it to run off the top of the screen. Now it won’t go farther than the top of the screen…what was even up there? Probably Murder Hornets, right? I don’t want to find out.
    • We fixed the colors on our “Try managing your budget with your Android” banner when using the web app while on a mobile device.
  • The Budget toolbar is now located within the Budget table to give more room to the Budget inspector. Am I the only one who is picturing like a detective sitting at a diner table messing around with tools (probably a magnifying glass) trying to figure out where a certain charge is from?
  • We fixed some display issues with the Accounts toolbar while on smaller screens.
  • For consistency’s sake, we’ve made sure all instances where we mentioned “recurring transactions” will now say “repeating transactions.” No one will ever mention the word “recurring” ever again. We’re now on team “repeating.” I’ll prove this to you now: We’re now on team “repeating.”
  • The content links on our dashboard pointed to somewhat outdated content. We’ve updated those links and prioritized the list slightly differently.
  • Lastly, just for good measure: we’re now on team “repeating.”

UPDATE: After the above release on June 2nd, we made another release:

  • If you tried to go directly to a bookmarked budget, but were logged in as someone else that didn’t have acccess to that budget, YNAB would give you an error message and tell you to reload, which give you the same error and ask you to reload… Not helpful! We’ve now fixed this.

Web Release Notes: May 28, 2020

Oh, the last release of May…it’s almost the end of Spring…which reminds me…have you done your Spring cleaning yet? Or maybe that is all anyone does these days since we’re all at home in this weirdo-with-a-beardo year of 2020. Either way, you may want to look at all of your bank accounts and do some Spring cleaning (AKA simplifying) for your financial life. We made a handy dandy guide on how to make that happen.

Speaking of simplifying: if you haven’t simplified your bank account situation, you may not have noticed this tiny little bug that we introduced. We recently updated some menus and with that update, we prevented the option to move transactions between accounts from becoming enabled if you had only two accounts. But today’s release fixed that issue. Sorry about that, my fellow simplifiers.

Also in today’s release: we’ve made it easier to click/check budget table rows by increasing the area needed to check a category row. This extra space is so luxurious.

Web Release Notes: May 26, 2020

Today’s release features a little bit of sunshine, a little dapple of rainbows and a whole lot of…behind-the-scenes changes. I saw a few mentions of args and like, an Object or maybe a function or something. The net result for you is that YNAB is stable as a table.

Web Release Notes: May 21, 2020

Update: We pushed out a second release today to smooth out some issues related to porting users over to our new direct import provider, Plaid.

There are certain things in life that we inherently know not to do:

  • Don’t touch a hot stove
  • Don’t stick your fingers into electrical sockets
  • Don’t go chasing waterfalls

But there are some things that are maybe less apparent like, “don’t upload an empty .csv to YNAB.” Apparently sometimes that would happen. A YNABer would go in and try and upload an empty .csv file (for whatever reason. We don’t judge) and then they would get a very generic and uninformative error message. With today’s release, though, we clear the proverbial empty .csv air (you know that old proverb, right?) with a much clearer error message:

[YNAB pushes up its glasses on its nose] “Um, are you trying to upload an empty .csv? Um.” [sighs as it puts down its 900-page History of Accounting book]

Also, there’s that old conundrum of “haphazardly clicking outside of popups when you’re right in the middle of something.” And I get it. Clicking on things is fun. Well, before this release, If you went to add a sub category and then you changed your mind and clicked outside of the popup (modal), an error would occur. Now it doesn’t, so feel free to click on anything and everything*.

*Please don’t click the “Unsubscribe from YNAB” button, unless you’re not using YNAB. But you are, right? I mean, you’re reading the Release Notes. Let’s be friends.

Web Release Notes: May 19, 2020

Update: We pushed out a second release today fixing issues with dark mode while adding accounts on mobile as well as fixing display issues in the accounts toolbar on Firefox.

On Sunday, my family and I went for a 5-mile hike up Green Mountain outside of Bremerton, Washington. We were a little worried that our 7-year-old was going to complain as this was easily the longest hike we had ever done. But, the opposite proved to be true. For whatever reason, she woke up and decided that she was no longer our daughter, Nora, but was now “Fluffy the Unicorn.” She dressed in full unicorn attire and decided that her new mantra was that “Fluffy never complains.” It was amazing.

My point here is that unicorns are magic. But you know what else is magic?! Our designers and developers! Check out what these digital unicorns have unicorned for us in today’s update:

  • In true unicorn fashion, we made some visual updates to the register toolbar and edit transaction menu to be more inline with the budget settings menu. And for good measure, we updated some icons as well. Magic!
If your YNAB looks different, it’s because we need you to follow your dreams more, maybe?
  • We’ve also made some visual updates to the budget table. Ooooh SPARKLY!
  • We’re now displaying account number identifiers (last 4 digits) when listing bank accounts to link to YNAB. Total unicorn move right there!

Web Release Notes: May 14, 2020

Big shout out to all of our Safari users today. We all know people who use Safari, right? I just picture all of them wearing black, mock turtle necks while drinking from really small espresso cups typing important things on their Macs. You know who you are, Safari users. Totally kidding. You’re normal and we love you. Also, our Visual Designer/Brand Owner, Lauren uses Safari and she’s one of the most smartest, most talentedest people we know.

Anyway, our pop up (modal) arrows were all askew in Safari, but Kyle went in and did some front-end Kung Fu on them and now they will show up properly in Safari and every browser ever invented until the end of time*.

Yeah…that arrow is supposed to be pointing to that account amount and not pretending to be a shark

*Don’t hold us to that. We can’t guarantee that arrows will exist in the future.

Web Release Notes: May 12, 2020

In today’s release, we made a couple little visual tweaky tweakies, which is a technical term. So, let’s get technical:

The header label for the goal inspector was a little tight…but not the good kind of saying of tight, like, “that Holiday Spending category balance being that high in May is tight, yo” (did you not realize that Jesse Pinkman has been YNAB-ing since YNAB 3?) It was more that it needed a little more breathing room there, so we added a little extra space.

Also, the budget bar background color was maybe kind of hiding a little bit. Not a lot of contrast there, but after this release, it is so noticeably brighter now that it kind of reminds me that I probably need to wash my car…?

Web Release Notes: May 7, 2020

Oh, hello. Nothing major to see here today; just a few behind-the-scenes changes. Something, something Javascript…there was maybe a mention of a database, possibly…I’m not sure what this whole “Skynet 1.0” addition is…hmmm…oh well…

Carry on…

Web Release Notes: May 5, 2020

You know how during this stay-at-home order you’re supposed to make sure you drive your car around every once in a while, so the battery “stays fresh” or something along those lines? Well, apparently, you need to do the same thing in YNAB with hidden categories. Every now and then, make sure you “unhide” them, just to keep them fresh…except, I’m totally kidding. It doesn’t work that way…

…But, it looks like some (not all!) of you fine budgeters had some hidden categories that would simply not come out from hiding! Clicking “unhide” would do nothing. For today’s release, though, we adjusted some behind-the-scenes validation that was causing this issue, so you should be able to unhide those categories now. Also, don’t forget to drive your car around!

Web Release Notes: May 1, 2020

Small change before the weekend. We’ve improved the messaging around some of our direct import connection statuses in the sidebar to make them clearer.

Web Release Notes: April 30, 2020

Update: We pushed out a second release today to fix an issue with our backend analytics tools. This is a behind the scenes change so nothing visible should have changed.

A long, long time ago, Firefox needed us to add basically any data set, so that it would support dragging and dropping to re-organize categories and accounts in YNAB. So naturally, behind-the-scenes we set that data set to “firefox needs this.” Fast forward to today, and now Firefox no longer needs that data set, but if you try dragging a category to reorganize on an iPad, Safari will now hilariously open a web search with “firefox needs this.” These are the kinds of bugs that Kyle, one of our front-end developers, lives and breathes for.

Web Release Notes: April 28, 2020

Update: We pushed out second release today to fix a minor issue with one of our monitoring tools that helps us make sure everything is running like it should. This is a behind the scenes change so nothing visible should have changed.

So, today is the first regular release, in a while, that doesn’t have anything to do with our big project of switching YNABers over to our new direct import provider, Plaid. And much like an angsty teen in Seattle in the early 90’s, we’ve gone to Plaid. We’re now rad like Plaid. Whoa. How is this word not pronounced “played?” Turns out, that there’s no way to know. What is knowable, however, is what we’ve released today:

  • Sorting by category wasn’t working as expected as of a couple of weeks ago. Categories were sorting by an internal ID instead of their names, which would explain why you kept overspending in your jf8s9dk-4jd8sd984-4jlf4gd category.
  • When converting a scheduled transfer transaction into a regular (non-scheduled) transfer transaction, running balances were incorrectly counting that transaction twice. If you saw this error, you are some kind of level 99 YNAB Red Mage or something. Converting a scheduled transfer transaction into a (non-scheduled) transfer transaction??? What even is happening there???
  • If you had a popup (modal) open while you were editing a transaction and then you had clicked the date dropdown for the transaction, the app would crash. We fixed that.
  • We’re asking Apple subscribers to confirm that they’ve canceled their subscription with Apple before going ahead to delete their YNAB account. Look, we think everyone needs a budget, but we also think that you probably don’t want to pay for an app that you’re planning on deleting.

API News

The Public API now supports importing transactions on Linked accounts. When transactions are available from your bank, we allow you to click the “Import (10)” button on the web or tap “10+ New transactions to import, approve, or categorize” on mobile apps to bring these into your budget. Now you can perform this import from the API with a POST to the endpoint.

Web Release Notes: April 27, 2020

It probably goes without saying, but importing transactions from thousands of banks into YNAB accounts is no small technical feat. We’ve only had the direct import option available since 2016, and it’s been an ADVENTURE, y’all. And this is a part of YNAB that we’re always working to improve. But this past week, a core team here at YNAB (and by “here,” I mean Earth, I guess, because we’re remote, so the team spans multiple countries) reached a major milestone in what we hope will bring a major improvement to direct import for YNAB.

Last week, we began porting several thousand YNABers over to our new direct import provider, Plaid. In order to do so, this small team had to design, develop and execute a transition plan that included new UI/UX flows and all sorts of contingencies for “what if” scenarios during the migration. And we’re not out of the woods yet, but things have gone swimmingly…or maybe even amazing. We’ll let you pick a fitting superlative here. 

Anyway, after long hours (which are rare here at YNAB) and tons and tons of quality work, this crew threw a “Plaid Pizza Party”…where the “pizza” is kind of up for interpretation:

It looks like Carlos found the first box that said “Pizza” at the grocery store, Chris ordered the Pizza of the South, AKA Fried Chicken from Zaxby’s. Dylan had $0.00 in his Dining Out budget, but he had enough points to order out (we practice what we preach, yo) and Jannelle whipped up a homemade version with tortillas and spaghetti sauce. I wish you all could understand exactly what went into all of this. This crew rocked it and they definitely deserve their “pizza.”

But also, did I mention these things are complicated? We’re pushing out a quick hotfix today to fix a few things related to all of this work:

  • When users were in Dark Mode, the account selection screen did not look amazing. It was pretty tough to read, so we pushed out a fix to make the text higher contrast along with some changes to the background color.
  • We also fixed the ability to unlink previously linked Cash accounts that have been updated

Web Release Notes: April 24, 2020

We get it. Linking and updating your bank connections is the last thing you want to be doing right now. That’s why we spruced up the list of update-able bank accounts with bigger buttons and more detailed account information. And in the off-chance your finger slips and inadvertently tries to link the wrong account, we now give you a chance to confirm your selection before saving.

Web Release Notes: April 22, 2020

You will likely see a few notices today letting you know that YNAB is updating and you may not see any visible changes. This is because we are in the middle of a few behind-the-scenes, infrastructural changes. If you’re not seeing any visible changes in the app, carry on. If you are, just know that we have our top people working in there, making sure your YNAB experience is as awesome as possible.

Web Release Notes: April 21, 2020

Tuesday. What a concept. This particular Tuesday, we’ve got a veritable cornucopia of fixes and improvements that we’ve shipped out…just in time for Thanksgiving! What? It’s STILL April?!!! OK. Well, we can at least agree that “cornucopia” is an amazing word and we don’t use it enough. There are no rules anymore, except DON’T TOUCH YOUR FACE…which is impossible…where were we? Oh yes, here is a lovely assortment of fixes we released today…just in time for Valentine’s Day…OK, I’ll stop:

  • In order to help all of our OG YNAB 4 users migrate over to…current YNAB(?) we have a link to assist in that migration for new budgets. Until this release, the “Migrate YNAB 4 Budget” link was showing up on the “Budget Settings” popup as well as the “New Budget” popup. It will now only show up on the “New Budget” popup, which makes more sense. 
  • Oh, hey, we fixed the tooltips on the Spending Trends chart. Before this release, Kyle (one of our front-end devs) said that an issue was causing the chart to “gobble the hover event.” Guessing there was a turkey involved there…so maybe Thanksgiving did come early??? ?
  • Before this release, we were sometimes showing an incorrect error message for certain direct import connections. We went through and changed this particular message so that it’s now correct. I know this is vague, but we are doing some exciting things with direct import connections in the coming weeks, so…I think this will make sense in the future.
  • We fixed an issue on the “Add Linked Account” popup where the “Known Connection Issue” text would animate and cover the input field. We fixed that, and we also learned a fun lesson about CSS transition properties as well. Win win?

API News

  • Hot off the presses: You can now specify a transfer payee_id for a subtransaction when creating a split transaction. This allows for split transactions that transfer to another account. I know…split transactions! Our old friend returns! It actually never left, though.
  • Before this release, when a user was presented with the authorization screen for the API and the user decided to log out and log in as a different user to authorize that user instead, they were redirected to their budget when they logged back in, instead of the authorization screen. Now they’re redirected back to the authorization screen so they can, you know, authorize the app.

Web Release Notes: April 16, 2020

So, we’ve had a busy week here at ye olde Y-N-A-B. Also, we don’t ever call it that, but hey, now is as good a time as any to bring out your inner pirate/old-timey shopkeeper. Avast! Look at all these glorious updates:

  • Although not every user will see this right away, we’ve made a ton of improvements to our direct import flow as it pertains to switching import providers. I don’t want to say that we overhauled it, but we definitely didn’t underhaul it either.
  • We’ve updated the text in our direct import connection dialogs to let users know about potential issues connecting to institutions because stimulus check deposits are slowing down some banks.
  • We no longer strip accented characters from the budget name when exporting your budget.
  • We fixed the tooltips on the spending trends chart.
  • We uncovered a user with bad data, where a debt account’s name differed from its payment category’s name. That user was unable to edit their payment category goal, because subcategory name validation was silently failing. This fix prevents name validation from executing except when the name is actually modified. This does not fix the bad data itself, which the user is already able to do, but it will allow them to update goals without having to fix this name issue first.

Web Release Notes: April 14, 2020

Good morning. Like most of us, I’m super distracted right now. I just found out that the new Instant Pot does sous-vide. THE GAME HAS CHANGED, folks. This is like that part in Jurassic Park where the raptors figured out how to open doors. Also, we’ve got some nice fixes and improvements that we’ve pushed out today!       

  • Just in time for Easter, we’ve added some new colors for the Spending Totals and Trends graphs to make the different categories easier to distinguish. Wait. We MISSED Easter?!!!
  • If you’re a regular reader of our Release Notes, you may have noticed that we jumped the gun on announcing some visual updates to the Reports header a few weeks ago (or maybe it was last week?). Well, now, we’ve actually shipped those visual changes where we’re being a little more judicious in our use of the color green and with our pill shapes as well. Consider the gun unjumped!
  • In the Manage Payees screen, you have the option to click to show transactions that are using a particular payee. In some cases, for scheduled transactions, the date being shown would be the first date that a scheduled transaction was…um…scheduled for rather than the next date it was scheduled for. Dates are hard!
  • You may have occasionally experienced an error when opening menus or modals and then trying to add an account. Whoopsies! We fixed this. You know what? Menus and modals are also hard!

Web Release Notes: April 8, 2020

Oh, hey. For those of you who are keeping score at home (and we’re all at home) we normally ship out our bug-fixes and improvements to YNAB on Tuesdays and Thursdays. But today is a Wednesday…or is it? It probably is, but there’s no reliable way of knowing. Either way, we’ve got a few fixes that we just pushed out to make your YNAB experience even better:

  • Most importantly, we fixed an issue that we caused that made it so that clicking “Show all hidden categories” was not actually unhiding hidden categories…so there was that. Those categories should be able to come out of hiding now.
  • In some cases where direct import connections/accounts were going into an error state, we weren’t properly reflecting when they last tried to sync. Basically, the “last updated” timestamp wasn’t reflecting reality. Fixed.
  • We made a minor (or major…hey, the glass is half full, Brady!) improvement when sorting by category: We will now group “Category not needed” and “This needs a category” transactions together.
A thing of beauty…if you don’t like category names, I guess?
  • We made another minor/major improvement so that now, when you click inside the grid container / register area (white space), we will flash the editor if you are currently editing a transaction and have made changes. If you have not made changes we will close the editor. Previously we only did this when clicking on another transaction. This is how it now looks / works:
We don’t like to showboat, but this change is pretty flashy

Web Release Notes: April 7, 2020

I’m sure you remember some of the little bibelots (knick knacks? Chachkies? You know, the junk that your parents hang on the wall) from your parents or grandparents house growing up. My dad got into computers pretty early and the pièce de résistance that he had hanging right above his computer in his office was a cartoon picture of a terrified guy getting covered with dot matrix printer paper while a computer malfunctioned. Above it, there was a huge block of text that read:


Over the years, I’ve heard more colorful versions of that saying, but in today’s fixes, we’ve fixed some human err(or)s that your computers eventually really fouled up:

  • In a previous release, we fixed a bug that allowed users to create duplicate categories when one was hidden. That fix unfortunately also prevented users who already had duplicate categories from saving goals on them. To fix this, we now do duplicate name validation of categories when the category name is being modified.
  • Ever clicked and highlighted the “Some transactions are hidden by filters” text at the bottom of the transaction list when you have filters on? [crickets] Neither had we! But some brave soul did and it apparently causes an error. It was as surprising to us as it was to them. But hey, we fixed it! To those of you about to click (on pretty much everything) we salute you!
  • Changing the flag on a scheduled transfer would sometimes not update the flag on the other side of the transfer. Now that “sometimes” has been turned to “no times(?)” and we’ve fixed the issue.

Web Release Notes: April 2, 2020

So long, March! Feel free to see yourself out. Thanks for nothing!!!! C’mon, April! It’s a new month, and you know what that means…everyone, say it with me…more edge case fixes for SPLIT TRANSACTIONS!!!! The more things change, the more things stay the same. I do feel like, eventually, split transactions will never come up again in the release notes #lifegoals:

  • If you scheduled a split that transfers to another account and then, you rejected the transaction on that other account when the scheduled transaction got entered, we weren’t rejecting the split transaction as well. Now we are! Is your head spinning? Mine is.

Web Release Notes: March 26, 2020

As I started writing these release notes this morning, a bird slammed into my office window…me too, buddy. Me too. Don’t worry, they’re OK. It’s going to be OK. 

We’ve got just a few visual tweaks to call out in this release (along with dozens of behind-the-scenes changes):

  • We made a visual layout change to the navigation bar in the Accounts screen. You’ll notice that the text is now on the bottom…and that Kyle runs a REALLY high balance on his credit card.
Never buy a mansion on credit.
  • We made a small change to the Payments label so that it matches the Overspending label. I lobbied to change them both to Papyrus (you know, real fancy-like, like a day spa or an Asian Fusion restaurant) but we settled on just making them not italicized.

Web Release Notes: March 19, 2020 - Part Two

This hot fix is a bit of a mulligan with our Sign in with Apple feature release from earlier today. Due to Apple not liking a certain kind of encoding, some users weren’t able to effectively Sign in with Apple (which is kind of the point). But we’ve pushed out a fix and this issue should be resolved.

Web Release Notes: March 19, 2020

Today’s release is jam-packed. We’ve pumped up the jam. You could say that this release is our jam. Jam. You get the idea:

Now you can access your YNAB account using Sign in with Apple!

You’ve signed in with a password and you may have signed in with Google, but I don’t think you’ve truly lived until you’ve signed in with Apple. And now, you can (sign in with Apple)! Just think of how convenient it will be to not have to remember your password every time you go into YNAB to give dollars jobs.

The future has truly arrived…or, at least, this is a nice-to-have feature for all of you die hard Apple fans…are we calling you AppleHeads™? I am now.

If you want to make your sign ins more hard core (I know what I did there) head on over to your Account Settings and enable Sign in with Apple!

Other features and fixes in this release

  • When entering a payee for a transaction, we now only select an existing payee automatically if what you typed matches the beginning characters of that existing payee. For example, before this fix, you could type in “Shop” and YNAB could auto-select “Donut Shop.” Now, YNAB will still filter down to “Donut Shop,” but it would only automatically select it if you typed in “Donut.” Oh, great. And now, I want donuts.
  • When creating a “Payoff Balance by Date” goal on a Credit Card Payment Category, selecting a different month and/or year was not working in some cases. Our homie, Brady, came in and dropped the hammer on this bug. All fixed.
  • At very small resolutions, some users were having trouble seeing or clicking buttons when using File-based import. We used a little CSS magic and made a change so that you’ll still be able to see these buttons and click them.
Real time shot of Brady using CSS Magic

Web Release Notes: March 17, 2020

We’re only two and a half months into 2020 and…whoa…not great, 2020. If I were to give the year a grade, it would be just me lighting a report card on fire while tattooing “see me after class” on its arm. There’s a lot of uncertainty and stress and clearly a lot of emotions and things that are best not written in release notes. 

We really do hope that, as a budgeting app and as teachers, we’ve been able to offer you less money stress. That’s the goal. And we will continue to do everything we can to lighten the load.

In today’s release:

  • One of our Product Designers, Emily, fixed up the SVG icons for the budget bar, so they look crisper (I really wanted to write “crispier”) on lower resolution screens. SIDE NOTE: If you want to read a really well written piece on how our designers handle color in YNAB, Emily wrote a three part series on our “Semantic Color System.” It’s fantastic.
  • We fixed an issue that would occur when moving a category from one group to the other. Turns out, we were not properly updating the group totals for Budgeted, Activity, and Available. Now we do!
  • As part of our continued effort to make the web and mobile experiences more cohesive, we have updated “My Account” to be “Account Settings.” We had to make this change in multiple places, and, to be clear, it’s still your account. We haven’t taken that away from you.
  • No way…shocker…we’ve made a fix to our lovable problem child, Split Transactions!!! Now, if you split your transaction but only add one sub-transaction, we’ll create a regular transaction. This mirrors the expected behavior on mobile devices.

Web Release Notes: March 10, 2020

For today’s release, think of YNAB as a really hot sports car…nope, that doesn’t work…maybe like a sensible hybrid that gets the job done, looks clean, yet simple? Maybe there’s a third row for picking up extra kids from basketball, or maybe you’re just putting the seats down for that Costco run where you cleaned them out of apocalypse toilet paper (please, don’t do this). Anyway, you get the idea. Let’s pretend YNAB is your ideal car…and today, we took it to the shop and made it even more…ideallier(?):

  • First stop is the auto body repair shop. We banged and buffed out a few dings from the wear and tear from all of your road trips. Before today’s release, If you created a really, really large goal target and budgeted a really, really small amount to the same category, you could get into a situation where syncing would fail. Kyle put some elbow grease behind this one and fixed it for you!
  • Next, we moved over to the internal messaging system. If you’re like me, you think that the Check Engine light is more of a suggestion than a demand, but messaging is important, so we made some tweaks: Before this update, clicking a Quick Budget button with no categories selected could apply budgeting to all categories. To prevent you from wiping out all your budgeting, we recently started showing a confirmation message. This message was incorrectly including the count of category groups and also indicating that all categories would have budgeting updated. But, depending upon the category, in some cases we might leave it as is! So, we adjusted the message to make this a bit more clear.
  • Who doesn’t love fuel efficiency…and POWER?!!! We made room for more Vroom (we should get this trademarked fast): The register is now faster! Those of you with large registers should notice a nice speed boost when performing actions in the register: sorting, filtering, editing, adding, etc. Scrolling is also a little less laggy.
  • Moving on to…we’ll call this…shocks and struts. It’s a split transaction fix, so I’m just looking for an analogy of something super useful and cool, but also kind of convoluted. Just kidding. We love you, split transactions! Never change…except for when we fix you. Have you ever clicked on a split transaction and it started editing the parent split? Now, if you click on a child split, it will actually start editing that child you clicked. Splitters rejoice!
  • Last stop: paint and detailing. Let’s get this puppy tricked out! Maybe some flames?? A saucy racing stripe? Skullzzzzz? Maybe not those things in particular, but we made visual updates to the settings menu and fixed a bug where the settings menu would show options for a previously opened budget. We also made some visual updates to the main sidebar navigation links.
Room to breathe…
Visual change will NOT add this many millions to your account, unfortunately

API News

Now you can now pass in include_accounts=true query parameter on /budgets endpoint to include each budget’s list of accounts. Bam! It is so on.

Web Release Notes: March 5, 2020

Uncovering and fixing bugs here at YNAB is kind of like an episode of Law & Order…but more like if Law & Order was done using webcam footage and it was just people thinking a lot and typing and clicking on things on their computers. But I would argue that some of the bugs we find and fix are just as intense as some of the crimes that they solve on Law & Order.

In the YNAB bug-fixing system, YNABers are represented by two separate, yet equally important groups: the Support Specialists who investigate potential issues and the Developers who prosecute fix the bugs. These are their stories:


  • We tracked down an interesting bug that seemed to haunt us from our past. Our sleuthing Support Specialist, Robert, uncovered a doozy: When editing a Build Your Savings / Target Balance (By Date) or a Plan Your Spending / By Date goal that has a target date in a prior year, YNAB would not display that year in the year dropdown, but instead pre-select the current year. Brady, threw the book at this bug and we were able to fix this issue for good. Sweet justice.
  • It was a cold Tuesday morning in January. Nothing seemed too out of the ordinary. Just another day of helping YNABers gain total control of their money in the YNAB Support Queue™. Suddenly, a bug. Robert stepped onto the scene of the crime bug to find that YNAB was accidentally closing modals if a user clicked within it, dragged their mouse outside of it and let go. With all of the evidence of this bug that had been brought to light, our hard-nosed Developer, Kyle made short work of this nasty bug. YNAB now only closes the modal if the user explicitly clicks outside the modal to close it. We rest our case…meaning we closed the issue in GitHub, but still.
  • On an undercover assignment (it was cold that morning, so he had a blanket) our Support Specialist, Dan found a small trace of users getting stuck while going through the welcome onboarding flow in YNAB. “Put on another pot of coffee. This may take awhile, team” Dan uttered. After extensive research set to an ominous music montage, he found that If a user set a filter or specified a search before completing the “Schedule a Transaction” onboarding step, they could get stuck on this onboarding step. Brady, our Developer, found that this bug couldn’t handle the truth, and put this bug away for life (I realize that the “A Few Good Men” quote has very little business being in this Law & Order fan-fiction, but it seemed appropriate).

API News

We’ve added some validation for payee_name when creating or updating a transaction through the API. The payee_name can no longer begin with any of the following: (Transfer* :, Starting Balance, Manual Balance Adjustment, Reconciliation Balance Adjustment). This may seem like a bummer when you’re buying a gymnastic balance beam from your favorite store, “Starting Balance,” but we have to draw the line somewhere.

*Note: While we will allow a payee_name beginning with the word “transfer” (or “Transfer”), we won’t allow it if it is followed by “ :” (i.e. “Transfer :”). This is to differentiate it from our standard transfer items.

Web Release Notes: March 3, 2020

API News

Can you do the splits? What am I saying? Of course you can…or, at least now you can. We’ve made our Public API even more flexible because it now supports creating split transactions by specifying a subtransactions array.

curl -H "Authorization: Bearer $API_ACCESS_TOKEN" \ \
-H "Content-Type: application/json" -X POST --data-binary @- << EOF
      "memo":"This is a split",
            "payee_name":"Split payee",
            "memo":"Split 1"
            "memo":"Split 2"
Hooray for split(s)…transactions!!!

Web Release Notes: February 27, 2020

We fixed some rare, but important bugs!

  • Let’s say you have a split transaction, and one of the split entries is a transfer to a “tracking account”, and you were to go into the tracking account and change the amount. With me so far? Well, we used to let you do that. Unfortunately, that could throw off the amount of the entire split transaction, which would cause other trouble down the line. So, we don’t let you do that anymore. If you need to change the amount of that transfer, do it from the split transaction instead please.
  • Here’s another one: Let’s say you moved money between “To Be Budgeted” and another category in the iOS app in January, your very first month of blissful budgeting! Now let’s say you didn’t like that month and deleted all the data because you finally figured this stuff out and wanted February to be your “first month”. Well… we wouldn’t let you have that Win. We’d always remind you of that time you spent in January. Specifically on the web app, reports would still show January, even though you had no data in there. We’ve corrected this issue with the data and fixed the bug in iOS that caused us to have the bad data. (That iOS fix will roll out at a later date).
  • The “Spent Last Month” Quick Budget button was incorrectly incorporating activity from Credit Card Payment categories when viewing all or multiple categories. No more! Now, “Spent Last Month” will only include regular category spending and not count Credit Card Payment activity as “spending”.
  • PS: A developer wrote these release notes instead of our regular, much funnier author. You will be relieved to know that our release notes will once again be full of animated gifs and much funnier jokes for our release next Tuesday!

Web Release Notes: February 25, 2020

So, I’ve been trying to get the devs here to make it so that when you search in YNAB, it plays U2’s “Still Haven’t Found What I’m Looking For” in the background. But I guess there are potential copyright issues…and I’ll concede that the song might wear on you, especially if you really can’t find what you’re looking for. Instead, though, this release makes a few improvements so that you can find what you’re looking for:

  • Previously, if you searched for some text that included a number (i.e. “2020 Ultimate Muffin Party”) we would also return transactions that had a matching amount (i.e. $2,020.00). That was a little presumptuous of us. Jeez, YNAB, not everything needs to be about money…sometimes it can just be about muffins, OK.
  • Before this update, searching for memos that included colons “:” would not work. Now they work, and you can finally search for all of the movie sequels you have purchased by their full names…The Fast and the Furious: Tokyo Drift, Home Alone 2: Lost In New York, City Slickers II: The Legend of Curly’s Gold…we got you.

Lastly, the modal (popup) for adding a sub category wasn’t opening in the correct place. It was more of a failed prototype for a game we like to call Whack-a-Modal. But now, it will show up in the right place.

Web Release Notes: February 20, 2020 - Part 2

UPDATE: We did an additional hotfix (i.e. this fix was NOT cold) this afternoon where we fixed a bug that occurred when users were navigating from the Net Worth report to another report.

Web Release Notes: February 20, 2020

Today we released a few stability fixes having to do with how we handle credit cards on the backend. Also, is Ember the color or your energy? Because we upgraded to Ember 3.2, which includes significant performance and security improvements throughout the app.

There are two improvements that you’ll see in your Accounts screen as well. One of them is pretty straight-forward and one of them might require you to put on another pot of coffee to explain. We might be here awhile:

We had a little currency po-tay-to v. po-tah-to thing going on that we fixed. But first, no one says “po-tah-to.” If you hear someone say that, just know that you may be talking with some kind of incognito alien character straight out of Men In Black. You’ve been warned. But, onto the currency fix:

For a lot of currencies (like USD), using “.” as a separator is the standard. Some use a “,” (like Euros) but for others, using a “/” is the way to go. Now, was I able to successfully Google which currency uses a “/”? Nope. But they exist, and now YNAB will allow users to use this formatting ($99/99) in the register!

Yes, we’re using the dollar sign in this example, but pretend it’s like whatever they use in Luxembourg, but also pretend like they don’t use Euros there.

Lastly, we made a fix to split transactions. And if it seems like we’re always making fixes to split transactions, it’s because we are. They’re complicated. If anyone out there is thinking of making a YNAB clone, and you decide that you’re going to add split transaction functionality…good night and good luck.

Previously, if you created a split transaction with a transfer sub-transaction, then used the Edit menu to categorize the split, it would orphan the transfer transaction. Now, categorizing will skip over the transfer transactions unless it’s to a tracking account. Are you confused? I am. But I have faith that there are YNAB power users out there right now fist-pumping and doing the Macarena because we finally fixed this bug. You are welcome, YNAB super-geniuses of the world.

Web Release Notes: February 13, 2020

Negative category pills are red
Our logo is blue (Sky Blue – #85C3E9)
Oh, hey, check out this fix we’ve just released for you:

Remember that weird extraneous line under the checkbox on the Include in Payee List option within “Manage Payees”? No? You didn’t? Yeah, neither did Kyle, but Alan sure did. Kyle fixed it, Alan! Jeez. Alan. Happy Valentine’s Day!!!….Alan.

Web Release Notes: February 6, 2020

They say that “the devil is in the details,” but they also say that “the devil went down to Georgia,” so unless that dude is cloning himself (we’re all in trouble, if that’s the case) my money is on Georgia. Because this week’s release gets well into the details, and the devil is definitely not in those details, but you know what is? Split transactions. Here are the details on those details:

Previously, if you had a split transaction with a search that partially matched one of the sub-transactions of the split, the bulk Edit > Categorize action would unsplit the transaction and delete all your sub-transactions. Now it only categorizes the transactions you have selected and will only unsplit the transaction if you have all of the sub-transactions of the split selected.

Warning: Budgeting professional at work here. Do NOT change your “Water” to “Electric.”
The results may shock you.

P.S. Look alive, Georgia…[fiddle starts playing]

Web Release Notes: January 24, 2020

Back when YNAB was just a spreadsheet, we only had one developer…and that was just our CEO/Founder, Jesse, creating fancy formulas and the sweetest macros Clippy’s eyes had ever beheld. But nowadays, we have dozens of developers and product designers. 

We have mobile developers for iOS and Android. We have developers who focus on the backend (coding in Ruby) our database (using SQL) and the frontend (using JavaScript, HTML and CSS). Most of our non-mobile developers are “full stack” developers. This normally means that they code in the backend, frontend and database.

In today’s release, one of our full stack devs, Kyle, got to flex his full stack dev chops (can one “flex” a chop?) outside of his normally front end world. Kyle fixed things so that, now, when creating an account for a credit card, if a user plans to pay a specific amount each month, YNAB will create a Monthly goal instead of a By Date goal. Here was the first review item that got checked off to complete this fix:

We also shipped a fix to the running balance feature that we released a few months ago. On an account with a large number of transactions with the same date, moving one of those transactions to the future (to make it a scheduled transaction) was breaking the running balances calculation. But we fixed this issue!…Hey YNABers, is your balance running? After this fix, you might want to go catch it! *rimshot*

Web Release Notes: January 21, 2020

Today we’ve released a handful of infrastructural changes along with a nice, little fix to our API…which, have you heard of our API? It’s pretty neat. It allows developers to do cool stuff like create connections for Australian bank accounts or get your Roomba to chase you around your house when you don’t budget enough in your household expenses category (this might not be possible). Basically, it allows developers outside of YNAB to create tools that interact with other public-facing API’s. Here’s what we fixed with the YNAB API in today’s release:

API News

When using the PATCH on the /budgets/{budget_id}/transactions endpoint to update multiple transactions, we allow you to specify either the import_id or the id of the transaction to update. But, if you specified an import_id and null for the id (rather than omitting id from the object) we would not save the transaction. Fixed!

Web Release Notes: January 14, 2020

Have you ever been sitting in a waiting room somewhere when you notice a picture is just slightly off center, but you didn’t want to stand up in front of a room full of people and adjust the picture so you just sat with your head tilted until it was your turn? Well, if you split a transaction the “remove” button was sort of like that off-centered picture you just couldn’t adjust.  We fixed it, so now there’s no need to tilt your head to keep the button aligned. 

Also, before today we made clicking the “c” button to clear a transaction really unclear–you had to click right on it to get the transaction to change clear statuses. Now, we fixed it so when you click near the symbol in that column it clears. No more squinting and fighting with your mouse to get it to work. Isn’t that perfectly clear? 

Finally, if you’ve ever used YNAB on a small screen or in a smaller window and struggled to scroll on a report and noticed a scrollbar missing or disappearing, we fixed that too, because that’s how we scroll.

Web Release Notes: January 9, 2020

A lot of our weekly releases are centered around bug-fixing and polishing to make YNAB incrementally better every week. Part of the challenge of some of these smaller fixes is determining user intent, which, if you think about it, can be a tricky thing to understand. No two users are the same. Green means “go,” but is green the best color for color blind users? The “Call To Action” or “Happy Path” is always on the right…unless some apps decide to put it on the left (some do). So, our goal is to communicate as clearly as possible in our UI, and also add guardrails to make sure you intended to do the thing you just did:

In this release, we made it so that the “Enter Now” option (in the Edit menu) is now disabled when editing a transaction to prevent accidentally editing a scheduled transaction you are entering now. This is because users would accidentally click on a scheduled transaction twice (going into edit mode), then using “Enter Now” they would fire off the transaction and finally save the scheduled transaction they were editing. So, the schedule transaction gets saved with the old date rather than updating to the next occurrence.

If you’re reading these release notes, we’re hoping that you intend to use YNAB forever. That makes sense, right. You love us, right? Right? Well, if you don’t and you decide to delete your account, we’ll now give you a prompt to disable Two-Step Verification (if you’ve enabled it…which, please do!). This was already necessary but we didn’t make it obvious.

API News

We know you’ve all been clamoring for more error types…wait, what? You haven’t? Oh, that might make sense. Well, we needed to add a new error type to our list. This new 503 error could be returned if we need to temporarily disable access to the API.

Web Release Notes: January 7, 2020

Picture this: It’s 2020. You’re in your flying car and you’re talking to your robot companion helper and you go to enter some account notes and also make some recurring goals to save for your Mars vacation in YNAB….you know, ‘cause it’s 2020 (psst…it’s the FUTURE). But then you realize three things:

  1. When you try to do a line break in the Account Notes section in YNAB, pressing shift + enter doesn’t do a line break, as expected. Ugh (and you were using your holographic keyboard, too…so disappointing).
  2. The “Make Recurring” button display looks a little off in the UI. C’mon!
  3. You don’t actually own a flying car and literally every science fiction author from the past was WAY off about 2020. But we do have Animojis that can make us look like a talking shark when we’re FaceTiming…so, we’re close.

The good news is that this release fixes those other two issues, so 2020 is looking OK already.

Web Release Notes: December 31, 2019

Oh, man. 2020, y’all. It’s coming. Tomorrow. So, tonight the main question on everyone’s mind is “should old acquaintance be forgot?”…you know, like, from the song that everyone sings on New Year’s Eve and is kind of unclear what it’s talking about? 

Well, we can’t answer that question (we have no idea who the old acquaintance in question is…maybe we forgot them already?) but we didn’t forget to fix a small bug that occurred where if you had a By Date Goal and the target date had already passed, we weren’t letting you save changes to a category. We fixed it, because the past is the past…and speaking of: we hope your 2019 was amazing. 

Let’s make 2020 the year you reach all those lofty #moneygoals! For Auld Lang Syne, fellow YNABers, For Auld Lang Syne!!!!

Web Release Notes: December 17, 2019

A developer at YNAB brings you the following notes.

  • When managing payees, deleting.a payee will no longer reset the scroll position back to the top
  • Minor text fixes
  • A wild confirmation dialog appears when you use a quick budget action and don’t have any categories selected. Doing this performs the action for all categories, but the dialog asks you to confirm that you really, really meant to click that button.
  • We apologise for the lack of humour in these release notes. Those responsible have been sacked.

Web Release Notes: December 10, 2019

You: Locked in a noble battle to control holiday spending. You roll with the punches and you hit your year-end budgeting goals.

Us: Engaged in a never-ending quest to pursue ultimate app performance. In this quest, though, we introduced a few strange bugs around scheduled transactions in the register. But after our valiant efforts, you shouldn’t see any of those now. We also rolled with a different set of punches here. 

That same code change also fixed a bug where the cleared icon was not being shown when editing a transaction. Instead the scheduled (calendar) icon was being shown.

All of us: Let us vanquish our foes together…and THE TROGDOR COMES IN THE NiiiiiGHT!!!!

Web Release Notes: December 3, 2019

Ah. Can you feel it in the air? That crisp December air is setting in and we all know what that means…a YNAB bug-fix release! Just us? Fine. I’m not sure I even know what “crisp” air is supposed to smell/feel/taste like. It’s air. Not an apple. Are people trying to eat air? Don’t eat air. It’s just a thing we say. Anyway, here’s a few nice, little bug-fixes to our onboarding:

  • We fixed an issue where “Adding a Savings Account” onboarding was not triggering properly. You could say we “saved” the day here…but should you say that?
  • We made it so that when a new user tries to exit out of onboarding by pressing the ESC key, it no longer throws an error. It also doesn’t kick an error or do anything having to do with an error. Just wanted to make sure we’re clear that we didn’t do a half-measure here.

Web Release Notes: November 26, 2019

Here we are just days before Thanksgiving in the U.S. and only a few days away from the end of our last 6-week development cycle of 2019 here at YNAB. We have a lot to be thankful for and I don’t want to do any kind of year-end review right now (we’ve got several more releases coming out before the end of the year) but I want to just say that I’m thankful for bug-fixes and the care and detail that goes into coding and testing these fixes to get them out the door.

So, without any further ado (I don’t know if that last bit qualified as “ado,” but I’m going with it) here is the bug-fix that we released today:

  • When new users go through onboarding, we teach them about setting goals by having them set a goal for “Software Subscriptions.” However, if the user had deleted that “Software Subscriptions” category before they got to the onboarding step to set a goal, it was causing an error. So, we fixed that.
  • Also, Happy Thanksgiving to all the YNABers in the US!…not a release, but we’re thankful either way.

Web Release Notes: November 21, 2019

You know the feeling: you get a transaction imported into YNAB and you’re like, “who or what is Firfen-Dirfen and what did I buy from them last week that cost me $10.99???…is it Ted Van Firfen-Dirfen’s Lawnmower Emporium, LLC Unlimited?” This is when you need to do some sleuthin’.

Today’s release gives you a nice little Sherlock Holmes-style sleuthin’ tool. We’ve added a copy button to the transaction details to copy the payee “as it appears on your statement.” With this handy button, you can now easily (crosses fingers) search your bank statement online and find the transaction there exactly as it was sent over to YNAB. The game is afoot, my dear Watsons!

Web Release Notes: November 14, 2019

?‍♀️ ⚖️ …coming soon…

Web Release Notes: November 13, 2019

Today’s release contains a fix to issues stemming from Safari’s Dark Mode overriding our default styles. They were turning some of our input text white, when it was on a white background…or, in other words…CAMOUFLAGE! This might be a good thing for hunting, or if you’re a professional chameleon. For input text in a user interface, it’s not great. So, we dechameleonized it. In related news, we invented a new word.

Web Release Notes: November 12, 2019

Listen. We like big budgets and we cannot lie. When you’ve been budgeting with YNAB for awhile and you’re giving dollars jobs, your budget grows. This is a great thing for you and for us. But when budgets start getting really, really big, it can pose a little bit of a problem for programmers to wrangle. Don’t get me wrong. Programmers love wranglin’ and they especially love wranglin’ problems. And this is what our programmers have been up to: wranglin’ big budget problems…and specifically, making bigger budgets faster. In today’s release:

  • We changed how we recompute transaction rows when a user clicks to edit a transaction. We now only change the row that’s being edited currently, which should greatly reduce lag on larger budgets. Ya’ been wrangled, editing transaction lag!
  • Our Code Sheriff™ got into the code and optimized how we handle array sorting in some cases and the changes we made showed a 30% improvement in time-to-load (15.5 seconds to 11 seconds) in one of our benchmark tests. This is a notable increase in speed. Hey, array sorting, ya’ been wrangled!
  • We also fixed a little whoopsy from our last code deployment where logging out from the Accounts screen wasn’t working properly. It might have been our mistake, but either way: WRANGLED!!!!…and yee haw!

Web Release Notes: November 7, 2019

Hmmmm….smell that? Yep. Fall is in the air. We all know what Fall smells like: Turkey, leaves, football, a pumpkin spice latte that slowly turns into a peppermint latte…But Fall at YNAB smells like prepping for some solid improvements. We’re working on things like the running balance column in the transaction list, integrating a new direct import partner and an overall faster YNAB.

Today’s release contains quite a few infrastructural changes in preparation for these bigger releases. They aren’t things you’ll see in your budget today, but they’re just around the corner.

Web Release Notes: October 31, 2019

First of all, HAPPY HALLOWEEN! Boo!…and what not. You’re scared. You get the idea. Today’s release took a little bit of a coding trick to yield a nice, little usability treat. And I realize that Halloween is more of a trick OR treat paradigm, but we felt like, “hey. Why can’t we just change history and turn Halloween on its head by using a trick to yield a treat?” So that’s what we did:

*Please read this release update in the Vincent Price Thriller voice for full effect*

Today’s release is kind of a sweet timesaver (I am going to run this trick or treat thing into the ground). When users experienced a foul error when trying to enter in their password to connect to a bank, they would be asked to re-enter their password (even if the error had to do with reCaptcha). This can be hauntingly painful. So, we’ve now made it so that we will keep the password field populated with the attempted password (in most cases) so that you can re-attempt without having to fiendishly type the whole thing in again, because of a reCaptcha failure or missing digit. Ha Ha Ha Ha ha ha ha *diabolical laughter*…*trails off*

Web Release Notes: October 29, 2019

For most of our releases lately, we’ve been pushing a lot of internal/infrastructural changes. Part of it is because we’re working on bigger features that will be launched in the coming months. But another part of it has to do with the software equivalent of mowing the lawn or getting the oiled changed. Part of what makes YNAB run so smoothly is that we’re constantly updating, pruning, refactoring, brushing, flossing, hydrating, getting our yearly physical and just doing all of the things so that it continues running smoothly AND so we can add amazing new features to a clean codebase (some of those were analogies…or were they?). Anyway, here are a few changes you may notice from today’s release:

  • Made a small change to the menus to make the “Categorize” menu icon match our mobile apps and we also modernized the way we handle the layout (flexbox) to make vertical alignment less messy. No one likes wrangling alignment issues…just try doing page layout in a Word Doc.
  • In our Direct Import flow, we added an empty “No Connections” screen to help with better UX and navigation when using the browser “backwards” and “forwards” navigation. While we did this, we were able to simplify the code, which will help a great deal as we work with new importing partners to make Direct Import even better going forward.

Web Release Notes: October 24, 2019

In our ongoing battle to make bugs a thing of the past*, today’s release squashes two somewhat obscure, but important bugs:

  • We automatically clear transactions created on a Cash account (this makes sense, because there is no bank involved to clear) but when creating a transfer from a non-Cash account to a Cash account, we weren’t clearing that transaction. Not a dealbreaker, because you can always clear it manually, but we value your time, so we fixed this issue and streamlined that for you.
  • Deleting payees can be dicey business, especially when they are tied to transactions. But if a payee is only tied to deleted transactions, then there should be no issues in letting YNABers delete those payees. This wasn’t the case, as YNAB was preventing payees with deleted transactions from being deleted. We fixed this. One might say that we “deleted” the issue of not allowing deletions when deletions were involved. One also might delete that last sentence.

*IMPORTANT: No actual, real-life, non-software bugs were harmed during this release

Web Release Notes: October 16, 2019

You know how sometimes you get so used to saying something out of habit that when the circumstances change slightly, you still say the same thing and it gets a little awkward? Like maybe you’re used to ending calls with your partner or your parents by saying, “K. Love you, bye.” But then, maybe you’re on a call with the city utility company trying to downsize your trash can and you accidentally say, “K. Love you, bye” to the person at the utility company. That’s probably never happened. But it has.

Today’s release fixes something super similar to showing accidental love to a stranger on the other end of the line. Sometimes, when YNABers were trying to link their bank account, we were showing them an error that said that they had failed to login, when, in fact, we were really just trying to tell them that they needed to confirm their email address. We’ve fixed that. And now your need to confirm your email will be clearly communicated, instead of a more generic failure error. Hopefully this will be less awkward. K. Love you, bye.

Web Release Notes: October 15, 2019

This release is comin’ in hot…actually, most of our web releases come in hot. I think it has something to do with Thermodynamics and heat loss from friction in the circuitry. It’s Physics. Don’t ask me for the details, though. Anyway, here’s the new hotness (remember, this is heat in the form of actual physical heat inside the servers AND from the hotness of squashed bugs and smoother YNAB-ing):

  • When you Fresh Start a budget, we were not carrying over the last used payment payee for credit card accounts which means it was not auto-filling the next time you entered a payment. Sorry about that. Sometimes we get a little overzealous with the level of freshness we offer. That may have been too fresh.
  • If you had a credit card account payment that was part of a split transaction and you clicked to view it from the Credit Card Payments “Activity” popover, an error would occur. Fixed!…I don’t know why we’re yelling here, but stomping out bugs sometimes requires an extra level of catharsis in the form of an exclamation point.
  • When you select a payee for a new transaction we try hard to remember the last category used for that payee and will auto-fill it. But, transfer payees pointing to Tracking accounts did not remember the category. We were able to jog its memory, though, so hopefully it will never forget your last category again.

Web Release Notes: October 14, 2019

Today’s release is brought to you by a small bug we introduced in the last release. This particular bug could prevent some users with linked accounts in specific error states from troubleshooting them, causing a uh-oh screen. Oops! Fixed now.

Web Release Notes: October 10, 2019

Today’s release is all about repeated attempts.

  • Ever tried to remember you password (in vain) so many times you got locked out? Now we’ve improved the message that you see when your account has been blocked due to that forgetfulness. This one’s not worth trying.
  • Ever wanted to start over in your budget and gotten a really weird list of budget names with things like My Budget  (Archived 10-10-19)  jumble in your budget dashboard? Now we ask for a name on a Fresh Start to improve clarity. We do recommend you try this one.

Web Release Notes: October 3, 2019

Do you know what’s better than one-step verification? That’s right, two-step verification…it’s almost double the verification steps! Twice as much, some might say. And, as of today, everyone should now have the option to enable two-step verification in YNAB. If you’re not familiar with two-step verification, it’s an added layer of security for when you log in to YNAB. In the hierarchy of safe and secure logins, it goes:

  1. Password = password – WEAK…c’mon, now
  2. Long password with a mix of letters, numbers and characters – STRONG
  3. Two-step verification – SUPER DUPER STRONG

We go to great lengths to keep data safe on our end (you can read all about it here) so we hope you’ll also do your best to keep your data safe on your end. Now, with our newly added two-step verification option (and biometric authentication on iOS and Android) we’re giving you the tools you need to keep your data safe.

For more details on how to set up two-step verification, check out this post.

But, wait…there’s more! Operators are standing by (by that, I mean our awesome Support reps are ready for any questions). If you call now (you can’t call) all YNABers will also receive:

  • A fix to inline equations where, if you accidentally enter multiple decimal points, YNAB is now smart enough to know you only meant to put in one decimal point. “$3..11” will get converted to “$3.11.”
  • Removed circle icons from our onboarding buttons to keep things consistent. Peace out, my sweet, sweet circle icons. You will be missed, but you were also not really necessary *Sarah McLachlan’s “I Will Remember You” playing in the background*.

Web Release Notes: October 1, 2019

As some of you may have noticed, we’ve made some changes to the way Goals are handled in YNAB. We’ve been slowly rolling these changes out, and as of today, all of you should see the new changes to Goals in YNAB. So, what’s new? You can read about all of the exciting details here, but here’s a quick rundown if clicking links isn’t your thing (I think I’ve just made up a person in my head that avoids clicking links at all costs):

  • We’ve broken Goal types down into two types: Plan your spending AND Build your savings.
  • Plan your spending Goals are really the new feature here and you can plan to spend a certain amount each month OR you can plan to spend a certain amount by a specific future date. The focus here is spending. Before, you might have had a goal to save for a vacation in the coming year. You wanted to set aside $200 each month, so you would have $2,000 saved for the trip. But, unless you live life fast and loose (which, we’re not judging you) you’re not buying your plane tickets on the day of your trip. You would likely buy them several months prior. So, with Plan your spending Goals, you would maybe set a Goal to spend $800 on plane tickets by March 1st. This way, your Goal doesn’t go yellow when you spend the money (that you were always going to spend to begin with).
  • Build your savings Goals behave in the same way that Goals have behaved since they were dropped on the world in 2016. You can set aside a monthly amount, or you can set a target balance (by date or otherwise).

So…welcome to Goal-klahoma!!! Goal-ing Green, Goal-hio!!!! Jackson Goal, Wy-Goal-ming…these are terrible. But you know what’s not terrible? The new Goals in YNAB. And this is just the first step in some even more exciting changes that we’re making to Goals to help you reach your…goals.

Web Release Notes: September 26, 2019

API News

Budgeting isn’t forecasting, but YNAB does give you the ability to schedule transactions and it also gives you the ability to “look” (and technically budget) one month into the future. A few weeks ago we made a change to the budgets/:id/months/:month endpoint so that it only includes current and past months in the budget window. We will now also provide one month ahead in the budget window as well. This change will help out in the scenario where you want to look at the next budget month to see if anything is budgeted. Careful, though…easy on the forecasting. We don’t want the Rule One police to show up at your door.

Web Release Notes: September 17, 2019

Whether you’re curious about how credit cards are handled in YNAB or if you’re looking for the best way to do a Fresh Start, we want you to find the information you’re looking for when you need it. While you can always reach out to our top notch Support team for answers, you can also find the information through this fancy, little, blue question mark in the corner of the web app:

This is “Beacon”…think of it as a more useful, less-annoying version of Clippy. Remember how Clippy used to follow you around in late 90’s Microsoft Office products asking you if you know what a pivot table is? Well, Beacon won’t hassle you about errors in your formulas or send you down an apocalyptic nightmare rabbit hole trying to figure out how to format a table inside of a Word Doc. Instead, Beacon allows you to search our help docs, find our free workshops or contact one of our awesome Support reps. It can be super helpful:

Today’s release adds Beacon to the “My Account” pages. Beacon is now there to help whenever you need it inside of the YNAB web app. Go away, Clippy!

Web Release Notes: September 10, 2019

As they say in Texas, “we’re fixing to release some fixes today.” And sure, our CTO, Taylor, and quite a few of our devs and support reps are from the great state of Texas and they have literally never uttered the phrase “we’re fixing to release some fixes today,” but it just feels Texas-y…and we fixed a few Texas-sized bugs today:

  • For some types of investment accounts that get used like checking accounts, transactions were being skipped because they were coming in with a value of 0. The reason for this was that these particular accounts were pulling the amount in via the “quantity” field as opposed to the “value” and “price” field (which were coming in with zeros). We fixed this issue for these types of accounts and hope to never have any issues with any bank direct import transactions ever again…takes huge deep breath
  • We found and fixed a really, really old sync bug. Like, it’s a bug that shipped with the first version of the mobile app. The bug was a little obscure, but fatal…for the app (phew, but still). If you ran into the bug, the only way forward was to uninstall and then reinstall the app. This bug occurred when users updated more than one split transaction since their last sync AND if the split parent had a value entered in the Memo field. Obscure, but also not that obscure for some of you. Found it. Fixed it. On to Cincinnati.

API News

The to_budget_budgeted value on the /budget/:id/months endpoint could sometimes be inconsistent with what you see on the web and mobile apps, if you had budgeted money in future months. We’ve fixed this so now this endpoint should be consistent regardless of whether you’re viewing it from the web or mobile app.

Web Release Notes: September 3, 2019

We all make mistakes (not the best way to start off release notes, to be honest). We’ve all went to pull the clothes out of the washing machine, only to realize that we put our bright, red shirt in with the whites, totally destroying a load of clothes. But what if there were someone there to prompt us just before we were about to make a big mistake? That would be helpful, right?

Today’s release includes a mistake failsafe prompt anytime a user goes in to delete 15 or more transactions. If you totally meant to do that, click “Delete,” and we’ll get to that deletion process. But, if it was a mistake, you can back out (by clicking “Cancel”) before you lose all that transaction data.

API News

  • What’s in a name? A lot, especially if two different things have the same name. In this release, the special “To be Budgeted” category returned on /budgets/:id/categories endpoint has been renamed to “Inflows”. This is to differentiate it from to_be_budgeted on /budgets/:id/months endpoint. These two values are related but different. The “To be Budgeted” amount at the top of a budget month is reduced by cash overspending in a prior month and any future budgeting. But don’t worry, that “To be Budgeted” that we renamed as “Inflows” will smell as sweet.
  • Previously the /budgets/:id/months and /budgets/:id/months/:id endpoints would sometimes return months outside of the first_month and last_month (the “budget window,” as we call it) of the budget. Well, we fixed that and now the returned data is more of a budget window than a budget sliding glass door.

Web Release Notes: August 29, 2019

Today’s release was focused on fastness, rapidity, or the more popular synonym: SPEED.

If you’ve got a budget on the larger size (15,000 transactions or more) you should see a noticeable difference.

We realize that we’ve still got some more work to do to get these big budgets moving even faster…and we’re working on it. Look for even more speed enhancements in future releases!

Web Release Notes: August 27, 2019

Today’s release contains quite a bit (well over a dozen different merges) of behind-the-scenes structural pieces for bigger features and improvements we are working on, but there are two bug fixes that some of our users will notice:

  • We fixed a login issue that occurred for some of our users stating that there was a “server error,” when, in fact, there was no server error and now there will be no message stating that there was a server error, because there wasn’t one to begin with…it seems like I could have shortened this explanation…oh, I’m still going, am I? I’ll stop now. OK, now. Moving on…
  • Splitting transactions is so huge for really getting granular with your budget. Who among us hasn’t bought socks and bread in one single Target run? Just me? Normally, when you add a transaction and then split the transaction in the Category field, the cursor automatically focuses on the next field to fill out: the Memo field. When you go to edit a transaction and change it to a split, the cursor was not focusing on the Memo field. That doesn’t make a lot of sense. But we’ve now fixed that issue:

Web Release Notes: August 22, 2019

We were so excited to get this release out, we may or may not have actually released it yesterday…we may never actually know. But here’s what we do know…this release contains the following fixes and improvements:

  • Fixing a number of scrolling issues in the Income vs Expense Report – The consistency and feel of scrolling in the Income vs Expense Report has always felt a little off. With this release, we’ve made a few tweaks to make scrolling much sleeker and much more pleasing to the eye. *singing off-key* “You can scroll your own waaaaaAAAAAaaaayyyyy!!!!”:

  • Performance boost from changing how we handle currency formatting – We’re always looking for ways to make YNAB even faster. In this release, we made a small change to one of the functions we use for currency formatting that netted a decent performance gain throughout the app! Vrrooom vrooom…you know…speedy things.
  • New CSV import doodle – When most people think of importing CSV files, the first word that comes to mind is probably “fun,” right? No? Just us? OK, well, we decided to bring, at least, a little amount of fun to importing CSV’s with this fun, little, YNABy doodle:

API News

Our PATCH /budgets/:id/transactions endpoint partially modifies the collection of transactions. In REST design, patching is used to make partial updates to collections and resources. Some of our API users expected this endpoint to also allow patching individual transaction resources within the collection. Well, now you can. For example, to set a Red flag on 3 transactions you could send a request body to PATCH /budgets/:id/transactions containing:

transactions: [
  {"id": "9d3bc63a-9942-4809-9cd2-d23069ac2b58", "flag_color": "red"},
  {"id": "77f3a961-a406-4dcc-8209-e90734b185ef", "flag_color": "red"},
  {"id": "4c42fdc7-0369-4e20-b150-508cdc0f35fd", "flag_color": "red"}

Previously, you would have had to provide the entire transaction representations (amount, date, etc.) to make these updates.

Web Release Notes: August 20, 2019

Who’s ready for “Back to School?” Ready or not, It’s that time of year, so let us take you to school with some of the fixes and features that we just rolled out:

  • Transfer payee name update fix – Did you know that when you import transactions and change the payee name on one of them, all other unapproved transactions from the same imported payee name will be updated to match the new payee name? Magical, right? And it’s convenient too, because you probably want to update all those other transactions’s payees too! When updating the payee and changing it to a transfer payee, however, we were not creating the other side of the transfer, which caused transfer orphans. Not great. This is fixed now.
  • Costco CitiBank card initials removal – Really getting into the weeds with this one. When transactions were coming through to the accounts of YNABers who used their Costco CitiBank card, the cardmember’s initials were getting prepended to the payee. “Who is HW-Costco? Do I own Costco now?” Yeah. We think that looks weird too, so we put in a fix to remove those pesky prepended initials (I wish there was a “p” word for initials to complete the alliteration trifecta).
  • Wide screen budget table alignment fix – You know the feeling. You go in to reconcile and something is off. And it’s just off by a few cents. If it were off by twenty dollars, or a specific, larger amount, you could do some quick detective work and solve it. But when it’s just slightly off, it’s almost worse. The same is true for the layout of the Budget screen. What if the decimal places were off…just by a little…like so?
    Yikes! Well, this was the case for users with screens wider than 1600 pixels. But it’s not the case anymore. We reconciled the pixel differences and we’re feeling good about it now.
  • Activity modals (pop-ups) not using the same sorting method – Not sure how many of you noticed this in the past, but there were some slight inconsistencies to how some of our activity modals were sorting transactions. But we’ve now went back and made sure all activity modals are now sorting using the same order: date (descending), account name (ascending), payee name (ascending), amount (ascending), entity ID (ascending). Pay attention. This will be on the quiz later.

Web Release Notes: August 13, 2019

When looking at the code we just pushed today, it’s amazing to think that YNAB started out as an Excel spreadsheet with some fancy macros. Back then, bug fixes were probably things like, “Font testing was a bust. Reverted font-style from Comic Sans back to Arial.” But now that YNAB is loaded with features and available on Web, Android and iOS, we have to squash some super edge-casey bugs. Check out this fix that went out today:

When confirming a user’s email change, we will now automatically assign any existing, unredeemed YNAB gift subscriptions that were sent to this new email address. Complicated and confusing, no? Let’s walkthrough the scenario where this applies:

You buy your cousin, Kim, a YNAB gift subscription for her birthday and gift it to [email protected] Cool. But Kim already has a YNAB trial account under her other email: [email protected] Hmmm…well, she won’t get that gift subscription as it is tied to that other email. So, the gift subscription would just sit in gift limbo with that picnic basket you bought your newlywed friends 8 years ago. With today’s fix, when Kim goes into YNAB and changes her YNAB account email to [email protected], that gift subscription you bought her will now apply to her account and Kim will have her shiny, new YNAB subscription you gifted her.

Web Release Notes: August 8, 2019

At YNAB, we work in six week cycles, and our current cycle is about to come to an end. So this release is most likely the calm before the storm of some more major releases in the weeks to come.

We pushed out a handful of internal structural changes to support upcoming features, BUT we also pushed out a seemingly smaller fix that you might notice: YNAB will now treat “Check No.” and “Check #” the same for payees. Hopefully, you’ll have # more problems when transactions go back and forth between the two…wait…did I do that right?

API News

Our API supports Cross-Origin Resource Sharing (CORS) which means you can call the API from within a web browser directly. But, we had something misconfigured and we were not allowing PATCH requests. This has been fixed so you can now patchy patchy ’til your heart is content on the /v1/budgets/default/transactions endpoint to update transactions directly from a browser.

Web Release Notes: July 30, 2019

Summer is in full swing here at YNAB and it’s been a light week for releases! For those of you that subscribed to YNAB via Apple, we fixed a small visual issue with the trial expiration date showing incorrectly in your account sidebar. 

And that’s all she wrote, folks! We’ll see you later this week for more. ?

Web Release Notes: July 25, 2019

You’re not going to see any big changes with your eyes from today’s release, but we hope you feel it in your hearts as we just pushed a bunch of changes to keep Direct Import rockin’ in the free world.

API News

We now support Delta Requests on the /budgets/{budget_id}/scheduled_transactions endpoint.  This allows you to ask the API only for changed scheduled transactions (Deltas, if you’re nasty).

Web Release Notes: July 23, 2019

As you may have noticed, we release new code every Tuesday and Thursday. Today’s release includes a number of changes that you probably won’t see in the app, but these changes are part of the necessary maintenance and set up that we do to facilitate larger improvements to YNAB and all of its glory.

While you may not notice these changes, you may notice that during our weekly releases, we take the app into maintenance mode for around 1-2 minutes, making the app unavailable. And sure, it might only be 1-2 minutes, but think of all the money-moving, reconciling and debt-crushing that can be done in that amount of time! So, chRIS (emphasis his) one of our super rad developers, found a way to only go into maintenance mode when we absolutely need to. So, carry on, knowing that we might totally be updating YNAB right now without you even realizing it!

Web Release Notes: July 16, 2019

Today’s release includes quite a few behind-the-scenes structural changes for larger improvements we’re working on. As for changes that you will see after today’s updates, here are some of the highlights:

  • There is a famous saying in Norwegian (translated to English): “It all comes down to dollars and cents.” Except, I’m totally kidding. They don’t use dollars in Norway. It’s all about the Kroner. And it would be helpful for YNABers who use currencies with number formatting similar to the Kroner, if YNAB’s Net Worth report would show values without wrapping. So, we fixed that. We’ve added a little more width to our Net Worth Report tool tips to give a clearer picture for larger-numbered currencies (and multi-billionaires…just in case)
  • Fixed a bug in Safari that would occur when a user would hover over the “Share YNAB. Get Free YNAB” button multiple times, causing the button to turn black. It weirded us out too. But now, it’s fixed.
  • When scheduling transactions for Cash Accounts, there will never be an indicator from a bank that the transaction has cleared. So, to save you a little bit of time, YNAB will now automatically clear that scheduled transaction for you on the scheduled date (for Cash Accounts only).

Web Release Notes: July 11, 2019

  • Could you smell what the Rock was cooking? Probably not 🙁 Anyways…Updating all of the calculated values is now 2-5x faster when said calculations need to update Age of Money. This makes up about 20% of all requests. This behind-the-scenes improvement makes the web app a little snappier when adding or updating transactions. As an added bonus, it also gives our friendly database a bit more breathing room. Whew!
  • Ever go into YNAB to do a Fresh Start and get annoyed that all of the account balances are at zero? Well, we fixed that. Linked accounts now pull in account balances and the current day’s transactions. Budgeting bliss with less distractions. That’s right, Fresh Start is no longer a chore.
  • For all of our Safari 12 users out there, we fixed an issue where some of our modals (pop-ups) were not positioned correctly. What’s even more fun is that the issue was being caused by a check that we were doing for an old version of Internet Explorer. Browsers! Who knew?!
  • A little while ago we unified our login experience in the app, but, as some of you may have noticed: the option to “show” your password characters while typing was gone after that change. But, fear not! Carlos giveth and Carlos taketh away…and then Carlos addeth the “show password” feature back into the app! Also, Carlos is one of our amazing developers who made this fix possible. Obrigado, Carlos! ??

API News

  • As a developer using the YNAB API, I’m sure you’ve come across a scenario where you only want/need “read-only” access for your app. Well, now all of you API application authors have the option of using the new read-only scope for the YNAB API inside of your app.

Web Release Notes: July 9, 2019

It’s a light release today with a few verbiage changes here and there along with some code changes to the web app that you shouldn’t notice if we did everything right.

Web Release Notes: July 4, 2019

For all you YNABers in the US, Happy 4th of July! A light week around here, just a few quick updates and we’ll let you get back to barbecuing. ?

  • Age of Money could be missing or calculated incorrectly for some months if you have $0 split transactions that have sub transactions which are on budget transfers. It should fix itself the next time you add or update a transaction in the improperly calculated month. ✅
  • When exporting your budget, we used to escape double quotes ” using \” now we’re using double double quotes “”, which is more inline with these .csv standards (for those of you that might be curious).

Web Release Notes: July 2, 2019

  • Super exciting news for all you goal setters out there: Goals for Credit Card Payments (Payoff Balance by Date and Pay Specific Amount Each Month) now count balances carried over from the month before the goal is created as progress toward the goal! ?
  • We installed a few minor updates on the backend to stay on top of security patches.  ?
  • Last but not least, we added a mini power-up to search results—now when you search for payees with apostrophes, they’ll show up even if the encoding of the apostrophe is non-standard.

Web Release Notes: June 27, 2019

  • For those of you using Safari or Firefox, you may have noticed a few wonky spacing issues when scrolling in the account settings area. We tidied up the margins so you can now scroll with adequate spacing.

    PS – If you haven’t visited the settings area in a while, this could be your excuse to check it out! There’s lots of fun things to do—link your Google account, update your billing info, give the gift of YNAB, and so much more!
  • If you’ve been relying on Chrome to autofill your password, the login button would sometimes stay disabled after the email and password were autofilled, which wasn’t very helpful given that you probably set up that autofill to save yourself time! This is now fixed and you can get back to automating-all-the-things. ?

API News

We did a little bit of housekeeping on the YNAB API this week…

(actual footage from our API dev team over the last few days)
  • OAuth applications now support default budget selection so you can ask users for a default budget when authorizing and then pass in “default” in lieu of a budget_id in API endpoint calls, making things simpler in a few cases.
  • A few Delta Request improvements:
    • Delta request on /budgets/{budget_id}/accounts endpoint will now return accounts that have had balance changes
    • The /months/{month} endpoint now returns server_knowledge.
  • Marked transfer_transaction_id and matched_transaction_id as strings rather than uuid in our API spec.

Web Release Notes: June 25, 2019

  • On the Net Worth report, months far in the past could get hidden, so we added a vertical scrollbar to the report so that we aren’t hiding such valuable data anymore.
  • While using shift + arrows to select multiple transactions in the register, if you reached the bottom and hit the down arrow one more time, it used to error but now it doesn’t. We even fixed using the up arrow to unselect transactions too. We even made you a silent film to show you what we are talking about:
  • Besides the two afore-mentioned items, we merged another 10 “pull requests”/”units” of work, but they are all marked as “internal”, meaning that we don’t normally talk about them here. But the author of these release notes thinks that is selling them short, so I’m going to talk about a few of them anyway! The technical folks reading this might appreciate that we:
    • Made it easier for our support teams to map a financial institution from one aggregation provider to another.
    • Fixed grammar/punctuation on a message related to expired password tokens.
    • Disabled reCAPTCHA when running automated tests. (It was easier than trying to trick Google into thinking our automated tests were human.)
    • Removed tracing from the iOS proxy generator templates. (That sounds too cool not to include it.)
    • Upgraded to Typescript 3.5.1 and upgraded RSVP to version 4.8.5.
    • Migrated to Yarn Workspaces. (We are big fans of this approach after having only used it a few days.)
    • Fixed some issues with our Docker development environment.

Web Release Notes: June 20, 2019

  • In Firefox we were unintentionally sorting by category when you were trying to resize a category column, we fixed that.
  • We’re smarter about which default dates we recommend when your make a transaction recurring depending on the frequency.

Web Release Notes: June 18, 2019

  • When adding a transaction, if you changed your mind and clicked on some other transaction, we’d always force you to cancel adding the transaction first. Now, if you have made no changes, we’ll just dismiss without asking to cancel. Because we’re cool with changing our minds. (If you made any changes to the transaction though, we’ll still ask you to cancel, just in case.)
  • When adding a transaction, you could click the Needs Category notification icon on another transaction to begin unintentionally editing it. Oops, not anymore.
  • When searching for a sub-transaction of a split, the collapse split button will no longer appear giving you the impression you can collapse a partially shown split, because you really can’t do that.
  • Fixed a layout issue when adding accounts on large tablet screens.

Web Release Notes: June 13, 2019

  • Fixed an error that could prevent loading the app on IE11.
  • Updated some build dependencies, keeping up with the latest and greatest out there.
  • We are currently testing some under the hood changes to decrease database load and improve performance.

Web Release Notes: June 11, 2019

Lots of under the covers updates to support some upcoming new features.

API News

  • We updated our documentation to make it clear that the API doesn’t yet support creating or updating scheduled transactions.

Web Release Notes: June 6, 2019

  • We made small changes to make the overspent and underfunded category colors stand out a bit more, especially if you have a form of colorblindness.
  • But if those don’t stand out quite enough for you, we also added an option in Account Settings to switch back to the Classic colors. Now you can decide which style works best for you.

Web Release Notes: June 5, 2019

Fixed an issue with transactions for some accounts importing with payees like U S Dollar, Canadian Dollar, British Pound, and the like, in the past couple of days. You might still see some lingering imported payees like that the next time you import, but going forward they should show up correctly like they used to.

Web Release Notes: June 4, 2019

API News

  • Creating or updating splits through the API isn’t supported (yet) but you can update the parent transaction of an existing split. The only catch is you cannot change the date, amount, or category. We updated our API docs to make this a tad clearer.

Web Release Notes: May 30, 2019

  • Now as scheduled transactions become real life transactions, we will attempt to match them to any previously imported transaction. Even when using Enter Now from the Edit menu. Usually scheduled transactions will fire before their imported counterparts are imported but in some cases the imported one will beat it. This is especially true if you are using an API integration that offers near real-time importing of transactions.
  • The Underfunded Quick Budget option is now available when you’ve selected a single category that is either overspent, has a goal that hasn’t been funded yet or if you haven’t budgeted enough for an upcoming transaction.

Web Release Notes: May 28, 2019

Just one noteworthy fix. If you have ever seen a $0.00 balance with a red color pill you might have been confused. We’ve fixed this rare scenario, which was caused by some rounding issues. High fives the other JavaScript developers.

Beyond that, a lot of behind the curtain lever pulls and button pushes, preparing for some upcoming features. What kinds of buttons and levers? Well, there was 4,247 lines worth of overhauled CSS, for starters. These changes should make our future efforts easier and faster, but you won’t notice anything different just yet.

Web Release Notes: May 23, 2019

Sorry folks, more sight unseen improvements today. But, these type of changes keep YNAB running smoothly for your budgeting pleasure. Interesting fact: we removed more lines of code today than we added.

Web Release Notes: May 21, 2019

Today’s release is all sight unseen improvements. Among other (unseen) things we are releasing a change to our database that should significantly help move some database metrics in a positive direction. You likely won’t notice, but we will because it should make internal-chat messages like “Alert: 95th% Response Time High” or “Hey Taylor, are you seeing this strange behavior?” a thing of the past.

Web Release Notes: May 16, 2019

  • Fixed a login error with the latest version of Firefox.
  • These are other items to give the illusion of more going on in this release.
  • There are also maintenance and security fixes going out.
  • But we don’t usually talk about those, so mum’s the word.

Web Release Notes: May 14, 2019

  • We’ve improved the contrast on our category balance pills. With these changes, users with visual impairments will be able to use YNAB more easily. Accessibility FTW.  Read today’s blog post to learn more.

API News

  • We’ve increased the max length of the memo field from 100 to 200 when creating or updating transactions. We’ve updated the docs accordingly (be sure to click ‘Model’ under the ‘data’ section).

Web Release Notes: May 9, 2019

  • A little bit ago we regaled you with news of our unifying the login/signup flows. In our excitement we forgot to put the “keep me logged in” checkbox on the revamped login screen. If that doesn’t ring a bell, it used to be called “remember me”. Whatever you call it, it’s back where it belongs.
  • Fixed a crash when Apple subscribers try to resubscribe after their subscription has expired.

API News

  • Thanks to Andre Bocchini’s generous work we now have a Swift API client for iOS/macOS/WatchOS/tvOS. Fittingly, we’ve added it to our list of community-supported libraries.
  • The login/signup unification mentioned above accidentally broke the API OAuth Login process. This release fixes it.

Web Release Notes: May 7, 2019

Just a maintenance release today, and a small one at that. We just got back from our annual retreat yesterday (it was wonderful), so I suspect we’ll have more to talk about here later this or early next week. Hope you’re having a great week.

Web Release Notes: April 25, 2019

Only performance and security updates going out today. If it’s any consolation, I find that just as boring as you. But let’s not dwell in the past. [cue inspirational music] Let us, instead, look forward to the undiscovered wonders of next week’s release notes…

Web Release Notes: April 23, 2019

  • We’ve updated the login/signup flows, unifying the look and feel across platforms. Along with refreshing the design, we’ve improved security and prepared the code for more significant updates in the future.
  • If you tried to change a Monthly Funding goal to be Target Balance by Date, on rare occasions we would delete it instead of saving it. Fixed now.

Web Release Notes: April 18, 2019

  • If you have a javascript disabled in your browser, the app won’t work well, if at all. We’re usually pretty good at detecting when it’s disabled and showing a lovingly crafted message asking you to re-enable javascript so we can carry on. Except for some pages in the My Account area. Things would just break and look weird, with no lovingly crafted message telling you what’s going on. We’ve now extended the coverage of the twice aforementioned lovingly crafted message to include the My Account pages.
  • If you selected “Make Recurring” for the date of an existing transaction, we were so eager to create your scheduled transaction we forgot to save any changes you may have made to the transaction you just made recurring. Now we save your changes, then go about creating the scheduled transaction.
  • Improved CSS loading performance, which improves app loading performance, which improves perceived loading time. I mean, if we’re being honest.

Web Release Notes: April 16, 2019

  • We now disable the Undo/Redo buttons while you’re editing a transaction. Once you’re done editing, we reenable them.
  • When deleting a Category Group, sometimes you’d have to click Undo/Redo multiple times. Now a single click does the job.
  • Much like we reported in the critically acclaimed April 9 release notes, we found another case where the list of accounts was ordered differently in the Payee dropdown for individual transactions compared to the main list of accounts on the left. Now that one’s fixed, too.
  • Keeping with the theme… The Account list in Edit > Move to Account menu was sometimes ordered differently than the sidebar. Now they’re consistent.
  • When viewing transactions for a particular payee in the manage-payee popover, we sometimes we displayed internal, non-displayable transactions. We don’t do that any more.

API News

  • Updated docs to include validation requirements for creating/updating transactions.
  • Fixed a typo in an error message we hope you’ll never see.

Web Release Notes: April 11, 2019

A somewhat disappointing release today insofar as there is little to talk about. All internal stuff, nothing user-facing. 

In an effort to stretch it out just a little bit longer, here’s a rough breakdown of the kinds of things we shipped, along with their relative number of updates:

  • 3x internal tooling (primarily to support our beloved support folks)
  • 2x increase direct import efficiency
  • 1x shore up Apple subscription plumbing
  • 2x paying down technical debt
  • 2x performance improvements
  • 1x remove now-obsolete workarounds
  • 1x prep server for mobile bug fix
  • 1x prep for upcoming feature

Web Release Notes: April 9, 2019

  • We’ve added a “finishes” date to Target Category Balance by Date goal progress. Now you can easily see when your goal will be finished, which wasn’t quite as discoverable before.
  • In certain cases when importing large numbers of transactions, the logic could go off the rails, incorrectly matching or not matching other transactions. Fixed now.
  • In a recent change, we improved how your search is saved. This caused a new bug where the old bug would reappear if you cleared out your search, once again putting you in a situation where you could never really clear your search. We’re gonna call this one “fixed” again and hope it sticks.
  • In rare cases, the list of accounts was ordered differently in the Payee dropdown for individual transactions compared to the main list of accounts on the left. Now they are both ordered like the main list of accounts on the left.

Web Release Notes: April 5, 2019

  • If you had an account register search saved from before our April 2 release, we would reuse that search when you came back to the account register, even if you had cleared it. It might have even made you say to yourself, “wait…”. Well, fret not, it’s fixed now. Have a great weekend.

Web Release Notes: April 4, 2019

  • Scheduled split transactions comprising transfer sub-transactions needed some attention. The split side didn’t provide a link to the other side, and if you clicked on the link from the other side, it crashed. LOL. Fixed now.

Web Release Notes: April 2, 2019

What’s New

  • We now store your filter, search, and sort order settings for the “All Accounts” view on a per-budget basis. Modifying filter, search, and/or sort order settings for one budget’s “All Accounts” view won’t affect those settings in any of your other budgets.

API News

  • When responding to delta requests for /categories, we weren’t considering the server_knowledge of some of the entities related to a given category’s monthly budget. Essentially we weren’t considering changes to activity or balance amounts when deciding which categories had changed since a given last_knowledge_of_server. Now we do and you get a more accurate view of categories’ changed states.

Web Release Notes: March 28, 2019

  • For the armchair grammarians among us, we now refer to your age of money as being “1 day” instead of “1 days.” I’m not sure how it could, but if this issue resurfaces, there’s a tried and true workaround.

API News

  • Thanks to the generosity of Taryn Phrohdoh we now have an API client library written in Rust. You can check out all the client libraries—official and community-supported—in the API documentation.
  • The documentation for our response to GET /budgets requests was incomplete. Each budget summary object also includes first_month and last_month dates. Those dates represent the earliest and latest budget months, respectively. The docs now make that clear.
  • We no longer choke on unsupported Unicode escape sequences in the request payload. Now we return HTTP 400 and error detail.
  • Fixed an issue where some transaction payees were nullified when importing multiple transactions in a single API request. Moral of the story: always reset your loop variables.
  • The GET /transactions endpoint wasn’t returning split transactions that had been converted to non-splits. Now it does.

Web Release Notes: March 26, 2019

  • Creating a new category from the category field of a new or existing transaction by clicking “Add Category”, then “Save” did nothing and no new category was created. That was sub-optimal, so we fixed it. Now it creates the new category.
  • The Income v Expense Report now remembers your expanded and collapsed rows. This was our intention all along, but we wrote a bug that broke it when we converted some related code from CoffeeScript to TypeScript. To our credit, the bug was type safe.
  • If you navigated from one side of a transfer transaction to another, and that other side happened to be a collapsed split transaction, the app would hang. :sadtrombone: Now you’ll see the expanded split. :lightheartedpiccolo:

API News

  • The API Endpoints documentation has long given you the ability to quickly and easily query your data. (All you need is a simple personal access token for authentication.) We’ve tweaked the validation rules for UUIDs to prevent some false-positive validation failures. Most notably, we now support last-used for IDs, where appropriate.

Web Release Notes: March 21, 2019

  • Several behind the scenes changes today, including some preparation for an exciting new feature! Have a great end of the week.

Web Release Notes: March 19, 2019

  • When creating a category in the register, if you used the keyboard it would accidentally create the category twice. Now it only creates a single category as expected.
  • When changing a budget’s name, the browser’s title wasn’t updating. Fixed!
  • When transferring from one Budget Account to another, using tab to select a Transfer Payee was moving the cursor into the Category field. YNAB doesn’t even allow you to categorize transfers between Budget Accounts, so that wasn’t helpful. Now hitting tab will skip directly the Memo field instead.
  • Keyboard selection in the account register is back to normal, we had a bug where you couldn’t select rows across the regular transaction section and the scheduled transaction section.
  • You can now type “split” into the category dropdown to automatically select the ability to split the transaction. Or “s” or “Sp” or “sPL” or “SPLit” I think you get the point…

Web Release Notes: March 14, 2019

  • In rare cases, the columns on the account register that cannot be resized (checkbox, flag, cleared) could become smaller than they should be. Once they got out of whack, there was no way to resize them back to the size should be. They are now at the correct size no matter what you do.
  • When you first start YNAB, we will helpfully start pointing you to certain parts of the budget screen and instructing you how to budget and move money around. But as it turns out, if you collapsed Category Groups before these instructions appear, we had no idea where to point you and would end up pointing these instructions to places that didn’t make sense. It was an especially embarrassing mistake for us because if you were seeing these instructions, you were likely new to YNAB. I’m relieved to tell you that we have wiped the proverbial egg from our face and have fixed the issue.

Web Release Notes: March 12, 2019

  • Some of you might not know this, but YNAB is great at importing transaction files downloaded from your bank. This is really helpful when your bank doesn’t support directly connecting to it, or the connection is having trouble. Now that we’re all on the same page, you should know that we improved the way we import dates and times for files that end in .ofx or .qfx. Now we take the time into account and not just the date, which means that your transactions are more likely to fall on the correct date when they’re imported.
  • When linking to your bank account, we could sometimes show a really cryptic error message that started with “Missing translation” and got worse from there. No more!
  • Sometimes, when we hit a snag while importing transactions from your bank, we will keep trying in the background, and all you have to do is wait a bit for things to catch up. But when that would happen, we would previously make it look all “doom and gloom” and put an error icon in your sidebar. Now we will correctly tell you that the syncing is merely “delayed”.
  • When importing from your bank, there was a rare scenario that could cause the same transaction to get imported twice. It was confusing, so we fixed it.
  • When importing from your bank, there was a rare scenario that could cause the same transaction to get imported twice. It was confusing, so we fixed it.
  • If you’re looking at your budgets list, you can now still  create a new budget directly from the menu in the upper left corner even though there is already a “create new budget” button in the list of budgets.
  • We made some improvements to the way we tell you about your goals.
    • Added “Started” month/year
    • Added the goal type in the title so that you know what kind of goal it is.
    • We dropped the “s” from “GOALS” because that “s” was silly.
    • P.S. Indented bullet lists are difficult to format.

API News (for you developers out there):

  • You can now use insecure redirect URIs for localhost (e.g. http://localhost:3000) with your OAuth Applications using the Authorization Code Grant Flow. Previously we’d require that you redirect to https://localhost:3000 for local testing, which required a lot of annoying hoop jumping and certificate management. Hat tip to @kordonme for the request!

Web Release Notes: March 7, 2019 — 2nd edition

  • Quick update to fix some minor display issues with the last release.

Web Release Notes: March 7, 2019

  • Escaping from the transaction editor during reconciliation would flat out cancel reconciliation. Now it just closes the transaction editor, allowing reconciliation to continue apace.

Web Release Notes: March 5, 2019

  • Direct Import: We fixed an issue where some transactions from different linked accounts could incorrectly import into the account being added or linked.
  • Move Money now shows available amounts from the currently selected budget month, rather than the current calendar month.
  • The status of iTunes Subscriptions through Apple shows more accurate and detailed information under My Account. Not that it was wrong before, but it’s much richer now.
  • You can now import transactions across all your linked accounts in the web app using the notification under “All Accounts”. It will include the grand total number of transactions available to import, approve, or categorize, and clicking the notification will trigger the import of available transactions, if any, while also filtering the list to display only those transactions. You may now import with reckless abandon.
  • The Turkish Lira becomes a first-class citizen as we now use its symbol, ₺, instead of our inauspicious placeholder, TL.
  • Budget-category-group checkboxes better reflect the state of their constituent sub-categories. It’s now more obvious when you have all, some, or no sub-categories selected for a given category group, whether that group is expanded or collapsed.
  • If you had any categories selected in your budget, then expanded or collapsed their category group (or just clicked the empty space in a category group row), we mistakenly de-selected your categories. Fixed now.
  • We’re now taking a more gentle approach to notify you of new releases, this present release notwithstanding.  Going forward we’ll pop up a little message to give you the option to “refresh” your browser immediately to get the new bits, or hold off on the update so you can finish whatever task is at hand. Regardless of your choice there, we also have an easy link to these very release notes, which may be the single most important item in this entire list. You can tell because it comes at the end, when most people have already given up reading. (If you are reading this bullet point in its entirety, please read it a second time to make up for all the people that punched out early. Thx.)

API News

  • We now explicitly designate the format (int32 or int64) of integer types in our OpenAPI spec. This change to the spec has no practical implications for our Javascript SDK and Ruby SDK, neither of which needed updating subsequent to this change. However, if you’re generating your own client library and your language of choice distinguishes between integer types, it’s time to update.

Web Release Notes: February 28, 2019

Sorry, not much to report today. Just maintenance and security bits. Important, but dull. That’s it. I yield back the balance of my time to the Chair.

Web Release Notes: February 26, 2019

  • When we import transactions from your bank, the “payee” field undergoes a fair amount of processing. First, we have to clean it up from its raw form, then we apply your payee renaming rules. We show the fully processed payee (i.e. cleansed and renamed) in the register. If you mouse over that, the tooltip will show you the cleansed version. And if you really want to see the original payee as provided by your bank, you can follow the “bank import details” link at the bottom of the payees dropdown, and there, in all its unrefined glory, you’ll find your “Sale AMZN Mktp US*MI5DF8ZV1” payee.
  • We fixed the currency ISO code for the current Azerbaijan Manat (its 3rd incarnation, if you’re counting). We originally had it as AZM, but everyone knows it’s supposed to be AZN as of the beginning of 2006. Apologies to beloved Azerbaijani and Turkmen YNABers, and thanks for gently correcting us.

Web Release Notes: February 21, 2019

  • When looking at your scheduled transactions and using the ‘Enter Now’ feature, we’ll create the new transaction and shift focus to it. We used to create the transaction but maintain focus on the scheduled transaction that spawned it.
  • Mobile only: Fixed an awkwardly large scroll area at the bottom of the Add Account and connection management screens on mobile.
  • The connection status of linked accounts is now more obvious.
  • In rare situations, deleting a category would not work. You click ‘Delete’ and nothing happens. Now it will delete the category.
  • Jumping from the budget’s ‘Activity’ popup to a specific transaction in the register could cause a crash if the target transaction was a collapsed split. Now we simply expand the split.


Web Release Notes: February 19, 2019


Scheduled transactions are a great way to automate your budget. Just set and forget. Until months later when you forget that you set and transactions seem to appear mysteriously. So to improve visibility, you can now collapse your scheduled transactions:

Web Release Notes: February 14, 2019

Once again we find ourselves announcing a maintenance and security release. Not very flashy, as release notes go, but important nonetheless. Good luck with the end of the week. I hope it’s all down hill from here.

Web Release Notes: February 11, 2019

  • A lot of stuff going out today, but it’s behind-the-scenes maintenance and security stuff, so we don’t have much to talk about here. Have a great week. (We’re rooting for you!)

Web Release Notes: February 7, 2019

  • You can now collapse individual split transactions.
  • We unified the two sidebar menus. The one-menu-to-rule-them-all now lives at the top left corner.
  • Para sa aming mga kaibigan sa Pilipinas, ang aming kasanayan sa Alexa ngayon ay nagsasalita ng mga piso!
  • For our Filipino friends, our Alexa skill now speaks pesos!
  • When Fresh Starting with scheduled credit card payments, we would miscalculate “Budget for Upcoming” and not show an underfunded alert. Fixed now.
  • We figured out how to get reordering accounts in MS Edge working.

Web Release Notes: February 5, 2019

Only small internal changes today (e.g. CSS maintenance; humans.txt updates). Mostly setting the stage for future updates. Nothing else to report.

Web Release Notes: January 31, 2019

  • Chrome v72 (the latest as of this writing) choked on our pristine CSS (UI styling rules), preventing users from scrolling to the bottom of the register. Fixed now.

Web Release Notes: January 29, 2019

API News

• The endpoints to list accounts, categories, payees, and months all now support delta requests. If you’re looking for speed and efficiency, deltas are the way to go.

Web Release Notes: January 24, 2019

  • Fixed an issue where scheduled payments from one credit account to another were not correctly calculating the “Budget for Upcoming” Quick Budget amount nor properly updating the payment category Available balance warning. Again, fixed now.
  • Fixed an edge case scenario that could prevent credentials from being retrieved or submitted when troubleshooting existing Direct Import connections.

Web Release Notes: January 22, 2019

• IE11 browsers and earlier versions of Edge were choking on the Spending Totals report. As a result, we don’t display sum totals in those browsers. Recent versions of Edge handle the report well so we now show the sum totals in Edge, just like all the other browsers. Except IE11, which is still (and forever will be) broken.

API News
Delta Requests on the /budgets/{id}/transactions endpoint now include any tombstoned sub-transactions, if they were tombstoned since last_knowledge_of_server.