We're currently experiencing a site outage. Please visit our status page for more details and to subscribe to updates.
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 our fund moving forward. Rest assured, we’ll review every report that’s submitted per our instructions.
Thanks for your patience!
Why Have Our QBO Coding Elections Suddenly Stopped Working?
We use Expensify integrations to both QBO and Accelo and both have been working as designed. Recently, we updated our project list from Accelo according to instructions and now all of our QBO coding elections AND our independent tagging from Accelo via spreadsheet import are no longer working.
Current QBO Coding options:
As you can see, we should have our COA mapped to Categories and we should see an option for Customers/Projects
Prior to tag update:
As you can see, the COA was mapping to our Categories and we had tagging for Customers/Project and an independent tag for Accelo projects.
Now, AFTER we updated our tagging items via regular spreadsheet import, we see this:
Categories have reverted to standard Expensify categories and we have no places to select Customers/Projects or Accelo project tags
Here is how our tags are configured:
Things we have tried:
Deleting and recreating independent tags
Disconnecting from and reconnecting to QBO (reconnections are successful with no errors - just no implementation of coding options selected in Connection)
It's literally as if Expensify has all of a sudden forgotten to integrate QBO and Accelo into expense tracking even through all of the settings call for them
Help is greatly appreciated.