Skip to content

[$175] Web - Spend - No Withdrawal ID after paid the report with Bussiness bank account #105215

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.24-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #104671
Email or phone of affected tester (no customers): leungbratt6+2210@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11/Chrome
App Component: Left Hand Navigation (LHN)

Action Performed:

Preconditions: The user has a Workspace with a Business Band Account and a Personal BA to withdraw

  1. Open the New Dot app
  2. Navigate to an approved report in Workspace chat
  3. Pay it with the Business Band Account
  4. Go to the Spend tab - Reports -Column - Select Withdrawal ID

Expected Result:

A Withdrawal ID appears in the paid report

Actual Result:

Blank at the Withdrawal ID (recheck the same paid report after 12hours, still blank)

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7298423_1793148344541.104671.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Chandana Kiran
Bug ID: 7298423

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @c3024

Activity

  1. applause-bot commented on Oct 28, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/4eb429b1d2975881dd787659882fea0de2039ed24d64b51198e82bb24e829e8f

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 28, 2026
  3. MelvinBot commented on Oct 28, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The App shows exactly what Search returns, and Search did not return a withdrawal ID for this report. This appears to be a backend/internal issue. A separate internal investigation is needed.

    The column only renders the report's withdrawalIDs field from the Search results. Nothing in the App sets that field, including the pay flow. The field is defined as the report's settled withdrawal IDs. An ACH payment from a business bank account may still be unsettled 12 hours later, so the blank cell may be expected behavior rather than a bug.

    Code evidence

    I couldn't check production logs in this run, so I haven't confirmed whether this withdrawal was created or settled.

    What changes do you think we should make in order to solve the problem?

    No App change is needed. An internal engineer should check this tester's paid report (leungbratt6+2210@gmail.com):

    1. If the withdrawal is still unsettled, this is expected. Recheck after it settles, and consider clarifying the QA steps in Add the Withdrawal ID custom column to expense report searches to say the ID appears only after settlement.
    2. If the withdrawal is settled and Search still omits withdrawalIDs, the fix is on the backend, outside the App repo.

    Related: [Due for payment 2026-11-03] [CFI] Add the Withdrawal ID custom column to expense report searches is the feature issue for this column.


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/105215) to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.


    view run

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 28, 2026
  5. melvin-bot commented on Oct 28, 2026

    @melvin-bot

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

  6. changed the title [-]Web - Spend - No Withdrawal ID after paid the report with Bussiness bank account[/-] [+][$175] Web - Spend - No Withdrawal ID after paid the report with Bussiness bank account[/+] on Oct 28, 2026
  7. melvin-bot commented on Oct 28, 2026

    @melvin-bot
  8. j3ffffff commented on Oct 28, 2026

    @j3ffffff
  9. camesenin commented on Oct 28, 2026

    @camesenin
  10. melvin-bot commented on Oct 28, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  11. hardik4love-lang commented on Oct 28, 2026

    @hardik4love-lang

    Proposal

    What is the root cause of that problem?

    In src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/ExpenseReportListItemRowWide.tsx (lines 272–274), the "Withdrawal ID" column renders item.withdrawalIDs directly from the Search index.
    When an expense report is settled via an ACH business bank account transfer, ACH clearance typically takes 1 to 3 business days. Until the transaction settlements are fully processed and confirmed on the server side, the backend Search response leaves withdrawalIDs empty/null.
    Because the frontend currently renders a blank cell without any visual distinction between an unsettled/pending payment vs a report with no payment attached, users and QA perceive this as a missing field / UI bug.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/ExpenseReportListItemRowWide.tsx:

      • If item.withdrawalIDs is populated, render the withdrawal ID string as usual.
      • If item.withdrawalIDs is null/empty but the report has an active pending settlement state (e.g., report.statusNum === CONST.REPORT.STATUS_NUM.PROCESSING or report.isWaitingOnBank), render a fallback pending indicator or localized message (e.g. translate('search.pendingSettlement') or dash/placeholder rather than an empty blank space) so users know the settlement is in flight.
    2. In src/libs/SearchUIUtils.ts:

      • Add a helper function or check isReportPaymentPending(report) that inspects the report state so the cell renderer accurately reflects unsettled ACH transfers without throwing or failing regression checks.

    What alternative solutions did you explore? (Optional)

    • Doing nothing / closing as expected behavior: Rejected because a blank cell gives no feedback to the user on whether the payment was dispatched or failed.
    • Fabricating or optimistically predicting a withdrawal ID on the client: Rejected because ACH withdrawal IDs are generated strictly by the server banking processor upon settlement confirmation.

    What automated tests can you add to prevent this from re-occurring?

    • Add unit test coverage in tests/unit/SearchUIUtilsTest.ts verifying that expense reports with pending bank payment status display the expected pending state before withdrawalIDs are received from the server.

    Contributor details
    Your Expensify account email: hardik4love@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~01ae8e58df76cb90f5

  12. melvin-bot commented on Oct 28, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  13. trjExpensify commented on Oct 28, 2026

    @trjExpensify
    Contributor

    @c3024 @JS00001 as this is within the regression period: #104139

  14. JS00001 commented on Oct 28, 2026

    @JS00001
    Contributor

    assigning kc as well to take a look

  15. c3024 commented on Oct 29, 2026

    @c3024
    Contributor

    I don’t think this is a bug. The report was paid from a Plaid test bank account, and Auth doesn’t create a reimbursement for those (found “Cannot reimburse from Plaid test bank account” in VictoriaLogs for their request), so there’s no withdrawal to show. On staging, report withdrawal IDs only appear for reports with settled Expensify Card expenses. Paying with a test bank account won’t produce one.

  16. trjExpensify commented on Oct 29, 2026

    @trjExpensify
    Contributor

    Cool, let's close it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions