People download the Expensify app for all kinds of reasons: accountants looking for a better (read: less shoebox-shaped) way to collect receipts from clients, employees sick of submitting taped receipts to their boss, and even individuals who just want an easy way to track how often they’re eating Taco Bell (me; too often). One of the major challenges we’ve faced is how to ensure that Expensify works for everyone without requiring tedious configuration. Enter Inbox. Continue Reading…
As Expensify has grown up, we’ve put more and more energy into adding functionality to give admins more control over how employees interact with Expensify. Today, we’re happy to announce that we fully support SAML single sign-on via both our website and mobile app. We can work with any identity provider, such as OneLogin and Okta, as long as they support SAML 2.0. Continue Reading…
In previous Expensify blog posts you may have heard us refer to WOW Fridays. Every Friday at Expensify, we allow our engineers the freedom to work on projects of their choosing, that aren’t necessarily part of our immediate product roadmap. We do this in order to allow them to exercise their creative freedom with the benefit that we end up with some really cool additions to the product. Well, the latest product of WOW Fridays is here: Continue Reading…
As we continue towards our major realtime expense reporting push, we are continuing to streamline the Expensify product. This started with simplifying our pricing structure and now involves changing the way report submission and approval works for those people using Expensify outside of an expense policy. When users submit reports outside of an expense policy, the reports are now moved to the “closed” state and shared with the person the report was submitted to. The recipient of the report still has the ability to approve the report by moving the report to a policy. Continue Reading…
One of the things we pride ourselves on at Expensify is flexibility. Our users have a very diverse set of needs and our goal is to find a simple solution that meets all of them. While the QuickBooks integration that we have built is great for most users, we realize that some people like an extra level of customization. This is why we are taking the time to let you know about this custom QuickBooks integration option.
QuickBooks is by far the most popular small business accounting software out there and is used by quite a few Expensify users. We wanted to take a moment to outline some best practices for the large constituency of QuickBooks accountants using Expensify.
Best practice #1: Export reports after reimbursing
If your company does reimbursement through Expensify, we recommend exporting reports after they have been reimbursed. This way the information that is reflected is most up-to-date and accurate. Otherwise, you will end up with a bunch of payables in QuickBooks that you will need to go in and manually reconcile.
Best practice #2: Remove any remnants of the Intuit App Center
Expensify used to offer the option to integrate with QuickBooks through the Intuit App Center. We recently discontinued this integration, so it is important to remove any remnants of this from your Expensify account. This includes deleting any secondary logins associated with the app center.
Best practice #3: Deleting and re-adding your connection
Whenever having problems with your QuickBooks connection in Expensify, the first thing to try is always to delete and re-add the connection. Sometimes the Intuit auth-token can timeout, causing the connection to break. In this scenario, simply deleting and re-adding the connection will fix the problem.
Additionally, in the case that there is a real problem, this allows us to identify and remedy any possible issues more quickly. When diagnosing issues in the integration, we need to start with a clean slate provided by readding the connection.
Best practice #4: Use customers/jobs for tags with billable expenses
If your company has billable expenses, you will want to use customers/jobs as tags. Expensify won’t be able to export billable expenses to QuickBooks unless there is a customer/job associated with each expense, so we recommend enabling customers/jobs as tags.
That’s it for today! As always, if you have any questions about anything QuickBooks related, please do shoot us an email at email@example.com.