Expensify
[$250] Expense - Tag field is not replaced with Project when connecting to Intacct and Remains on Expense.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: V9.2.66-3 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/search?q=3741 Email or phone of affected tester (no customers): [email protected] Issue reported by: Applause Internal Team Device used: Redminote 10S Android 13 App Component: Money Requests
Action Performed:
- Launch app
- Create a workspace
- Enable accounting and connect to sage intact
- Create another workspace
- Enable tags and add a tag
- Open workspace chat
- Create an expense with tag
- Go to workspace settings - enable accounting
- Connect to existing sage intact connection
- Open workspace chat
- Open the expense details
Expected Result:
Tag field is removed, and replaced with Projects. The selected tag is listed as an out of workspace Project
Actual Result:
The expense contains both a Project field and Tag field, which is incorrect. More detail in comment here
Workaround:
Unknown
Platforms:
- [x] Android: App
- [x] Android: mWeb Chrome
- [ ] iOS: App
- [ ] iOS: mWeb Safari
- [ ] iOS: mWeb Chrome
- [x] Windows: Chrome
- [ ] MacOS: Chrome / Safari
- [ ] MacOS: Desktop
Screenshots/Videos
https://github.com/user-attachments/assets/4b40c0c7-a014-43de-b2fc-c597641bf0f6
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021997850488460226735
- Upwork Job ID: 1997850488460226735
- Last Price Increase: 2025-12-15
Issue Owner
Current Issue Owner: @eVoloshchak
Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
![melvin-bot[bot] avatar](https://avatars.githubusercontent.com/in/179547?v=4 "Published by a pub.dev verified publisher"){kind=small}
So there is an issue here, but the Expected Result is a bit off. When connecting to Sage Intacct (or any other accounting integration) we should remove the Tag line, as it would be replaced by Classes, Customers, Projects, Departments, Locations, etc (whatever the customer decides to import in from Sage Intacct). The default "tag" option should not be listed, and instead be replaced by one of those options as it is a requirement that when you connect to an accounting integration – categories and tags are imported into Expensify from that accounting integration.
So, the idea of the incorrect tag, "Fer" being listed as an incorrect Project is fine, but the Tag field on the expense needs to be removed.
Does that make sense @vincdargento? I wanted to make sure that we clear before I edited the main comment on the GH
Job added to Upwork: https://www.upwork.com/jobs/~021997850488460226735
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)
@eVoloshchak — I wonder if that change would potentially require a BE change due to the nature of the fields. Interested to hear your thoughts as I am not 100% sure on whether a BE or FE fix would be best.
Hey team! I am heading OoO until Dec. 17. If you need anything from a BZ perspective, please reach out in Slack, otherwise I will get it sorted as soon as I am back! Thanks!
@eVoloshchak Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@eVoloshchak @CortneyOfstad this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
@eVoloshchak 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
I wonder if that change would potentially require a BE change due to the nature of the fields.
@CortneyOfstad, this will require a BE fix. Not fully sure whether an FE one will be needed (but most probably yes, I wonder if external contributors can connect to sage intact)
@eVoloshchak Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@eVoloshchak 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
I think this is the expected behavior.
- https://github.com/Expensify/Expensify/issues/71274
- https://github.com/Expensify/Integration-Server/pull/4422
- https://github.com/Expensify/Integration-Server/blob/e6a06fcdfaf3768c0a9170c9bff3b46d766be910/src/expensify/policy/PolicyUtils.java#L226
cc @nkuoch @francoisl
@francoisl can you confirm if the workspace tag should still be listed when connected to an accounting integration? I was under the impression that:
If employee selects a workspace tag ("Entertainment") on an expense and later connects to an accounting integration ("QBO") and selects the option to import Classes as tags, the Tag field should be renamed to Classes but still show the original workspace selection ("Entertainment") but list it as a violation.
Is that logic not the case anymore? Here is my original comment showing an example: https://github.com/Expensify/App/issues/76448#issuecomment-3612406594
After reading https://github.com/Expensify/Expensify/issues/57982 and https://github.com/Expensify/Expensify/issues/71274, it seems like the current behavior is correct. When you connect to an accounting solution, we need to keep your existing tag lists, and prepend the integration tag lists into your policy.
It sounds like we can close this issue, but we might also need to update the test case linked in the OP so it's not considered a bug again in the future.
