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

March 16th, 2021

Filing taxes is SO fun (said no one, ever). It might be a little less terrible starting today, though, because now you can export a selection of transactions from YNAB into a handy CSV file—the perfect thing to send to your preferred account or tax preparation professional! And even better, this export will include your scheduled transactions. Finally, for those of you that have a large number of payees, we have implemented an update that will speed up all facets of your payee management experience!

March 11th, 2021

We’re still joyously keyboard-deep in champagne popping GIFs (we have a few fans of bulk-flagging around here), but we had one more (small) bulk editing tweak up our sleeves. If you’ve ever clicked the “select all” box while you had a partial selection going, everything was deselected. You may’ve thought, “Wait, this doesn’t follow the recommended checkbox behavior…” And you’d be right! We’ve corrected the “select all” box so it actually selects all when clicked, even when you have a partial selection going. To deselect all, simply click again. 

March 9th, 2021

Prepare yourselves fellow YNABers; today’s release is hefty. Hefty new thing number one: rejoice, for you can now bulk edit flags. Hefty new thing number two: after importing new transactions into your register you’ll find a handy “Approve All” option in the edit menu. Selecting each individual transaction is no longer required! Finally, hefty new thing number three: Manage Payees is now equipped with a search bar. Finding your desired payee has never been easier.

March 4th, 2021

Today, in an effort to improve  legibility, we bid farewell to italicized text in YNAB (bon voyage!) -. In addition, we’re introducing a small enhancement whereby we’ll use the name of your bank account as a default nickname when adding an account. That being said, you’re still welcome to change it to your heart’s desire.

Also, over the past week we’ve been rolling out a small change to the inspector that moves the goals section up to the top. We hope this change will bring more visibility to goals as you go about your day to day budgeting!

March 2nd, 2021

Some internal house cleaning today. Additionally, we’re fixing a minor visual glitch with scroll bars having a dark colour when they shouldn’t, as well as making an onboarding tooltip more helpful.

February 25th, 2021

Tuesday’s release was a big one; today’s a bit less so (though no less mighty). We added support for Botswanan Pula, fixed the rendering of the Philippine Peso symbol (₱), and posted an in-app reminder that we no longer support Internet Explorer.

February 23rd, 2021

Have you been racking up hidden no-longer-needed categories, wishing there was an easy and safe way to delete them? We–ok, fine–I certainly have. The wait is over! Today’s update makes deleting a category with budgeting history a breeze, helping you quickly reassign all transactions and budgeted amounts to the category of your choice. Spread your re-organizational wings and simplify to your heart’s content. Also, rest assured, the option to hide a category isn’t going anywhere, we got you 😉. 

In other news, we fixed a bug where, in certain circumstances, our duplicate detection for file-based transaction imports would get confused and well, not detect duplicates. That was not good, and it won’t happen anymore.

February 18th, 2021

Today’s release is all about the backend, baby! While there isn’t anything shiny and new to see right now, you can always take a peek at  what’s coming up next.

February 16th, 2021

It’s a bug fixes and performance improvements type of Tuesday. The enter now option on scheduled transactions now works from either side of a transfer on mobile. Reconciling is faster if it’s been a while since your last reconciliation (so it’s a good day to get all caught up in your account registers). Finally, matching pending transfers with cleared counterparts is now certifiably bug-free.

February 11th, 2021

Some bug-fixing today—like the one where, if you had a lot of budgeting history (and you do!), scrolling in the Net Worth report could cause header and background colors to slip.

As for the rest of the release, like an oil change that you can’t actually see when you drive your car but can feel when you drive it, we’re cleaning up and optimizing, and hope your budgeting experience in 2021 has been cruising along.

February 9th, 2021

Today’s release  supports a small experiment we’re running that we hope improves the process of connecting a new YNABer’s first account with Direct Import. It also has a few technical improvements (hello TypeScript upgrade, if you’re into TypeScript upgrades) and bug-fixes.

February 5th, 2021

Small fix to have Direct Import transactions importing quicker, for some YNABers, after a recent change from our provider.

February 4th, 2021

Today’s release fixes a couple of tricky visual bugs with goals and updates the summary display for accounts without transactions.

February 2nd, 2021

Today we released a few visual improvements to the Add Account flow, in addition to more backend changes to support upcoming features. Can you believe it’s February already? Cheers to a new month of budgeting!

January 28th, 2021

Today’s release fixes some display issues you may have had if you’re using dark mode on Chrome 88. Or if, like me, you didn’t realize Chrome 88 was a thing, this will serve as your friendly reminder to update. Rest assured, dark mode should work just fine.

January 26th, 2021

