[$250] Change the default columns to remove total and add amount

[iwiznia]

Problem

The amount column is in line editable in the report page, but the total column is not. Usually, we only show one column (total) by default and AFAIK we only show the amount one if the report has transactions on a different currency. This means you can inline edit all fields but not amount.

Solution

Make the amount column the one that's shown by default instead of the total one. Keep the existing logic of showing both when needed.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022064248258930516110
• Upwork Job ID: 2064248258930516110
• Last Price Increase: 2026-06-23

Issue Owner

Current Issue Owner: @x-dev90

[melvin-bot]

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

[trasnake87]

🚨 Edited by proposal-police: This proposal was edited at 2026-06-09 07:31:34 UTC.

Proposal

What is the root cause

The expense report view (the transaction list inside a report) defaults to showing the total column (an expense's amount converted to the workspace currency) and hiding the amount column (the expense's own-currency amount). This default is set in two coupled places:

1. src/libs/SearchUIUtils.ts — getColumnsToShow() builds the initial column-visibility map for isExpenseReportView: true. At line 5534 it sets TOTAL_AMOUNT ('amount') to false and at line 5536 sets TOTAL ('total') to true. The multi-currency branch at line 5709 then adds TOTAL_AMOUNT only when an exchange rate exists, keeping TOTAL as the sole default.

2. src/pages/settings/Report/ReportDetailsColumnsPage.tsx — The REPORT_DETAILS_DEFAULT_COLUMNS constant (lines 27–34) hard-codes TABLE_COLUMNS.TOTAL and omits TABLE_COLUMNS.TOTAL_AMOUNT. Additionally, requiredColumns (line 93) locks TOTAL as mandatory in the column picker so the user cannot deselect it.

What changes do we think we should make

1. Swap defaults in getColumnsToShow — src/libs/SearchUIUtils.ts

// lines 5534 and 5536 — flip the two booleans
[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: true,   // was false — amount is now the default
[CONST.SEARCH.TABLE_COLUMNS.TOTAL]: false,          // was true — total hidden unless needed

Flip the multi-currency branch at line ~5709 so TOTAL (workspace currency) is added as a supplemental column when a foreign-currency conversion exists, instead of TOTAL_AMOUNT:

// was: columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT] = true;
columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL] = true;

Update the comment above that block to reflect the new invariant: "AMOUNT (transaction's own currency) is shown by default; TOTAL (workspace currency) is added when a conversion exists."

2. Swap defaults in the column-picker page — src/pages/settings/Report/ReportDetailsColumnsPage.tsx

// REPORT_DETAILS_DEFAULT_COLUMNS — replace TOTAL with TOTAL_AMOUNT (line 33)
const REPORT_DETAILS_DEFAULT_COLUMNS: SearchCustomColumnIds[] = [
    CONST.SEARCH.TABLE_COLUMNS.RECEIPT,
    CONST.SEARCH.TABLE_COLUMNS.DATE,
    CONST.SEARCH.TABLE_COLUMNS.MERCHANT,
    CONST.SEARCH.TABLE_COLUMNS.CATEGORY,
    CONST.SEARCH.TABLE_COLUMNS.TAG,
    CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT,   // was TOTAL
];

// requiredColumns — lock TOTAL_AMOUNT instead of TOTAL (line 93)
const requiredColumns = new Set<SearchCustomColumnIds>([CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]);

This ensures the column picker's "reset to defaults" button and the pre-selected checkboxes both reflect the new default.

What alternatives did we explore

1. Only change the column-picker constant — Updating REPORT_DETAILS_DEFAULT_COLUMNS would fix the picker UI but leave the live table unaffected for any user who has never opened the column picker, because getColumnsToShow determines the rendered columns independently using its own default-visibility map. Both layers must be kept in sync.

2. Make both columns always visible — Showing amount and total simultaneously by default on every report (including single-currency ones) would be redundant; the two columns carry the same value unless a foreign-currency conversion is present. The multi-currency branch already handles the "show both when needed" case, so the cleanest fix is simply swapping which column is the base default.

