Feature Requests

When you need to sign off a task to be done, you need to go to the date field and scroll down to get to today. Placing the today at the top of the calendar makes so much sense to me or defaulting to today in the field when you click on it for it to be done. Also who ever clicks it to be done - changing it to the person who click it done and todays date would be AMAZING. Maybe make this a default setting you can turn on or off

Ability to review client file connections in Practice Settings, even if the clients were deleted. Use case: A way to cross reference historical invoices to show which clients were connected at the time of the invoice (aka included on the client count).

Ability to update Tracking Categories on postings in Xero in the same way we can use Classes in QBO within Keeper

You can sort the activity log but you can't do anything with it. It would be nice if you could download the report into CSV or Excel.

Our firm is happy with Keeper and your team has a great mind for heading in the right direction on ideas we can actually utilize. Maybe we're impatient but we certainly could appreciate some more coding engineers on the Keeper team to push out more updates more frequently and with higher quality & feature-rich thought . Some of the features tend to feel half-baked and minimal, and despite full faith that fixes & updates will come- we feel sometimes they take too long and we have to find solution elsewhere. There's at least a dozen features we wish Keeper had, and easily could have, but it just quite simply doesn't. There's also half a dozen features Keeper does have but fall short of user experience expectations and don't fulfill our firm's or clients needs. Keeper is awesome and has great potential but needs to capitalize more successfully and start rolling out code or it may continue to waste fruit that was ripe to be picked

I'd like to limit which users can access what information n Keeper. especially W9s in Keeper. To manage our internal controls, not everyone has access to SSN and EINs. We already limit this in QuickBooks as well. Another piece would limiting hat the clients upload to Keeper under non transaction questions. This is where we remind clients to upload their bank and credit card statements. We like to redact the account numbers before sharing it with the team that reconciles the accounts.

Offer an open API for Keeper

Let's be real. You guys either hate Xero or simply just don't care about Xero integrations. Not only does Keeper keep adding on my utility on their platform, but they can barely keep Xero integrations working correctly. So, all of these fun features continue to be pointless for over half of our clients and therefore our process gets interupted. Keeper: "We now have an upgraded reporting!" Us: "Looks cool, let's make this part of our process." Keeper: "Nope... not allowed for Xero clients." Keeper: "We now have AI Categorizing in keeper!" Us: "Looks really efficient, let's see if we can streamline our process more." Keeper: "Nope... only have it for QBO." I know most of your clients are on QBO, but Xero users can't help but feel you just give them the middle finger. The core functions work in Keeper, and that is the primary reason we stay and they work pretty decently. But it gets annoying when you want to train and develop your practice and you can only implement half of the features on half of your clients.

Xero requires the use of account numbers (codes) which makes it kind of a PITA to add a new account on the fly with Keeper because we have to know what account number is available before we can add it. Typically this means going into Xero's COA and finding an open number, then coming back to Keeper and creating the account. If there was a way where Keeper could "suggest" open account numbers based on the standard numbering convention for the account type/what's currently in use in the Xero file, that would be amazing. I'm not sure how possible this is but even just being able to see a dropdown of the current COA on the same screen so we can look to see what's in use would also be helpful. Currently we don't know if something's in use until after we've gone through the whole input of the information and tried to save it just to have it fail.