We’ve made some in-app copy more friendly and clear. Call us idealists—we like to think the whole budgeting experience can be fun and easy, even those rare occasions when you  hit a maintenance page. Otherwise, the slew of January’s ‘behind-the-scenes’ changes continue!

January 21st, 2021

Today we’re cleaning up some old code, and introducing the foundations for features to come. And while you won’t feel or see any of them quite yet, they sound the promise of more exciting and delightful times ahead!

January 19th, 2021

Today, we’re updating the way we display a pending transfer between a linked and an unlinked account in your budget. Unlinked accounts generally do not show pending transactions, but they can appear when a pending transfer comes from a linked account. This change makes sure that you only see the clock icon on linked accounts, and that unlinked ones behave as they should do!

January 14th, 2021

In today’s release we fixed a bug that would occasionally result in duplicate transfer transactions (not fun).  We also cleaned up some out-of-date copy related to updating direct import connections and a misleading report filter option.

January 12th, 2021

Today, we’re making it easier for you to close a tracking account on the web. Previously, if the tracking account was carrying a balance and you tried to close it, we would require you to make a transfer of the balance. Now, we’ll automatically close the account and adjust the balance to 0 for you. Happy budgeting!

January 7th, 2021

We fixed an issue in the account settings when the dark theme is enabled and some small fixes to some behind the scenes stuff previously mentioned.

January 5th, 2021

Today’s release contains more behind the scenes changes. A bit of tidying up after the New Year!

December 29, 2020

Today’s release contains behind the scenes changes. A bit of tidying up before the New Year!

December 10, 2020

OAuth is here! We started migrating the first set of direct import connections late last month and look forward to many more financial institutions making the switch soon.

What’s OAuth, you ask? It’s an “open-standard authorization framework”—basically, a widely accepted method for giving one entity (in this case, YNAB via our direct import partners) access to a specific set of data from another entity (in this case, your transaction information from your financial institution).

What does this mean in YNAB? Let’s say you’re creating a connection to “YourBank” and YourBank supports OAuth. As a part of the process, you will enter credentials and authorize this connection directly with YourBank. We expect OAuth powered connections will be more stable and require fewer re-authorizations, which means more time for good ‘ole budgeting!

December 8, 2020

Here at YNAB, December isn’t quite its own month. It’s kind of an Almost-January. Sort of a Pre-January—because January is when new budgeters and old-hand budgeters alike tend to experience a renewed enthusiasm, and we want to be perfectly ready for you all. So you’ll see a fair share of “behind the scenes improvements” over the coming weeks.

One small bug fix today to go with the backgrounders: When (and if!) you ever had a transfer from a cash account, and you then reconciled that transfer in the cash account, then you reconciled the other side of that transfer, we were mistakenly setting the cash side (where you started) back to cleared instead of reconciled. That won’t happen anymore!

December 7, 2020

Another small release today—just a  few behind-the-scenes changes to help us more quickly identify certain direct import issues. We also cleaned up a confusing message that some users were seeing after being directed to authenticate their direct import connection at their financial institution.

December 3, 2020

Over the past few weeks, we’ve been rolling out some design and flow changes to the part of the app where you add and link direct import accounts. These changes will only affect some users, so you may not see anything new. Happy Thursday!

December 2, 2020

Small release including some changes that will help as we roll out Direct Import OAuth for more users.

November 30, 2020

Small release today, to help users that have not updated their mobile app to the latest version with issues that could appear configuring their direct import.

November 24, 2020

We’re hard at work on some big DI improvements, and this release continues the push toward getting them in your hands. You’ll be happy to know that when you do see these changes, any pending transfers that show up in your budget will be excellent at communicating with their pending-transfer-counterpart in the other account. What does that actually mean? Just that transfers should behave as expected, on both sides. 

We’re also reversing the change we made to category deletion on November 12th—you will be able to delete categories that have budgeting again. Before you get too excited, these types of category deletions can still lead to unexpected or surprising results. So why the change? We weren’t satisfied with our original solution and we’re going to keep working towards a better way to handle this pesky scenario. In the meantime, thank you to all the YNABers who shared feedback with us about this change—we’re grateful for your input! 

Speaking of gratitude (sentiment alert!), if you’re reading this release note it means you care about YNAB, at least a little. I know I speak for all of us at YNAB when I say we’re happy you’re part of our community. Wherever you are on your budgeting journey, whether you’re celebrating Thanksgiving in the US this week or not, thank you for being a YNABer!

November 19, 2020

Just some small quality of life changes today: we’ve improved the message that displays when you remove an OAuth bank connection and made a small tweak to the numbers shown in the inspector when you select multiple categories.

