github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Add Investment Account Support for Pluggy.ai Bank Sync #2206

New Issue
Closed
opened 2026-02-28 20:06:32 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 20:06:32 -06:00
Owner
Copy Link

Originally created by @gustavostz on GitHub (Jun 15, 2025).

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?

The current Pluggy.ai integration successfully syncs Brazilian bank accounts and credit card accounts (thank you @lelemm for this amazing contribution! 🎉). However, investment accounts were not included in the initial implementation. Brazilian users who have investment accounts at their banks would benefit from being able to track their complete financial picture, including their investment portfolios, within Actual Budget.

Basically, I would love to see the Pluggy.ai integration extended to include support for investment accounts.

Describe your ideal solution to this problem

Suggested Implementation Approach

Based on the existing code structure, here are some areas that might need enhancement (not entirely sure, but it seems to be the path):

1. Account Name Display (CreateAccountModal.tsx)

The current implementation differentiates between BANK and CREDIT accounts. We could extend this to include INVESTMENT accounts:

// Current approach (line 177)
name: `${oldAccount.name.trim()} - ${oldAccount.type === 'BANK' ? oldAccount.taxNumber : oldAccount.owner}`,

// Could be extended to:
name: `${oldAccount.name.trim()} - ${
  oldAccount.type === 'BANK' ? oldAccount.taxNumber : 
  oldAccount.type === 'INVESTMENT' ? `Investment - ${oldAccount.owner}` : 
  oldAccount.owner
}`,

2. Balance Calculation (CreateAccountModal.tsx)

Investment accounts might have different balance structures:

balance:
  oldAccount.type === 'BANK'
    ? oldAccount.bankData.automaticallyInvestedBalance + oldAccount.bankData.closingBalance
    : oldAccount.type === 'INVESTMENT'
    ? oldAccount.investmentData?.totalBalance || oldAccount.balance
    : oldAccount.balance,

3. Transaction Processing (app-pluggyai.js)

The transaction processing logic could be enhanced to handle investment-specific transaction types and ensure they are properly formatted for Actual Budget.

🙏 Additional Context

As mentioned by @BrunoPradoBR in the #4049 PR discussion, the Pluggy.ai API already provides investment account data in the payload.

Thank you for considering this feature request! The Pluggy.ai integration has already been incredibly valuable for the Brazilian Actual Budget community, and this enhancement would make it even better.

Teaching and learning

No response

Originally created by @gustavostz on GitHub (Jun 15, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? The current Pluggy.ai integration successfully syncs Brazilian bank accounts and credit card accounts (thank you @lelemm for this amazing contribution! 🎉). However, investment accounts were not included in the initial implementation. Brazilian users who have investment accounts at their banks would benefit from being able to track their complete financial picture, including their investment portfolios, within Actual Budget. Basically, I would love to see the Pluggy.ai integration extended to include support for investment accounts. ### Describe your ideal solution to this problem ## Suggested Implementation Approach Based on the existing code structure, here are some areas that might need enhancement (not entirely sure, but it seems to be the path): ### 1. Account Name Display (`CreateAccountModal.tsx`) The current implementation differentiates between BANK and CREDIT accounts. We could extend this to include INVESTMENT accounts: ```typescript // Current approach (line 177) name: `${oldAccount.name.trim()} - ${oldAccount.type === 'BANK' ? oldAccount.taxNumber : oldAccount.owner}`, // Could be extended to: name: `${oldAccount.name.trim()} - ${ oldAccount.type === 'BANK' ? oldAccount.taxNumber : oldAccount.type === 'INVESTMENT' ? `Investment - ${oldAccount.owner}` : oldAccount.owner }`, ``` ### 2. Balance Calculation (`CreateAccountModal.tsx`) Investment accounts might have different balance structures: ```typescript balance: oldAccount.type === 'BANK' ? oldAccount.bankData.automaticallyInvestedBalance + oldAccount.bankData.closingBalance : oldAccount.type === 'INVESTMENT' ? oldAccount.investmentData?.totalBalance || oldAccount.balance : oldAccount.balance, ``` ### 3. Transaction Processing (`app-pluggyai.js`) The transaction processing logic could be enhanced to handle investment-specific transaction types and ensure they are properly formatted for Actual Budget. ## 🙏 Additional Context As mentioned by @BrunoPradoBR in the #4049 PR discussion, the Pluggy.ai API already provides investment account data in the payload. Thank you for considering this feature request! The Pluggy.ai integration has already been incredibly valuable for the Brazilian Actual Budget community, and this enhancement would make it even better. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:06:32 -06:00
GiteaMirror commented 2026-02-28 20:06:32 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 15, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!

@github-actions[bot] commented on GitHub (Jun 15, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 -->
GiteaMirror commented 2026-02-28 20:06:33 -06:00
Author
Owner
Copy Link

@AugustoPinheiro commented on GitHub (Jun 17, 2025):

https://github.com/actualbudget/actual/pull/5184

@AugustoPinheiro commented on GitHub (Jun 17, 2025): https://github.com/actualbudget/actual/pull/5184
GiteaMirror commented 2026-02-28 20:06:33 -06:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 18, 2025):

Hi @gustavostz,

Thanks for raising this feature request and for your engagement with the project.

After reviewing it carefully, we’ve decided that this is not something we’ll support in the core codebase—now or in the future. The main reason is that investments from Pluggy.ai don’t have transactions, and modeling each investment as a fake bank transaction doesn’t align with the design principles we want to maintain. It would introduce functionality that feels out of place and could create long-term maintenance issues.

This type of customization is exactly what we want to enable through our upcoming plugin system. Once that’s available, it’ll provide a clean and maintainable way to implement features like this without impacting the core.

Thanks again for your understanding!

@lelemm commented on GitHub (Jun 18, 2025): Hi @gustavostz, Thanks for raising this feature request and for your engagement with the project. After reviewing it carefully, we’ve decided that this is not something we’ll support in the core codebase—now or in the future. The main reason is that investments from Pluggy.ai don’t have transactions, and modeling each investment as a fake bank transaction doesn’t align with the design principles we want to maintain. It would introduce functionality that feels out of place and could create long-term maintenance issues. This type of customization is exactly what we want to enable through our upcoming plugin system. Once that’s available, it’ll provide a clean and maintainable way to implement features like this without impacting the core. Thanks again for your understanding!
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#2206
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?