[melvin-bot]

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

[godzillaxbox19982014-lgtm]

Proposal

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

[$250] Change the default columns to remove total and add amount

What is the root cause of that problem?

I traced this to the path that handles selected currency, AFAIK, amount:

• src/pages/iou/request/step/IOURequestStepAmount.tsx:433 (navigate): Navigation.navigate(ROUTES.MONEY_REQUEST_STEP_CONFIRMATION.getRoute(CONST.IOU.ACTION.CREATE, iouTypeTrackOrSubmit, transactionID, targetReport?.reportID));
• src/pages/Search/SearchMoneyRequestReportPage.tsx:265 (if): if (iouAction || transaction?.pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD || !!transaction.linkedTrackedExpenseReportAction?.childReportID) {
• src/libs/actions/IOU/DeleteMoneyRequest.ts:194 (updateIOUOwnerAndTotal): : updateIOUOwnerAndTotal(iouReport, reportAction.actorAccountID ?? CONST.DEFAULT_NUMBER_ID, amountDiff, currency, true, false, isTransactionOnHold, unheldAmountDiff);
• The local evidence matches this recurring failure shape: optimistic transaction/report data is written to one Onyx key but the visible list reads another derived key. Here, src/pages/iou/request/step/IOURequestStepAmount.tsx:433 and src/pages/Search/SearchMoneyRequestReportPage.tsx:265 do not agree on the same selected currency, AFAIK, amount value, so the user-visible path can show a missing or stale state even though nearby data already has the needed context.

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

• Update src/pages/iou/request/step/IOURequestStepAmount.tsx:433 to derive selected currency, AFAIK, amount from the report/transaction source that owns this flow before the value is consumed.
• Carry the same normalized value through src/pages/Search/SearchMoneyRequestReportPage.tsx:265; that follows the safer family move to align optimistic/success/failure data with the selector consumed by the screen, so the write/optimistic/read paths agree instead of only changing the visible component.
• Keep the change inside the Reports, Expenses, IOU, Transactions surface and avoid changing payment actions, personal/deleted policies.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

1. Add or update a regression in tests/unit/ReportUtils*.ts for the exact issue flow: [$250] Change the default columns to remove total and add amount.
2. Cover the counter-case near src/pages/iou/request/step/IOURequestStepAmount.tsx:433 so valid existing selected currency, AFAIK, amount behavior still works.
3. Manually repeat the issue steps after the patch and confirm the visible state/action is no longer stale.

What alternative solutions did you explore? (Optional)

• I would not add a broad new condition outside these referenced paths; the safer fix is to keep selected currency, AFAIK, amount consistent at the first read/write boundary shown above.

[aswin-s]

Proposal

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

On the expense report (Money Request Report) view, the Total column is shown by default and the Amount column only appears when the transaction's currency differs from the report's currency. Because only Amount is inline-editable, users cannot inline-edit transaction amounts in the common (same-currency) case. Expected: show Amount by default; show Total only when needed (transaction currency differs from report currency), keeping both visible in the conversion case.

What is the root cause of that problem?

getColumnsToShow in src/libs/SearchUIUtils.ts (lines 5516-5536) seeds the expense-report-view defaults with TABLE_COLUMNS.TOTAL: true and TABLE_COLUMNS.TOTAL_AMOUNT: false, and the conditional at lines 5707-5709 only flips TOTAL_AMOUNT to true when hasExchangeRate is truthy. So in the same-currency case the table renders Total (non-editable) instead of Amount (inline-editable). The same TOTAL-as-default assumption is hard-coded in REPORT_DETAILS_DEFAULT_COLUMNS and requiredColumns in src/pages/settings/Report/ReportDetailsColumnsPage.tsx (lines 27-34, 93).

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

1. In src/libs/SearchUIUtils.ts (lines 5534, 5536), swap the expense-report-view default seeds: set TABLE_COLUMNS.TOTAL_AMOUNT: true and TABLE_COLUMNS.TOTAL: false.
2. In the same file (lines 5707-5713), invert the conversion branch for isExpenseReportView: when hasExchangeRate is true, set columns[TABLE_COLUMNS.TOTAL] = true (additive) so both Amount and Total remain visible on conversion; otherwise only Amount shows. Leave the search-page (ORIGINAL_AMOUNT) branch unchanged.
3. In src/pages/settings/Report/ReportDetailsColumnsPage.tsx (lines 27-34), replace CONST.SEARCH.TABLE_COLUMNS.TOTAL with CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT in REPORT_DETAILS_DEFAULT_COLUMNS so the columns settings page reflects the new default selection.
4. In the same file (line 93), update requiredColumns to pin TABLE_COLUMNS.TOTAL_AMOUNT instead of TABLE_COLUMNS.TOTAL so users cannot deselect the new default column.
5. Verify the isDefaultExpenseColumnSelection comparison at line 5577 (which uses TYPE_DEFAULT_COLUMNS.EXPENSE) is not impacted — this constant governs the search page, not the expense-report-view defaults being changed; leave it untouched.

What alternative solutions did you explore? (Optional)

[lorretheboy]

Proposal

What is the root cause of that problem?

In the money request report view, the visible columns come from getColumnsToShow. For an expense report (isExpenseReportView), the default column map hard-codes the read-only Total column on and the editable Amount column off:

App/src/libs/SearchUIUtils.ts

Lines 5534 to 5536 in 0fd4dab

	[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: false,
	[CONST.SEARCH.TABLE_COLUMNS.COMMENTS]: shouldShowCommentsColumn,
	[CONST.SEARCH.TABLE_COLUMNS.TOTAL]: true,

TOTAL_AMOUNT (header label iou.amount → "Amount") is then only flipped on when a currency conversion exists:

App/src/libs/SearchUIUtils.ts

Lines 5704 to 5713 in 0fd4dab

	// Expense report view: TOTAL (workspace currency) is always shown; add AMOUNT
	// (transaction's own currency) when a conversion exists so both are visible.
	// Search page: show ORIGINAL_AMOUNT column (transaction's original amount).
	if (hasExchangeRate) {
	if (isExpenseReportView) {
	columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT] = true;
	} else {
	columns[CONST.SEARCH.TABLE_COLUMNS.ORIGINAL_AMOUNT] = true;
	}
	}

The two columns render differently. TOTAL renders a plain, non-editable AmountCell:

App/src/components/TransactionItemRow/TransactionItemRowWide.tsx

Lines 569 to 588 in 0fd4dab

	case CONST.SEARCH.TABLE_COLUMNS.TOTAL: {
	const isFromExpenseReport = isExpenseReport(transactionItem.report ?? report);
	const hasConvertedAmount = transactionItem.convertedAmount != null;
	// Offline expenses don't have a BE-computed convertedAmount yet — fall back to the unconverted
	// amount in the transaction's own currency so users don't see a misleading $0.00 placeholder.
	// Pass isFromExpenseReport so IOU reports stay positive while expense reports get NewDot's signed display.
	const totalAmount = hasConvertedAmount ? getConvertedAmount(transactionItem, isFromExpenseReport) : getAmount(transactionItem, isFromExpenseReport);
	// When converted, display in the report's output currency; otherwise use the transaction's own currency.
	const totalCurrency = hasConvertedAmount ? (report?.currency ?? policy?.outputCurrency ?? getCurrency(transactionItem)) : getCurrency(transactionItem);
	return (
	<View
	key={column}
	style={[StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT, {isAmountColumnWide, shouldRemoveTotalColumnFlex})]}
	>
	<AmountCell
	total={totalAmount}
	currency={totalCurrency}
	/>
	</View>
	);

while TOTAL_AMOUNT renders an inline-editable TotalCell (canEdit={canEditAmount}, onSave={onEditAmount}):

App/src/components/TransactionItemRow/TransactionItemRowWide.tsx

Lines 419 to 435 in 0fd4dab

	case CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT:
	return (
	<View
	key={column}
	style={[StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT, {isAmountColumnWide, shouldRemoveTotalColumnFlex})]}
	>
	<TotalCell
	transactionItem={transactionItem}
	shouldShowTooltip={shouldShowTooltip}
	shouldUseNarrowLayout={false}
	canEdit={canEditAmount}
	onSave={onEditAmount}
	report={report}
	policy={policy}
	/>
	</View>
	);