November 17, 2020

This release contains a fix to an annoying bug that would sometimes prevent you from selecting a payee (for example after creating a new category from within the transaction). Hopefully, you’ve never encountered it, but if you have: rest assured it’s gone for good.

November 12, 2020

In today’s release we’re introducing a change to category deletion. Previously, all categories were deletable under all circumstances, but deleting a category with budgeting history could cause unexpected or surprising results. We now prevent such category deletions. Categories can always be hidden, and for those who want to channel their inner Strong Bad, categories can still be deleted once all budgeted dollars and transactions have been moved elsewhere.

November 10, 2020

Previously, users of the YNAB API were unable to add splits to imported transactions. No longer! Split to your heart’s content. This release also includes a fix for a very uncommon issue involving converting a non-transfer transaction into a transfer transaction on two different devices at the same time (say that three times fast). Previously, this could cause your budget to be out of sync with itself, which was a bummer. Now, smooth sailing. Budgets ahoy!

November 5, 2020

More background changes in today’s release. Rest assured, YNAB is getting better and more secure for all YNABers.

November 3, 2020

Today’s release includes work on opposite ends of the spectrum: from deep in the codebase we’re making updates to support future features. At the same time, it’s never too late for a little design polish. If you’ve been dreaming of a small but pleasing update to the header buttons when adding accounts, today’s your day!

October 30, 2020

We love a good transfer from checking to savings after an unexpected windfall, or vice versa when it comes time to buy that sweet new slow cooker you’ve been saving up for. Today, we’re releasing a few small fixes to transfers in YNAB. In some rare cases, you may have noticed an “orphaned” transfer transaction in one account missing its corresponding buddy transaction in the other account. With this fix, you can confidently delete that orphaned transaction without concern, and the issue shouldn’t happen again. Rejoice!

October 28th, 2020

You’ve probably noticed a lot of releases last week and this week. It’s been a little noisy—but we’ve been focused on quite a few small “behind the scenes” updates to keep YNAB speedy and secure recently, and most of those have needed to go out the door one at a time. More to come on that front! We’re also continuing to set the stage, code-wise, for some exciting new features (check out Up Next for more)!

Release Notes: October 21st, 2020

Today’s release contains important code updates to support features to come! Stay tuned for an update to Up Next. We also fixed a visual glitch in reports and added some design polish to account creation in the mobile apps.

Release Notes: October 14th, 2020

If YNAB were a restaurant, most of today’s changes would be happening in the kitchen—you wouldn’t see them, but your food would definitely taste better. A few small design tweaks were seasoned into the Quick Budget part of the inspector, enhancements that will improve some bank connections are thawing in the fridge, we finished frosting some new transactional emails, and we fried up a change that’ll aid our support team if you ever have to send in mobile diagnostics (which we hope you don’t). (Disclaimer: on the scale of ‘things not to do while hungry’, writing release notes falls between grocery shopping and watching online cooking tutorials. Bon appétit!)

Web Release Notes: October 7th, 2020

In today’s release, we’ve fixed a split transaction issue that would appear in a (really) rare case. Imagine you were managing some payees. Now let’s say you’re working with a payee inside a split transaction, if you had a scheduled split transaction with that payee, and then you tried to view the associated transactions from the Manage Payee window (we told you it was rare!)… then the app would crash! Anyway, that’s fixed now, so rest assured that you won’t be falling down that rabbit hole.

On a brighter side, we’ve also made some small design tweaks to the inspector panel to improve the legibility of the app.

Web Release Notes: September 24th, 2020

A few months ago, we introduced section headers, which make it easy to show or hide your scheduled transactions. In the spirit of simplicity, we’ve removed the checkbox in the filter menu that accomplished the same task.

Web Release Notes: September 22nd, 2020

The inspector (the section on the right hand side of the web app) got a design refresh this week. The updated colors, spacing, and typography should all make it easier for you to see the details of your budget categories, in all of their detailed glory! 

Web Release Notes: September 17th, 2020

Ever seen $0.00 To be Budgeted at the top of your budget with a red background color (warning! bad! attention!)? Well, most everyone has not. But, some of you have, and the reason is because of rounding issues in budget calculations. This can happen when changing the currency format on a budget or if you have a Linked account with a bank that tracks transactions to a very, very tiny amount (442.345). We’ve made some improvements in this area that should fix these rough rounding issues.


Also, consider your split transactions officially freshened up, after today’s release. Specifically, we made a few visual improvements in the add and remove split buttons. Now if only we could do the splits

Web Release Notes: September 15th, 2020

