Users should be able to hide or remove specific sub-categories from the transaction category picker so they don’t accidentally use the same sub-category name under different parent categories. Currently, some sub-category names (like “Groceries”) appear under multiple parent categories (e.g., both “Groceries” and “Food and Dining”), which can lead to transactions being split across duplicate […]

Currently, transactions categorized as “Transfer” – such as automatic mortgage payments – are excluded from the Budget screen. This means large recurring expenses like mortgage payments are invisible in budget tracking, even though they are a significant monthly outflow. It would be very useful to have the option to include specific Transfer-type transactions in the […]

Allow users to invite a spouse, partner, or family member to access the same Piere household. This would enable couples or families who share bank accounts and finances to both have their own login while viewing and managing the same connected accounts, transactions, budgets, and net worth data together. Currently, each user must create their […]

When a loan or account (e.g., a mortgage that has been sold or paid off) is no longer active, there is currently no way to mark it as closed or archive it. These accounts continue to appear as disconnected in the institutions list, creating clutter and confusion. It would be helpful to have the ability […]

It would be useful to receive email (or push) notifications when a bill or recurring expense is coming due. Users could opt in and choose which bills or subscriptions they want to be alerted about, and how far in advance. This would help users stay on top of due dates without having to open the […]

When using the “Contact the Team” feedback form on the web version of Piere, there is currently no option to attach a screenshot or image. Adding the ability to attach screenshots would make it much easier for users to show exactly what they’re seeing when reporting a bug or issue, leading to faster and more […]

Users who create custom sub-categories in Piere currently have no way to remove or delete them if they were added by mistake or are no longer needed. It would be helpful to have a “Delete” or “Remove” option on custom sub-categories, similar to how custom categories can be managed. This would help users keep their […]

Allow users to set a persistent, custom sort order for their accounts in the Net Worth view. Currently, accounts may appear in a different order each session, making it difficult to reference balances in a consistent way across external tools or workflows. A static, user-defined ordering would let users quickly find and reference account balances […]

Some modern fintech cards (such as those issued through partners like Evolve Bank & Trust) operate without traditional usernames and passwords – authentication is handled entirely through their mobile app rather than credential-based login. This makes it impossible to connect these accounts through standard Plaid or MX bank-linking flows, which require credentials to authenticate. It […]

With the introduction of 530(a) “Trump Accounts” (also known as MAGA accounts – Money Account for Growth and Advancement) through recent US legislation, users are asking to connect and track these new tax-advantaged child savings accounts in Piere. This would involve adding support for 530(a) account types in Piere’s account classification system and enabling connections […]

Currently, when a budget category goes negative (overspent), the deficit is limited to a single month and does not roll forward into subsequent months. Users want the ability to have negative budget balances extend beyond one month – similar to how positive rollover budgets carry a surplus forward. This would give a more accurate picture […]

When switching between apps or returning to Piere after it has been left open in the background, the app should display a privacy screen (e.g. a blurred or opaque overlay) to prevent sensitive financial information from being visible in the app switcher or to bystanders. This is a common privacy feature in banking and finance […]

Allow users to track self-custody cryptocurrency wallets by importing a blockchain wallet address (e.g. an Ethereum or Bitcoin public address) directly into Piere, rather than only being able to connect through a centralized exchange (CEX) like Coinbase or Kraken. This would let users who hold crypto in hardware wallets, MetaMask, or other non-custodial wallets see […]

Allow multiple users (e.g., spouses or partners) to access the same Piere household under their own login. Currently, each person must create their own separate account and household. Many couples and families track shared finances together – being able to log in independently and view the same accounts, transactions, budgets, and net worth would make […]

Allow users to resize or customize the size and layout of widgets on the Piere dashboard – for example, making the net worth card smaller so more information fits on screen at once. This would give users more control over their dashboard experience and let them prioritize the data that matters most to them.

It would be helpful to have a way to view all connected accounts at a glance – either as a widget or section on the main dashboard, or as a dedicated entry in the sidebar navigation. This would allow users to quickly check balances across all their accounts without navigating away from the main view. […]

For users who rely heavily on credit cards, it would be extremely useful to have dedicated tracking of credit card billing cycles – specifically showing the current statement balance and the upcoming payment due date for each card. Most personal finance tools show credit card balances in real time but don’t surface the statement amount […]

Allow users to toggle off the chat/AI bot that appears on the app’s opening or splash screen. Some users prefer a cleaner launch experience without the bot prompt. A simple toggle in Settings would give users control over whether this feature is shown at startup.

When transactions are automatically categorized, it would be helpful to have an option to restrict auto-categorization to only categories that have an active budget set up. This would prevent transactions from landing in unbudgeted categories by default, increasing the likelihood that they are correctly categorized from the start and reducing the amount of manual re-categorization […]

When a transaction’s category is changed, the overall budget view should update automatically when you navigate back to it – without needing to manually hit refresh. Currently, after making a category change, users return to the budget overview and see stale data until they manually refresh the page or view. Real-time updates would make the […]

Allow users to expand the budget to show all individual transactions in a single scrollable view, organized by their own custom categories rather than Piere’s default category headings. This would make it easier to scan all spending at a glance without having to drill into each category separately. Useful for users who want a full […]

Allow users to categorize transactions by dragging and dropping them directly into the desired category. This would provide a faster, more intuitive way to organize transactions compared to the current tap/click-to-edit flow – especially useful when reviewing multiple transactions at once. A drag-and-drop interface would make bulk categorization feel more natural and reduce the number […]

Some users prefer the previous home screen experience – with widgets displayed on the dashboard and the main menu accessible directly from the home screen – over the current AI-driven home screen. This request is to offer an option (or revert) to the widget-based home screen layout with dashboard-level menu access, giving users more control […]

Some users prefer to navigate and manage their finances without AI-assisted suggestions or prompts. It would be helpful to have a setting that allows users to disable or opt out of the in-app AI assistant entirely, so they can use Piere on their own terms without AI interactions.

Currently, investment accounts are classified broadly using asset-type labels like “US Stocks”, “International Stocks”, and “Bonds”. Many users would prefer account-level classifications such as “Brokerage”, “Other”, and “Retirement” to better understand the purpose and structure of their holdings at a glance. Additionally, target-date funds (e.g., TDF 2055) are displayed as a single line item. It […]

Allow users to create fully custom budget categories that are not tied to transaction data. Users would manually enter the amount they plan to spend or pay for each category at the start of each month – for example, credit card balances due, recurring services (lawn care, house cleaning), and other planned expenses. This would […]

Currently, rollover budget calculations are finalized at month-end and do not reflect edits made to transactions after the month has closed (such as recategorization or amount corrections). This means the carried-over balance can be inaccurate if any transactions are changed retroactively. The request is for rollover budgets to dynamically recalculate whenever a past transaction is […]

Currently, transaction rules can only be viewed and managed from the mobile app. It would be great to have full access to transaction rules – including creating, editing, and deleting them – from the web version of Piere at beta.piere.com. This would make it easier for users who primarily manage their finances on desktop to […]

When a user edits or recategorizes a budget category, the change currently only applies to the month in which the edit is made. There is no way to apply the updated category to past months without manually editing each one. This request is for a “Recalculate Budget” option (or similar) that would allow users to […]

Allow users to bulk review, approve, or dismiss transactions from the web/desktop version of Piere, similar to the swipe-to-review (Transaction Stacks) experience on mobile. This would make it much faster to process large numbers of transactions on desktop, where a mouse and keyboard interface lends itself well to batch actions. Use cases include reviewing many […]