[$250] Adding bank account to receive invoice payment is confusing

[m-natarajan]

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.66-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation (hyperlinked to channel name): Expensify-billpay

Action Performed:

1. Go to staging.new.expensify.com
2. Create a workspace if needed
3. Go to More features, scroll down and enable Invoices
4. Click green plus, Send invoice
5. [User A] Send an invoice to User B
6. [User B] Go to invoice chat and pay the invoice as business
7. [User A] Go to invoice report
8. [User A] Click Add bank account
9. [User A] Note that the button leads to Invoices on workspace settings
10. [User A] Click Add bank account and add a bank account
11. [User A] Go back to workspace chat

Expected Result:

After adding a bank account for the invoice report the user should be navigated back to it, and the add bank account button should be gone. We could potentially have a system message saying that they added a bank account to receive the invoice payment.
Also, maybe instead of directing the the workspace settings after clicking add bank account, we should instead have an informational page at the end of the flow in the RHP that explains the account has been added as the invoice transfer bank account.

Actual Result:

The add bank account button on the invoice report navigates to settings, then after adding it you land back on the settings page and have to manually navigate back to the invoice report. Additionally, the add bank account button will remain present until you go to invoicing settings, click on the overflow menu of the bank account, and make it the default payment method.

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 evidence

InvoiceConfusing2024-11-22_14-31-39.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021863586879380659008
• Upwork Job ID: 1863586879380659008
• Last Price Increase: 2024-12-02

[melvin-bot]

Triggered auto assignment to @johncschuster (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]

Triggered auto assignment to @arosiclair (AutoAssignerNewDotQuality)

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[abzokhattab]

I think this is a dupe of #50474

[arosiclair]

Unassigning since this isn't a quality issue

[johncschuster]

Agreed. I think this fits into #expense better. I also think this behavior is expected. I've raised a discussion here to chat about it.

[johncschuster]

Discussion is ongoing

[johncschuster]

Not much chatter in Slack on this one. I've pinged my pal, @garrettmknight to chime in as the project curator 👍

[johncschuster]

Ok! It sounds like we all agree that the expected behavior outlined here is the behavior we want (i.e. when a user gets routed to add a bank account from an invoice, they should be brought back to the invoice after adding the bank account).

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021863586879380659008

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

[abzokhattab]

is this a different issue from this #50474?

[johncschuster]

Good shout, @abzokhattab! It does sound like these issues are pretty similar. @neil-marcellini, what do you think?

[neil-marcellini]

Woops yes I think these are the same thing, it was probably a mistake of mine to create a separate issue. I will close this in favor of the original issue and bring any information from here over there.