You won’t see changes in the app directly after today’s release. We’re shipping code updates and setting the stage for new features to come. Pay no attention to that person behind the curtain!

Web Release Notes: September 10th, 2020

Good morning! Today we’re doubling down on those pesky transaction selections that would persist in unwanted cases. In the last release, we fixed the case where you would navigate away and back to your account. Today we’re addressing hidden checked transitions 🕵️‍♀️. In certain situations, you could have transactions that remained checked even if you couldn’t see them because of a filter or a search. We’ve fixed that to make sure you don’t accidentally bulk edit any transactions you didn’t intend to!

We’ve also upgraded Ember, the framework powering our front-end, to a newer – and greater-  version.

Web Release Notes: September 8th, 2020

In today’s release, we fixed a bug related to the selection of transactions in your accounts. Those of you with scrupulous attention to detail will have noticed that when switching from one account to another, you would have to manually deselect any previously selected transactions. This could become a problem because, in plain language, it was possible to have transactions selected that you didn’t know were selected, as they were filtered out of view. That could lead to all sorts of unexpected behavior! We now automatically clear your selection when you navigate away from (and back to) an account. Bug begone!

Web Release Notes: September 3rd, 2020

My little cheat sheet for today’s release says “no notable changes”. Yes, things like upgrading to TypeScript 4 are notable from a developer’s perspective (take note, developer-budgeters out there)—but it won’t be noticeable next time you pop open your budget. In other words, it’s all under the hood today, carry on.

Web Release Notes: September 1st, 2020

We never want to make too much of where this button is or that button is, but here goes, because it can actually be a real thing: We’ve continued to simplify the design of the account widget, what we oh-so-lovingly call the part of the app where you add accounts (really, we love it, but it hadn’t gotten as much attention as, say, the sidebar recently). Our goal is to make the account widget more helpful, readable, and easier to navigate. Today we’ve tried to do all three by moving the back and cancel buttons to the top, improving readability, navigability, and opening up the bottom real estate for the aforementioned helpfulness.

Now, a lot of other things happened since last week—from bug fixes related with To Be Budgeted in the first-time user experience and in subscription management, to some API formatting clean-up and more clean-up around the logic underlying Quick Budget. But for the details, let’s just say: “Bug fixes and background improvements.”

Web Release Notes: August 27th, 2020

Oh, hey there. We’re back to talk about some fixes that we just shipped out in YNAB today. Here’s what we have for you:

We made some design improvements to the linked/unlinked account selection screen so UI (User Interface) details are more consistent across the whole app. The icon style is more reflective of what you see in the app today. The purple information link in the “after” image is also more consistent with what you would see in other areas, so it stands out when you need a bit of assistance.

Before
After

Sometimes, in ever-so-pretty-rare scenarios, deleting a subcategory would not work (that’s a bummer). It would just stay there and not be removed after clicking “Delete”. Fixed!

Web Release Notes: August 25th, 2020

Oh, hello. Thanks for dropping by to check out some of the fixes that we just shipped out in YNAB today. Here’s what we have for you:

When showing errors for direct import issues, sometimes the bank/institution names were adding some weird characters in the name. For example, “Oliver’s Super Fancy Bank” was showing up as “Olivers Super Fancy Bank” and that’s probably not the best name for a bank…though it still is fancy, I guess. So, we fixed this issue, so that these weird characters won’t show up anymore.

In most browsers, you have the ability to expand text areas (i.e. the Account Notes section in YNAB) both horizontally and vertically. But, when you expand the text area horizontally in YNAB, it can “break” the layout as the text area can flow into other areas of the screen.

While we want you to be able to write all of the text in the world (if you want) we don’t want you to have to choose between writing a lot of text and breaking the layout. So, we have disallowed horizontal expansion of text areas, BUT we still allow vertical expansion, which will allow you to write EVERYTHING without breaking the layout.

Web Release Notes: August 20th, 2020

If Google is to be trusted, we’ve got just about one more month of Summer left. And then, here comes Autumn…more like ODD-umn, am I right? But let’s not focus on that just yet. Let’s celebrate another hot YNAB update during what remains of Summer:

  • We fixed an issue when managing payees, where if you deleted a payee, we’d scroll you back to the top of the list of payees, and you lost your place. Don’t worry, after today’s release, we’ll now stay put, so you can keep on managing payees.
  • During File Based Import (AKA the lesser known FBI acronym) we were combining transactions into one account (even in scenarios where they should be placed into multiple accounts) if your account identifiers had the same last 4 digits. Who knew bank accounts could have the same last 4 digits? What are the odds? Turns out…high enough to warrant a fix! So, we are now using the full account identifier, so you should not run into this problem anymore.
  • At certain browser heights, the help beacon in the bottom righthand corner of the app covered numbers in the Income vs. Expense Report. Hey, help beacon…not very helpful! We’ve added a bit of extra space to the bottom of that report to ensure that all of the numbers are unobscured and easy to read.

