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-10-05] Payment issue for E/App PR#101646 #102455
@Ollyws The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other: New feature
Where bug was reported:
2a. Reported on production
2b. Reported on staging (deploy blocker)
2c. Reported on both staging and production
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A new feature
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
1. Open an expense report reimbursed through ACH whose expected deposit date has passed.
2. Locate the payment action in the report history.
3. Verify the payment action shows the expected completion date.
4. Open an older ACH-reimbursed report whose PAY action does not contain expectedDate but whose hidden REIMBURSED action does.
5. Verify the payment action still shows the expected completion date.
6. Open a report paid elsewhere or with a wallet.
7. Verify no reimbursement ETA is appended.
Activity
melvin-bot commentedon Sep 28, 2026
@Ollyws The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Oct 1, 2026
@Ollyws Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Oct 4, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 4, 2026
Payment Summary
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 6, 2026
Payment Summary
Contributor+: @Ollyws due $175 via NewDot
@Ollyws plz complete the Contributor+ checklist and tag me in a post once you have. Thx
melvin-bot commentedon Oct 12, 2026
@mallenexpensify Huh... This is 4 days overdue. Who can take care of this?
Ollyws commentedon Oct 13, 2026
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A new feature
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/691391
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-05af-abbc-c3eb-2343fee5ebb4Ollyws commentedon Oct 13, 2026
@mallenexpensify checklist done and payment requested.
flaviadefaria commentedon Oct 16, 2026
Approved: @Ollyws due $175 via NewDot