Merge branch 'main' into fix/add-reason-attributes-reimbursement-account-skeletons

Author: sosek108

Mobile-Expensify

@@ -111,8 +111,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009033400
-        versionName "9.3.34-0"
+        versionCode 1009033500
+        versionName "9.3.35-0"
         // Supported language variants must be declared here to avoid from being removed during the compilation.
         // This also helps us to not include unnecessary language variants in the APK.
         resConfigs "en", "es"

android/app/build.gradle

@@ -63,7 +63,7 @@ const webpack = {
 };
 
 const metro = {
-    presets: [require('@react-native/babel-preset')],
+    presets: [[require('@react-native/babel-preset'), {disableImportExportTransform: true}]],
     plugins: [
         ['babel-plugin-react-compiler', ReactCompilerConfig], // must run first!
 
@@ -174,5 +174,14 @@ module.exports = (api) => {
     const runningIn = api.caller((args = {}) => args.name);
     console.debug('  - running in: ', runningIn);
 
-    return ['metro', 'babel-jest'].includes(runningIn) ? metro : webpack;
+    // Jest runs in Node.js without Metro's experimentalImportSupport transform,
+    // so Babel must handle import/export transforms for tests.
+    if (runningIn === 'babel-jest') {
+        return {
+            ...metro,
+            presets: [[require('@react-native/babel-preset'), {disableImportExportTransform: false}]],
+        };
+    }
+
+    return runningIn === 'metro' ? metro : webpack;
 };

babel.config.js

@@ -9,3 +9,29 @@ Contributors are eligible to be paid via Expensify 18 months after they were ass
 - View [Receive Payments](https://help.expensify.com/articles/expensify-classic/bank-accounts-and-payments/payments/Receive-Payments) for details on receiving payments in the US and internationally, including via Wise (formerly TransferWise), Paypal, Venmo and more.  
 
 After approval it can take between 1 business day and a week, depending on the country and service you use.  
+
+## For issues with deposits
+If you're having an issue with the deposit, ie. a report gets _stuck_ in a state like Approved, start a chat with Concierge. Ask them to create a Github issue using [this template](https://github.com/Expensify/Expensify/issues/new?template=MISSING_REIMBURSEMENT_TEMPLATE.md). Provide as many details below as possible
+
+### Please provide the following details:
+> - Report ID:
+> - Reimbursement ID:
+> - Amount of reimbursement:
+> - Date reimbursement was initiated:
+> - Date reimbursement was expected:
+> - Last 4-digits of the deposit account:
+> 
+> ### Is the missing reimbursement international (CAD > CAD, USD > GBP, etc.) or domestic?
+> 
+> ### If this is an international reimbursement, please provide the following details
+> - Location of reimbursement account (AUD, CAD, GBP, EUR, USD)
+> - Location/currency of deposit account
+> 
+> ### Have you received reimbursements to the connected deposit account successfully in the past?
+> - Yes or No
+> 
+> ### Please select which option best describes the scenario:
+> - The recipient connected a deposit account that was closed
+> - The recipient entered the bank details incorrectly when connecting their deposit account
+> - The recipient entered the correct bank details, but the reimbursement is still missing
+> - Something else (please describe below)

contributingGuides/PAYMENT_VIA_EXPENSIFY.md

@@ -73,7 +73,7 @@ This is a signed document authorizing a client’s bank to pull payments via dir
 Once the bank account is approved for global reimbursement:
 1. Go to **Settings > Workspaces > [Workspace Name] > Workflows**.
 2. Scroll to **Make or track payments**.
-3. Choose your verified EU account as the default reimbursement method.
+3. Choose your verified UK/GBP account as the default reimbursement method.
 4. Instruct employees to connect their deposit account:
    - Go to **Settings > Account > Wallet**.
    - Click **Add deposit-only bank account** and input their account details.

docs/articles/expensify-classic/bank-accounts-and-payments/payments/Global-Reimbursement-UK.md

@@ -42,7 +42,7 @@ You can reimburse submitted and approved reports in Expensify using direct depos
 For international bank transfers.
 
 ## Setup requirements
-- A Workspace Admin must [enable global reimbursements](https://help.expensify.com/articles/expensify-classic/bank-accounts-and-payments/bank-accounts/Enable-Global-Reimbursements).
+- A Workspace Admin must [enable global reimbursements](https://help.expensify.com/articles/expensify-classic/bank-accounts-and-payments/payments/Enable-Global-Reimbursement).
 - Recipients must [connect a deposit account](https://help.expensify.com/articles/expensify-classic/bank-accounts-and-payments/bank-accounts/Connect-Personal-US-Bank-Account).
 
 > Only verified business accounts can send global reimbursements.

docs/articles/expensify-classic/bank-accounts-and-payments/payments/Reimburse-Reports.md

@@ -0,0 +1,66 @@
+---
+title: CER937 Error in Certinia Integration
+description: Learn what the CER937 error means in Certinia and how to update the Expensify integration configuration to restore syncing.
+keywords: CER937, Certinia export error, update Expensify in Certinia, Certinia connection issue, Expensify Certinia sync error, Workspace Admin
+internalScope: Audience is Workspace Admins and Certinia Admins using the Certinia integration. Covers resolving the CER937 error caused by an outdated Certinia integration configuration. Does not cover other Certinia error codes.
+---
+
+# CER937 Error in Certinia Integration
+
+If you see the error:
+
+CER937: Please update Expensify in Certinia.
+
+This means Certinia has detected that the Expensify integration configuration is outdated and must be updated before exports or syncs can proceed.
+
+---
+
+## Why the CER937 Error Happens in Certinia
+
+The CER937 error typically indicates:
+
+- A newer version of the Expensify integration is available in Certinia.
+- The existing integration configuration has not been updated.
+- Certinia is blocking exports until the integration version is aligned.
+
+This is a Certinia configuration issue, not a Workspace configuration issue.
+
+---
+
+## How to Fix the CER937 Error
+
+This issue must be resolved in Certinia.
+
+1. Log in to Certinia as an administrator.
+2. Locate the **Expensify Integration** configuration.
+3. Select the option to **Update** the integration.
+4. Follow any prompts to upgrade, reinstall, or refresh metadata.
+5. Confirm API credentials or OAuth tokens if prompted.
+6. Save your changes.
+
+If you do not see an update option, contact your Certinia administrator or Certinia support to confirm access to the latest integration release.
+
+After updating Certinia:
+
+1. Go to **Settings > Workspaces**.
+2. Select your Workspace.
+3. Click **Accounting**.
+4. Click **Sync Now**.
+
+Then retry exporting the report.
+
+---
+
+# FAQ
+
+## Can I Retry the Export?
+
+You can attempt to retry the export after updating the integration and selecting **Sync Now**. If the error persists, confirm the integration version in Certinia is current.
+
+## Does CER937 Mean My Data Is Lost?
+
+No. The report remains in Expensify. The export is simply blocked until the Certinia integration is updated.
+
+## Is CER937 Caused by Workspace Settings?
+
+No. CER937 is triggered when Certinia requires an integration update. Workspace accounting settings are not the cause.

docs/articles/expensify-classic/connections/certinia/Troubleshooting/Authentication-and-Login-errors/CER937-Error.md

@@ -0,0 +1,125 @@
+---
+title: Certinia Integration FAQ and Export Troubleshooting
+description: Learn why reports may not export to Certinia, how to manually export, fix company card export issues, manage project limitations, and disconnect the Certinia integration.
+keywords: Certinia export not working, automatic export failed, manual export Certinia, company card wrong account export, preferred exporter domain admin, disconnect Certinia, Certinia project status export limitation, assignment status export, Workspace Admin
+internalScope: Audience is Workspace Admins and Domain Admins using the Certinia integration. Covers common export failures, manual export restrictions, company card export mapping, project limitations, and disconnecting Certinia. Does not cover specific Certinia error codes.
+---
+
+# Certinia FAQ 
+
+## Why is my report not automatically exporting to Certinia?
+
+An error is preventing the report from exporting automatically.
+
+You can find the error in several ways:
+
+- The **preferred exporter** (as configured in Expensify) receives an email with error details.
+- The error appears in the report’s comments section.
+- Automatic exports will continue to fail until the error is resolved.
+
+### How to resolve automatic export failures
+
+1. Open the affected report in Expensify.
+2. Review the error message in the comments section.
+3. Make the required corrections.
+4. Have a Workspace Admin manually export the report.
+
+---
+
+## Why am I unable to manually export a report to Certinia?
+
+Only reports in **Approved**, **Done**, or **Paid** status can be exported.
+
+If the report is in **Draft** status, selecting export may result in an empty screen.
+
+### How to resolve manual export issues
+
+1. Submit the report if it is in Draft status.
+2. Have an approver approve the report if it is Outstanding.
+3. Once the report is Approved, Done, or Paid, a Workspace Admin can manually export it.
+
+---
+
+## Why are company card expenses exporting to the wrong account?
+
+Company card expenses may export to the wrong account if the card export mapping is incorrect or if the exporter does not have proper permissions.
+
+### How to verify company card export mapping
+
+1. Go to the navigation tabs on the left.
+2. Click **Settings**.
+3. Click **Domains**.
+4. Select **Company Cards**.
+5. Click **Edit Export** for the affected card.
+6. Confirm the correct export account is selected.
+
+Also confirm:
+
+- The expenses display the **Card + Lock icon**, which ensures they are mapped correctly.
+- The preferred exporter is a **Domain Admin**.
+
+If the preferred exporter is not a Domain Admin, exports will default to the fallback company card account set in the Workspace configuration.
+
+### How to check the preferred exporter
+
+1. Go to the navigation tabs on the left.
+2. Click **Workspaces**.
+3. Select your Workspace.
+4. Click **Accounting**.
+5. Click **Configure**.
+6. Review the **Export** settings.
+
+---
+
+## How do I disconnect the Certinia connection?
+
+Disconnecting removes the active integration and clears imported options.
+
+### How to disconnect Certinia
+
+1. Go to the navigation tabs on the left.
+2. Click **Settings**.
+3. Click **Workspaces**.
+4. Select your Workspace.
+5. Click **Accounting**.
+6. Click the gray **Disconnect** button under the Certinia connection.
+7. Confirm to disconnect.
+
+Note: Disconnecting clears all imported options from Expensify.
+
+---
+
+## Are there export limitations based on projects in Certinia?
+
+Yes. Project settings in Certinia can prevent expenses from exporting.
+
+### Expenses can be exported when:
+
+- **Project Status** = Active or In Progress
+- **Assignment Status** = Closed, Active, or Completed
+- **Closed for Expense Entry** = Unchecked
+
+### Expenses cannot be exported when:
+
+- **Project Status** = Closed
+- **Closed for Expense Entry** = Checked
+
+### How to resolve project export limitations
+
+1. Check the Project Status in Salesforce.
+   - If Project Status is Closed, expenses cannot be entered or exported.
+   - If Active or In Progress, continue to step 2.
+2. Verify the **Closed for Expense Entry** setting.
+   - If checked, uncheck it to allow expense exports.
+3. Manually test expense entry in Salesforce.
+   - If manual entry works, the Expensify–Certinia integration should also allow export.
+
+---
+
+## Does assignment status affect expense exports?
+
+No.
+
+Assignment Status in Certinia (Closed, Active, or Completed) does not impact expense entry or export.
+
+Only Project Status and the Closed for Expense Entry setting affect export eligibility.

docs/articles/expensify-classic/connections/certinia/Troubleshooting/Certinia-FAQ.md

@@ -0,0 +1,64 @@
+---
+title: CER047 Error in Certinia Integration
+description: Learn what the CER047 error means in Certinia and how to enable the Expense Ops Edit permission to restore syncing.
+keywords: CER047, Certinia export error, Ops Edit permission, Expense Ops Edit, approved records permission error, Expensify Certinia sync error, Workspace Admin
+internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER047 error caused by missing Expense Ops Edit permissions. Does not cover other Certinia error codes.
+---
+
+# CER047 Error in Certinia Integration
+
+If you see the error:
+
+CER047: "Ops Edit" permission is required to edit approved records.
+
+This means the Certinia integration user does not have permission to edit approved expense records, preventing the export from completing.
+
+---
+
+## Why the CER047 Error Happens in Certinia
+
+The CER047 error typically indicates:
+
+- The connected Certinia integration user lacks the **Expense Ops Edit** permission.
+- Certinia requires permission to modify approved records during export processing.
+- The export is blocked due to missing permissions.
+
+This is a Certinia permission configuration issue, not a Workspace configuration issue.
+
+---
+
+## How to Fix the CER047 Error
+
+This issue must be resolved in Certinia.
+
+1. Log in to Certinia.
+2. Go to **Permission Controls**.
+3. Select the permission set assigned to the integration user.
+4. Locate **Expense Ops Edit**.
+5. Enable the permission.
+6. Save your changes.
+
+After updating permissions:
+
+1. Go to **Settings > Workspaces**.
+2. Select your Workspace.
+3. Click **Accounting**.
+4. Click **Sync Now**.
+
+Then retry exporting the report.
+
+---
+
+# FAQ
+
+## Can I Retry the Export?
+
+Yes. After enabling **Expense Ops Edit** and selecting **Sync Now**, retry the export. If the error persists, confirm the permission is applied to the exact user connected to the integration.
+
+## Does CER047 Mean My Expense Was Deleted?
+
+No. The report remains in Expensify. The export was blocked due to missing permissions.
+
+## Is CER047 Caused by Workspace Settings?
+
+No. CER047 is triggered by missing permissions in Certinia. Workspace accounting settings are not the cause.