Skip to content

[Due for payment 2026-08-05] [$250] Expense form: reduce scrolling by removing the "To" label and shrinking the empty receipt state #95564

Closed

Description

@MelvinBot

Problem

When creating or editing an expense, many fields aren't visible by default — users have to scroll to reach fields beyond Category, including required ones (e.g. required tags, the Reimbursable toggle). Because it isn't obvious there's more below the fold, employees miss important fields, which then get flagged as violations.

Proposed change

Start with two straightforward space-saving wins (agreed as the starting point in the discussion):

  1. Remove the "To" label above the recipient row.
  2. Use a smaller empty state for the receipt preview when no receipt has been added, keeping the current (larger) receipt size once a receipt is attached.

Mockup:

Image

Platforms

  • Web
  • Mobile

Slack thread: https://expensify.slack.com/archives/C03U7DCU4/p1783431421163959

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Jul 8, 2026

    @melvin-bot

    Current assignee @shawnborton is eligible for the NewFeature assigner, not assigning anyone new.

  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 8, 2026
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 8, 2026
  4. samranahm commented on Jul 8, 2026

    @samranahm
    Contributor

    Proposal

    What is the root cause of that problem?

    This is a NewFeature, so the "root cause" is the layout that forces scrolling. When an employee opens the expense confirmation form, the top of the view is taken up by (a) a full size receipt preview even when no receipt is attached, and (b) a "To" section label above the recipient row. Both consume vertical space above the fold, so the field rows rendered by ConfirmationFieldList (required tags, the Reimbursable toggle, etc.) are pushed below the fold and users miss them.

    The field rows themselves are computed and rendered here, and their visibility is already driven by computeFieldVisibility, so nothing is hidden by logic, it is purely vertical real estate above them:

    function ConfirmationFieldList({
    policy,
    policyTags,
    selectedParticipants,
    distanceData,
    amountDisplay,
    requiredFlags,
    visibilityFlags,
    errorState,
    toggleHandlers,
    compactState,
    }: ConfirmationFieldListProps) {
    const styles = useThemeStyles();
    const theme = useTheme();
    const {translate} = useLocalize();
    const icons = useMemoizedLazyExpensifyIcons(['Sparkles', 'DownArrow']);
    const {action, iouType, transactionID, isReadOnly, isPolicyExpenseChat, isDistanceRequest, isPerDiemRequest, isTimeRequest, isTypeInvoice} = useConfirmationFields();
    const policyTagLists = getTagLists(policyTags);
    const flags = useFooterDerivedFlags({
    action,
    iouType,
    transactionID,
    policy,
    policyTagLists,
    isPolicyExpenseChat,
    isReadOnly,
    isDistanceRequest,
    isPerDiemRequest,
    isTimeRequest,
    isTypeInvoice,
    shouldShowSmartScanFields: visibilityFlags.shouldShowSmartScanFields,
    });
    const {tagVisibility, previousTagsVisibility} = useFooterTagVisibility({
    shouldShowTags: flags.shouldShowTags,
    policy,
    policyTags,
    transactionID,
    });
    const fieldVisibility = computeFieldVisibility({
    shouldShowSmartScanFields: visibilityFlags.shouldShowSmartScanFields,
    shouldShowAmountField: visibilityFlags.shouldShowAmountField,
    isDistanceRequest,
    shouldShowMerchant: visibilityFlags.shouldShowMerchant,
    shouldShowTimeRequestFields: flags.shouldShowTimeRequestFields,
    shouldShowCategories: visibilityFlags.shouldShowCategories,
    isCategoryRequired: requiredFlags.isCategoryRequired,
    shouldShowDate: flags.shouldShowDate,
    tagVisibility,
    policyTagLists,
    shouldShowTax: visibilityFlags.shouldShowTax,
    shouldShowAttendees: flags.shouldShowAttendees,
    shouldShowReimbursable: flags.shouldShowReimbursable,
    shouldShowBillable: flags.shouldShowBillable,
    isPolicyExpenseChat,
    });
    const shouldShowMoreButton = hasBelowShowMore(fieldVisibility);
    return (
    <View style={[styles.mb5, styles.mt2]}>
    {compactState.isCompactMode && (
    <View style={[styles.flexRow, styles.alignItemsCenter, styles.pl5, styles.gap2, styles.mb2, styles.pr10]}>
    <Icon
    src={icons.Sparkles}
    fill={theme.icon}
    width={variables.iconSizeNormal}
    height={variables.iconSizeNormal}
    />
    <Text style={styles.rightLabelMenuItem}>{translate('iou.automaticallyEnterExpenseDetails')}</Text>
    </View>
    )}
    <TransactionDetailsFields
    policy={policy}
    amountDisplay={amountDisplay}
    distanceData={distanceData}
    requiredFlags={requiredFlags}
    errorState={errorState}

    The "To" label and the receipt preview are rendered above this footer by the parent confirmation list component (MoneyRequestConfirmationList), which is where the two space savings must be applied.

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

    1. In MoneyRequestConfirmationList.tsx, remove the standalone "To" section header/label above the recipient row so the recipient row renders directly. The recipient row already shows the participant, so the label is redundant. This reclaims one line of vertical space. Keep the recipient row readable (validate copy so it still reads as who the expense is sent to).

    2. In the receipt preview block of MoneyRequestConfirmationList.tsx, render a smaller empty state when no receipt is attached, and keep the current larger size once a receipt exists. Gate the height on whether a receipt is present:

    const hasReceipt = !!receiptImage || !!receiptThumbnail;
    const receiptContainerStyle = hasReceipt ? styles.moneyRequestImage : styles.moneyRequestImageEmptySmall;

    Use the third mockup's empty state treatment for the smaller container, and reuse the existing larger style once hasReceipt is true.

    1. Verify on both web and mobile that removing the label and shrinking the empty state brings Category, required tags, and the Reimbursable toggle above the fold, matching the goal in the issue. The fields below still render through ConfirmationFieldList linked above, so no visibility logic changes are needed.

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  5. melvin-bot commented on Jul 8, 2026

    @melvin-bot

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

  6. wildan-m commented on Jul 8, 2026

    @wildan-m
    Contributor

    Proposal

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

    When creating or editing an expense, the confirmation form ("Confirm details") uses more vertical space than it needs, so fields below the receipt preview — including important ones like the Reimbursable toggle and required tags — sit below the fold. Because it isn't obvious there is more content underneath, people miss those fields and their expenses get flagged as violations. As a first step we want two space-saving wins: remove the "To" label above the recipient row, and use a smaller empty state for the receipt preview when no receipt has been attached (keeping the full size once a receipt exists).

    What is the root cause of that problem?

    Two pieces of the confirmation form each consume vertical space that isn't strictly needed in the empty/default state:

    1. The recipient section is always rendered with a "To" section header when a participant is selected, which costs an extra line even though the recipient row underneath already communicates who the expense goes to. The header text is set here:

    options.push({
    title: selectedParticipants.length > 0 ? translate('common.to') : undefined,
    data: participantRows,
    sectionIndex: 0,
    });

    1. The receipt preview area uses a single fixed height (180px) for both states — when a receipt is attached AND when it is empty. The empty "add a receipt" placeholder only needs to show a small icon, so reserving the full 180px tall box for it pushes the rest of the form (Amount, Merchant, Description, Date, and the fields below) further down. The empty state reuses the same moneyRequestViewImage style (fixed height: 180):

    App/src/styles/index.ts

    Lines 4880 to 4888 in 3b116cd

    moneyRequestViewImage: {
    ...spacing.mh5,
    overflow: 'hidden',
    borderWidth: 1,
    borderColor: theme.border,
    borderRadius: variables.componentBorderRadiusLarge,
    height: 180,
    maxWidth: '100%',
    },

    The empty state is rendered here, applying that full-height style:

    return (
    <ReceiptEmptyState
    onPress={() => {
    if (!transactionID) {
    return;
    }
    Navigation.navigate(ROUTES.MONEY_REQUEST_STEP_SCAN.getRoute(CONST.IOU.ACTION.CREATE, iouType, transactionID, reportID, Navigation.getActiveRoute()));
    }}
    style={[compact.isCompactMode ? undefined : styles.mv3, compact.isCompactMode && compact.compactReceiptStyle ? compact.compactReceiptStyle : styles.moneyRequestViewImage]}
    />
    );

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

    1. Remove the "To" label above the recipient row.

    In useConfirmationSections, stop setting the participants section title to the "To" string and leave it empty (undefined). The section list already suppresses the header row entirely when the title is empty (the header is only emitted when section.title is truthy), so no blank space is left behind — the recipient row simply moves up by one line. The recipient row itself (avatar, name, email, chevron) still reads clearly as who the expense is sent to.

    2. Use a shorter empty state for the receipt preview.

    Add a small dedicated style (e.g. moneyRequestViewImageEmptyState with a reduced height of ~100px, comfortably fitting the 64px receipt icon and its "+" badge) and apply it to the receipt area in ReceiptSection only for the empty state (i.e. when no receipt image/thumbnail is present and compact scan mode is not active). Because the empty-state style is appended after moneyRequestViewImage, it overrides only the height and keeps the existing border, radius and horizontal margin. When a receipt is actually attached, the code continues to render the full-size moneyRequestViewImage (180px), so attached receipts are unchanged.

    Together these free roughly one line plus ~80px of height in the default (no-receipt) form, bringing more fields above the fold on both web and mobile without affecting any behavior.

    Verified on the confirmation form (Create expense → Manual → choose recipient): with the change, the "To" header is gone and the empty receipt box measures 100px tall instead of 180px, while the recipient row and attached-receipt sizing are unchanged.

    Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/95564-expense-form-reduce-scrolling?expand=1

    What alternative solutions did you explore? (Optional)

    • Collapsing the receipt preview into a smaller inline "Add receipt" button (row-style) rather than a shortened box. This saves even more space but is a bigger visual departure from the current design and from the referenced mockup direction, so the shorter box is the lower-risk first step.
    • Keeping the "To" header but reducing its top/bottom spacing. This saves less than removing the line entirely and still leaves a redundant label above a self-explanatory recipient row.
  7. changed the title [-]Expense form: reduce scrolling by removing the "To" label and shrinking the empty receipt state[/-] [+][$250] Expense form: reduce scrolling by removing the "To" label and shrinking the empty receipt state[/+] on Jul 8, 2026
  8. melvin-bot commented on Jul 8, 2026

    @melvin-bot
  9. 61 remaining items

  10. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2074788311240941773/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. emkhalid commented on Aug 5, 2026

    @emkhalid
    Contributor

    @inimaga @shawnborton Would a total payment of $500 be reasonable considering the additional work completed?

    In PR #96203, I addressed several design refinements beyond the initial scope, including the receipt field’s spacing, sizing, icon, hover states, and verification across all themes. I also reproduced, validated, and thoroughly tested the follow-up refinement in PR #97207 under the affected Android font and display settings.

    Please let me know if this payment adjustment works for you. Thanks!

  12. sobitneupane commented on Aug 6, 2026

    @sobitneupane
    Contributor

    Regression Test Proposal

    Test:

    1. Sign in as an employee of a workspace with Category, required Tags, and Reimbursable enabled.
    2. Start creating a manual expense.
    3. Enter an amount, select the workspace recipient, and continue to Confirm details without adding a receipt.
    4. Verify the "To" header is not displayed.
    5. Verify the empty receipt state is a compact row containing the receipt icon and bold "Add receipt" text.
    6. Verify more expense fields, including Category, required Tags, and Reimbursable, are visible without scrolling.
    7. Tap Add receipt and attach a receipt.
    8. Verify the attached receipt uses the existing larger preview.
    9. Start creating an invoice and continue to its confirmation screen.
    10. Verify the invoice still displays the "To" header.

    Do we agree 👍 or 👎

  13. melvin-bot commented on Aug 7, 2026

    @melvin-bot

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  14. mallenexpensify commented on Aug 8, 2026

    @mallenexpensify
    Contributor

    @sobitneupane coming from above, If you think the work warrants an increase, plz follow the steps in the C+ doc.

  15. sobitneupane commented on Aug 8, 2026

    @sobitneupane
    Contributor

    There had been some minor design tweaks, but I don't think they were significant enough to justify doubling the price. Small UI/UX adjustment are generally expected as part of addressing the issue.

  16. mallenexpensify commented on Aug 8, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @emkhalid paid $250 via Upwork
    Contributor+: @sobitneupane due $250 via NewDot

    @emkhalid can you please accept the job below? Please reply here and tag me once you have.
    If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal.
    https://www.upwork.com/jobs/~022086130813428571509

    Thx @sobitneupane

  17. emkhalid commented on Aug 9, 2026

    @emkhalid
    Contributor

    @mallenexpensify I accepted the offer, Thanks!

  18. mallenexpensify commented on Aug 10, 2026

    @mallenexpensify
    Contributor

    @emkhalid paid, summary updated above. Thx.

  19. JmillsExpensify commented on Sep 18, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @sobitneupane

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions