How Much Time Do You Have?
On average, new budgeters save $600 by month two and more than $6,000 the first year! Pretty solid return on investment.
Try YNAB FREE for 34 days
Start taking control of your money
After your trial, continue for $4.17/month, billed annually at $50
No credit card required.
A steady stream of YNAB improvements for your reading pleasure. Grab some tea. Curl up with a Snuggy® and enjoy.
Content-Type: application/jsonheader when you
PUT, we’ll respond with a helpful error message. Previously the error message was a bit cryptic.
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.
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.
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.
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.
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.
Today’s release notes are narrated by the inimitable Armstrong Wedgewood.
UPDATE: The inflow and outflow fields in IE were unresponsive after this morning’s release. Fixed.
UPDATE: Part of today’s release broke some things. They’re fixed now:
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.
Another release with nothing much to report. Just some security-related updates, but nothing we tend to talk about in detail.
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.
KeyboardEvent.keyCodeis 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.keyCodefor browsers of advanced age.
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:
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.
• 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.
• 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.
What if we all work for Callister? Takes a bit of the shine off the new year, doesn’t it?
We’ve implemented two sought-after features from YNAB 4:
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.
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.
IE6 Safari 11 fixes this round:
[Obligatory ate-too-much-at-Thanksgiving joke here. Pause for obligatory chuckle in response.]
This is going to be kinda boring. Fair warning.
There can be only one release note.
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.
before: xx/xx/xxxxfilter, split scheduled transactions were sometimes shown even if the date was after the filter value. Those false positives have been quashed.
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.
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.
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.
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!
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.
Unfun Money. Prior to this release, searching for
Category: Fun Moneywould 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
-) 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?)
Electric, then go to next month. Now deselect
Phone. Now go back to the previous month and both
Phonewere selected. This is fixed now. It’s jamais vu all over again.
Yesterday morning we started seeing reports of transactions importing without payee/memo information, as well as some duplicate transactions. We temporarily paused transaction importing to prevent more errant transactions from being created while we worked with our direct import partner to diagnose and fix the issue. Unfortunately we were a little late to the party as many YNABers had already imported some of these wayward transactions.
Thankfully our direct import partner quickly fixed the bug that caused this issue. That said, we’re releasing some tweaks to YNAB to prevent more of these ne’er-do-well transactions from being imported in the future.
Transaction imports are now running at full capacity and will very likely be caught up by the time you read this. Unless you’re a really fast reader, in which case transaction imports are now running at full capacity and will very likely be caught up by the time our slower (but much beloved!) readers finish this paragraph.
We’ve removed many of the offending transactions (those that were already downloaded and waiting to be imported into an account), but there might still be some laying around. If you see any duplicate transactions the next time you import, just delete them to get back to budgeting. (Pro Tip: use the search to find all transactions that need approval with “Is: Unapproved”.) If you’re still seeing duplicate transactions in subsequent imports, please contact [email protected] and we’ll get it sorted, posthaste.
Finally, please accept our apology for this little kerfuffle (or curfuffle if you live near Graham). As we mentioned above, we’re doing our best to make sure it doesn’t happen again. Thanks for understanding and have a great weekend 🙂
This was one of our biggest polish releases in quite some time! So while we only give you the highlight reel here, there was a whole lot done behind the scenes.
A super small Thursday release that paves the way for some bigger changes coming down the pike:
We’re working on some bigger (or would you say, “smaller?”) stuff that will release all at once. Hence the short lists of improvements as of late. 🙂
UPDATE: Part of our first release today made it impossible to use Reconciliation, which (like a link to nowhere) was not helpful. Our second release delivered the fix. Reconcile away!
The Reports Report
A few post-launch fix-ups and polish for the new Reports…
“Goal line push”
“The Calm Before the Storm” Release
The Fiddler on the Roof edition.
Happy Thursday to you all!
An early-week release that’s laying the groundwork for some secret things. Also:
A middle-of-the-week quick little release to handle a few things. Bigger things coming. (Always.)
All the engineers are here at YNAB HQ hacking away on some cool stuff for the next two days, but wanted to get out this release!
Just lots of under the hood fixes to make things better for you, without you ever really knowing what they were.
The Stranger Things Edition
And we’re done until next week. No way we’re going to do another push so close to the weekend.
Happy Father’s Day!
Hey U.S. folks, let’s all just pause and enjoy the fact that we don’t pay taxes today, but in three days.