[Due for payment 2026-03-30] [CFI] [$250] Members Import (CSV): Add Custom Field 1 and 2, Approval Limit, and Over Limit Forward To mapping options (parity with Classic)

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.25-13
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Go to Workspace → Members in New Expensify
2. Select Import from spreadsheet
3. Upload a CSV file
4. Observe the column mapping dropdown options

Expected Result:

The column mapping dropdown should include the ability to map:
Custom Field 1
Custom Field 2
Approval Limit
Over Limit Forward To
This should match the functionality available in Expensify Classic.

Actual Result:

These fields are not available in the mapping dropdown.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Recording.2424.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022026418367145798809
• Upwork Job ID: 2026418367145798809
• Last Price Increase: 2026-02-24

EXFY-20174

[melvin-bot]

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

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When importing workspace members via CSV (Workspace → Members → Import from spreadsheet), the column mapping dropdown only offers 4 usable mapping options: Email, Role, Submit To, and Forward To. It is missing 4 fields that exist in Expensify Classic: Custom Field 1, Custom Field 2, Approval Limit, and Over Limit Forward To.

What is the root cause of that problem?

The columnRoles array in ImportedMembersPage.tsx:42-48 hardcodes only 5 options (Ignore, Email, Role, Submit To, Forward To). The 4 missing fields were never wired into this list, even though the infrastructure for them already exists:

• CONST.CSV_IMPORT_COLUMNS already defines CUSTOM_FIELD_1, CUSTOM_FIELD_2, REPORT_THRESHHOLD, and APPROVE_TO_ALTERNATE constants (CONST/index.ts:7949-7953)
• The ImportColumn component already auto-detects CSV headers like "customfield1", "payrollid", "approvallimit", "overlimitforwardsto" (ImportColumn.tsx:57-88)
• The PolicyEmployee type already has employeeUserID (Custom Field 1), employeePayrollID (Custom Field 2), approvalLimit, and overLimitForwardsTo fields (PolicyEmployee.ts:8-38)
• Custom fields are already editable on the member details page for Control policies (WorkspaceMemberDetailsPage.tsx:353-372)

The gap is that these constants, types, and auto-detection logic were never connected to the member import column mapping UI, the import parsing logic, or the IMPORT_MEMBERS_SPREADSHEET API call.

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

1. Add the 4 missing column roles to the columnRoles array in ImportedMembersPage.tsx — add entries for CUSTOM_FIELD_1, CUSTOM_FIELD_2, REPORT_THRESHHOLD, and APPROVE_TO_ALTERNATE using appropriate translation keys (existing keys for custom fields, new keys needed for "Approval limit" and "Over limit forward to").

2. Extend the import parsing logic in the importMembers callback of ImportedMembersPage.tsx — extract the 4 new column types from the spreadsheet data and include them in the member objects passed to importPolicyMembers.

3. Update the ImportedSpreadsheetMemberData type in ImportedSpreadsheetMemberData.ts — add optional fields for customField1, customField2, approvalLimit, and overLimitForwardsTo.

4. Update the PolicyMember type and importPolicyMembers function in libs/actions/Policy/Member.ts — extend the local type and include the new fields in the JSON serialization sent to the IMPORT_MEMBERS_SPREADSHEET API.

5. Add missing translation keys in en.ts (and other language files) for "Approval limit" and "Over limit forward to" column labels if they don't already exist in the common namespace.

Open question (requires backend verification): The IMPORT_MEMBERS_SPREADSHEET backend command needs to accept these additional fields in the employees JSON payload. If the backend doesn't already handle them, a corresponding backend change in Auth would be needed.

What alternative solutions did you explore? (Optional)

N/A — the approach above is the natural extension of the existing pattern. The constants, auto-detection, and PolicyEmployee model fields are already in place; this is purely a matter of wiring them into the import flow.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.

[melvin-bot]

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

[melvin-bot]

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

[bilalup]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When importing members via CSV in workspace settings, the column mapping dropdown is missing several fields that exist in Expensify Classic:

• Custom Field 1
• Custom Field 2
• Approval Limit
• Over Limit Forward To

Users cannot map their CSV columns to these fields, forcing them to manually add this data after import.

What is the root cause of that problem?

The column mapping dropdown options are defined by a columnRoles array in ImportedMembersPage.tsx. This array currently only contains 5 options:

App/src/pages/workspace/members/ImportedMembersPage.tsx

Lines 42 to 48 in e1af99c

	const columnRoles: ColumnRole[] = [
	{text: translate('common.ignore'), value: CONST.CSV_IMPORT_COLUMNS.IGNORE},
	{text: translate('common.email'), value: CONST.CSV_IMPORT_COLUMNS.EMAIL, isRequired: true},
	{text: translate('common.role'), value: CONST.CSV_IMPORT_COLUMNS.ROLE},
	{text: translate('common.submitTo'), value: CONST.CSV_IMPORT_COLUMNS.SUBMIT_TO},
	{text: translate('common.forwardTo'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO},
	];

The missing fields (CUSTOM_FIELD_1, CUSTOM_FIELD_2, REPORT_THRESHHOLD, APPROVE_TO_ALTERNATE) are not included in this array, so they never appear in the dropdown even though the constants exist in CONST.CSV_IMPORT_COLUMNS.

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

Add the missing fields to the columnRoles array in ImportedMembersPage.tsx. This will make them appear in the dropdown menu for users to select.

File 1:

App/src/pages/workspace/members/ImportedMembersPage.tsx

Lines 42 to 48 in e1af99c

	const columnRoles: ColumnRole[] = [
	{text: translate('common.ignore'), value: CONST.CSV_IMPORT_COLUMNS.IGNORE},
	{text: translate('common.email'), value: CONST.CSV_IMPORT_COLUMNS.EMAIL, isRequired: true},
	{text: translate('common.role'), value: CONST.CSV_IMPORT_COLUMNS.ROLE},
	{text: translate('common.submitTo'), value: CONST.CSV_IMPORT_COLUMNS.SUBMIT_TO},
	{text: translate('common.forwardTo'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO},
	];

Replace this with this

const columnRoles: ColumnRole[] = [
    {text: translate('common.ignore'), value: CONST.CSV_IMPORT_COLUMNS.IGNORE},
    {text: translate('common.email'), value: CONST.CSV_IMPORT_COLUMNS.EMAIL, isRequired: true},
    {text: translate('common.role'), value: CONST.CSV_IMPORT_COLUMNS.ROLE},
    {text: translate('common.submitTo'), value: CONST.CSV_IMPORT_COLUMNS.SUBMIT_TO},
    {text: translate('common.forwardTo'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO},
    {text: translate('workspace.people.customField1'), value: CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_1},
    {text: translate('workspace.people.customField2'), value: CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_2},
    {text: translate('workspace.people.approvalLimit'), value: CONST.CSV_IMPORT_COLUMNS.REPORT_THRESHHOLD},
    {text: translate('workspace.people.overLimitForwardTo'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO_ALTERNATE},
];

File 2:

App/src/languages/en.ts

Line 3868 in 1e72ec1

workspace: {

Add these translation strings inside the workspace.people section:

workspace: {
    people: {
        // ... existing translations
        customField1: 'Custom Field 1',
        customField2: 'Custom Field 2',
        approvalLimit: 'Approval Limit',
        overLimitForwardTo: 'Over Limit Forward To',
    }
}

File 3:

App/src/languages/es.ts

Line 3692 in 1e72ec1

workspace: {

Add the Spanish translations if needed :

workspace: {
    people: {
        // ... existing translations
        customField1: 'Campo personalizado 1',
        customField2: 'Campo personalizado 2',
        approvalLimit: 'Límite de aprobación',
        overLimitForwardTo: 'Reenviar si excede el límite',
    }
}

Why this works:
The columnRoles array is directly passed to the ImportSpreadsheetColumns component which renders the dropdown options

Adding these items makes them appear in the dropdown for users to select

The constants already exist in CONST.CSV_IMPORT_COLUMNS, so the values will be properly recognized

The import logic in the same file already handles these fields when they're mapped (the code processes submitsTo, forwardsTo, etc.)

Adding translations ensures the text appears correctly in the UI

What alternative solutions did you explore? (Optional)

I considered making the dropdown dynamic based on policy settings, where these fields would only appear if the workspace has advanced approval workflows enabled. However, this would require more complex changes and wouldn't match Expensify Classic's behavior where these fields are always available regardless of policy configuration. The simpler approach of adding them directly to the columnRoles array matches Classic's implementation and requires minimal changes with zero risk of breaking existing functionality.

[twinkle-react]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Members CSV import in New Expensify does not allow users to map CSV columns to Custom Field 1, Custom Field 2, Approval Limit, and Over Limit Forward To because these options are missing from the import dropdown.

What is the root cause of that problem?

In this implementation, the columnRoles configuration inside src/pages/workspace/members/ImportedMembersPage.tsx does not include the Classic member fields even though ImportColumn.tsx already recognizes them through header detection logic. Since ImportColumn only renders mapping options that exist in columnRoles, the system assumes unsupported fields should not be selectable, which prevents these columns from appearing or being auto-selected during import.

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

// src/pages/workspace/members/ImportedMembersPage.tsx
const columnRoles: ColumnRole[] = [
    {text: translate('common.ignore'), value: CONST.CSV_IMPORT_COLUMNS.IGNORE},
    {text: translate('common.email'), value: CONST.CSV_IMPORT_COLUMNS.EMAIL, isRequired: true},
    {text: translate('common.role'), value: CONST.CSV_IMPORT_COLUMNS.ROLE},
    {text: translate('common.submitTo'), value: CONST.CSV_IMPORT_COLUMNS.SUBMIT_TO},
    {text: translate('common.forwardTo'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO},
];

// src/pages/workspace/members/ImportedMembersPage.tsx
{ text: translate('workspace.common.customField1'), value: CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_1 },
{ text: translate('workspace.common.customField2'), value: CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_2 },
{ text: translate('workspace.workflowsApprovalLimitPage.reportAmountLabel'), value: CONST.CSV_IMPORT_COLUMNS.REPORT_THRESHHOLD },
{ text: translate('workspace.workflowsApprovalLimitPage.additionalApproverLabel'), value: CONST.CSV_IMPORT_COLUMNS.APPROVE_TO_ALTERNATE },

// src/components/ImportColumn.tsx
case 'payroll':
case 'payrollid':
case 'payrolls':
case 'payrol':
case 'customfield2':
    attribute = CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_2;
case 'userid':
case 'customfield1':
    attribute = CONST.CSV_IMPORT_COLUMNS.CUSTOM_FIELD_1;
case 'approvallimit':
    attribute = CONST.CSV_IMPORT_COLUMNS.REPORT_THRESHHOLD;
case 'overlimitforwardsto':
    attribute = CONST.CSV_IMPORT_COLUMNS.APPROVE_TO_ALTERNATE;

// src/CONST/index.ts
CSV_IMPORT_COLUMNS: {
    EMAIL: 'email',
    NAME: 'name',
    GL_CODE: 'glCode',
    SUBMIT_TO: 'submitTo',
    APPROVE_TO: 'approveTo',
    CUSTOM_FIELD_1: 'customField1',
    CUSTOM_FIELD_2: 'customField2',
    ROLE: 'role',
    REPORT_THRESHHOLD: 'reportThreshold',
    APPROVE_TO_ALTERNATE: 'approveToAlternate',
}

// src/pages/workspace/members/ImportedMembersPage.tsx
// inside ImportedMembersPage.importMembers when building members[]
customField1 = ...;
customField2 = ...;
approvalLimit = parsedNumberOrNull(approvalLimitRaw);
overLimitForwardsTo = ...;

return {
    email,
    role,
    submitsTo,
    forwardsTo,
    customField1,
    customField2,
    approvalLimit,
    overLimitForwardsTo,
};

// src/types/ImportedSpreadsheetMemberData.ts
type ImportedSpreadsheetMemberData = {
    email: string;
    role: string;
    submitsTo: string;
    forwardsTo: string;
};

// src/libs/actions/Policy/Member.ts
const parameters = {
    policyID: policy.id,
    employees: JSON.stringify(members.map((member) => ({
        email: member.email,
        role: member.role,
        submitsTo: member.submitsTo,
        forwardsTo: member.forwardsTo
    }))),
};

// src/libs/actions/Policy/Member.ts
employees: JSON.stringify(members.map((member) => ({
    email: member.email,
    role: member.role,
    submitsTo: member.submitsTo,
    forwardsTo: member.forwardsTo,
    customField1: member.customField1,
    customField2: member.customField2,
    approvalLimit: member.approvalLimit,
    overLimitForwardsTo: member.overLimitForwardsTo,
}))),

What alternative solutions did you explore? (Optional)

A UI-only change that adds dropdown options without extending parsing and serialization was considered but rejected because mapped values would not be included in the import payload.