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
{{ message }}
Repository navigation
[Due for payment 2026-09-28] Add Auto report option when moving expenses for multiple employees (to existing options New report + existing report) #87954
Feature Request: Mirror Classic reconciliation auto-report functionality for statements
Problem
When reconciling unreported expenses in New Expensify, we currently can only create reports on the admin's default workspace. This doesn't match Classic behavior and forces admins to revert to Classic for reconciliation workflows.
Specifically, New Expensify is missing:
Auto-report option — Classic allows adding unreported transactions to the appropriate existing report (the last report created by the user) with a single click, even across multiple employees at once
Correct workspace targeting — Classic creates reports on the card's preferred workspace if the cardholder is a member, falling back to the cardholder's default workspace. New Expensify incorrectly uses the admin's default workspace
Existing draft report visibility — Cardholders' existing draft reports should appear in the report selection list
Expected Behavior (Classic)
When reconciling unreported expenses, the dropdown provides:
Auto-report: Add to the last report created by the user (supports bulk operations across 100+ employees)
New report: Create a new report using the card's preferred workspace (if cardholder is a member) or the cardholder's default workspace
Specific reports: List of all open/processing reports belonging to the cardholder
Current Behavior (New Expensify)
Reports are created on the admin's default workspace, which is often not the workspace the cardholder should submit on. Draft reports are not shown.
They find it very useful. They can more easily find the unreported transactions because we separate "Unapproved" into "Unreported, Draft and Outstanding" which can be selected individually. Their problem is that they as admins can't do anything about them in the way they can from Classic.
Gotcha, so my read on that is that the fundamental problem is that they are looking for unreported transactions. I think it's fine if we do this, but I do feel that it's not the "best practice." We should just make it super easy to flag and find unreported transactions. Because that should never happen. It's an oddity of Expensify that it happens in the first place.
I see the recently deployed PR supports the multi-submitter workflow. Is there another PR coming to make sure that the option to select an existing Draft report is available when selecting multiple expenses from the same submitter? I'm working with a customer who only sees the option to create a new report when selecting multiple unreported card expenses
Sorry for the delay. I just missed the initial notification.
@greg-schroeder I tried to reproduce this and couldn't, In my test an admin selects several unreported card expenses from one cardholder, and that cardholder's draft report does show up next to "Create report"
bug.mov
Could you check a few things on the customer's side?
Did they also see an Auto report row, or only Create report? A screenshot would help.
Is the cardholder's draft report on a workspace the admin belongs to? We only list reports from the admin's own workspaces.
Activity
melvin-bot commentedon Apr 15, 2026
Triggered auto assignment to Design team member for new feature review - @shawnborton (
NewFeature)melvin-bot commentedon Apr 15, 2026
Triggered auto assignment to @dannymcclain (
Design), see these Stack Overflow questions for more details.shawnborton commentedon Apr 15, 2026
Anything needed from (double) Design here?!
twisterdotcom commentedon Apr 15, 2026
I think we just need to understand how we show "Auto-report" here:
To match the Classic options we see:
shawnborton commentedon Apr 15, 2026
We do have that same icon available to us for NewDot, so we could quite literally do the same thing here (add a separate row for Auto-Report).
JmillsExpensify commentedon Apr 15, 2026
Totally fine with us doing this, though just for my clarity, @twisterdotcom did they not find the updated reconciliation report on ND useful?
twisterdotcom commentedon Apr 16, 2026
They find it very useful. They can more easily find the unreported transactions because we separate "Unapproved" into "Unreported, Draft and Outstanding" which can be selected individually. Their problem is that they as admins can't do anything about them in the way they can from Classic.
JmillsExpensify commentedon Apr 16, 2026
Gotcha, so my read on that is that the fundamental problem is that they are looking for unreported transactions. I think it's fine if we do this, but I do feel that it's not the "best practice." We should just make it super easy to flag and find unreported transactions. Because that should never happen. It's an oddity of Expensify that it happens in the first place.
103 remaining items
twisterdotcom commentedon Oct 5, 2026
I think given this was part of the problem idenfitied early, we need to fix that here too. Here: #87954 (comment)
@heyjennahay said:
daledah commentedon Oct 8, 2026
Sorry for the delay. I just missed the initial notification.
@greg-schroeder I tried to reproduce this and couldn't, In my test an admin selects several unreported card expenses from one cardholder, and that cardholder's draft report does show up next to "Create report"
bug.mov
Could you check a few things on the customer's side?
Auto reportrow, or onlyCreate report? A screenshot would help.melvin-bot commentedon Oct 8, 2026
@mkhutornyi Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Oct 12, 2026
@mkhutornyi 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
twisterdotcom commentedon Oct 13, 2026
@greg-schroeder any screenshots, even redacted could help here I think.
mkhutornyi commentedon Oct 14, 2026
Awaiting response from @greg-schroeder
melvin-bot commentedon Oct 19, 2026
@mkhutornyi Huh... This is 4 days overdue. Who can take care of this?
daledah commentedon Oct 21, 2026
friendly bump @greg-schroeder
melvin-bot commentedon Oct 21, 2026
@mkhutornyi Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Oct 23, 2026
@mkhutornyi Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!