Skip to content

[Tracking] Custom Report Names on New Expensify #44340

Closed
14 of 14 issues completed
Closed

Description

@m-natarajan

DESIGN DOC ➡️

Proposal

Custom report names on New Expensify

Strategy: New Expensify aims to capture the untapped small business expense management market through an intuitive product that spreads virally from employees to company decision makers, and between companies and friends via word of mouth consensus as the best tool for the job. To achieve this goal it must quickly solve customer problems and simplify their life, providing a seamless experience to become an indispensable tool that is sharp and reliable.

Background: Classic and New Expensify allow workspace admins to configure "Custom Report Names" using a formula made up from any text and various "formula parts" such as {report:type}, {report:startdate}, etc. Some parts allow selecting various subfields like {report:submit:from:firstname}
and functions can be applied to all parts, such as {report:submit:from:email|frontPart}. For a full list of supported formula parts, see the report level formulas and the functions on this help page.

On Classic, when the formula is updated to a new value and a user loads the reports page, all non-chat reports loaded by the app that have not been approved yet, and do not have a manually set name, will have their name recomputed according to the formula and saved to the database. There is also a setting to prevent users from manually setting a report name. Formulas can reference data at the report level, transaction, policy, and user levels. When referenced data is updated and a report is loaded again on classic, the name will be updated with the new value (in most cases). Users have very likely come to expect this behavior since it has worked this way for many years.

Report titles are one of our most popular features. Over 82% of admins change the default to something more specific. Custom report names are useful at all levels of approval and for admins, as it helps give context to what kinds of expenses are being grouped together.

New Expensify is built on a foundation of realtime chat, and all information it displays updates without requiring any manual page refreshes. Users can go offline and use the app, confident that everything will save and any missed updates will load when they go back online. Reports are not loaded from the database when refreshing the page manually or navigating to the inbox page. Instead, reports are loaded from the server once on sign in and thereafter updates to the reports and other data are sent from the backend as soon as they occur. If the app misses updates for any reason, it will fetch them from the server. Due to that architecture, when data is changed on the server it will queue all updates that are required to put the users' UI into the correct state.

Classic requires refreshing the page to update almost all data and when doing so it is almost always completely reloaded from the database.

Problem: When a user saves a custom report name formula in their workspace settings on New Expensify, reports in New Expensify will not have their names set based on the formula, which causes confusion, prevents the user from trusting our pre-accounting system, and prevents them from having their reports named in a uniform manner with important information.

Solution: Make custom report names work on New Expensify by doing the following.
In progress or already done:

  • Move report name computation from Web-E to Auth so that names can be computed following our 1:1:1 rule
  • Computing the name in Web-E would add 3+ Auth requests to every API command that could affect the name formula, which is many commands.
  • Move a few formula parts at a time to Auth, deploying each part to production but hiding it behind a very limited "beta"
  • Start with the most commonly used formula parts, based on querying usage for users billed in the last 3 months
  • Update the computed report name from Auth whenever the report updates, then similarly for transactions
  • Implement custom report field formula parts
  • Implement the rest of the supported formula parts
  • Create a system to Monitor and resolve differences in auto report title computations between the Web-E and Auth implementations

To do:

  • Update custom report names using Bedrock jobs when the policy and other referenced data changes and requires updating many existing reports
  • Determine which data should update existing report names, if not all
  • Display notes in the UI when custom report names may be stale
  • Plan and implement a system for optimistic report title formula computation
  • Once there are no undesired differences between the Web-E and Auth implementations, slowly roll it out to more customers, monitoring for any problems
  • After it's working well for many customers including large ones, remove the beta

