Expensify.org/hunger SNAP campaign status

The number of families signing up for reimbursement has vastly outnumbered the limited funds available. Though we’re unable to provide a specific timeline on when your report will be reimbursed, we’re doing our best to drive donations and keep reimbursements moving forward. Rest assured, we’ll review every report that has been submitted per our instructions.

We're no longer accepting new participants as our focus is on reimbursing existing claims. Additionally, as of July 1, 2020, we will no longer accept new report submissions from existing policy members. Thanks for your understanding!

If you know anyone who can donate to this campaign please direct them to Expensify.org/donate.

We're currently experiencing issues with our American Express and Capital One connections. Please visit our status page for more details and to subscribe to updates.

FAQ - QuickBooks Desktop: The Wrong QuickBooks Company is Open

Brigid  BelloBrigid Bello Expensify Team Posts: 77 Expensify Team

This error indicates that you have the wrong company file is open in QuickBooks Desktop. To resolve, after taking the general troubleshooting steps outlined here, take the steps outlined in the error message:

  1. If you can see that the wrong company file is actually open in Quickbooks, go to QuickBooks and Select File > Open or Restore Company > [Company Name]. Once the correct company file is open, attempt to sync your policy again.
  2. If the correct company file is open and you're still getting this error, close out of QuickBooks Desktop completely, reopen the desired company file, then sync again. 

If you are still getting this error after taking the steps above, log into QuickBooks as an admin in single user mode, go to Edit > Preferences > Integrated Applications > Company Preferences, and remove the Expensify Sync Manager listed there. 

Next, try sync your policy again in Expensify. You'll be prompted to re-authorize the connection in QuickBooks, and this should allow you to sync successfully. 

If the error persists, double check that the token you see in the Sync Manager matches the token in your connection settings:

Sign In or Register to comment.