[Payment 2025-01-02] List of card-level export accounts are not displayed when using Intacct and vendor bills

[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:
Reproducible in staging?:
Reproducible in production?:
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: @joekaufmanexpensify
Slack conversation (hyperlinked to channel name): expense

Action Performed:

Prerequisite: User added a company card

1. Navigate to company card
2. Click the added cards to view the details page
3. Click on export options and select Intacct

Expected Result:

List of card-level export accounts when using Intacct and vendor bills

Actual Result:

List of card-level export accounts are not displayed when using Intacct and vendor bills

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

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot]

Triggered auto assignment to @strepanier03 (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.

[narefyev91]

Hi, I’m Nicolay from Callstack and I would like to investigate this issue.

[dukenv0307]

@strepanier03 I'm working on WS Feed project so I can help take it as C+

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.78-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [Internal QA]: Fixes for Sage connection and Xero #54411

If no regressions arise, payment will be issued on 2025-01-02. 🎊

For reference, here are some details about the assignees on this issue:

• @narefyev91 does not require payment (Contractor)
• @dukenv0307 requires payment through NewDot Manual Requests

[melvin-bot]

@dukenv0307 @strepanier03 @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]

[mountiny]

@dukenv0307 can you please complete the checklist and then we can close this to handle the payments

[melvin-bot]

Payment Summary

Upwork Job

• Contributor: @narefyev91 is from an agency-contributor and not due payment
• Reviewer: @dukenv0307 owed $250 via NewDot

BugZero Checklist (@strepanier03)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[strepanier03]

@dukenv0307 - Bump on the checklist here, thanks! I'll check this again on Monday.

[dukenv0307]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production
• 2b. Reported on staging (deploy blocker)
• 2c. 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:

• [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: N/A

• [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. Yes

Regression Test Proposal Template

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Test:

• Prerequisite: User added a company card

1. Navigate to company card
2. Click the added cards to view the details page
3. Click on export options and select Intacct
4. Verify that user sees list of available intacct accounts

Do we agree 👍 or 👎

[dukenv0307]

@strepanier03 I completed the checklists

[strepanier03]

Payment Summary

• $0 - @dukenv0307 via New Expensify (paid later as part of the project)
• $0 - @narefyev91 (agency)

[strepanier03]

All right, @dukenv0307 - I've created the reg test GH and the payment summary is here.

You can request payment and I'm going to close this as complete.

[dukenv0307]

@strepanier03 I shouldn't be getting paid here, it belongs to WS feed project so will be paid later cc @mountiny

[mountiny]

updated