So by default the report shows the non-editable Total column and hides the editable Amount column, which only appears when transactions are in a different currency. That is why every field is inline-editable except the amount.

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

Swap the defaults in the expense-report-view branch of getColumnsToShow so the editable Amount (TOTAL_AMOUNT) is the column shown by default and Total (TOTAL) becomes the data-driven one:

• In the default column map (lines 5534/5536), set TOTAL_AMOUNT: true and TOTAL: false. Move TOTAL_AMOUNT to the Total's position in the key order so the amount stays the right-most money column.
• In the hasExchangeRate block (lines 5707-5713), for the expense report view enable TOTAL (the workspace-currency column) instead of TOTAL_AMOUNT, so both columns still appear together when a transaction has a currency conversion.

This keeps the "show both when needed" behavior while making the always-visible money column the inline-editable Amount.

What alternative solutions did you explore? (Optional)

Keep TOTAL as the default column but make its AmountCell editable (pass canEdit/onSave). This avoids changing column selection, but it diverges from the existing editable TotalCell used by TOTAL_AMOUNT and would duplicate edit wiring, so swapping the default column is cleaner.

[github-actions]

⚠️ @lorretheboy Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[yusufdeveloper2903]

Proposal

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

In the money request report view (the report table), the Total column is shown by default while the Amount column is only shown when the report contains transactions in a different currency. Because the Amount cell is inline‑editable and the Total cell is not, a single‑currency report lets you inline‑edit every field except the amount. We want Amount to be the default money column, while keeping the "show both when needed" behavior for multi‑currency reports.

What is the root cause of that problem?

The column visibility for the report view is computed in getColumnsToShow() in src/libs/SearchUIUtils.ts. For the expense report view (isExpenseReportView === true), the default visibility map hardcodes TOTAL on and TOTAL_AMOUNT (the "Amount" column) off:

https://github.com/Expensify/App/blob/d73a7bcc480/src/libs/SearchUIUtils.ts#L5431-L5449

[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: false,   // "amount" — hidden by default
...
[CONST.SEARCH.TABLE_COLUMNS.TOTAL]: true,           // "total" — shown by default

The amount column is only flipped on later, and only when a currency conversion exists for the transaction (i.e. multi‑currency):

https://github.com/Expensify/App/blob/d73a7bcc480/src/libs/SearchUIUtils.ts#L5592-L5601

// Expense report view: TOTAL (workspace currency) is always shown; add AMOUNT
// (transaction's own currency) when a conversion exists so both are visible.
if (hasExchangeRate) {
    if (isExpenseReportView) {
        columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT] = true;
    } else {
        columns[CONST.SEARCH.TABLE_COLUMNS.ORIGINAL_AMOUNT] = true;
    }
}

For the default (non‑custom) path the function simply returns the columns whose flag is true (https://github.com/Expensify/App/blob/d73a7bcc480/src/libs/SearchUIUtils.ts#L5702), so a single‑currency report yields TOTAL and never TOTAL_AMOUNT.

Why that matters: in the row renderer, TOTAL_AMOUNT ("amount") renders an editable TotalCell (canEdit={canEditAmount}, onSave={onEditAmount}), while TOTAL ("total") renders a plain, read‑only AmountCell:

• editable amount: https://github.com/Expensify/App/blob/d73a7bcc480/src/components/TransactionItemRow/TransactionItemRowWide.tsx#L408-L424
• read‑only total: https://github.com/Expensify/App/blob/d73a7bcc480/src/components/TransactionItemRow/TransactionItemRowWide.tsx#L540-L560

(The constants confirm the mapping: TOTAL_AMOUNT: 'amount' and TOTAL: 'total' — https://github.com/Expensify/App/blob/d73a7bcc480/src/CONST/index.ts#L7423-L7426.)

So the root cause is purely the default‑visibility choice in getColumnsToShow: TOTAL (read‑only) is the default money column and TOTAL_AMOUNT (editable) is conditional. Swapping that default resolves the inability to inline‑edit the amount.

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

Swap which money column is the default in the isExpenseReportView branch, and add the other one (Total) only when a conversion exists — mirroring the current logic with the roles reversed.

1. Flip the defaults in the isExpenseReportView visibility map:

-              [CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: false,
+              [CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: true,
               [CONST.SEARCH.TABLE_COLUMNS.COMMENTS]: shouldShowCommentsColumn,
-              [CONST.SEARCH.TABLE_COLUMNS.TOTAL]: true,
+              [CONST.SEARCH.TABLE_COLUMNS.TOTAL]: false,

2. Add Total (instead of Amount) on conversion, since Amount is now always present:

 if (hasExchangeRate) {
     if (isExpenseReportView) {
-        columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT] = true;
+        columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL] = true;
     } else {
         columns[CONST.SEARCH.TABLE_COLUMNS.ORIGINAL_AMOUNT] = true;
     }
 }

This keeps the exact "show both when there's a conversion" behavior — now Amount (the transaction's own currency, editable) is always shown and Total (the report's output currency) joins it for multi‑currency reports. The Amount column already sits before Total in the map, so the visual order (own currency → converted total) is preserved.

Supporting changes (described, not diffed, since they just follow from the swap):

• nonDataColumns set (https://github.com/Expensify/App/blob/d73a7bcc480/src/libs/SearchUIUtils.ts#L5677-L5697): this set marks the "always present" money column so it's kept when a user has custom‑ordered columns. It currently lists TOTAL; it should now list TOTAL_AMOUNT instead (and drop TOTAL), so that a user who explicitly picks Amount always keeps it, and Total becomes data‑driven like Amount was. Update the adjacent comment accordingly.
• Tests: tests/unit/Search/SearchUIUtilsTest.ts has expense‑report‑view assertions that reference TABLE_COLUMNS.TOTAL as the default money column (e.g. the ordering check at https://github.com/Expensify/App/blob/d73a7bcc480/tests/unit/Search/SearchUIUtilsTest.ts#L8423). These should be updated to expect TOTAL_AMOUNT by default, plus a new case asserting that a single‑currency report returns TOTAL_AMOUNT (not TOTAL) and a multi‑currency report (transaction with an exchange rate) returns both.

Edge cases covered:

• Offline / no BE conversion: the editable TotalCell already falls back to the transaction's own amount/currency, so a freshly created offline expense still shows an editable Amount with no $0.00 flash.
• Multi‑currency: unchanged — both columns appear, just with Amount always first.
• Platforms: this is shared logic; behavior is identical across web/iOS/Android. Inline‑edit affordance is wide‑layout (table) only, which is where the report columns render.
• EXPENSE_REPORT data type (Search grouping) and the Search page paths are untouched — the change is scoped to the isExpenseReportView branch.

What alternative solutions did you explore? (Optional)

• Make the Total cell inline‑editable instead of changing defaults — rejected: Total is the report‑currency (often converted) value; editing it is ambiguous for multi‑currency transactions, and the issue explicitly asks to default to the Amount column, not to add a second editable money cell.
• Force the Amount column on in the row component / via a UI flag — rejected: it duplicates column‑selection logic outside the single source of truth (getColumnsToShow) and would desync the table header, the Columns settings page, and the saved reportDetailsColumns order.

[KJ21-ENG]

🚨 Edited by proposal-police: This proposal was edited at 2026-06-09 07:49:56 UTC.

Proposal

What is the root cause of that problem?

The report-details column selection is inverted for the desired behavior. In getColumnsToShow(), the isExpenseReportView default map enables TOTAL and disables TOTAL_AMOUNT:

App/src/libs/SearchUIUtils.ts

Lines 5516 to 5537 in 0fd4dab

	const columns: ColumnVisibility = isExpenseReportView
	? {
	[CONST.SEARCH.TABLE_COLUMNS.RECEIPT]: true,
	[CONST.SEARCH.TABLE_COLUMNS.TYPE]: true,
	[CONST.SEARCH.TABLE_COLUMNS.DATE]: true,
	[CONST.SEARCH.TABLE_COLUMNS.MERCHANT]: false,
	[CONST.SEARCH.TABLE_COLUMNS.DESCRIPTION]: false,
	[CONST.SEARCH.TABLE_COLUMNS.CATEGORY]: false,
	[CONST.SEARCH.TABLE_COLUMNS.CATEGORY_GL_CODE]: false,
	[CONST.SEARCH.TABLE_COLUMNS.TAG]: false,
	[CONST.SEARCH.TABLE_COLUMNS.CARD]: false,
	[CONST.SEARCH.TABLE_COLUMNS.MCC]: false,
	[CONST.SEARCH.TABLE_COLUMNS.TAX_CODE]: false,
	[CONST.SEARCH.TABLE_COLUMNS.TAX_RATE]: false,
	[CONST.SEARCH.TABLE_COLUMNS.TAX_AMOUNT]: false,
	[CONST.SEARCH.TABLE_COLUMNS.EXCHANGE_RATE]: false,
	[CONST.SEARCH.TABLE_COLUMNS.REIMBURSABLE]: shouldShowReimbursableColumn,
	[CONST.SEARCH.TABLE_COLUMNS.BILLABLE]: shouldShowBillableColumn,
	[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT]: false,
	[CONST.SEARCH.TABLE_COLUMNS.COMMENTS]: shouldShowCommentsColumn,
	[CONST.SEARCH.TABLE_COLUMNS.TOTAL]: true,
	}

Then, when an exchange rate is detected, the report-view branch adds TOTAL_AMOUNT, so both columns are only visible for converted/multi-currency transactions:

App/src/libs/SearchUIUtils.ts

Lines 5700 to 5713 in 0fd4dab

	const hasExchangeRate = getExchangeRate(transaction, reportCurrency) !== '';
	if (hasExchangeRate) {
	columns[CONST.SEARCH.TABLE_COLUMNS.EXCHANGE_RATE] = true;
	}
	// Expense report view: TOTAL (workspace currency) is always shown; add AMOUNT
	// (transaction's own currency) when a conversion exists so both are visible.
	// Search page: show ORIGINAL_AMOUNT column (transaction's original amount).
	if (hasExchangeRate) {
	if (isExpenseReportView) {
	columns[CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT] = true;
	} else {
	columns[CONST.SEARCH.TABLE_COLUMNS.ORIGINAL_AMOUNT] = true;
	}
	}

That leaves same-currency reports with only TOTAL. The TOTAL branch renders a plain AmountCell, while TOTAL_AMOUNT is the column wired to TotalCell with canEditAmount and onEditAmount:

App/src/components/TransactionItemRow/TransactionItemRowWide.tsx

Lines 419 to 435 in 0fd4dab

	case CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT:
	return (
	<View
	key={column}
	style={[StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT, {isAmountColumnWide, shouldRemoveTotalColumnFlex})]}
	>
	<TotalCell
	transactionItem={transactionItem}
	shouldShowTooltip={shouldShowTooltip}
	shouldUseNarrowLayout={false}
	canEdit={canEditAmount}
	onSave={onEditAmount}
	report={report}
	policy={policy}
	/>
	</View>
	);

App/src/components/TransactionItemRow/TransactionItemRowWide.tsx

Lines 569 to 588 in 0fd4dab

	case CONST.SEARCH.TABLE_COLUMNS.TOTAL: {
	const isFromExpenseReport = isExpenseReport(transactionItem.report ?? report);
	const hasConvertedAmount = transactionItem.convertedAmount != null;
	// Offline expenses don't have a BE-computed convertedAmount yet — fall back to the unconverted
	// amount in the transaction's own currency so users don't see a misleading $0.00 placeholder.
	// Pass isFromExpenseReport so IOU reports stay positive while expense reports get NewDot's signed display.
	const totalAmount = hasConvertedAmount ? getConvertedAmount(transactionItem, isFromExpenseReport) : getAmount(transactionItem, isFromExpenseReport);
	// When converted, display in the report's output currency; otherwise use the transaction's own currency.
	const totalCurrency = hasConvertedAmount ? (report?.currency ?? policy?.outputCurrency ?? getCurrency(transactionItem)) : getCurrency(transactionItem);
	return (
	<View
	key={column}
	style={[StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT, {isAmountColumnWide, shouldRemoveTotalColumnFlex})]}
	>
	<AmountCell
	total={totalAmount}
	currency={totalCurrency}
	/>
	</View>
	);

The report columns settings page mirrors the same old default and required column by preselecting and requiring TOTAL:

App/src/pages/settings/Report/ReportDetailsColumnsPage.tsx

Lines 27 to 34 in 0fd4dab

	const REPORT_DETAILS_DEFAULT_COLUMNS: SearchCustomColumnIds[] = [
	CONST.SEARCH.TABLE_COLUMNS.RECEIPT,
	CONST.SEARCH.TABLE_COLUMNS.DATE,
	CONST.SEARCH.TABLE_COLUMNS.MERCHANT,
	CONST.SEARCH.TABLE_COLUMNS.CATEGORY,
	CONST.SEARCH.TABLE_COLUMNS.TAG,
	CONST.SEARCH.TABLE_COLUMNS.TOTAL,
	];

App/src/pages/settings/Report/ReportDetailsColumnsPage.tsx

Lines 93 to 94 in 0fd4dab

	const requiredColumns = new Set<SearchCustomColumnIds>([CONST.SEARCH.TABLE_COLUMNS.TOTAL]);

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

Swap the report-details defaults so TOTAL_AMOUNT is the default money column and TOTAL becomes the additive conversion column.

Concretely:

1. In getColumnsToShow(), for isExpenseReportView, set CONST.SEARCH.TABLE_COLUMNS.TOTAL_AMOUNT to true and CONST.SEARCH.TABLE_COLUMNS.TOTAL to false.
2. In the hasExchangeRate branch, when isExpenseReportView is true, enable TOTAL instead of enabling TOTAL_AMOUNT. This preserves the existing "show both when needed" behavior for converted transactions: Amount remains visible and editable, while Total is added for the report/workspace currency value.
3. Update ReportDetailsColumnsPage defaults and required columns from TOTAL to TOTAL_AMOUNT, so the settings UI matches the new default and keeps the editable money column pinned.
4. Add focused coverage for getColumnsToShow() / report-details columns:
   • same-currency report transactions include TOTAL_AMOUNT and do not include TOTAL by default;
   • converted/multi-currency report transactions include both TOTAL_AMOUNT and TOTAL;
   • saved/custom report columns still preserve user order while keeping the required TOTAL_AMOUNT column.

Scope boundaries: this should stay in the report-details column selection/settings logic. It should not change expense search-page defaults, grouped search columns, amount calculations, inline edit actions, transaction detail pages, or backend/API behavior.

What alternative solutions did you explore? (Optional)

I considered keeping TOTAL as the default and making its AmountCell editable, but that edits a derived/converted display in some cases and duplicates the existing edit path already owned by TOTAL_AMOUNT. Swapping the default column is narrower and matches the product requirement to show Amount by default while still showing Total when conversion makes both values useful.