Web Release Notes: August 13th, 2020

If you’re like me, sometimes you’ll find yourself scrolling through your transactions in a few different accounts to see if you bought something on your credit card or if it was from your checking account. But when you go back and forth between accounts, you have to “re-scroll” to the place you were before. What a pain!…but wait…today, the 13th of August, marks the last time you’ll ever have to “re-scroll,” because YNAB will now remember your “scroll position” in the last account you were on. I guess you could say that we know how to “scroll” with the punches…oh boy.

Web Release Notes: August 11th, 2020

API News

Good morning! We’ve pushed out a handful of infrastructural changes throughout different areas of the app, but, for now, we’ll just mention that a new POST /budgets/{budget_id}/accounts endpoint has been added to the API which allows the creation of an unlinked account.

Web Release Notes: August 6th, 2020

Today we’re releasing some improvements to managing Accounts. Along with some design improvements when selecting and confirming a financial institution’s account to link a YNAB account to, we’ve also improved the messaging when connections get out of sync. This should improve clarity! Also, we used to auto-capitalize words when you entered an account name but we will no longer do this because it didn’t always work like it should and most folks would prefer to control their own capitalization.

Web Release Notes: August 4th, 2020

Today’s release has quite a few under the hood changes and a fix for something you may or may not have encountered before. Sometimes when clicking a Quick Budget button soon after clicking another one, nothing would happen. This should now be fixed.

Also, we have upgraded the YNAB database to a more powerful server. We are observing better performance in the metrics we track and hope you will notice a difference as well!

Web Release Notes: July 30th, 2020

Who doesn’t love a two-for-one? A BOGO (buy one, get one free)? Two-in-one conditioner/shampoo? Getting something extra is always a good thing…except for when it’s not. In today’s release we fixed an issue that would happen when hitting Enter on the “Add another split” button for Split Transactions that would cause two new rows to be created instead of one. Row plus, anyone? No thanks. Maybe we thought you loved splitting transactions so much that you just wanted to add even more? Either way, it’s fixed!

Web Release Notes: July 28th, 2020

Let’s get directly to the point of today’s release…which, directly speaking, has a lot to do with Direct Import (connecting YNAB to your bank to import transactions). We have made a ton of different improvements to our Direct Import flow over the past few months, but we were being a little indirect with our language…kind of like what I’m doing right here.

With today’s released, we’ve cleared up the wording dealing with “delayed” connections to better communicate what is happening during the connection process. We’ve also taken a more direct approach to not allow linked “Cash” accounts…because linking to “cash” is not really a thing that is possible…because no one (that we know of) has credentials that we could use to link to your sock drawer or under your mattress.

Web Release Notes: July 23rd, 2020

Lots of good stuff-a-brewin’ in today’s release…but with any kind of brew, sometimes the sum of the ingredients is what stands out more than any one spice or flavor. That being said, a lot of the “ingredients” we pushed out today are less like cilantro (loud and overbearing…and why?) and more like a bay leaf…like, you don’t even know it’s in there until you’re trying to enjoy some spaghetti and then, all-of-a-sudden, you’re biting into a dry leaf…but in this release’s case, this is a good thing, believe me.

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.

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

After:
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 https://api.youneedabudget.com/v1/budgets/:id/transactions/import 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:

“TO ERR IS HUMAN; TO REALLY FOUL THINGS UP REQUIRES A COMPUTER.”

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:

[GONK GONK]

  • 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" \
https://api.youneedabudget.com/v1/budgets/last-used/transactions \
-H "Content-Type: application/json" -X POST --data-binary @- << EOF
{ 
   "transaction":{ 
      "account_id":"00d17281-a898-4bac-a3e4-0cbcb947c6e7",
      "date":"2020-02-18",
      "amount":-200000,
      "memo":"This is a split",
      "subtransactions":[ 
         { 
            "amount":-100000,
            "payee_name":"Split payee",
            "category_id":"99e33804-e58f-4121-9930-ba013c8bb4c3",
            "memo":"Split 1"
         },
         { 
            "amount":-100000,
            "payee_id":"f7d7779a-0084-4023-91fd-7de2a80f9105",
            "category_id":"3b9dcabc-ca09-4c7f-a26e-cb823209194d",
            "memo":"Split 2"
         }
      ]
   }
}
EOF
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: