The start of a new year always brings a renewed interest in keeping your finances under control. At ClearCheckbook we want to make this as easy for you as possible. To help make our Jiving (balancing / reconciling) process much easier to understand for beginners, we made a dedicated tutorial page that has a video tutorial as well as a guided written walkthrough and some troubleshooting FAQ's. This tutorial can be found here: https://www.clearcheckbook.com/help/jive

This time of year can also lead to some headaches when it comes to adding transactions. When you're adding a transaction, be very aware of which year you're adding it for. If you add some transactions for early 2017 and then go back to add some from December 2016, make sure the year is switched to 2016. Also, the opposite is true. If you're adding transactions from late last year and then want to add a transaction for January 2017, make sure the year is correct. If it's not correct, the transaction will be added as January 2016 and you won't see it at the top of your transaction list (since it'll be with all of the year old transactions).

2016 saw a lot of behind-the-scenes work plus some new features and a revamped iOS app. Plans for 2017 include a new Android app as well as a lot of enhancements to ClearCheckbook as a whole.

We've been very pleased with the continued growth of the site. You can help us even more though by spreading the word of ClearCheckbook to any friends or family members who might be looking to get a better grasp on their finances for the new year.

Thanks and happy new year!

- The ClearCheckbook Team

Today, Friday October 21, 2016, there was a major DNS outage that affected an untold number of sites including Netflix, Twitter, Spotify, Reddit, GitHub, New York Times, Heroku (who we use as a server solution) and more which took ClearCheckbook offline as well.

Unfortunately in situations like this there's nothing we're able to do. The issue was with technology controlling how the internet fundamentally works and nothing we actually have any control over.

It appears things are coming back online now. We're sorry for the inconvenience and wish there was something we were able to do.

More information on the outage can be found here:
https://www.wired.com/2016/10/internet-outage-ddos-dns-dyn/
https://techcrunch.com/2016/10/21/many-sites-including-twitter-and-spotify-suffering-outage/

We're happy to announce that the ClearCheckbook app for iOS is now available for download in the App store.

The app has been completely redesigned from the ground up using the latest iOS development tools and technologies which will help future-proof it for upcoming updates to iOS.

The ClearCheckbook iOS app behaves similarly to the old app and has most of the same features. One thing to note is to edit or delete any accounts, transactions, budgets, reminders or categories, simply swipe the item to the left and you'll be presented with an option to edit or delete it.

This is just the first iteration of the app. We've got a lot more updates for it in the works and will let you know more about those in the future.

iOS Screen Shots:

We want to give a special thanks to all of the users who helped beta test the app over the last few weeks. You provided some extremely valuable information that helped us catch and fix a lot of issues.

If you have any issues while using the app, please use the Contact Us form at the bottom right side of ClearCheckbook.com and we'll work on getting any problems fixed.

We're making some final updates to the last version that was out for beta testing and plan on submitting the app to Apple this week for review. We'll have more information and screen shots when we actually submit the app for approval.

On June 1, 2016 starting at around 10:20am ET, ClearCheckbook was hit by an extremely massive amount of fake logins which overwhelmed our database and caused the site downtime some of you had experienced.

These kinds of attacks are used either by a competing organization to cripple their rivals or by nefarious individuals or groups that use the attack to expose any weaknesses in the database which would let them gain access to it.

We're still not sure what the reasoning for the attacks were but none of your data was compromised while the issues were going on.

I'm extremely sorry for any inconveniences this caused you today. We'll be monitoring our logs to keep an eye on similar attacks and fix them quickly now that we know what to do.