Expensify.org/hunger SNAP campaign status
We’re no longer accepting new participants as our focus is on reimbursing existing claims. While 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. If you know anyone who can donate to this campaign please encourage them to enable Personal or Corporate Karma on their Expensify account.
NetSuite and "Edit Multiple" Tagging Questions
We have successfully imported the Classifications tag from NetSuite to one of our policies, but have a few issues with the results:
1) When we go to the Expenses tab (as opposed to the Report tab) it looks like we are only able to "Edit Multiple" expenses that are either "Open" or "Processing"--does this mean employees cannot "Edit Multiple" Unreported expenses to add a tag to all of them at one time?
2) Also on the Expense tab, when we select all expenses and then select "Edit Multiple" for Open or Processing expenses, our new tags ("Policy A Tags") are not available, and only tags from an unrelated policy ("Policy B Tags") are available. Based on our Policy A Tag settings, the Policy B Tags have not been synced and only the Policy A Tags should be showing up. Additionally, these Policy B Tags are a portion of some of the tags from that list so it seems like this may be a glitch? The categories that are available are for the correct Policy A, so it seems odd that the tags are incorrect and for Policy B. Naturally, we would like to delete these Policy B Tags from being an option on our Policy A expenses.
3) Continuing with the situation from #2, is there a way to make our Policy A tags available from this menu (Expense tab -> Select all Expenses -> Edit Multiple)? While our new tags do become available if you select an individual expense or go to the report level and edit from there, why are they not available from the "Edit Multiple" on the Expense tab referenced in #2 above? We don't want our staff to have to tag each expense individually, and staff members will need to apply two different tags to a bulk number of items so the "auto/default" tagging wouldn't work here.