Release Notes

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

YNAB Is Always Improving
YNAB Is Always Improving

Web Release Notes: March 26, 2019

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

API News

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

Web Release Notes: March 21, 2019

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

Web Release Notes: March 19, 2019

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

Web Release Notes: March 14, 2019

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

Web Release Notes: March 12, 2019

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

API News (for you developers out there):

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

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

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

Web Release Notes: March 7, 2019

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

Web Release Notes: March 5, 2019

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

API News

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

Web Release Notes: February 28, 2019

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

Web Release Notes: February 26, 2019

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

Web Release Notes: February 21, 2019

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


Web Release Notes: February 19, 2019


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

Web Release Notes: February 14, 2019

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

Web Release Notes: February 11, 2019

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

Web Release Notes: February 7, 2019

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

Web Release Notes: February 5, 2019

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

Web Release Notes: January 31, 2019

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

Web Release Notes: January 29, 2019

API News

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

Web Release Notes: January 24, 2019

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

Web Release Notes: January 22, 2019

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

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

Web Release Notes: January 17, 2019

  • When deleting a transfer transaction with the other side being a split transaction, we failed to delete the other side’s sub-transactions. Fixed now.
  • When entering an invalid date in the register, we would continue to display the invalid value while behind the scenes we would use the last valid value. That was confusing so now we’re making it more transparent and reverting the invalid value as soon as you leave the field.

Web Release Notes: January 15, 2019

  • Page titles got some love. They’re more reflective of what’s happening on a given page (e.g. “Income v Expense Report | [Budget Name] | YNAB”). Bookmark them all, then brag to your friends.
  • We recently pushed up some changes to ‘Enter Now’ to prevent it from duplicating sub-transactions in rare situations. Unfortunately, those changes inadvertently broke Enter Now for people who had already used it for a scheduled date and later deleted the transaction. It’s now working as you would expect: If you delete a transaction created by a previous use of Enter Now, then use Enter Now again, we’ll create another transaction.
  • A while back we addressed some issues with Spending Reports, particularly how we handle net positive spending, where a category group has more inflows than outflows for a particular month. Unfortunately, we missed the mark a bit, causing some confusion. Now we plot net inflows (as negative values), and you can more clearly see how all the numbers add up.

API News

  • PATCH is now supported on the /budgets/:id/transactions collection to allow bulk updates. Also, import_id can be passed in lieu of id to update an existing transaction with that import_id.
  • Updated a few error responses for consistency.

Web Release Notes: January 10, 2019

API News

  • The API now supports matching when creating transactions. If you specify an import_id, we’ll attempt to match an existing user-entered (i.e. not imported) transaction, just like we do for Linked accounts. Woot.

Web Release Notes: January 8, 2019

  • If you used “Enter Now” for a scheduled split then changed back to the originally scheduled date, you could end up with duplicate splits in some situations. We fixed that.
  • If you tried linking the Alexa Skill from an iOS 11 device, you would end up on the My Account screen, mysteriously. That’s not right so we fixed it. It’s actually an upstream bug, but it’s relatively easy enough for us to work around in our code.
  • We used to allow imported transactions to be matched with balance adjustments and starting balance transactions. That’s wrong so we stopped doing it.
  • We fixed a bug where a scheduled transfer from a credit card account to a tracking account would not correctly show up as an upcoming transaction in the quick budget section of the budget inspector nor change the category to orange. All better now.
  • Fixed a rare issue with linking accounts and downloading transactions.

API News

  • We had some issues with how we were handling the month URL segment. It only worked when you passed in the first of the month (e.g. 2018-12-01) Otherwise, you’d get an error. Now you can pass in any valid day of the month (e.g. 2018-12-17) and we’ll handle it properly.
  • If you pass in an invalid value for the month URL segment, we’ll return a more helpful error:

HTTP 400 Bad Request
"error": {
"id": "400",
"name": "bad_request",
"detail": "invalid date"

Web Release Notes: January 3, 2019

  • Auto-categorizing to Credit Card Payment categories is no longer an option in Manage Payees. It didn’t work anyway, it just created uncategorized transactions. PSA: Categorize credit card spending to the category it was budgeted for (e.g. groceries) and we’ll automatically move money from the spending category (again, groceries) to the credit card payment category.
  • The payment recommendation text in the credit card account inspector was removed. It wasn’t very helpful. It is sorry, and will go to its room and think about what it’s done.
  • If you’re logged into YNAB and purchase a gift subscription with a different credit card than your current subscription, your upcoming renewal now shows this new card will be charged. It didn’t before, but our payment system uses the latest credit card info.

Web Release Notes: December 31, 2018


  • Big budgets (accounts with 5K+ transactions) are snappier when loading.
  • If you overspent on credit, the category tooltip could erroneously include underfunded goal amounts in its reporting of the overspent amount. It now reports only the overspent amount.

Web Release Notes: December 27, 2018

What’s New

  • On the Income vs Expense report, the “Question Mark Button” was crowding, and in some cases overlapping the table. We put a stop to that.

Web Release Notes: December 11, 2018

General Goodness

  • If you cancel your subscription after entering the dunning process, we cancel any outstanding invoices. If you don’t know what dunning is, you’re in good shape.
  • Fixed an edge-case Direct Import scenario where we’d throw an “uh-oh” error before you could re-enter account credentials when troubleshooting a connection.

API Goodness

  • GET /budgets/last-used/settings was erroneously returning HTTP 404. It now returns the settings for the 'last-used' budget, if so specified.

Web Release Notes: December 10, 2018

Not much to report

  • In some circumstances a Direct Import institution can become unavailable for a prolonged period of time. We improved connection handling for those cases so they properly reflect these unavailable statuses.

API News

  • If you attempted to create a new transaction in an account that doesn’t exist or belong to the designated budget we would return an HTTP 500 error. That made it difficult for the client to figure out how to recover. We now return HTTP 404 with appropriate error details: 'Account does not exist in this budget..

Web Release Notes: December 6, 2018

What’s new

  • Onboarding got more personalized. We now ask new folks a few questions after sign up, to help tailor support and materials to get them going.

Other stuff that’s cool but not as cool as personalized onboarding

  • We sometimes replaced well-formatted payee names with all uppercase payee names. WE ARE SORRY AND WILL NOT DO THAT AGAIN.
  • Fixed an error that could cause the screen to go blank when logging out, requiring a page reload.

Web Release Notes: December 4, 2018

Using a fork or your hands, gently split the Release Notes in half.

  • For a long time now we’ve “rolled the calculations” before the first of the month (or FOTM, affectionately) for your most frequently accessed budgets. This makes them load more quickly after the transition to the next month. We’ve now got things dialed in on the server side so we’re expanding the pre-calc behavior so it includes less frequently access budgets as well. Essentially, we pre-calc all budgets now so they’ll all load more quickly. (I suppose I could have just gone with that last sentence, but I wanted to provide context. Context makes it more interesting, right? At least it does so for writing release notes, if not reading, which ain’t nothin’.)
  • We’ve resolved a quarrelsome popover situation where two popovers could appear when editing a transaction then hovering over a Direct Import status. We all know there can be only one. DI status wins.

Web Release Note: November 29, 2018

API News

  • There was a bug in the PATCH budgets/:budget_id/months/:month/categories/:category_id endpoint. Regardless of the month designated, it would always update the current month. Fixed now.

Web Release Note: November 27, 2018

  • Fixed an edge case issue that could cause an uh-oh error when navigating and dismissing the account flow while one of the interstitial screens is loading data.

Web Release Notes: November 22, 2018

The Turkey Edition

  • We fixed a loading issue that was affecting some people when opening the app, preventing them from budgeting for the turkey. Happy Thanksgiving!

Web Release Notes: November 20, 2018

The Pre-postprandial Lethargy Edition

  • When searching or filtering transactions, clicking on the empty area underneath the checkbox next to the filter message would result in an error. That’s fixed.
  • When creating a new category from the register, the “Add Category” popup was visually separated from the nascent transaction. This was offensive to even the most liberal senses of order. Fixed now.

Web Release Notes: November 15, 2018

  • Firefox was displaying an errant “E” in empty checkboxes. Fixed.
  • Reset password flow got some design love. Now password resets are more flowy and (to bury the lede) work on mobile.

Web Release Notes: November 13, 2018

Answers to the “What Changed with YNAB” Quiz

  • We now support drag-and-drop file importing for Edge browsers. All the other browsers are happy to have Edge join the party, but if you’re going to come late, bring dessert.
  • We’ve made it more obvious how to create a new category when entering a transaction. Spoiler alert: you click the “Add Category” link that greets you when the popover opens. We used to wait until you started typing the category name before we showed the link. Now the link’s always visible.
  • When authorizing a Works with YNAB application, we now show the email address with which you are currently logged in. There’s a convenient logout link, too, if you need to switch accounts.
  • Direct Import: If there’s a known issue with your particular financial institution, we’ll display a modest “known connection issue” banner, with a link to “Show” more information. Problem was, you could click, click, clicky all day and you’d never see more information. That’s fixed now. Never seen this banner before? Cool.

Web Release Notes: November 8, 2018

Pretty quiet today.

  • Direct Import: Fixed an edge case where connection tips weren’t being displayed when troubleshooting existing connections and being asked to re-enter credentials.

Web Release Notes: November 6, 2018

Things That Are Now Slightly Different

  • Fixed an issue with extracting dates when importing OFX/QFX files that use (if not abuse) new lines.
  • Adding a new unlinked account now requires a current balance. We used to set it to zero if you left it empty, but that resulted in a bunch of mistakenly created zero-balance accounts. You still can create zero-balance accounts, you just have to be explicit about it.

Web Release Notes: October 30, 2018

Spooky News

We sent 3,744 lines of code haunting the web app to the graveyard. Paying off technical debt is almost as satisfying as paying off financial debt.

Not So Spooky API News

Learn about the YNAB API

  • Using the nifty new PATCH /budgets/{budget_id}/months/{month}/categories/{category_id} was not properly updating some behind-the-scenes data which caused some very strange things to happen with budgeted and available amounts on mobile apps. The issue didn’t always happen but when it did it was creepy.

Web Release Notes: October 25, 2018


You can now drag the lines between column headers in the register to resize the columns.

Resize Columns

Bug Fixes

  • When adding a secondary Google login we were sometimes showing that last login as the Primary one. Fixed!
  • When making a split transaction recurring, we were incorrectly focusing on the memo field instead of the date field. Fixed!
  • When editing a transaction that needs approval if you pressed Enter/Return when focused on the Approve button we were not exiting edit mode. Fixed!
  • The available column tooltip was showing encoded characters for currencies that use an apostrophe as group separator. Fixed!

API News

Learn about the YNAB API

  • Restricted Mode will now be restricted to 25 unique users, rather than 25 access tokens issued.

Web Release Notes: October 18, 2018

Improvements & Bug Fixes

  • Back in September we started opening the approval popover after the notification banner was clicked. We’ve received very constructive feedback since then and learned that flow is not ideal. We’re going back to the drawing board to create a more pleasant solution!

Web Release Notes: October 15, 2018

What We Have to Show for Our Work

  • Fixed a bug with the sorting of transfer account payees on tracking accounts.
  • We improved the performance of the YNAB 4 migration process on several fronts. Should be snappier now. (Tell me you didn’t just have the thought, “Oh, YNAB 4’s still a thing?”)
  • The edit transactions dropdown at the top of the register lists a bunch of actions you can perform on your selection. Some of those actions aren’t appropriate in some contexts, so we simply gray them out to visually *indicate* their inappropriateness for the given context and pray to all that is good that you don’t actually click on one of them. Well, after quiet reflection and careful consideration we’ve decided it makes more sense if we actually disable the buttons too. So we did. :half_heartedly_blown_birthday_horn_emoji:
  • When only some transactions are selected in the accounts page, we’re turning the check all checkbox to an uncheck all button. Handy!

API News

Learn about the YNAB API

  • The GET /budget/{budget_id}/.../transactions endpoints now support Delta Requests.
  • As a convenience, we allow you to pass in 'last-used' in lieu of an actual budget id. It’s supposed to return the budget you last used, obv. As an inconvenience, we sometimes returned deleted budgets. That’s fixed now and 'last-used' no longer considers deleted budgets.

Web Release Notes: October 4, 2018

Slow News Day

  • IE/Edge only: Fixed an issue where Payee type-ahead search for transfer accounts could throw an error.

API News

  • We’ve soft-deprecated POST /budgets/{budget_id}/transactions/bulk. It still works and we still support it, but POST /budgets/{budget_id}/transactions with a transactions array is likely the more future-proof way of creating multiple transactions.

Web Release Notes: October 2, 2018

It’s all about the API today.

  • When creating a transfer transaction, or converting an existing transaction to a transfer, we were setting the transfer transaction’s cleared attribute to match that of the source transaction. We now set the transfer transaction’s cleared attribute to 'uncleared ' to match the behavior of the mobile and web clients.
  • /budgets/:id/categories/:id/transactions, /budgets/:id/payees/:id/transactions, and /budgets/:id/accounts/:id/transactions return transactions and subtransactions that have the specified category or payee. We were erroneously including some subtransactions belonging to deleted transactions. We’ve stopped doing that.

Web Release Notes: September 27, 2018

Nothing much to talk about in this release. At least nothing specific. Sorry. OK, maybe we’ll just list a few to give the illusion of substance to this release. And fair warning, if you’ve read this far you’re in on the ruse, thus ceding the moral high ground along with the rest of us. Let’s agree not to judge each other. Anyway, here are the things going out in this release that don’t warrant mentioning:

  • More gracefully handle the scenario where the user has no budgets. You have to work to get yourself into this situation though, because we create a default budget for you when you first sign up. Not a widely encountered issue, but fixed nonetheless.
  • Round some rough edges of the account widget build script.
  • Feature-flagged features we’ll announce later, once they’re more widely released and proven effective.
  • Remove a feature flag that’s been ramped to 100%.
  • Add some preparatory Direct Import plumbing that currently does nothing but will eventually.
  • And that’s it! It looks like a big deal when you throw a lot of words at it.

Web Release Notes: September 25, 2018

Improvements & Bug Fixes

  • It’s now easier to approve or reject imported transactions. When you click the “View” button next to the the transactions-need-approval message, we now not only filter for those transactions needing approval, we walk you through each, asking if you want to approve or reject. It’s quick and reduces friction. We’ll call it a win.
  • The “% of Total” values were missing from the Spending report tooltips. Fixed.
  • We now hide the payee dropdown until you add your first payee. Not much use in showing you an empty list.
  • Fixed an issue where the month name wasn’t showing up in some of the copy in the budget header.
  • Transfer payees now respect the sort order you’ve defined.
  • Searching for “payments” or “transfers” will match the transfer payee list.

API News

  • Budgeting is now supported with the newPATCH support added to the
    /budgets/{budget_id}/months/{month}/categories/{category_id} endpoint.
    Zum Beispiel:

     curl -i -X PATCH \ \
       -H "Authorization: Bearer c1326058-972a-FAKE-64cfa9975f26" \
       -H "accept: application/json" \
       -H "Content-Type: application/json" \
       -d "{ \"month_category\": { \"budgeted\": 394595 } }"

  • The create and update transaction endpoints now support transfers by specifying a payee_id of a transfer payee (i.e. a payee with a non-null transfer_account_id).
  • For convenience, we’ve also added a new field on the Account model called transfer_payee_id, which is the payee_id to use when transferring to that account.
  • You can now create multiple transactions on the POST /budgets/{budget_id}/transactions endpoint by passing a transactions array in the payload. You can still create a single transaction with this endpoint by passing a transaction object.

Web Release Notes: September 20, 2018

[no release notes]

This one’s pretty much a maintenance release. A bit dull if we’re being honest. But today’s my IRL cake day, so I’ll take license and tell a story. [Fair warning, we’re about to go “inside baseball” so feel free to stop reading now. You won’t miss anything of import. —Ed.]

Updates to the app are made using “pull requests”, as in the author of the update is requesting these changes be pulled into main codebase (from which all the apps are built). Each pull request (commonly known as a PR) has a title, and if the author deems the update unworthy of inclusion in the release notes, s/he will append “[no release notes]” to the title. It’s one of my favorite phrases.

I love seeing [no release notes] on a PR because it means I don’t have to write anything, I can just move on, less work. Don’t get me wrong, I love writing release notes, but it’s not a task to which I ever look forward. Once I get rolling I’m fine, but I’m always resistant to start. And each PR that includes [no release notes] means I can further delay the start.

And I must admit my excitement builds as I work through each PR and each seem to include that magic phrase of reprieve: [no release notes]. But it’s a delicate balance. Ideally each release has two items I can include in the release notes, then there’s something to write, but not much. If only one item makes the cut, the release notes look anemic. If none makes it, then I’m faced with a dilemma. I could just phone it in with something along the uninspiring lines of “bug fixes and performance improvements”. Or, I could pull myself up by my professional pride and burn waaayyy to much time trying to think of something clever to write, write three drafts of it, quickly grow to dislike each, and ultimately settle for something akin to what I originally had in mind but couldn’t quite execute well enough to be grateful for not having to write release notes today.

Web Release Notes: September 18, 2018

Improvements & Bug Fixes

  • When adding a transaction to a cash account, we now default the transaction to be cleared. One less click for those of us who use cash and one more click for those with an intricate multi-wallet cash clearing system.
  • Previously in manage payees, you could auto-categorize a payee to be Inflow: To be Budgeted. We (royally) broke that in a recent update but now we (royally) have fixed that with a proper regression test.
  • If you had a transaction categorized, then hid that category, editing that transaction would recommend creating that hidden category. Now it doesn’t.
  • We now prevent an edge case scenario that triggered multiple syncs of your Direct Import connections concurrently, when (in a movie voice) there should be only one.
  • We also now prevent autofocusing on the account type when adding an unlinked account on mobile, which is a bit forced behavior on mobile since it triggers the dropdown for selection right away.

Web Release Notes: September 13, 2018

Improvements & Bug Fixes

  • If we can’t determine the date format of your file-based import file, we ask you. But we weren’t remembering your answer so you had to remind us every time you (file-based) imported. That’s fixed now.
  • We show your authorized OAuth applications on your “My Account” page. In some cases we were showing duplicates. They’ve now been removed.
  • Previously, if you typed 1*1) into the inline calculator, the browser would look incessantly for the non-existent opening parenthesis, eventually crashing from the effort. We now simply ignore the unmatched parenthesis and carry on.
  • When recording a split transaction and clicking the “Add another split” button, we now focus on the newly added split’s payee field.

Web Release Notes: September 11, 2018

Our Attempts to Delight You

  • Some time ago we added steps to help you create a goal to pay off your balance when you add a linked credit card account with a negative balance. If you happened to step backward in that process (say, to fix a typo in the account name) we’d lose the account name and you’d see a blank field instead. That’s fixed now.
  • The confirmation banners we show at the top of the screen (e.g. after confirming your email or resetting your password) now appear in front of the onboarding steps (if they’re visible, of course). They used to appear behind the onboarding steps, which is to say they didn’t appear at all. You just had to intuit the message we were conveying.
  • If you didn’t select a category in the “scheduled transaction” step of onboarding, we’d show a warning asking you to remedy the situation. But after you dutifully selected a category we failed to remove the warning. Fair is fair, and you’ve held up your end of the bargain, so we now happily remove the warning.

API News

  • Previously, we JSON-encoded validation errors before returning them in a 40X error response to the client. That didn’t work well. We now return a comma-delimited list of errors as a simple string.
  • We’ve updated our API spec to remove the “nullable” types (was: "type": ["string", "null”] ; now: "type": "string"), which are not officially supported in the Swagger 2.0 specification. We were using these mainly for some develop-time tooling support, but it caused trouble for folks using our spec in their own tooling. The API still returns null values where applicable; this just changes our spec.

Web Release Notes: September 5, 2018

This release is solely focused on sprucing up the architecture underlying trials and subscriptions. It’s been a year in the making. We’re excited, to say the least. These changes will improve performance, in general, and position us well to build out functionality in the future.

Web Release Notes: September 4, 2018

Improvements & Bug Fixes

  • Some OFX files contain odd line breaks and other unexpected formatting in the memo field. We now parse those better so File-based Importing can read those files.
  • Fixed the warning displayed when creating an account with a negative balance for an account type that normally has a positive balance.
  • The “Add another split” button was really a common web link LARPing as a button. You still had to click on the text itself to add the next split line item. Fixed now.

Web Release Notes: August 30, 2018

Improvements & Bug Fixes

  • We now display a proper minus sign (Unicode U+02212 for the pedants among us) for negative amounts. It’s longer than a hyphen, easier to see, and technically correct (again, for the pedants among us).
  • Moving a reconciled transaction to a different account can bring the reconciliation out of balance. We now show a warning before saving such changes.

API News

(Learn more about our API.)

  • Previously we re-issued existing access tokens for subsequent application/user requests. This was problematic for apps with multiple clients because once a refresh token was used by one client, all the others would no longer be able to get a new access token from the refresh token because it was now expired. This issue is fixed now, as we issue a new access token for each request.
  • If any of the current month values for a category (budgeted, activity, balance, etc.) have changed, a delta request will now include that category in the top-level categories array, provided the last_knowledge_of_server dictates the client should know of the change. Previously, only changes to the category itself would trigger its inclusion.

Web Release Notes: August 23, 2018

Improvements & Bug Fixes

  • The available balance shown in the inspector for an underfunded goal had a yellow pill with a green pill inside of it! No more!
  • In other inspector news: upcoming scheduled transactions from closed or deleted accounts are not going to show up there anymore.
  • With our continued quest to improve the register performance, we made it faster to scroll through transactions using the browser scrollbar.
  • Deleting a category just got a little bit easier: now you don’t have to click an extra confirmation modal. Not that we want you to delete all your budget categories, but simplifying things a bit always feels good.
  • Fixed a bug where clicking a credit card payment category could cause a crash if your last payment was part of a split transaction.
  • When filtering out some categories in the Spending reports, the breadcrumbs weren’t updating correctly and kept showing “All Categories”. Fixed!

API News

  • When creating or updating a transaction, we used to allow dates to be date-“ish” and attempted to parse them. However, some formats were passing this validation but resulted in a 500 server error when saving the transaction. Now, we’ll require transaction dates to be ISO formatted (2018-08-23) to keep things simple and consistent.

Web Release Notes: August 21, 2018

What’s New

If you use File-based import, your bank might be sending transactions with dates formatted in such a way that causes them to appear off by one day when imported into YNAB. We’ve added a new option called “Adjust to local time” to address this when importing a file, which converts the transaction dates to your local timezone. You’ll be able to see a preview of the effect on the transactions prior to importing when selecting this option, so you can see if it will help fix this “off-by-a-day” annoyance.

Improvements & Bug Fixes

  • When making a split transaction recurring, we weren’t honoring the order of the sub transactions. It turns out, sub transactions in random order don’t look so nice in the register, so we now preserve the original order.
  • We fixed the little dot indicator for the currently selected month on the Budget screen, it was floating around but is now back to doing the work it’s meant to.
  • Fixed some styling for the Activity and Available amounts of the Hidden Categories. Now they look like all the other categories.
  • Another small tweak to our login page that should help password managers fill & submit the form.

Web Release Notes: August 16, 2018

Improvements & Bug Fixes

  • Keyboard shortcuts FTW. You can now navigate the “move money” and “cover overspending” popovers using the <enter> key. Pressing <enter> will move to the next field, or save when all fields are valid.
  • We now show pretty institution logos on the list of popular institutions when adding a linked account.
  • Marginally improved category deletion performance and made it easier to select a category you want to re-categorize.
  • When deleting a payee and choosing a new payee to change the old transactions, you now have the joy of a plain old select dropdown, rather than the functionally decayed dropdown we had before. Same for choosing an account and date format during file based imports. (I wish I could take credit for the deliciously evocative “functionally decayed” phrasing, but that’s all Chris. Ed.)
  • We fixed an issue with the date filters in the register where switching between a custom date range and a suggested one was not working correctly.

Web Release Notes: August 14, 2018


You can now use your Google account to sign up and log in to YNAB. This can be in addition to or instead of your email/password combo; both login methods will continue to work. Impress your friends by switching between the two with an air of nonchalance.

Improvements & Bug Fixes

  • Register scrolling performance got a huge boost. And that’s an understatement.
  • General performance improvement across the app (thanks to an upgrade to Ember v2.9).
  • We tweaked the login and signup forms to play nicer with password managers.
  • Imagine you’ve activated a filter on the accounts page (e.g. to show only transactions from “This Year”). If you then searched your transactions, we’d actually clear the filter so it wouldn’t interfere with the search results. Then if you cleared the search, we’d restore the previously active filter. And we did, for the most part. Except if you cleared the search term using the <delete> key we wouldn’t restore your filter. Or if you used multiple search terms and tried to clear the search by clicking on the little X icon. So when I wrote “we’d restore the previously active filter,” maybe I was speaking more aspirationally. Regardless, however you choose to clear the search, we’ll restore any previously active filters.
  • On some budgets, filtering by a date range other than “All Dates” wasn’t returning the proper results. Fixed.
  • Closed tracking accounts will no longer appear in the spending report.
  • Clicking on different Credit Card Payments categories was not updating the “last payment” section in the inspector. That’s fixed.
  • We recently made a change to focus on the outflow field when pressing <enter> on the memo field instead of saving the transaction. We’ve now reverted that change so pressing <enter> saves the transaction. Also, pressing <enter> on a selected transaction will activate edit mode, which sounds cooler than it probably is.
  • Our messaging was slightly off after you confirmed an email address change. The change went through OK, but the copy we displayed didn’t exactly jibe. That’s fixed now.

API Goodness

  • You can now pass in the pseudo-budget-id 'last-used' instead of an actual budget id, to specify the last-used budget. So instead of using something like, you could simply use It’s especially convenient if you only ever work with one budget.
  • If you specified a payee_id or category_id as an empty string (i.e. ""), we would return a 500 error. Not particularly helpful. Now, we’ll return a 400 error with a message indicating that “a valid UUID must be specified”. Use null if you don’t want to stipulate a payee_id or category_id. For example, for an uncategorized transaction you should specify "category_id": null.
  • OAuth refresh tokens can only be used once. If you obtain a new access token using a refresh token, you will be given a new refresh token that should then be used for the next refresh. We’ve clarified this in the docs.

Web Release Notes: August 9, 2018

A few release note poems for your enjoyment,
to go along with today’s deployment:

Improvements & Bug Fixes

  • When reordering your budget categories in Safari,
    dragging it out of view didn’t scroll, sorry.
    Now as you drag your category to the bottom or top,
    your categories will scroll so you can choose where to drop.
  • In Safari the keyboard shortcut Cmd + Shift + N,
    opens a new private window so your internet adventure can begin.
    We used to take over that shortcut to add a new transaction,
    now instead Ctrl + Shift + N or more simply Ctrl + N will handle that action.
  • Clicking the status icon of a linked account,
    no longer causes the information popover to dismount.
    Also while that popover is shown,
    pressing escape will make it leave you alone.

Web Release Notes: August 7, 2018

Improvements & Bug Fixes

  • If viewing a category in a month before a goal was created, we used to show a goal progress indicator that was blank. And no progress could be made because you were in a month before the goal was created. Now, we’ll display the category as if a goal hadn’t been created (because it hasn’t, at least not in the prior month).
  • Also, our new shiny available amount goal progress indicators were incorrectly showing on categories in months before any goal was created. Now they will not show in previous months. Kind of like finally fixing that mystery light in your car’s dashboard.
  • Fixed an issue where the categories dropdown would highlight multiple categories, no big deal.
  • If you imported a transaction, split it and then later matched it to a manually entered transaction (phew!), the splits from that imported transaction would forget to take that left turn at Albuquerque and show up in the activity for a category. We gave it better directions and a few carrots for the road.
  • Shifting gears to the register, holding down shift and pressing up/down let’s you select mutliple transactions. This used to work but we broke it but now it’s back. By the way, how do you say “mea culpa” if it’s more than one person’s fault? Wea culpa?
  • While the register hood was open, when selecting a transaction other than the first transaction, then holding down shift and selecting a transaction further down on the list to accomplish multi-select, all transactions from the first row would be selected rather than only those starting from the row you initially clicked. Fixed.
  • shift+click for transaction multi-select would not work if you held down shift and clicked another transaction checkbox. It would work if you clicked on another transaction row but if you clicked on the checkbox of a transaction, it would not multi-select. Fixed. Try not to wear out your shift key trying out all these shift key fixes.
  • Fixed an incorrect back navigation that was available when linking an account or managing connections, and no connections were available yet because nobody wants to back into that.
  • If you updated a budgeted amount and then pressed up, down or tab we would move the focus to an adjacent category but not update the budgeted amount. The available amount would update and navigating back would show the update so it was being saved but it was a display glitch.

API News

Our YNAB API Contest is still going on and there is a little less than 2 weeks to get your submissions in. There’s still time!

  • If using PUT or POST on /budgets/{id}/transactions to create or update a transaction and you specified an import_id (to mark it as imported), we will now return a 409 status code if another transaction with the same import_id already exists on the target account. Previously we would return a 400 error but hey, at least it wasn’t a 418 error because seriously, have you ever tried brewing coffee in a teapot?

Web Release Notes: August 2, 2018


  • When adding or editing a transaction, if you opened the Manage Payees window and changed the “Automatically categorize payee” option, we’ll go ahead and update the transaction you are working with because that’s probably why you updated the setting in the first place.
  • Credit Card Payment categories can now show underfunded warnings for scheduled credit card payments. That means if you have a credit card payment scheduled in your credit card account, you’ll see a warning on the budget screen if your payment category doesn’t have enough money! (This will only apply for new or newly updated scheduled payments so if you want these warnings to start showing up on your budget, deleting and recreating the scheduled payment is your ticket.)
  • More hotness for Credit Card Payment Categories: We’ve significantly improved the performance when clicking on a Credit Card Payment Category where the corresponding account has many transactions.
  • When hovering over the Available amount of a category with a “Target Balance by Date” goal, we would show a helpful tooltip explaining the progress of your goal but we were showing some <notsohelpful/> characters too. No more!
  • We fixed a minor alignment issue on the inflow/outflow inputs when editing a transaction. It was only happening on Internet Explorer 11 and Safari and fairly difficult to notice, but our keenly observant users are the best. We’re going for pixel perfection here folks.
  • We have added reCAPTCHA when connecting to an institution as an added layer of security and to make sure you are a real, living, breathing, human being.


The “Internal Master Category” category group contains categories that are not displayed on the budget directly. Two of these have been renamed for clarity:

  • Immediate Income -> “To be Budgeted”
  • “None” -> “Uncategorized”

Web Release Notes: July 31, 2018


  • Let’s say that this morning your Linked Account was having a temporary issue contacting your bank, so you dutifully used File-based importing to bring in your latest transactions. But, you changed your mind and clicked ‘Undo’. At this point, you would rightfully expect things to be just the way they were before you imported, but instead you see 3 transactions pending import on the account. Now, Undo will really undo that File-based import on a Linked Account.
  • Tabbing to the inflow and outflow fields on Internet Explorer 11 was incorrectly landing on the calculator icon, rather than the input box. Oh, IE, how we love you.
  • Navigating in the date picker with arrow keys was just not working on Internet Explorer 11. Oh, IE, didn’t we say we loved you?
  • When editing a transaction, clicking on a date (that was not a future date) was not advancing the focus to the next field. Now it will take you to the Payee field and you’ll be on your way.
  • For categories with a Target Balance or Target Balance by Date goal, we used to show the total amount that had been budgeted towards the goal (since it was created) in the inspector. This was meant to explain the goal progress but since these goal types are based on the current Available amount for a category, this was confusing. Now, we’ll show the current Available amount right next to the goal Target amount, so you can see where you stand. Unfortunately this change will not effect your actual goal progress.
  • When trying to sign up with an already registered email (you know who you are) we’ll show a friendlier message and give you a link (nudge) to the forgot password screen.


Have you heard about our new Public API? We’ve made a few improvements to it in this release:

  • We’ve added income, budgeted, and activity aggregate values to endpoints that return budget month data (like /budgets/:id/months).
  • If flag_name or cleared fields were specified as numeric values when saving a transaction, a 500 server error would be returned rather than a 400 error. Fixed!

Web Release Notes: July 26, 2018

Improvements & Bug Fixes

  • On the log in, sign up, and forgot password forms, we turned off spellchecker for the email field. We probably should have done that from the get-go. Actually, we did, but we got the syntax wrong (spellcheck="false" vs. spellcheck=false), so it doesn’t really count.
  • We fixed a number-formatting bug for budgets with number formats that use apostrophes. We were displaying the character code (&#x27;) instead of the apostrophe character itself. LOL
  • For Safari we fixed an issue where pressing the <enter> key on a budget field would correctly exit the field but not remove its calculator icon. Now we exit the field and remove the icon. Well, it’s not really removed so much as returned to the pile of unused calculator icons we keep off to the side, just out of view of your browser. It would be wasteful to throw them away. Calculator icons don&#x27;t just grow on trees.

Web Release Notes: July 24, 2018


  • If you want to budget in Tanzanian Shillings, Barbadian Dollars, Cayman Islands Dollars, West African CFA franc, or Central African CFA franc then this is your lucky day since we now support those currencies.
  • Have you ever wondered “why is this Available amount all orange?” We’re adding some cool icons that will explain it!
  • We also added an icon that shows your goal progress at a glance. More clarity, less clicking!
  • We fixed a problem that caused us not to be able to show the emergency maintenance page if we needed to take our servers offline unexpectedly. (Instead it would show you an error, which is exactly what we were trying to avoid by showing you a beautiful maintenance page).
  • When editing or adding a transaction, pressing the Enter key on the memo field used to save the transaction. Not anymore, since now it will take you to the next field which we think makes more sense.
  • We’ll now hide the “Budget for Upcoming” button in the Quick Budget section if your scheduled transactions add up to a positive amount (or an inflow, if you will). Previously in those circumstances, that button would cause it to budget a negative value, which was weird.
  • When direct importing transactions, we used to only allow transactions starting from the last transaction reconciled date. That caused some issues with possible transactions posting with a date a few days prior to the reconciliation date, which can be common with some credit cards, so now we’ll allow a few extra days past the last transaction reconciled date to account for that.

Bug Fixes

  • Are you a Safari Full Screen mode user on macOS? Then pressing the Escape key while budgeting or entering transactions will no longer take you out of Full Screen mode.
  • We fixed a small misalignment in the inflow and outflow fields that was only visible in Firefox.
  • If you clicked the “You can fix this in your budget!” button on an overspent credit card then the app was throwing an error, this wasn’t nice so we fixed it.

Web Release Notes: July 20, 2018


  • We fixed a crash in Internet Explorer 11 in when viewing the Net Worth Report.

Web Release Notes: July 19, 2018

API News

  • For those of you developers using our API, we now return a friendlier error message if you submit a transaction entity with its account_id, payee_id, or category_id properties set to anything other than null or a valid UUID.

Web Release Notes: July 18, 2018


  • We improved scrolling performance of the Income vs Expense report for newer browsers.
  • When a category has net positive spending, meaning the total amount of spending in the category is actually a positive amount (e.g. spent $100, got $150 in refunds), we now ignore it on the Spending Reports and don’t include it in the totals/averages in the inspector. We still show it in the list of category totals in the inspector, though.
  • In the spending totals/trends transaction list, if a sub-transaction doesn’t have a payee, we default it to the parent transaction’s payee.

Bug Fix

  • We fixed a rare issue when troubleshooting Direct Import connections where we would incorrectly display a “missing translation” message at the top of the the credentials or challenges screen.

API News

  • Goal data is now returned from endpoints that include categories. Fields include: goal_type, goal_creation_month, goal_target, goal_target_month, and goal_percentage_complete.

Web Release Notes: July 12, 2018

API News

  • If you don’t include a Content-Type: application/json header when you POST or PUT, we’ll respond with a helpful error message. Previously the error message was a bit cryptic.
  • If you received an access token via the OAuth flow then subsequently visited the OAuth Authorized page and did not click ‘Authorize’ (just visited), we would revoke all existing tokens. Now, we’ll only do this when authorizing the Alexa Skill.
  • Restricted Mode will not be enforced when authorizing an OAuth application you own.
  • The docs now correctly indicate that access tokens created using the Implicit Grant Flow in OAuth will expire 2 hours after creation.

Bug Fixes

  • If you deleted a payee with a renaming rule, then created a new payee and assigned it an identical renaming rule, the rule wouldn’t work for the new payee. Fixed now.
  • When creating a new payee on a different client (i.e. mobile) we weren’t adding it to the Manage Payees payee list on web. You had to refresh the page in your browser to see it. That’s suboptimal, so we fixed it.

Web Release Notes: July 10, 2018

Bug Fixes

  • When deleting an account while looking at “All Accounts”, we weren’t automatically closing the popover. That’s fixed now.
  • On very small screens, the register dropdown options could sometimes block the input. Fixed.
  • Ignoring the obvious question of why? for the time being, if you create a $0 goal target, we’ll now display the goal as 100% complete. This also fixes a edge-case issue with “Payoff balance by date” goals on credit card payment categories where they were showing 0% after you made a payment on the card.
  • If you imported a transaction, reconciled it, then manually matched it to a manually-entered transaction that was not reconciled [you still with me? – ed.], the resulting matching transaction would not be reconciled. Now, if either the manually-entered or imported transaction is reconciled, the matched transaction will also be reconciled.

Web Release Notes: July 5, 2018


  • Previously when jumping to a transaction in the register, if your filters hid that transaction we would display a message with the option to turn off the filters. Nine times out of 10 if you’re jumping to a transaction in the register, you want to see that transaction. Now we automatically turn off the filters and display a message letting you know we’ve done so.

Bug Fix

  • Fixed an issue displaying image challenges for a couple of institutions when connecting accounts for direct import.

API News

  • All API endpoints that return categories now include an original_category_group_id field. That field will be populated for hidden categories and will contain the id of the original category group, before it was hidden.
  • We now support urn:ietf:wg:oauth:2.0:oob as the redirect URI for the Authorization Code Grant flow in OAuth. We used to return HTTP 401. Sorry about that.

Web Release Notes: July 3, 2018

What’s New

  • You can now manage renaming rules for transfer payees in Manage Payees. (That’s actually a lot cooler than it sounds.)


  • The Direct Import add-account flow got assorted fixes/tweaks/improvements to its layout and navigation.
  • And the alert we show during that flow when there’s an active incident with your institution got some big design love. I hope you never see it.

Bug Fixes

  • Sometimes clicking a register checkbox in just the wrong (right) spot would deselect all previously selected transactions. Now those previous selections persist.
  • With the “Show Scheduled Transactions” filter turned on, if you clicked on the “1 transaction needs to be approved or categorized” notification (which kicks off an “Is: Unapproved or Needs Category” search) then cleared that search, all your scheduled transactions disappeared (from sight, not existence). That no longer happens.

API News

  • The new /budgets/:id/settings endpoint allows you to get budget settings for a single budget. If you’re just looking for the date and/or currency settings for a single budget, this is your endpoint. Hitting /budgets/:id would be overkill in this case since it pulls down the entire budget.

Web Release Notes: June 28, 2018


  • When adding or troubleshooting a Direct Import connection and the connection is blocked, we often need to ask you to re-enter your  credentials in order to resume the process. Now, in a few of these scenarios, we will be able to restart the process by just asking you to retry, so you don’t need to re-type that random 30-characters password so often.
  • The Direct Import connection tips we released last week got some design love. Same information, just easier on the eyes.
  • We used to ignore payee rename rules for those payees you didn’t “Include on Payee List” (on the Manage Payees popover) for reasons. Now that you can manage these hidden payees from the Manage Payees popover, it’s reasonable to expect the rename rules are always enforced, so now we always enforce them.

Bug Fixes

  • Fixed a rare Direct Import scenario where responding to a real-time code challenge while adding a bank connection could result in an error, even though the connection continued to process in the background.

API News

Web Release Notes: June 26, 2018

The API, nascent as it is, needs a little polishing. Sorry if you’re not that interested in API news. You can feel good for the people who are though. They’re having a good day.

API Improvements

  • For the /budgets/:id endpoint, the API now sorts categories and category_groups the same as on web and mobile.
  • We improved the styling of the API documentation when being viewed on smaller devices.

Web Release Notes: June 22, 2018

What’s New

Thanks to many of you, the YNAB support team has collected “connection tips” for lots of different financial institutions. Now we display those tips right on the account credentials screen. So, if you’re about to connect to Capital One 360, we’ll tell you where to get that 12-digit access code* you’ll need. We’ll also give you a heads up if your financial institution will frequently prompt you to re-authenticate the connection (confirm you’re you) before importing transactions.

*In your Capital One 360 account, go to Settings > Privacy.

Web Release Notes: June 19, 2018

What’s New

The big news for this release is PAPI going live! What’s PAPI, you say? It’s our public API, so named because we were already in the habit of refering to our internal API as “API” and we needed to distinguish the public bits from the not public bits. If it helps, you can consider PAPI to be the beloved grandfather of public-budgeting-API world: always there to help, not the least bit judgmental, and thinks the world of you. Read more about it in the blog post.

Bug Fix

  • Checkboxes for empty category groups on the budget now behave as expected.

Web Release Notes: June 14, 2018

All internal stuff going out today, and rather pedestrian at that: a job to migrate deprecated account types and some PAPI detail work. Underwhelming, I know. Maybe the next release will bring more exciting news. Fingers crossed.

Web Release Notes: June 12, 2018


  • In the Manage Payees popover, we fixed an issue so now clicking a given payee’s name displays its details on the right.

Bug Fix

  • Direct Import: Fixed an issue where we displayed escaped characters in some institution credential labels.

Web Release Notes: June 7, 2018


  • Last week we had an issue with one of our Direct Import providers that caused them (and subsequently us) to import batches of older transactions to some customers’ accounts. We’ve now added some extra checks to prevent this from happening in the future.
  • We’ve simplified the Account Types list on the Add Account popover. Less noise.
  • We sort transactions by date, most recent first. If two are on the same date, we sort by amount, largest to smallest. Now if you click the Date header cell to reverse the sort order, so you see oldest transactions first, we also invert the secondary sort to show smallest amounts first. Simple, right?

Web Release Notes: June 5, 2018

Today’s release notes are narrated by Owen Meany. Use the voice you heard in your head when you read the book, as opposed to Simon Birch’s. And the hard-core among you will wish these notes were written in Owen’s shrill, ALL-CAP STYLE, but I just couldn’t bring myself to do it. I mean we have standards. We can only take things so far in the name of fading literary references.

What’s New

  • We’ve added an indicator to the status bar for Direct-Import-connected accounts, showing the current state of the connection: good, error, delayed, or maintenance. Hovering over the icon will display a popover with more detailed information about the status, such as the time of the last successful aggregation or details of any errors. This feature is presently being rolled out and we plan to make it available to everyone by week’s end.


  • Displaying the list of connections when adding or connecting an account, or managing your connections just got a little bit faster.

Bug Fixes

  • We no longer show weird characters in the spending and net worth reports when using a currency with apostrophes in it.
  • The deselection of “Automatically categorize payee” in the Manage Payees popover wasn’t being persisted. Now that change persists.

Web Release Notes: May 31, 2018

Today’s release notes are narrated by the inimitable Armstrong Wedgewood.


  • We moved the position of the “Record Payment” button so it’s more difficult to click it when you meant to click the “Edit” or “Import” buttons instead.
  • We added some more generic payee names to the list of those we ignore when automatically renaming payees after direct-importing transactions or importing from a file.

Bug Fix

  • If you clicked outside of the “New Category Group” popup after typing a name we’d create the category instead of canceling the popup. It’s fixed now so we just cancel the popup without creating the new category.

Web Release Notes: May 30, 2018


  • From the Chicken Little Department: When editing a transfer with the other side reconciled, we show a message warning about the possibility this edit could bring your reconciliation out of balance. We were showing this message even if you innocuously changed the memo. We now only show the warning if you change the amount.
  • Date fields in the register were reportedly feeling claustrophobic so we added more space to let them breathe a little.
  • If a cash account was inadvertently linked to a bank, you can now disconnect it from the bank.

Bug Fixes

  • We fixed a currency-setting issue when adding a manual account or creating a credit-card goal in mobile.
  • Fixed a regression with adding/subtracting decimals that don’t start with a “0.”.

UPDATE: The inflow and outflow fields in IE were unresponsive after this morning’s release. Fixed.

Web Release Notes: May 24, 2018

What’s New

  • As part of our ongoing EU General Data Protection Regulation (GDPR) compliance efforts, we now require users to explicitly agree to our Terms of Service and Privacy Policy before creating an account.


  • If you’re adding transactions with your window sized very small, the transaction dropdowns do their best to stay within the window. But sometimes they can cover up the very inputs they’re supposed to be assisting. Now if there isn’t enough room, they’ll go outside the window.

Bug Fixes

  • Fixed an issue where visible scrollbars would knock some UI elements out of alignment.
  • Searching your account register for the word “payment” failed to return any credit card payment transactions. Fixed.
  • Onboarding fixes:
    • The “set a goal” step automatically scrolls the budget on small screens so the category appears in the middle.
    • On the “schedule transaction” step the register fields stopped working if a category was left empty. Silly mistake.
    • Also on the “schedule transaction” step, we now mark the step as complete as you create a transfer transaction. Gotta give credit where credit is due.
    • On the “budget” and “schedule transaction” steps the calculator popover was hiding behind the overlay. No need to be shy, little fella’, you’re among friends here.
  • When creating a new category from the register, the Cancel and Create buttons could break alignment. Quoth the Raven “Nevermore.”

Web Release Notes: May 22, 2018

What’s New

  • File-based Import (affectionately known as FBI to YNABers the world over) is a decent alternative to Direct Import. Sure, it requires a little more hand-holding, but it gets the job done. Unfortunately, some banks play fast and loose with the OFX spec, which means your debits could come across as credits during the import. We’ve added a “Swap Inflow and Outflow” option to the FBI flow for such situations. You can toggle it on and off to preview the effect. Not a bad way to start a random Tuesday in late May.


  • When editing the other, non-reconciled side of a reconciled transfer transaction, we now show a warning pop-over, explaining that editing the amount will render out-of-balance the reconciliation of your other account. Tread lightly.
  • Inline calculators now respect parenthesis. 1.20 * ($10 + $20) now equals 36 instead of 32. All is right with the world.

Bug Fix

  • In other OFX-related news, we now handle multiple credit card accounts properly during the import. Prior to this fix we’d attribute all transactions to a single card. Now we spread the love appropriately.

Web Release Notes: May 10, 2018


  • When viewing transactions on the Spending Totals/Trends reports, we now sort first by descending date, then payee name.

Bug Fixes

  • In some cases, the sidebar UI truncated account balances erratically. Fixed.
  • A few months back we stopped allowing the creation differently-cased-but-otherwise-identically-named payees. That was an unintended consequence of other decisions we’ve made, and after careful reconsideration we’ve decided to allow it again. So if you have a BOOKSTORE payee, you can create a separate Bookstore one. Advanced budgeters may even want to experiment with a new bOOkstOre payee, but caution is advised.
  • The Spending Totals/Trends reports’ tooltips were cutting off letter descenders (e.g. y, p, g, etc.). Fixed.

Web Release Notes: May 8, 2018

Bug Fixes

  • In Firefox the inflow and outflow input boxes were out of alignment with their siblings, as if on tippy-toe. They are now back in proper rank.
  • In IE 11, payees were right aligned when they should be left aligned. Fixed.
  • If you select a future date when adding a transaction, the date picker (calendar) should stay open to give you the opportunity to select a frequency for the scheduled transaction you’re likely setting up. It wasn’t staying open. It is now.

Web Release Notes: May 3, 2018


  • When exporting a Spending Totals report, we now order your categories the same as they appear in your budget.

Bug Fixes

  • We’re supposed to show a warning when you delete a transfer with only the other side reconciled. You would see the warning if you were deleting via the “Edit” menu, but not if you used the delete key. Now you’ll see the warning regardless of how you initiate the deletion.
  • When moving money or editing a budgeted amount, the totals on the move money dropdowns didn’t update accordingly. They do now.
  • If you used quick budget with a given category, clicked on a different category then back to the original, the value would revert to the old budgeted amount. Similarly, if you added or edited a budgeted column, then used undo and clicked on the same budgeted column, the value would revert to it pre-undo value. Both are fixed now, so they retain the proper value.

Web Release Notes: May 1, 2018


  • Budget and category editing got a nice performance boost.
  • We now show the calculator icon on hover.
  • We upgraded our database (to PostgreSQL v10.3) and updated some of our database procedures to take advantage of some improvements in the new version. In a nutshell: our pretty fast database got pretty faster(er).

Bug Fixes

  • If you moved a categorized transaction to an off-budget account then tried to delete one of the related categories, it didn’t work. Now it does.
  • We fixed an issue where some hidden categories were terminally hidden, never to be seen on the “click to unhide a category” list. Now that list shows all hidden categories.
  • If you were looking at a split transaction and clicked “Make Recurring”, we’d create the scheduled split, but we’d also include any previously deleted sub-transactions. Not good, so we fixed it.
  • In the last step of adding a Credit Card account with a goal to pay it off over time, mobile apps were displaying a blank screen. Fixed!

Web Release Notes: April 26, 2018

Bug Fixes

  • The register numbers (i.e. “Working Balance” and friends) were not being updated properly when adding a new account, nor would they be updated for any change on the new account. A simple browser refresh fixed the issue, but we’ve now fixed it for good.
  • Fixed a bunch of small, edge-casey errors from the move to Ember v2.4.

Web Release Notes: April 24, 2018

What’s New

  • You can now type to search categories when auto-assigning a category in manage payees.

Bug Fix

  • Fixed a timing issue for rendering and resizing elements, which will fix some rare issues with modals not displaying correctly.

Web Release Notes: April 19, 2018


  • We upgraded our web framework, Ember, to v2.4. This speeds up the budget screen by about 10% and the register by some 33%. Not too shabby.

UPDATE: Part of today’s release broke some things. They’re fixed now:

  • We fixed an issue deleting account.
  • We fixed an issue resetting passwords.

Web Release Notes: April 17, 2018

Bug Fixes

  • When manually matching two categorized split transactions, we weren’t updating category activity and balance immediately. They would eventually get updated, just belatedly. Fixed now.
  • Register payee search for single-character payees was wonky. It’s no longer wonky.
  • If you manually entered a transfer, then manually matched an imported transaction with one side of that transfer, we weren’t properly updating the other side of the original user-entered transaction. This would result in mismatched amounts on either side of the transfer. Fixed now.

Web Release Notes: April 12, 2018

Bug Fix

  • For a vanishingly small number of budgets, unhiding categories would throw an error. Now it just unhides the categories.

Web Release Notes: April 10, 2018

Bug Fix

  • Refactor some internal navigation logic to fix an “uh oh” error commonly encountered when using the unofficial toolkit extension and possible edge-case routing scenarios.

UPDATE: Part of our release today completely borked the links to switch between the spending totals and trends reports. We’ve now pushed out a fix for those links. We sincerely hope this doesn’t become a trend.

Web Release Notes: April 5, 2018

Bug Fixes

  • Some browsers were retaining the sign in screen background color so when the register loaded, its background appeared blue. Buck up, little register screen, we’ve chased those blues away.
  • Fixed a rare bug where a fresh-started budget would get wonky when adding transactions on a credit account, but only if the new transaction caused the account balance from negative to positive. Fixed now.

Web Release Notes: April 3, 2018

Another release with nothing much to report. Just some security-related updates, but nothing we tend to talk about in detail.

Web Release Notes: March 29, 2018

We’ve got nothing to report for this release. It’s all internal stuff. And mostly boring (e.g. “Install Postgres 10.3 as part of provisioning” and “Improvements to test account creation”). I suppose we could just trot out the old and well-worn “bug fixes and performance improvements” trope, but that would be lazy and shameful. And I feel we owe you more than that since we likely just interrupted your flow with our bittersweet “refresh to get the new hotness” message and you were kind enough to click through to read these very release notes. How could we let you down after all that? We couldn’t, of course. So go forth and budget, bolstered by the knowledge that test account creation is less hateful than it used to be.

Web Release Notes: March 27, 2018

What’s New

  • We now include hidden categories when exporting a budget to CSV.


  • We now prevent the Manage Payees sidebar from scrolling when toggling multiple payees.

Bug Fixes

    • After using a math operator in the budget and navigating away from the field using an arrow key, the input was being left in an active state. Fixed now.
    • We fixed a layout issue when displaying Direct Import challenge options with longer labels.
  • When changing an account name while on the Reports page, the accounts filter was not updated with the new name. Fixed.

Web Release Notes: March 22, 2018

What’s New

  • We updated the icons in the sidebar navigation to match mobile and further reduce visual complexity.


  • Connecting to a financial institution for Direct Import can take some time. To help in those cases, we’ve increased the timeout before aborting the connection attempt.
  • We tweaked the Direct Import messaging when our provider goes into scheduled maintenance or their service becomes temporarily unavailable.

Bug Fix

  • When editing a transaction and clicking ‘Manage Payees’, the given payee should be automatically selected. Sometimes that wasn’t the case. Now we select the correct payee every time.

Web Release Notes: March 20, 2018

What’s New

  • We added renaming rules to ‘manage payees’ so you can now automate how your payees are renamed as they are imported.


Bug Fixes

  • Credit Card Payment categories in the ‘move money’ popover were always listed at the top instead of being in the same position as in your budget. Fixed now.
  • In the register:
    • Clicking the checkbox when editing a transaction no longer causes the edit button to enable/disable.
    • Overflow text no longer gets unceremoniously cut off. We add an ellipsis to soften the blow.
    • The placeholder on the memo input in splits has returned. We didn’t ask where it was, and it didn’t offer any explanation. We’re just going to leave it at that. No matter, we’re just happy it’s home.
    • When split amounts were mismatched, hitting escape would erase your work on the transaction. Now it just closes the warning, a slightly less obtrusive response.

Web Release Notes: March 16, 2018

Bug Fixes

  • Removing all data from the first month in the budget caused ‘To be Budgeted’ to be off for that month.
  • Yesterday’s release quietly introduced a bug with Direct Import failing to display the proper message when adding or troubleshooting a connection. Fixed!

Web Release Notes: March 15, 2018

Bug Fixes

  • Bipartisan mobile fix: On both Android and iOS, the ‘Subscribe Now’ button was interminably disabled. It now behaves like the desktop, only disabled when one or more fields is invalid.
  • In the cover overspending popover, you could use the keyboard to select a category group, causing an error. We no longer allow the selection of category groups via keyboard or otherwise. /ht Josh Madewell, toolkit dev, for the the heads-up!

Web Release Notes: March 13, 2018

Bug Fixes

  • In some cases, after fresh starting your budget you might have seen pre-fresh-start data on post-fresh-start reports. We’ve renamed the feature to “Mostly Fresh Start”. Kidding, of course. It’s fixed now.
  • Fixed an IE 11 issue when miss-clicking on the calculator (e.g. clicking between calculator buttons).

Web Release Notes: March 8, 2018

What’s New

  • My Dear Aunt Sally, today we added a calculator to budgeted inputs, inflows and outflows. We also added inline calculations to inflows and outflows. And those inline calculations got some improvements, too, such as typing an operator moves the cursor to the right of the numbers.


  • Displaying challenges when adding or troubleshooting Direct Import connections got a bit faster.

Web Release Notes: March 6, 2018


  • Previously, pressing the tab key when editing a goal amount would close the goal editor and lose your changes. Now tabbing moves focus to the “Save” button so you can save your work.

Bug Fixes

  • We were incorrectly allowing transactions to be matched several times. Unsurprisingly, this led to errors, especially when trying to undo the second match. Fixed now.
  • In the unlikely event you were to remove all of the transactions from the oldest month of your budget, we failed to remove that month from reports. Reports now ignore such months devoid of transactions.
  • When looking at an inflow transfer from a liability account to an asset account, we were incorrectly showing the transfer payee as “Payment from: <liability account>”. That wasn’t quite right. Now we show “Transfer from: <liability account>”.

Web Release Notes: March 1, 2018

What’s New

  • Credit card categories have long been the odd man out in the budget-category world. Styled differently and stubbornly fixed in position, they’ve not had aesthetic nor functional parity with their non-credit-card category colleagues. Well today is a day that will be widely vaunted in the annals of credit-card-category history. Credit card categories now have the same look and feel as other categories, including the ability to be moved hither and yon. We’ve also added some helpful summary amounts to category headers: budgeted, activity, and available. Not a bad day if you’re a credit card category.


  • Removing Direct Import connections got a speed boost.
  • The “There’s a new update available” page got a bit of a makeover, now linking to these release notes. Apparently we’ve “arrived”. Much love to the OGs among you who were reading these notes before we made it so strikingly obvious where to find them.

Web Release Notes: February 27, 2018


  • Adding multiple connected accounts got a speed boost.

Bug Fixes

  • We fixed a regression introduced by our recent keyboard-input-handling changes. The plus sign (+) now advances the day in the register calendar again.
  • The amount label below the credit card Payment header was bolded when it shouldn’t have been. Fixed.
  • If you had a category group bereft of categories and clicked “Show all hidden categories” from the “Hidden Categories” group, that category group would remain hidden. Now we show it, as you would expect.

Web Release Notes: February 21, 2018


  • When renaming a payee on the Manage Payees modal we were reseting the scroll position of the payees list on the left. This was confusing so we stopped doing it.

Bug Fixes

  • Creating a credit card account without direct import could generate a starting balance one day in the future. Or, time zones are hard. Whatever your choice, it’s fixed.
  • In the process of background-syncing direct import connections ( e.g. when you first open YNAB) we were incorrectly showing the “needs attention” message under those connections until the process was complete. In an effort to “give you your space” and be “less needy” we now wait until the import is complete before displaying messages for the connections that actually need your attention.
  • If your browser autofilled email/password on the forum sign-in page, the “Sign In” button would still be disabled. Now it will be enabled.
  • Payee search used to be too permissive, matching section headers. For example, if you searched for “pay”, looking for a payee with “pay” in its name, we would return all payees under the section header “Saved Payees”. Payee search is now more discerning.

Web Release Notes: February 14, 2018


  • We’ve updated the code behind keyboard shortcuts so they, once again, work as expected. KeyboardEvent.keyCode is deprecated and some of our key mappings based thereon started failing in latest Chrome. We now use the de rigueur KeyboardEvent.key, falling back to KeyboardEvent.keyCode for browsers of advanced age.
  • If you have a bunch of payees, we’ll only show the first 100 (sorted alphabetically) when editing a transaction, though you can still easily search for others. Paring down this list gives a tremendous performance increase to those with a plethora of payees.

Bug Fixes

  • In days of yore, clicking on a transaction memo would launch the transaction editor with the memo selected. You couldn’t delete or edit it, or even get a cursor to appear, by mouse-clicking. Only if you used the arrow keys. Fixed now.
  • In the budget view, selecting the same month in a different year did nothing. Now it switches to the proper month and year, as any reasonable person would expect.
  • If you had a transaction on the first of the month, then selected that month as the beginning of your spending report date range, that transaction would be omitted from the CSV export. Fixed.
  • If you untoggled “Include in Payee List” for a payee under “Manage Payees” then later deleted that payee, we would still show it as “hidden” when searching for payees when editing a transaction. Silly mistake. Fixed.

Web Release Notes: February 7, 2018

Not many public-facing updates today. Sorry. To atone for this dearth of real release notes, let’s take a quick peek behind the dev curtain. Here are some of the commit messages for the workaday updates that went out today:

  • <redacted> integration: 1st pass to start internal testing
  • papi: some new feature requests implemented
  • papi: Some minor scheduled transaction improvements
  • only exclude Recurly requests from Recurly throttle bypass
  • Remove .only from test and fix FOTM test failures
  • Track inline calculations on the soon to be old inline calculator
  • vscode: formatOnSave false by default, true for specific languages
  • Do not allow import txn to transfer if it matches
  • Set higher lock/statement timeouts when running migrations in heroku
  • Revert “Dirty form tracking: Do not disable by default”
  • Remove Transaction event handlers

Now that we’ve given the casual release-notes skimmers a false sense of there being substance here, let’s move on to the actual release note. Singular.

Bug Fix

  • If you edited an unapproved, matched transaction via the “approve” popover (by clicking the chain icon, then the “Approve” button in the popover), and then clicked the “Approve” button in the transaction row, an error message was displayed. A bit of a mess, so we fixed it.

Web Release Notes: January 31, 2018

What’s New

  • We added a new “Manage Connections” option to the budget menu. Consider it one-stop shopping for all your bank connections needs. You no longer have to trudge through the “Add Account” flow to add, remove, or troubleshoot connections.


  • Buttons and checkboxes now work better with screen readers. And if you discover other areas of the app that need similar love, please let us know!
  • Reports now use the date format specified in your budget settings.

Bug Fixes

  • When clicking on an older transaction to navigate to the accounts page, sometimes you get a message saying the transaction was hidden by the filters even if it wasn’t. Be gone, silly message.

Web Release Notes: January 26, 2018


  • The export format for reports now better handles numbers, names with quotes in them and currencies that use quotes as decimal separators.

Web Release Notes: January 24, 2018

What’s New

  • We added an export button to export each of the reports as a CSV file. This exports data only. You’ll have to make your own pretty pixtures.
  • We added a “Record Payment” button (next to “Add Transaction” for credit card accounts. Click it and it’ll create a new transaction with helpful defaults, such as last-used payee and payment amount as inflow.


  • We added a “Payment or Transfer” button to the category dropdown when recording a credit card transaction. Click it and it’ll open the payee dropdown so you can select the proper account for the payment/transfer.
  • We changed how transfer payees are displayed to clarify whether they’re being used to pay a card or transferring money.
  • If you’re YNABing on a very small screen, you’ll notice that when searching for transactions the undo/redo buttons turn into an ellipsis (…). Fret not, dear very-small-screen YNABer, click the ellipsis and the undo/redo buttons will magically appear (and the search field will shrink a bit to give the buttons some room).
  • We implemented a considerable number of UI fixes to make things more consistent and refined. In the interest of conserving space, amusing myself, and transforming pedantry into novelty, I’ll list them without spaces:
    • roundedcornersforthecheckboxes
    • left-aligntheaddaccountbutton
    • useendashinsteadofhyphensforranges
    • increaseletterspacingfortextinallcaps
    • nodotted/dasheddividersoninspector
    • monthpickerdropdown,indicatecurrentmonth
    • newstyleonreconcilebutton
    • removesidebargradient
    • newloadingmessagestyle
    • removeiconsfromalmostallbuttons
  • If you set a flag on a scheduled transfer transaction, when the scheduled transaction fires the flag will now be applied to both sides of the transfer. Previously, that flag would only be applied to one side.
  • We changed the export confirmation label from “Don’t remind me” to “Don’t show again”. Select it and we’ll neither remind you nor show it again.

Bug Fixes

  • When matching transactions sometimes we’d create a duplicate transaction that couldn’t be approved or rejected. Frustrating and fixed.
  • Searching transactions by payee was not returning sub-transactions with empty payees when the parent transaction matched the search term. Now it does.
  • For users with the old-style onboarding, clicking the link to review TODO steps wasn’t working properly. Fixed.
  • Fix a crash that could happen when using “Enter Now” on scheduled transactions. Rare, but fixed nonetheless.
  • In the accounts header we were showing a “pointer” cursor for “Cleared Balance,” “Uncleared Balance”, and “Working Balance” when they were negative, as if there was some action to perform by clicking them. There isn’t, so we now show the default cursor (typically an arrow).

Web Release Notes: January 17, 2018


• We removed the Cancel button from the edit-category popover for debt categories since those categories are not editable. The remaining OK button is your escape hatch from the popover.
• We added some more generic payee names to the list of those we ignore when automatically renaming payees after direct importing transactions or importing from a file.

Bug Fixes

• We fixed an issue that prevented a small number of referral program credits from being applied. If you’re due a free month and haven’t gotten it, drop us a note at [email protected] and we’ll fix it up right quick!
• Recommended search wasn’t working for categories with the same name as a previously deleted category. It is now.
• Register dropdown search was not working properly for payees or categories with a colon. I:t i:s n:o:w.
• Register rows for transfer transactions were a tiny bit taller than their non-transfer brethren. No longer.

Web Release Notes: January 10, 2018

What’s New

  • The YNAB Alexa Skill is now available in Canada and Australia! If you were looking for the perfect reason to move to either of these wonderful countries, this might be it.

Bug Fixes

  • Scheduled inflows on credit card accounts could cause the available amount on a category to be displayed with a “negative” status (red) instead of the proper “caution” status (yellow). Fixed now.
  • YNAB 4-Migration News:
    • In some budgets migrated from YNAB 4 scheduled split transactions with transfers would not “fire” correctly when their time came. The split transactions would be created, but in certain cases the transfers wouldn’t be executed. This has been fixed.
    • Sometimes sub-transfers had different dates on each side of the transfer. We now ensure they match.
    • Sometimes split transfers would not correctly assign the transfer payee correctly on one side of the transfer. It’s now assigned correctly.
    • Scheduled transactions migrated from YNAB4 were skipping the first instance. For example, if you scheduled a transaction with daily frequency set to fire first on 2 January, it would not fire on 2 January but would instead start firing 3 January, then continue per schedule after that. We now handle the first instance properly.
  • We fixed some layout issues when confirming email from a mobile device.

Web Release Notes: January 3, 2018

What if we all work for Callister? Takes a bit of the shine off the new year, doesn’t it?


  • Safari 11 news: Previously Safari didn’t support naming the file that gets downloaded when you export your budget. Safari 11 now does, so you’ll get a properly named zip file for your efforts.

Bug Fixes

  • Apple subscription statuses are now more fresher freshier up-to-date.  If things are copacetic with your Apple subscription you should be good to go accessing the software. Apologies to the small number of YNABers for whom this wasn’t the case.
  • If you had two similarly named categories in different category groups, moving money would accidentally select the wrong category in some cases. Now it selectively selects the category you’ve selected, pickled peppers notwithstanding.
  • Firefox 2 news: Setting a custom timeframe in the reports filters would jump around unexpectedly. Dragging an amount from outflow to input would crash. Both fixed. (Maybe now would be a good time to upgrade? Unless, of course, you’re still running Windows 98 or NT 4.0, in which case we’ve got you covered.)
  • We fixed a borked link in the old on-boarding flow. Precious few of you still have the old on-boarding so feel free to not care about this one.

Web Release Notes: December 12, 2017

What’s New

We’ve implemented two sought-after features from YNAB 4:

  1. Set Available Amounts to $0.00
  2. Reset Budgeted Amounts

The first option will adjust budgeted amounts so that the available amounts are zero. Shocker, I know. Similar to existing Quick Budget options, we only update the un-budgeted categories when no categories are explicitly checked. If you’ve checked one or more categories, we’ll update those (even if they already have budgeted amounts).

The second option resets budgeted amounts to zero. Unlike the other Quick Budget options, this will affect categories with budgeted amounts when no categories are explicitly checked. We’ll pop up a modal asking for your confirmation before we make the adjustments. We’re considerate like that.

Web Release Notes: December 11, 2017


  • We added a hover state to the “jump to transaction” button so it looks less like two random arrows pointing in opposite directions in the Payee field.

Bug Fixes

  • The “reject transaction” button on the “approve transaction” dropdown is now properly styled.
  • For transactions that don’t require a category we show a slightly knocked out “Category not needed”. The tooltip should show the same copy, but didn’t in some cases. Fixed now.

Web Release Notes: December 6, 2017

What’s New

You can now create new categories while adding transactions. You used to have to abandon your nascent transaction, go to your budget, create your new category, then go back to adding your transaction. Not exactly frictionless budgeting. Now you can add the category right from the register.


The “move money” search filter now behaves as well as the register filter, matching text in the middle of words and not choking on emoji.

Bug Fixes

More IE6 Safari 11 fixes this round:

  • You used to have to select a category twice in order to make it stick. Now it’s once and done, as it should be.
  • When selecting a category from the dropdown and pressing enter, the search text was committed instead of the selected category. That’s not what you meant so we fixed it.
  • In the account register, popovers would reappear after shifting focus to another input. This happened with date, payee, and category popovers. Sloppy, but fixed now.


  • Previously, you could transfer a split transaction to an off-budget account, and you could also specify any of the sub-transactions as transfers as well. This caused duplicate transfers, throwing off account balances. Fixed now.
  • When creating a scheduled split transaction with a date prior to today, the first transaction created did not include the splits, although subsequent transactions would get them.
  • When editing an existing scheduled transaction with splits and changing its date to a date prior to today and modifying any of the splits, a transaction would be created but have the old split information.

Web Release Notes: November 29, 2017

[Obligatory ate-too-much-at-Thanksgiving joke here. Pause for obligatory chuckle in response.]

What’s New

  • Now you can jump from one side of a transfer transaction to the other, like a veritable Bob Beamon of the budgeting world. Just click the icon next to a transfer transaction and—BANG!—you’re on the other side. You can also click a transaction in any activity list (budget activity, upcoming transactions, spending report transactions, or income vs expense transactions) and we’ll take you to that transaction.


  • If you add an account using the mobile app before using the web app for the first time, we now allow you to preferentially skip the “add account” onboarding step. We used to make you jump through the hoop of adding another account in order to get credit for that step in our deceptively educational game of onboarding, but that was being somewhat dismissive of your accomplishment. We’re all for giving credit where credit is due.
  • In our never-ending quest to bolster Direct Import (DI), we’ve started preventing the creation of duplicate DI connections for a given institution/username combination. If you were lucky enough to have created duplicate connections in the past, through no fault of your own, we’ll politely ask you to relink those accounts through a single connection.
  • When selecting the date format for a budget, we show a preview using the current date. That’s all well and good unless the day and month number happen to match, like 11/11/2017. In such cases it’s not obvious which part is the month and which the day. Now, instead of using the ever-fickle and oft-ambiguous current date, we always use 12/28/2015, arguably the single most important date in personal-budgeting history.
  • And we now set a more appropriate date for the goal we create during onboarding.

Bug Fixes

  • We fixed an unfortunate currency formatting issue in the error modal we show when trying to match a split transaction with a regular transaction of a different amount.
  • If there was sufficient time to accumulate two or more instances of a scheduled transaction since you last logged in (no judgment), we only created the first one. That’s fixed. Now we create them all.
  • We fixed an issue with adding/editing transactions on Safari 11 (the IE6 of the modern era) where you couldn’t shift focus from one field to another with a click.

Web Release Notes: November 15, 2017

This is going to be kinda boring. Fair warning.


  • We now show a warning message when you delete a non-reconciled transfer when the other side is reconciled. The warning is essentially the same one we already show for reconciled transactions.

Bug fix

  • When creating a new credit card with a name that’s already being used by another of your accounts, we were showing an inaccurate validation message. We still aren’t allowing duplicate names but the error message is now on point.

Web Release Notes: November 9, 2017

There can be only one release note.

Bug fix

  • If you were editing an account, set its balance to zero, then closed the account we weren’t creating the corresponding adjustment transaction. We now create the adjustment before closing the account.

Web Release Notes: November 8, 2017

These relatively unembellished release notes are brought to you by looming deadlines and lack of sleep. Please insert your own jokes where you see fit, then chuckle gently to yourself. And you’re completely free to work blue, though I’m not seeing much fodder in this batch.


  • You can now select an existing transaction and either click the Edit menu or the Make Recurring button on the calendar dropdown to create a scheduled transaction based on the selected transaction.
  • If you’re setting up an account and your search for your financial institution comes up empty, you can now suggest our Direct Import provider adds support for it.
  • If one of your Direct Import financial institutions is having issues we’ll display a new status message in-app. That message will include a link to the status page for more information.

Bug fixes

  • When searching transactions by date using a before: xx/xx/xxxx filter, split scheduled transactions were sometimes shown even if the date was after the filter value. Those false positives have been quashed.
  • If you clicked outside the edit account modal to close it (as opposed to clicking the Cancel button) and that modal was displaying a validation error message, the next time that modal was opened the old validation error message was still showing, even if you had switched accounts. That’s fixed now.

Web Release Notes: November 2, 2017

Good artists copy; great artists steal. Two bullet points below are lifted verbatim from the iOS v2.0.5 release notes. But you, dear Web Release Notes reader, can consider them original content since Apple takes its sweet time approving new releases and the iOS release notes haven’t been published yet. I would apologize for the self-plagiarization, but it’s a gray area and my creativity is faltering.


  • Some banks include invalid unicode characters in their export files (shocker!). Our file-based importer would crash on those characters. Now it doesn’t.
  • If we see a check number in a direct imported bank transaction we now prepend that check number to the memo. Unless the check number is already there, because we don’t like duplication. Unless the check number is already there, because we don’t like duplication. Also, check numbers imported through direct import or file-based import will be prepended with a # sign, creating an inadvertent hashtag. Bonus!
  • Scheduled transaction handling got some love (and by love I mean a major overhaul). It’s now less error-prone and much more performant (not a word, but perfectly cromulent in this case).

Bug fixes

  • You can now split a transaction if you are transferring to to a tracking account. (/ht Aquamarine Projector)
  • Fixed a regression so after adding a new bank account and closing the accounts modal we, once again, automatically select the account you just added.
  • When adding a transaction, we show available balances next to each category. But if you added a transaction for a given category then added another for the same category, we didn’t update its available balance. That’s fixed now, so we always show the latest available balance in the dropdown. Accuracy FTW!
  • When importing transactions from your bank, if a transaction was not yet approved and matched another transaction you weren’t able to “unmatch” them and save as separate transactions. You could tap the “Unmatch” button until the cows came home, but nothing happened. That’s fixed now. And I’m happy to report the cows made it home safely.

11 Oct 2017

What’s New

  • The new “My Account” design is making its debut. But it’s not like some prim and stuffy coming out party. Or maybe it is, but only after The Lady Chablis saunters in.


  • Nothing in particular to call out here. Just the normal paying down some technical debt and implementing performance efficiencies. (Of note for you technically leaning YNABers, Taylor cut our IO load on Postgres by about half. BANG!)

Bug Fixes

  • More Safari 11 fixes. Just like last time, only more. Hopefully this covers all the places you could get it into an infinite select-text/focus-field loop in Safari. Kindly let us know if you stumble across any wayward squatters. As a reward you’ll get to read about it in the next release notes, warmed by the knowledge that “Hey! I told them about that!”
  • Some Apple subscribers were running into an issue where they got charged for the subscription but the app was telling them they weren’t subscribed. Frustrating, to say the least. I apologize for that issue. This release fixes it (he said, furtively crossing his fingers).

02 Oct 2017

What’s new

  • Not much, just a couple of improvements and a bug fix. What’s new with you?


  • We had changed the payee-selection behavior to prioritize the payee name you typed, as opposed to auto-selecting the first match. This made it easier to create new payees. Well, swayed by your feedback, we’ve changed our minds. Or maybe it’s more accurate to say you changed our minds. Regardless, now we auto-select the first matching payee so you can simply hit the <enter> key and move on with your life. As a result, you’ll now have to explicitly select “Create ‘[payee name]’ payee” to create a new one.
  • When you select a future date while creating a transaction in your account register, you’re most likely creating a recurring transaction so we no longer close the date picker and focus on the payee field, forcing you to go back to the date picker to select a frequency. Now the date picker remains open, patient awaiting your choice of repeat-frequency. It’s UX with a better X. UX, if you will.

Bug Fixes

  • Fixed a bug where the previous month listed on the inspector when a category is selected wasn’t always the actual previous month. Apparently the order of months on the Julian calendar is significant. Who knew?

25 Sep 2017

Monday releases are cool because they add a modicum of shine to an otherwise universally derided day. Unless you’re the one writing the release notes. Then it’s every bit a Monday. Please calibrate your expectations of these notes accordingly.


  • For the product team the first day of the month (FOTM) can be somewhat harrowing. When the month rolls over we do a bunch of calculations to summarize the previous month and prepare for the next. To understate the issue this can cause some stress on our beloved database while it catches up. We have a few knobs to turn and settings to tweak to help it along, and if you imagine The Great and Powerful Oz when Toto pulls back the curtain that would be a fair approximation of what we look like on the FOTM. Well, with October 1 looming, we’ve identified and addressed some performance bottlenecks in those FOTM calcs, and generally made the process more efficient. It’s likely not the end of the story but we’re getting closer to not caring about month rollovers.
  • Direct Import gets some love in the form of a “Skip” button that allows you switch to adding an account manually. The “Continue” button has the same effect when your institution search yields no results. And if you selected an institution from the list the “Back” button takes you back to search, unless you got a credentials error before you clicked “Back”, in which case we take you back to the banks list. Got it? Good, there will be a quiz tomorrow.

Bug Fixes

  • File Based Importing (affectionately known as FBI) had an issue when dragging and dropping files in Firefox. That’s fixed now so you won’t see the FBI overlay appear when it shouldn’t.
  • When you focus on a field we automatically select the text in that field so you can just start typing. Efficient, right? Not so much in Safari 11. When you select text in Safari 11 it fires its focus event. We see that focus event and select the text, which causes Safari 11 to fire its focus event, and ’round and ’round we go. That’s fixed now; you’re free to use Safari 11 with impunity.

21 Sep 2017

This small hotfix release fixes a problem users who upgraded to Safari 11 were having when adding or editing a transaction.  There was an erratic jumping behavior that was quite distracting but it should not be happening anymore.

20 Sep 2017

Folks, our witty release notes author, George, is taking a much needed vacation this week so the notes are going to be a bit more dry this week. Sorry! George will be back at it soon!

  • We made some welcome improvements to error messages when adding a new account. If we are having issues connecting one or more banks, we will tell you about it and give you a handy link to either our status page or a troubleshooting guide that should be helpful.
  • If your date format has a “-” in it, we previously fixed it so pressing “-” didn’t go back a day but let you type in a date with dashes in it. But this also disabled the left arrow key. So we have now restored the left arrow hotkey on the calendar for users with “-” in their date format. If your date format does not have a “-” in it, you never even knew this was a problem.
  • We fixed an issue where the selecting of existing text when editing a transaction is delayed so for some fast typers (you know who you are), the beginning of the word they’re typing gets overwritten by the rest of the word they’re typing.
  • We used to do a lot of work behind the scenes when you moved a category to another master to keep things updated. We’ve removed most of this work so things should be much faster now. Why do work when you don’t have to?
  • The text for the tooltips in the Credit Card Payments budget section have been updated to be more consistent.
  • Fixed text formatting when showing a loading message during the process of connecting an account to a bank. For those that know what “double escaping” means; yeah, that was the problem.
  • Ctrl+Click on a sidebar account to open in a new window on Windows has been fixed!
  • When entering a transaction and searching for a category, the filtered list of budget categories were not always listed in the same order as they were in your budget itself. Fixed!

13 Sep 2017

  • In the register, when you select a payee we suggest a category based on the category you previously used for that payee. Helpful, right? But if you just hit <enter> on the auto-suggested category we’d pull the ol’ switcheroo and replace it with the category you used when last entering a transaction. So if you created a transaction with “Whole Foods” as the payee, we would auto-suggest (and highlight) the category “groceries”. But if you just hit <enter>, intending to save the auto-suggested “groceries” category, we’d save it as a different category, like “life insurance”. Maybe that’s a poor example since one could make the argument that groceries are a type of life insurance, but the app’s not that smart. Yet. Weak example notwithstanding, it’s fixed now.
  • We no longer select a partially matched payee from the list of suggestions, only exact matches. To select a partial match, you’ll have to exercise those arrow keys or (horror!) use the mouse.
  • When selecting a payee or category for a split transaction we’d shift focus to the next field to fill in (hooray!) but on the wrong sub-transaction (boo!). Somewhat disorienting, but fixed now.
  • When selecting a transfer payee, we now correctly shift focus to the memo field, not the disabled category field.
  • Manage Payees continues to grow in strength and stature: if you’re combining 10 payees or more, we’ll display a confirmation dialog to make sure that’s what you’re intending to do. Turns out that “select all” checkbox is actually a footgun.

12 Sep 2017

  • With no categories selected, clicking any “Quick Budget” option did nothing. It did nothing instantly so “Quick Budget” is still a fair descriptor. Now those options actually change your budget, albeit a few milliseconds more slowly.
  • If you added a split transaction then removed one of the child transactions we used to erroneously create an orphaned sub transaction. Fixed now.
  • Fixed an issue with Firefox where you couldn’t change the frequency of a scheduled transaction. Dr. Baronovich implores, “You must think in Russian”, but it should work either way.
  • Fixed an issue with the links the unofficial toolkit for YNAB injects into the sidebar. In unrelated news, today’s word of the day is magnanimous.

06 Sep 2017

Howdy, friends! Invigorated by the prospect of the young’uns returning to school we’ve been busy little bees. There’s a lot going on in this release so kick back, put every electronic device within earshot on DND, and laissez le bon temps roulet.

  • Selecting multiple transactions in a big register via shift+click now works as you’d expect, even if you have to scroll, scroll, scroll before you shift+click.
  • You should notice substantial performance improvements when editing transactions. And “substantial” is in italics so it means “really a lot”.
  • No more jumping to the memo field when categorizing a newly imported uncategorized transaction.
  • Transaction dropdowns now open on Safari 11, which is helpful.
  • No more setting goals on the “Uncategorized Transactions” pseudo-category in the budget. If you have uncategorized transactions we roll those up in the aforementioned pseudo-category in your budget. And we used to let you attach goals to that category. That serves no appreciable purpose, so we removed the “feature”.
  • We’re slowly rolling out improved account_category_payee/memo searching, giving priority to items starting with the search term and accounting for some tpyos.
  • Select a few entries on an account register (use shift+click for bonus points!) and we’ll show you a “Selected Total” at the top. “That’s old hat!”, you say. To which I reply, “yes, it is old hat, but let me finish.” With this release that selected total better accounts for split transactions! Disappointed in the anticlimax you shake your head thinking, “just because you add an exclamation point at the end doesn’t make it exciting.” Fair point!
  • More search geekery: when searching for a specific account, payee or category, and you have some that are similarly named, we’d match ‘em all. Now we prioritize complete matches in the results. For example, say you have two categories: Fun Money and Unfun Money. Prior to this release, searching for Category: Fun Money would also match the “Unfun Money” category. Now it only matches “Fun Money” because it’s a complete match and we prioritize complete matches. If you want both results returned you can leverage partial matches with Category: Fun.
  • The hyphen/dash (-) hotkey usually goes back one day when entering a date in the register. But things got a little wonky if you configured your budget to use a date format with dashes. Said wonkiness is now gone. Now dash away! Dash away! Dash away all! (Too soon?)
  • It’s déjà vu all over again. Moving between budget months was keeping categories selected even if they were later explicitly deselected. For example, select Electric, then go to next month. Now deselect Electric and select Phone. Now go back to the previous month and both Electric and Phone were selected. This is fixed now. It’s jamais vu all over again.
  • Your browser should now stop asking to remember bank credentials for Direct Import.
  • When fresh starting a budget, the starting balance will now reflect your time zone’s ”today” instead of UTC’s “today”. Unless, of course, you only fresh start your budgets in Greenwich, in which case no such bug ever existed. “Just joke”, as a friend used to say.
  • We added two new aliases for wiring up institutions for direct import: “amex” will get you “American Express”; and “unionbank” will get you “Union Bank”. I sincerely hope this bullet point finds its way to that one YNABer who uses both Union Bank and American Express. The time savings will be unprecedented.
  • We fixed some issues with printing reports. The trees aren’t happy, though Hank Stamper and family applaud the effort.
  • We now include commas in amounts when exporting budgets. Jesse previously refused to let us export them saying, “Let Excel use its own commas.” He has since softened on this position.
  • The register now shows “Category not needed” whenever a category isn’t needed, like for transfers, split transfers, and debt account (e.g. credit card) starting balances. If you have a positive starting balance on that shiny new debt account, we’ll show “Inflow: To be Budgeted [sic]”.
  • The “Income v Expense” report no longer classifies starting balances as income. I would explain the technical details behind this decision, but unless you’re an accountant you’d be bored. And if you are an accountant you’d just roll you eyes at my rudimentary explanation.
  • We now prevent the self-service modal from getting hidden behind the on-boarding banner on small screens. It would be funny if the part that was hidden had said, “Get a bigger screen.”

24 Aug 2017

  • When editing existing connections to banks that are no longer on the enabled institutions list we no longer display the loading screen until the eschatological end of days.
  • For cash accounts, we no longer show the “Set Up Direct Import” section on the “Import Transactions” modal. That’s just silly. Unless your purse/wallet/pocket/mattress has an API for cash transaction aggregation, in which case we should talk.
  • The budget menu copy got tightened up a bit. See if you can spot the differences.
  • In some very specific circumstances, with a small number of institutions, we were incorrectly importing empty memos/payees from bank transactions. Can you say “unanchored regular expression”?


17 Aug 2017

  • We love mobile, especially with all its new hotness, but we had to give it a little talking to so it would play nice with payee management. If you deselected “Automatically categorize payee” option on the “Manage payees” modal then used that payee when entering a transaction on mobile, the option would be re-selected automatically. Then the next time you entered or imported transactions with that payee auto-categorization would keep auto-categorizing. That’s likely not what you wanted so we fixed it. The fix will take a short while to roll out to everyone so hold tight if you have this problem, knowing it will be fixed up soon!
  • There was a very edge-casey scenario (oh, so rare!) that could cause To Be Budgeted to get thrown off temporarily when deleting a category. No more!
  • We’ve freshened up this little nugget: humans.txt
  • More security fixes about which we shall remain hand-wavy.
  • Some good news before the bad news: we added a subtle animation when closing modals, because who doesn’t like subtle animations? (Not to get too excited, it’s more Steamboat Willie than Toy Story, more Wallace and Gromit than Fantasia, more South Park than The Wall.)
  • Now the bad news: the beloved Reconciliation Dance modal will dismiss itself after 2 seconds. We used to wait for you to click somewhere before dismissing, but that could get a bit awkward. On the upside, the auto-dismissal features a subtle animation, so you’ve got that going for you, which is nice.

08 Aug 2017

  • Ok, so apparently ending a sentence with a preposition is bad mojo. Remember yesterday, when we so boldly told you the Net Worth report excludes closed accounts? Well, we got it wrong. Turns out, for historical reasons, closed accounts should be included, otherwise you’ll see a big bump in net worth for the month you closed the account.
  • We introduced a little regression (in the vernacular) with our last release which prevented linking YNAB to Alexa. It’s fixed now.
  • So far we’re 0 for 2 in terms of “cool stuff” in this release, but take heart as we can now legitimately appropriate the term iatrogenic.
  • You might think morale is a bit low on our end, what with two mistakes in the previous release, but if you look closely through the egg on our collective face, we’re positively beaming today. Why, you ask? Well, we’re completely stoked (at the risk of sounding too technical) to release our full-featured mobile apps today! Get ’em while they’re hot!

07 Aug 2017

  • The Net Worth report excludes closed accounts. When you close an account you transfer the balance to another account, so everything’s accounted for.
  • We have no official position on ending sentences with prepositions.
  • We fixed an issue with matched transactions that prevented them from being approved.
  • When fresh starting a budget we append to its name the date your old budget was archived. The only problem was we were using UTC time to determine the date. Those of you who’ve had the unmitigated pleasure of dealing with time zones are now gently nodding your heads in knowing assent. Those of you who don’t know that particular joy: sometimes our dates were a day off. Regardless of which camp you’re in, we now use local time so this issue is behind us. Get thee behind me, time zones.
  • Cursors have been foiled again. (Snidely Whiplash anyone?) Cursor styles on the register and budget now more closely follow web standards. You know, things like the pointy hand for things you can select, and I-beam pointers where you can enter text. (Whoever named the “I-beam pointer” phoned it in that day. Or maybe the rockstar who named the octothorpe had the day off.)
  • If you use the Grammarly extension with Chrome, your going to love this one: you’re budget totals should be back in alignment.
  • We no longer show the “cleared” icon/column for scheduled transactions. We weren’t saving it anyway so this was misleading, which is out of character for us. Apologies.
  • It’s tougher than you think to work the word “splash” into release notes. Well, maybe not if you’re not overly concerned with subtlety.

03 Aug 2017

  • We took the liberty of sprinkling in some security bits. Those of you expecting me to paraphrase Ben Franklin’s quote here will be sadly disappointed. I got my ears soundly boxed the last time I ventured away from the safety of apolitical rhetoric.
  • If you’re in that elite group of users managing their payees in IE 11 (holla!), we now correctly determine the first checked payee.
  • In other Manage Payee news: we added some more generic payee names to the list of those we ignore when automatically renaming payees after direct importing transactions or importing from a file. This includes such stalwarts as ‘withdrawal pos‘, ‘check with image: inclearing check‘, and the granddaddy of ’em all: ‘atbol interac e-transfer rcvd‘.

01 Aug 2017

  • Our new Payee Management feature is now available to everyone!
  • Quick Budget: When you have no categories selected, the Quick Budget amounts previously only included values for categories that weren’t budgeted ($0.00). Now we include values across the entire budget. Please note, if you use a Quick Budget option with no categories selected we’ll still only budget un-budgeted categories ($0.00). It has worked this way for a long time and will continue to do so. This will save you the frustration of budgeting a bunch of stuff then clicking “Average Spent” which otherwise would have blown away all the work you just did, which you might not have intended.
  • For those of you with a keen (or even indifferent) design aesthetic, the account widget now uses all the available vertical space. This was only noticeable on bank connections with a bunch of accounts. Awkward whitespace no more.
  • When managing payees we now default the combined payee to be the first payee you actively selected.
  • We fixed the sort order of hidden categories. This is tantamount to grooming your dust bunnies. Most people won’t look under the couch, but if they do, your dust bunnies will be on point.

20 July 2017

  • We’ve made some updates to Payee Management so we can continue slowly rolling it out to everyone. Thank you all for the feedback!
  • Notably, a newly combined payee loved the ride so much that it would try to sneak into your next combine. We now deselect all payees after combining or deleting.
  • Scrollbars. Apparently they are useful. They have returned to your long list of payees.
  • And a small but important fix for adding accounts with those unadventurous default browsers, IE and Safari.

19 July 2017

  • We’re slowly rolling out the Payee Management feature, which got some love. Renaming a payee used in a split transaction no longer throws an error. And here’s a fun one: Go to ‘All Accounts’, then ‘Reports’, now open ‘Manage payees’. Did you get the Uh-oh! error? Of course not, because we fixed it, silly goose.
  • Direct Import got some improved connection-status and error messaging, which gives us all a bit more visibility into the quagmire that is bank-transaction aggregation.
  • Speaking of direct import, searching for your beloved financial institution now includes URLs in the results list. This should give you a bit more confidence that we’re all talking about the same bank.
  • And the direct import improvement train keeps rolling: We introduced a bunch of aliases for common search terms. For example, if you search for “FCU” we’ll return results for “Federal Credit Union” too. And we support (USPS) state postal abbreviations, too, so you can just type “MA” instead of trying to remember how to spell Massachusetts. That’s of dubious value, though, since if your financial institution is in Massachusetts, you probably live in Massachusetts. And if you live in Massachusetts, you probably know how to spell Massachusetts. (At least one would hope.)
  • When you’re adding an account, waiting for direct import to connect to your bank is now a more pleasant experience. As the various steps of the connection process complete, we update the interface to let you know things are happening. It’s the next best thing to playing the countdown music for Final Jeopardy! in the background.
  • For bank connections requiring your attention, we’ve replaced the little warning icon with a more descriptive banner. (And now we have a few thousand little warning icons laying around, collecting dust, if anyone’s in the market.)
  • We fixed an issue where starting balances were being dated “tomorrow”. Optimistic, yes, but helpful? Not so much. (For our developer friends: timezones, amirite?)
  • Other UI polish, such as indenting the splits in split transactions in the register; and suppressing the needs-category-alert icon when creating new transactions, before you’ve even had a chance to categorize it. Patience, young grasshopper.
  • Also, Jar Jar Binks is the real Phantom Menace.

12 July 2017

  • Too clever by half seems an apt description of this one. When importing transactions from your bank we used to mash together the original payee name with the memo field. The thought was this would give you a handy reference to the original in case our cleaned up version of the payee name was off. Nice touch, but it could lead to some confusion if not downright duplication, so we don’t do that anymore.
  • If you have any payee rename rules that affect incoming transactions, we now include the imported payee name in the tooltip we display when you hover over the payee field in the account register. Think of this as the xkcd tooltip of the budgeting world.
  • We’ve improved duplicate detection when direct importing transactions from your bank. This kind of thing is conspicuous only in its absence. Like that single, crisp dollar bill your grandmother included in every birthday card she sent.
  • We noticed some folks were missing Credit Card Payment categories which caused errors when selecting credit card accounts. We fixed that. Please accept this joke as an apology: What do you get when you cross a joke with a rhetorical question?
  • For budgets using non-decimal currencies, search results weren’t including inflow/outflow queries. Now they do and all is right with the world.