You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Number: 9.0.99.0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.new.expensify.com
Create a Workspace
Go to Workspace Settings
Enable Per Diem via More Features
Go to Per Diem and import a CSV containing two currencies for the same country (Use attached CSV)
Complete importing Per Diem
Expected Result:
The imported per diem entries matches the country and currency pairs from the CSV
Actual Result:
The imported per diem entries for one of the countries uses USD on all entries even thought there should be only one USD entry in the CSV
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6745957_1739813447412.Recording__154.mp4
The system assigns one currency per country, using the first entry’s currency (e.g., USD for Afghanistan).
Subsequent entries for the same country ignore their currency field (e.g., EUR rows for Afghanistan are overridden).
Changing the first entry’s currency (e.g., USD → EUR) updates the FE display for the entire country.
This appears intentional. Could you confirm this is the desired logic with the team?
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: 9.0.99.0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The imported per diem entries matches the country and currency pairs from the CSV
Actual Result:
The imported per diem entries for one of the countries uses USD on all entries even thought there should be only one USD entry in the CSV
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6745957_1739813447412.Recording__154.mp4
1_german_per_diem_-dependent_tags___2.csv
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: