Skip to content

[Due for payment 2026-08-21] [CFI] Add Canadian Multiple Tax Export template to New Expensify for workspaces using CAD #97231

Closed

Description

@melvin-bot

Overview

When default export templates were migrated to New Expensify, we intentionally started with the most commonly used generic templates. The Canadian Multiple Tax Export template was not migrated over. The plan was to add the remaining templates based on customers' product usage.

Requested change

Automatically make the Canadian Multiple Tax Export template available in New Expensify for customers who have a workspace with the output currency set to CAD, so it isn't shown as clutter to non-CAD customers.

The existing template lives in Web-Expensify at lib/Integrations/defaultExportTemplates/multiple_tax_export.ftl. This should be a mostly backend change, similar to when the other default templates were added to New Expensify.

Context

  • Customers currently have to switch back to Classic to access the Canadian tax export, which we'd like to avoid encouraging.
  • Nikki Wines has offered to review the PR if a backend contributor picks this up — it should be fairly similar to when the other templates were added.

Reported in Slack.

Issue OwnerCurrent Issue Owner: @thelullabyy

Activity

  1. flaviadefaria commented on Jul 28, 2026

    @flaviadefaria
    Contributor

    Trying to find a BE contributor to help out.

  2. self-assigned this
    on Jul 28, 2026
  3. melvin-bot commented on Aug 4, 2026

    @melvin-bot
    Author

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  4. mitarachim commented on Aug 4, 2026

    @mitarachim

    Deploy Blocker #97748 was identified to be related to the PR #97255 that attempted to fix this issue.

  5. mitarachim commented on Aug 4, 2026

    @mitarachim

    Deploy Blocker #97749 was identified to be related to the PR #97255 that attempted to fix this issue.

  6. melvin-bot commented on Aug 4, 2026

    @melvin-bot
    Author

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  7. jponikarchuk commented on Aug 4, 2026

    @jponikarchuk

    Deploy Blocker #97760 was identified to be related to the PR #97255 that attempted to fix this issue.

  8. lanitochka17 commented on Aug 4, 2026

    @lanitochka17

    Deploy Blocker #97818 was identified to be related to the PR #97255 that attempted

  9. 48 remaining items

  10. thelullabyy commented on Aug 29, 2026

    @thelullabyy
    Contributor

    @mallenexpensify We have 4 regressions on this issue

    #97818
    #97748
    #97749
    #97760

  11. mallenexpensify commented on Aug 31, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @thelullabyy due $75 via NewDot

    yowza... I think I want to set the floor for regressions to 25% (ie. 50% reduction, twice) cuz we want contributors to fix the regressions and anything lower than that could lead to the issue being abandoned. Also.. lower than 25% would be $37.5 which would round to $50 so... the difference between that and $75 is negligible .

    @thelullabyy do we need/want a test case here?

  12. melvin-bot commented on Sep 1, 2026

    @melvin-bot
    Author

    @thelullabyy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  13. melvin-bot commented on Sep 3, 2026

    @melvin-bot
    Author

    @thelullabyy Huh... This is 4 days overdue. Who can take care of this?

  14. melvin-bot commented on Sep 4, 2026

    @melvin-bot
    Author

    @thelullabyy Eep! 4 days overdue now. Issues have feelings too...

  15. melvin-bot commented on Sep 4, 2026

    @melvin-bot
    Author

    @thelullabyy Eep! 4 days overdue now. Issues have feelings too...

  16. mallenexpensify commented on Sep 4, 2026

    @mallenexpensify
    Contributor

    @thelullabyy do we need/want a test case here?

  17. thelullabyy commented on Sep 6, 2026

    @thelullabyy
    Contributor
  18. laurenreidexpensify commented on Sep 7, 2026

    @laurenreidexpensify
    Contributor

    $75 approved @thelullabyy New Expensify

  19. mallenexpensify commented on Sep 7, 2026

    @mallenexpensify
    Contributor

    @thelullabyy can you use the exact C+ checklist? I have automation to key off ## Regression Test Proposal in the comment. Thx.

    ^ Test case created. Thx

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 productionDailyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions