github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #6141] [Feature] Currency Redenomination Support #16857

New Issue
Closed
opened 2026-04-14 19:51:36 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-14 19:51:36 -05:00
Owner
Copy Link

Originally created by @ariqpradipa on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6141

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Hello, my country may soon undergo a major currency redenomination. Although it has not happened yet, there is a high chance it could be implemented. If it does occur, I'm concerned that it will significantly affect my existing ledger in Actual. The new currency format would drastically scale down values (e.g., 1000 becomes 1), which could scramble or invalidate the accuracy of my historical data.

I understand this is a very niche feature that may not be widely needed, but redenomination support or bulk value conversion would be extremely helpful in cases like this.

Is there currently any recommended approach or built-in functionality in Actual that can help convert all existing entries to the new denomination?

Describe your ideal solution to this problem

Ideally, we need a safe and controlled way to apply a global scaling factor to all historical data when a currency redenomination occurs. This could take several possible forms:

  1. Bulk Conversion Tool
    A dedicated feature that allows users to apply a multiplier or divisor (e.g., divide all amounts by 1000) across all transactions, budgets, accounts, and scheduled entries. This would help ensure historical accuracy without manually editing thousands of entries.

  2. One-Time Redenomination Wizard
    A guided workflow that:

    • Prompts the user to confirm the redenomination ratio
    • Shows a preview of the changes
    • Performs the conversion while creating a backup for safety
      This would reduce risk and make the process more user-friendly.

Any of these approaches would help users adapt their financial data safely in scenarios where a national redenomination occurs.

Teaching and learning

No response

Originally created by @ariqpradipa on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6141 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Hello, my country may soon undergo a major currency redenomination. Although it has not happened yet, there is a high chance it could be implemented. If it does occur, I'm concerned that it will significantly affect my existing ledger in Actual. The new currency format would drastically scale down values (e.g., 1000 becomes 1), which could scramble or invalidate the accuracy of my historical data. I understand this is a very niche feature that may not be widely needed, but redenomination support or bulk value conversion would be extremely helpful in cases like this. Is there currently any recommended approach or built-in functionality in Actual that can help convert all existing entries to the new denomination? ### Describe your ideal solution to this problem Ideally, we need a safe and controlled way to apply a global scaling factor to all historical data when a currency redenomination occurs. This could take several possible forms: 1. **Bulk Conversion Tool** A dedicated feature that allows users to apply a multiplier or divisor (e.g., divide all amounts by 1000) across all transactions, budgets, accounts, and scheduled entries. This would help ensure historical accuracy without manually editing thousands of entries. 2. **One-Time Redenomination Wizard** A guided workflow that: - Prompts the user to confirm the redenomination ratio - Shows a preview of the changes - Performs the conversion while creating a backup for safety This would reduce risk and make the process more user-friendly. Any of these approaches would help users adapt their financial data safely in scenarios where a national redenomination occurs. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-14 19:51:36 -05:00
GiteaMirror commented 2026-04-14 19:51:37 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 14, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:3530690340 --> @github-actions[bot] commented on GitHub (Nov 14, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#16857
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?