Tasks

  • Post Proposal (full Problem/Solution statement) in #whatsnext
  • Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
  • Paste Proposal in the space above with a link to the Slack thread
  • Email strategy@expensify.com and paste in the Proposal
  • Host a pre-design meeting (example) in an appropriate slack channel to discuss any necessary details in public before filling out the High-level of proposed solution section.
  • Fill out the High-level overview of the problem, Timeline, Terminology, and High-level of proposed solution sections of the Design Doc
  • Email strategy@expensify.com (continue the same email chain as before - your last message should be the WN Proposal) with the link to your Design Doc containing your high-level problem and solution
  • Add the DesignDocReview label to get the High-level overview of the problem and High-level of proposed solution section reviewed
  • Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Host another pre-design meeting in the appropriate slack channel to ask for engineering feedback on the technical solution.
    • N/A, a pre-design was not deemed necessary
  • Fill out the Detailed implementation of the solution and related sections.
  • Re-add the DesignDocReview label to this issue
  • Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Email strategy@expensify.com one last time to let them know the Design Doc is moving into the implementation phase
  • Implement the changes
  • Add regression tests so that QA can test your feature with every deploy (instructions)
  • Send out a follow up email to strategy@expensify.com once everything has been implemented and do a Project Wrap-Up retrospective that provides:
    • Summary of what we accomplished with this project
    • What went well?
    • What could we have done better?
    • What did we learn?

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @neil-marcellini

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 24, 2024
  2. melvin-bot commented on Jun 24, 2024

    @melvin-bot

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

  3. trjExpensify commented on Jun 25, 2024

    @trjExpensify
    Contributor

    @caitlinwhite1 @thienlnam is this on your radar? Will it need to be Internal?

    Adding it to #wave-control in the meantime. CC: @JmillsExpensify

  4. thienlnam commented on Jun 25, 2024

    @thienlnam
    Contributor

    Is there a photo of what the report title looks like in NewDot?

    IIRC this is partially expected. NewDot generates the report title based on the formula optimistically since it could be offline, but the thing it can't support is long report IDs, or anything that requires server side knowledge.

    However, if you are online it should just take the report name. So depending on the circumstances this is likely external

  5. heyjennahay commented on Jun 25, 2024

    @heyjennahay
    Contributor

    If I look at the reports in my personal online web NewDot they have the incorrect format

    image

  6. thienlnam commented on Jun 26, 2024

    @thienlnam
    Contributor

    Oh gotcha, so it's not just a visual bug in NewDot.

    Hmm, I was testing this on dev and it seems to work alright for me.
    Screenshot 2024-06-26 at 10 24 12 AM

    My only other guess is NewDot Test - Expensify a collect policy not a control policy?

  7. self-assigned this
    on Jun 26, 2024
  8. heyjennahay commented on Jun 26, 2024

    @heyjennahay
    Contributor

    @thienlnam can you please check your personal NewDot Test reports in NewDot? To confirm your theory about the Collect v Control workspace being the cause? My NL Test workspace is Collect but the US Test workspace has been Control for about a month now so if your theory is correct then I would expect to see a difference.

    That said, why would the formula not be applied to both Collect and Control workspaces (this feature applies to both types in OldDot today)? Also if the intention is to require you to upgrade to Control to use Report Formulas then I would still expect the default report title for Collect workspaces to show the short report ID and not the long. So I still think there is an issue that needs to be resolved.

  9. thienlnam commented on Jun 26, 2024

    @thienlnam
    Contributor

    I agree there's a bug here, just trying to isolate where the problem might be. It does seem to be a control policy so that rules out that theory.

    Screenshot 2024-06-26 at 1 20 03 PM

    So it looks like the report fields are not being returned into this policy - going to have some queries run to see why that is the case. This would be internal
    Screenshot 2024-06-26 at 1 24 43 PM

  10. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jun 26, 2024
  11. thienlnam commented on Jun 27, 2024

    @thienlnam
    Contributor

    Created an internal GH for a query request here

  12. 516 remaining items

  13. neil-marcellini commented on Feb 4, 2026

    @neil-marcellini
    Contributor
  14. neil-marcellini commented on Feb 5, 2026

    @neil-marcellini
    Contributor

    (Neil's AI Agent)

    Daily Update - Feb 5, 2026

    Key milestones:

    Unblocked today:

    Reviews completed:

    Still open:

    Neil

    Ok, interesting. I didn't really mean for my agent to do that, but it's a decent update. I'll probably post a more carefully reviewed update towards the end of my work day.

  15. neil-marcellini commented on Feb 5, 2026

    @neil-marcellini
    Contributor

    Polishing up the last details - today's update

  16. neil-marcellini commented on Feb 7, 2026

    @neil-marcellini
    Contributor
  17. neil-marcellini commented on Feb 10, 2026

    @neil-marcellini
    Contributor
  18. neil-marcellini commented on Feb 11, 2026

    @neil-marcellini
    Contributor
  19. neil-marcellini commented on Feb 11, 2026

    @neil-marcellini
    Contributor
  20. neil-marcellini commented on Feb 17, 2026

    @neil-marcellini
    Contributor

    I took a 4 day weekend but will do an update later today

  21. neil-marcellini commented on Feb 17, 2026

    @neil-marcellini
    Contributor

    Wrap up email sent with the subject Project Wrap-Up: Custom Report Names on New Expensify.

    Closing this! What a relief 😌 😄

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions