Many employers use Alight Solutions as their 401(k) and benefits provider. Alight operates employer-specific login portals (e.g., worklife.alight.com/[employer-slug]/login), which means each employer has a distinct URL rather than a single shared login page. Users would like the ability to connect their Alight-managed retirement accounts to Piere so that their 401(k) balances and transactions are automatically […]

Allow users to import historical transactions in bulk by uploading a CSV or spreadsheet file. This is especially useful when switching between data providers (e.g., from MX to Plaid) where the new provider only retrieves a limited history window, leaving a gap in older transaction data. Users who have downloaded or reformatted their historical transactions […]

Add the ability to export all net worth history and associated account balances to a CSV file. Then, allow an edited CSV to be imported to Piere to update the existing net worth data.

Users who created their Piere account natively (with a phone number and password) currently have no way to add multi-factor authentication (MFA) or switch to a more secure login method such as Google SSO. It would be valuable to support: (1) MFA/2FA for native accounts (e.g. via authenticator app or SMS), and (2) the ability […]

Users with retirement accounts managed through Alight Retirement for AIG are unable to connect their accounts because the AIG-specific Alight portal URL (https://worklife.alight.com/ah-angular-afirst-web/#/web/aig/login) is not currently supported. Alight Retirement operates employer-specific URLs for different companies, and the AIG version is not listed as a supported institution. Adding support for this URL would allow AIG employees […]

When viewing your net worth in Piere, it would be useful to be able to tap or click into the total to see a breakdown of which accounts and balances are contributing to the calculation. This would make it easier to spot anomalies (like a duplicated account inflating the number), verify accuracy, and understand exactly […]

When a user’s income budget category is exceeded, the current notification message says “Adjust other categories in your budget to still end the month under budget.” This phrasing doesn’t make sense for income – exceeding an income budget is a positive event (you earned more than expected), not a spending problem. A smarter alert for […]

It would be useful to see a grand total of spending per category across a full year (or custom date range), not just month by month. This would help users understand their annual spending habits at a glance and make it easier to plan budgets for the following year. Currently, the “Transactions by Category” view […]

When a loan is manually added to Piere, users should be able to edit the loan details after initial submission – including fields like the minimum payment amount. Currently, once a manual loan is submitted, certain details (such as minimum payment) cannot be updated, leaving users unable to keep their loan information accurate over time. […]

Users want the ability to manually trigger account refreshes more frequently – ideally daily or on-demand – rather than being limited to approximately once per week. Currently, even when accounts show a “green” connected status, the last sync can be 2-3 days old and triggering a manual refresh is restricted in frequency. This is especially […]

Users who have created custom transaction categories currently have no way to delete or edit them after creation. Adding the ability to rename, merge, or delete custom categories would give users more control over how they organize their transactions and keep their category lists clean over time.

When transactions are excluded from the budget (e.g. investment account activity, robo-advisor transfers), they still appear in the transaction review stack, requiring users to manually dismiss them one by one. It would be useful to have a way to auto-accept or bulk-dismiss these excluded transactions so that the review queue only surfaces transactions the user […]

Currently, Piere shows net worth and percentage change in investment account values, but does not calculate true investment performance or return on investment (ROI) over time. Users would like to see metrics such as time-weighted return, total gain/loss, and annualized performance for their investment accounts – going beyond simple value change to reflect actual portfolio […]

Allow users to create and manage multiple households or separate account spaces within a single Piere login. This would enable users to keep different sets of accounts (e.g., personal vs. business, or separate financial entities) fully isolated from one another — with separate transaction histories, budgets, and net worth tracking — without needing to create […]

Currently if I get a new credit card from the same institution that is already connect to piere I cannot add it to Piere without connecting to the institution again as a new connection. We should be able to just refresh the institution to add new accounts under the same login. More discussion about this […]

Currently, Piere requires users to log in with their phone number and password. It would be useful to also support logging in with an email address, giving users the flexibility to choose their preferred credential. This would improve accessibility for users who prefer email-based authentication or who have trouble remembering which phone number is associated […]

On the Piere web/desktop app, the profile icon and account controls (including logout) are currently located at the bottom of the sidebar. Most web applications follow the convention of placing these controls in the top-right corner of the screen, which is where users instinctively look for them. Moving the profile menu, logout button, and related […]

When filtering transactions by merchant in the Transactions screen, the list of available merchants should be displayed in alphabetical order. Currently the list has no apparent sorting, making it difficult to locate a specific merchant – especially for users with a large number of merchants. Alphabetical sorting would make the filter much easier to use.

Users would like the ability to manually designate which accounts contribute to the “Savings” total displayed on the dashboard, regardless of account type. For example, a checking account used primarily for saving (such as an investment app’s cash account) would ideally count toward the Savings figure. Currently, only accounts classified as Savings under Banking contribute […]

When setting up a Move with a goal like “pay off high interest credit cards,” users would like the ability to manually select which specific accounts or cards are targeted – rather than having Piere choose automatically. This would give users more transparency and control over how their money is directed, especially when the app’s […]

Users would like the ability to mark an account as “closed” to indicate it is no longer active, without fully removing it from Piere. This would allow closed accounts to remain visible for historical reference (e.g., past transactions, net worth history) while being clearly distinguished from active accounts in the UI. This is especially useful […]

We can toggle whether or not a purchase has been reviewed. This should be reflected in filtering to quickly look at unreviewed transactions

I have a lot of cash transactions in foreign currency, and I would love if I could add those into Piere and have them automatically converted to USD. At the moment I have to take the extra step of putting amounts into a currency conversion app before entering into Piere, and since it’s kind of […]

It would be useful to be able to exclude specific categories or tags from reports. For example, a user might want to create a report showing only discretionary spending by hiding a “Bills” category, or exclude transactions tagged as “travel” (funded from sinking funds) to get a cleaner view of their regular monthly budget. This […]

Allow users to filter their financial data by year-to-date (YTD) and view a running total of income vs. expenses across that period – not just a month-by-month breakdown. This would give users a clearer picture of their overall financial progress throughout the year and complement the existing monthly view.

When setting up a transaction categorization rule (e.g., “always categorize this vendor as Groceries”), users would like the option to apply that rule retroactively to all existing transactions from the same vendor – not just future ones. This would save significant time when a vendor has many historical transactions that need to be recategorized, and […]

Allow users to manually edit the rolled-over amount on rollover budget categories. Currently, rollover budgets automatically carry forward the surplus or deficit from the previous month, but there is no way to override or manually set the rollover amount. An edit option (e.g., a pencil icon on the budget category detail screen) would let users […]

When a budget amount is changed, the update currently applies retroactively to all past periods. It would be useful to have budget amounts locked to the period they were set in, so users can see what their budget was at any given point in time and whether they were within budget based on the original […]

On the budget tab in the web/browser version, clicking on a category’s monthly allowance amount currently navigates to the monthly view for that category. It would be more intuitive if clicking the number directly opened an inline edit field to adjust the monthly allowance – similar to how spreadsheets work. This would save users from […]

I have a handful of manual transactions that I have created that I did not assign an account to. It is listed as NA in the web browser version under account. It would be nice if all these accounts gets sorted into a NA manual account and under transactions, I can filter by NA account.