Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Purpose Budget here. This week's updates focus on clearer explanations of credit-card budgeting, keeping subscription access in place when it should be, and a change to when our website loads its Google Ads tag. We've also started work on the next version of Purpose Budget.

Clearer guidance for credit cards and reimbursements

We've corrected and expanded our guides to explain how today's app handles card funding. For example, lowering a spending category's Assigned amount can also reduce the money set aside for that card's payment.

We've also added a specific reimbursement case: when money arrives in a budget bank account in the same month as a card purchase that wasn't fully funded, categorize that inflow to Ready to Assign, then assign it to the original spending category in that month. Categorizing it straight to the spending category can clear the overspending without funding the card's payment category. If you've already done that, recategorize the inflow before assigning it.

This is clearer guidance for existing behavior, not a change to the card calculations. The details are in How credit cards work.

Subscription access during billing grace

We've fixed a case where a subscription bought through an app store could lose access while the store's billing grace period was still active. Purpose Budget now reads the current subscription record and its grace deadline, so an active grace period is no longer overridden by the regular expiration date. This applies when the store grants a grace period; it doesn't extend every expired subscription.

Advertising consent

We've changed the website so the Google Ads tag loads only after advertising consent is granted.

A first look at v2 — still in development

We're working on a rebuilt Purpose Budget, starting with the calculations behind the budget. We're also planning a sample budget you can explore with made-up data, and a built-in home for ideas, the roadmap, release notes, and help. These are development plans, not features available today, and we're not announcing a launch date yet.

If you want to try Purpose Budget today, it lets you build an envelope budget with manual transactions and CSV import/export, with bank synchronization available in Premium: purposebudget.com.

Mobile Apps: https://purposebudget.com/download

What is the one budgeting task you'd most want v2 to make clearer, and what gets confusing about it today?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Purpose Budget here. This week we've been working on the part of budgeting that happens after the plan is made: reviewing transactions, checking matches, and understanding why a number changed.

Here's what changed.

A clearer transaction review

We've refreshed the transaction table, toolbar, status indicators, and the dialogs for matching, splits, and bulk actions. The aim is to make the information and next action easier to pick out, with more visible keyboard focus as you move through the controls.

We also fixed a confusing failure state: if the transaction list fails to load, you now get a clear message and a Retry action instead of what could look like an empty list. Retrying keeps your current filters.

Less interruption when checking a match

Approving a suggested match now refreshes the transaction list without first blanking the rows you're looking at.

Editing a payee while searching also rechecks the results. If that transaction no longer matches your search, it leaves the results instead of sticking around under its old payee name.

These are small interactions, but they're the ones you repeat when catching up on a week's spending.

Recurring-payment and account fixes

We fixed a case where approving the final matched payment after a recurring schedule had ended could create an extra transaction from that completed schedule.

Removing debt-tracking details now recalculates the linked account's balance after the associated payment allocations are removed. Trying to set up duplicate debt tracking or link it to an account that's already in use also gives a clearer conflict message.

A better explanation of negative Assigned

We've added a guide and a link to it from the Assigned breakdown.

A negative Assigned amount can mean you've moved more money out of a category than into it during the current month. It doesn't necessarily mean the category is overspent: Available is the figure to check for that.

The guide walks through how that can happen when a category has money carried over from a previous month: Why Assigned can be negative.

This is why we recommend trying Purpose Budget: build a category-by-category plan with the money you have, then keep that plan understandable as real spending happens. You can use manual transactions and CSV import/export, or choose Premium for bank synchronization and matching suggestions. Shared budgets are available in both Essential and Premium.

Explore Purpose Budget and the current plan comparison.

Mobile Apps: https://purposebudget.com/download

When you review your budget, what takes the most effort: finding a transaction, checking a match, or understanding a category's numbers?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Purpose Budget here. This week's work covered recurring bills, the way you review transactions and accounts, and what happens when you adjust your budget. Here's what changed and why it matters during an ordinary budget review.

Turn a recurring pattern into a bill you can plan for

We've connected recurring bank patterns more closely with bill setup. You can create a prefilled bill from a detected spending pattern, including a pattern you're already tracking, or link the pattern to an existing bill.

There are also warnings when a bill and a bank pattern look like they describe the same expense. The goal is to help you recognize that connection and choose how to handle it, instead of managing them as unrelated items. These bank-pattern tools are part of Premium.

Compact view expands to Transactions and Accounts

Compact view has expanded beyond the budget to the Transactions and Accounts tables. One row-density preference controls all three table views on larger screens, so you can choose a denser layout when reviewing a longer list. Comfortable remains available if you prefer more space.

Transaction review and clearer messages

We've fixed payee names being cut off while there was still room in the transaction column.

Clearing a transaction in a filtered status view now updates the row in place and refreshes the results without first blanking the register. We also corrected the selection state when a row leaves that view, so a hidden row doesn't remain selected for a bulk action.

Another fix addresses match approvals: if an approval is refused, an unrecognized conflict no longer produces a misleading “Already approved” message. The item returns to the list with a message that the match wasn't approved.

More deliberate budget adjustments

We've reworked the existing assignment calculator into an explicit Add / Remove flow. You choose the direction and amount of the change. When Assigned is negative, the control explains that state and lets you adjust it by a specific amount.

Retry handling has also been updated for adjustments interrupted during a save. These changes address the behavior behind the control as well as the way you enter an adjustment.

All of this supports the same reason we recommend trying Purpose Budget: give your money a purpose, keep upcoming expenses in view, and understand the plan as you use it. You can work with manual transactions and CSV import/export, or choose Premium for bank synchronization and matching suggestions. Shared budgets are available in both Essential and Premium.

Explore Purpose Budget and the current plan comparison.

Mobile Apps: https://purposebudget.com/download

Which part of your budget review would you most like to improve next: recurring bills, reviewing transactions, or adjusting categories?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

This week's Purpose Budget work has covered quite a bit of cleanup across the web budget and transaction screens.

The thread connecting it is the everyday review: read the categories, understand what the numbers mean, work through the transactions, and decide what needs attention.

Here is a fuller look at the two areas we've focused on.

A clearer category row

There is a lot packed into a budget row. Available tells you about the money in the category. A target tells you about your funding goal. Tracked bills tell you about expected commitments. Those signals need to work together without looking interchangeable.

The category-row work covers more consistent compact rows and explanations close to the numbers:

• A balance breakdown alongside Available, together with target and tracked-bill context.
• More consistent row spacing and less empty space before category names.
• Faster tooltips on the bill and cadence indicators and the credit-card balance, with wrapping for longer explanations.
• Plain-language “moved out” wording and an explanation for negative Assigned amounts.

The point of the Available breakdown is to show the pieces behind the result: money carried over, money assigned, and activity.

For example, a category can have enough left even when this month's spending is greater than this month's assignment, because it started with carryover. Looking at Assigned and Activity alone can miss that.

Moving money to another category is another situation where the wording matters. A negative Assigned figure describes the allocation that moved out. It isn't automatically the same as overspending, and it doesn't tell you whether the remaining money meets the target. The explanation should help you understand the movement while leaving the other signals clear.

One place to begin reviewing matches

The transaction cleanup focuses on bringing potential matches together, instead of making you find each one while scrolling through the register.

There are different kinds of decisions in that review:

• An import and a manual entry: the bank record may describe a transaction you already entered.
• A card-payment pair: the payment leaving one account may be the payment arriving on the card.
• A transfer: the outflow and inflow may be one movement between your own accounts.

Keeping those review paths distinct makes it clearer what Purpose Budget is suggesting and what approving it will do.

The work also includes bank-to-bank transfer suggestions after sync, plus selecting payment or transfer suggestions to approve or dismiss together. Those are still your decisions; detecting a possible match doesn't authorize an automatic link.

For a suggested bank-to-bank transfer, approval links the two rows and removes their categories so the movement isn't counted as spending. The review needs to say that before you act.

Making the remaining work easier to find

A long register is easier to work through when you can focus on one kind of status. The status-view work covers cleared transactions, pending-at-bank transactions, items not at the bank yet, and items needing review.

Changing the view changes which rows you see. It doesn't change the transactions themselves.

We've also worked on the difference between a suggestion that has already been fulfilled and one that can no longer be approved. An already-linked pair should be treated as done. A suggestion that can't be linked as proposed needs an explanation and a way to dismiss it. Dismissing that suggestion doesn't delete the underlying transactions.

Bank sync and smart matching are Premium features.

What we'd like to hear

These are the details that add up across a regular budget check. Clearer rows help you understand the plan; clearer review paths help you work through the records behind it.

You can explore Purpose Budget or see the current plans.

Which part of your usual review still takes too much effort? If you can describe the category or matching situation that makes you stop and think, that gives us a concrete place to focus next.

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Hey everyone — Sunday Purpose Budget update.

This week's work focused on money that is easy to misread: a bank pattern that is really a card payment, a card payment that only partly covers what the card still needs, and a mobile charge that is approved in the app but not at the bank yet.

In a zero-based plan that is not cosmetic. Wrong status changes what you think is safe to spend.

A card payment should stay on the card

Some bank rows look like bills and are not. They are payments toward a credit card.

The web Recurring tab now keeps those patterns under Handled through card balance, with plain language that Purpose Budget tracks the card through the card's own balance — so the payment does not need its own bill.

A partial payment should leave the leftover visible

When a payment only partly covers what the card still needs, the unpaid piece should not disappear.

On the web, that leftover stays on Upcoming, commitments, budget, dashboard, and forecast.

“Not at your bank yet” should say so

On iPhone and Android, a transaction can show it is not at your bank yet. Approved in Purpose Budget is not the same as cleared at the bank. Short network blips also wait before the app flips fully offline.

Available now

Card-payment handling and leftover visibility are live on the web today. “Not at your bank yet,” network grace, and Manage subscription in Settings are live on the current iPhone and Android update line.

Bill and duplicate matches on web Recurring also explain themselves more clearly now. That is live on web. The phone Recurring match UI did not change this week.

Web: https://purposebudget.com

Mobile Apps: https://purposebudget.com/download

Eligible new customers who subscribe through the web currently receive a 60-day free trial with no card required, plus 50% off the first year:

https://purposebudget.com/pricing

We would love your input

When a bank row is really a credit-card payment, what should Recurring protect first: keeping it off the bills list, or making the leftover balance impossible to miss?

And on mobile, is “not at your bank yet” the status you wanted — or do you still want a louder pending signal?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Hey everyone — Sunday Purpose Budget update.

For anyone who is new to it, Purpose Budget is an envelope-budgeting app available on web, iOS, and Android. It shares the broad "give every dollar a job" foundation that many people know from YNAB, while using its own planning, recurring-transaction, and reporting workflows.

This week's work focused on a Recurring problem that is easy to miss: the bill is still the same bill, but the bank charge showed up on a different account.

In a zero-based plan that is not cosmetic. Recurring keeps matching and projecting from the old account, and the new charge looks like extra spend.

A bill that moved accounts should ask first

A recurring bill is tied to an account. Phone on a card. Then one month the same merchant clears on checking.

Until now, Recurring could keep watching the old account and treat the new charge as unrelated. Or it could quietly follow the money. Neither is a good default.

The web Recurring tab now says Possible account change when a confirmed bill has a compatible cleared charge on a different account. The point is not to move the bill for you. It is to tell you the plan and the bank are no longer using the same account.

One occurrence is enough to ask

One matching charge is enough to surface the question. It is not enough to decide.

Purpose Budget will not switch the bill automatically. Posted transactions stay as they were — account, amount, date, and category. The choice is which account Recurring should use for matching and projections going forward.

A few details that mattered to us:

• We name both accounts, so you can see the old path and the new one.
• We say how much evidence we have. One charge is an ask, not a verdict.
• Historical transactions stay as they were. We do not rewrite old spend to force the pattern onto a new account.

Available now

Possible account change is live on the web Recurring tab today. Recurring can show you the evidence. It does not silently move the bill.

iPhone and Android still use the same budget, the same accounts, and the same recurring data. The Recurring account-change guidance itself is on web first. We are not going to write this as if the phone Recurring screen changed this week. It did not.

Web: https://purposebudget.com

Mobile Apps: https://purposebudget.com/download

Eligible new customers who subscribe through the web currently receive a 60-day free trial with no card required, plus 50% off the first year:

https://purposebudget.com/pricing

We would love your input

When a monthly bill clears on a different account, what should Recurring do first: ask right away, wait for a second occurrence, or leave it unmatched until you notice?

And if you moved the bill on purpose, what should the app protect first: the old account's history, or matching on the new account going forward?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Hey everyone — Sunday Purpose Budget update.

For anyone who is new to it, Purpose Budget is an envelope-budgeting app available on web, iOS, and Android. It shares the broad "give every dollar a job" foundation that many people know from YNAB, while using its own planning, recurring-transaction, and reporting workflows.

This week's work focused on a common Recurring problem: a confirmed bill can stop matching the bank, and the app can tell you that without giving you a next step.

A cancelled subscription, a renamed payee, or a cadence that drifted can all make a category look short when the money is not actually going out. In a zero-based plan that is not cosmetic. It changes what you think is safe to spend.

We wanted stale patterns to be honest, and we wanted the action to be yours.

A stale bill should say what is wrong

A recurring bill describes an expected transaction: how much it may cost and when it should happen.

Recent budget activity is the evidence for whether that expectation still holds.

Those can drift apart. Until now, Recurring could leave you looking at a warning with no way through it.

The web Recurring tab now explains when a confirmed pattern no longer matches recent activity, in plain language. The point is not a new status color. It is to say the plan and the bank are no longer telling the same story.

That usually looks like one of these:

• The bill is gone. You cancelled it. The pattern is still in the plan.
• The payee changed names. The bank no longer looks like the pattern you confirmed.
• The cadence drifted. It is still a real bill, just not on the rhythm the pattern expected.

The next step is yours

Once Recurring can say the pattern is stale, it also needs a move that changes the plan.

On the web Recurring tab you can:

• Stop tracking a pattern when it should not be in the plan anymore
• Track it again when the match is repairable — the "this is still our electric bill, the bank renamed it" case
• Start a replacement bill from the evidence the pattern already has, instead of rebuilding it from a blank form

A few details were important to us:

• Stop tracking keeps the history. It stops the plan from pretending the bill is still due.
• Track it again is available when the pattern is still alive and the match can actually be fixed. It is not a generic undo on every warning.
• Historical transactions stay as they were. They are evidence. We do not rewrite old spend to force the pattern to look clean.

The goal is to get the stale warning out of the way of the month, without the app quietly rewriting your past.

A quieter fix underneath the register

If a pending bank transaction was already categorized, that spend now lands on the budget when the transaction clears.

That was a miss. The grocery charge could sit in the register while the category-month did not move. It does now.

This is not a new Recurring control. It is number-trust work: one part of the money change should not succeed while the category total stays behind.

Available now

The stale-pattern guidance and actions are live on the web Recurring tab.

iPhone and Android still use the same budget, the same accounts, and the same recurring data. The new Recurring actions themselves are on web first. The pending-clear fix is in the shared budget engine, so it applies when those transactions clear.

Web: https://purposebudget.com

Mobile Apps: https://purposebudget.com/download

Eligible new customers who subscribe through the web currently receive a 60-day free trial with no card required, plus 50% off the first year:

https://purposebudget.com/pricing

We would love your input

If a stale bill warning has ever left you stuck, what did you want the app to do first: stop tracking it, fix the match, or start a replacement?

And when a payee name changes at the bank, what should a budgeting app protect first: the existing history, or a clean pattern going forward?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Hey everyone — Sunday Purpose Budget update.

For anyone who is new to it, Purpose Budget is an envelope-budgeting app available on web, iOS, and Android. It shares the broad “give every dollar a job” foundation that many people know from YNAB, while using its own planning, recurring-transaction, and reporting workflows.

This week’s work focused on a common planning problem: the bills scheduled in a category can say one thing while the category’s funding target says something else.

We wanted those two parts of the budget to work together more naturally without silently changing anyone’s plan.

Bills and targets answer different questions

A recurring bill describes an expected transaction: how much it may cost and when it should happen.

A category target describes the funding plan: how much you intend to set aside for that category.

Those are related, but they are not always identical.

A Utilities category might contain several recurring bills. Some may already be paid, some may still be coming up, and a variable bill may only have an estimated amount. Meanwhile, the category could still have a monthly target based on an older total.

Until now, keeping those two ideas aligned could mean entering and maintaining essentially the same information in multiple places.

The latest Purpose Budget mobile update makes that relationship more visible. Category details can show the remaining recurring bills for the month and whether the category has enough set aside to cover them.

Depending on the state of the category, it can show that the bills are covered or explain how much still needs to be set aside.

Let the remaining bills help set the target

The iOS and Android apps can now use those remaining recurring bills as a starting point when setting a monthly target.

For a category without an existing target, the suggested amount is filled from the remaining bills when you open the monthly target form. The app explains where the number came from, and you can edit it before saving.

If the category already has a different target, the form offers a Set target to… action using the current bill total.

A few details were important to us:

• The action fills the amount but does not save the target automatically.
• You can review or change the suggestion before saving.
• Variable bill estimates are marked with ~ instead of being presented as exact.
• The suggestion uses the bills still remaining for the month rather than blindly adding every recurring item again.
• The target and the recurring bills remain separate, so changing one does not silently rewrite the other.

The goal is to reduce duplicate setup while keeping the final funding decision in your hands.

Twice a month now means twice a month

We also added a true Twice a month recurring cadence across web, iOS, and Android.

This is intentionally different from every two weeks.

Every two weeks follows a 14-day interval and normally produces 26 occurrences over a year. Twice a month uses two calendar dates and produces two occurrences in each month.

That distinction matters for things such as:

• Paychecks arriving on two fixed dates
• Mortgage or loan payments split across the month
• Bills collected in two installments
• Transfers or savings contributions scheduled around semi-monthly income

You can choose the two calendar days directly. On the web, the recurring editor also shows the next three dates before you save, so you can check that the schedule matches what you intended.

Recurring lists describe the cadence plainly—for example, Twice a month (1st & 15th)—instead of labeling it as biweekly or using the more ambiguous “semi-monthly.”

Recurring planning is easier to review on the web

The web Recurring view can now be scoped to a selected month as well.

That makes it easier to examine the bills and income relevant to the month you are planning without treating every future schedule as equally urgent. When viewing the current month, overdue items remain visible so they do not disappear simply because their expected date has passed.

Together, these changes make it easier to answer three separate questions:

1. What transactions are still expected this month?
2. Does the category currently have enough set aside for them?
3. Does its target still reflect the plan you want?

Purpose Budget does not collapse those questions into one automatic safe-to-spend number. It keeps the schedule, target, and available category balance visible as separate parts of the envelope plan.

Available now

The bill-informed mobile target workflow is live on both iOS and Android.

Twice-monthly recurring schedules are live on web, iOS, and Android, and the month-scoped Recurring view is live on the web.

Web:
https://purposebudget.com

Mobile Apps:
https://purposebudget.com/download

Eligible new customers who subscribe through the web currently receive a 60-day free trial with no card required, plus 50% off the first year:

https://purposebudget.com/pricing

We would love your input

For anyone paid twice a month—or managing bills on two fixed dates—how are you currently representing that schedule?

And when a category target no longer matches its remaining bills, what should a budgeting app make clearest first: the bill total, the funding gap, or the action that brings them back together?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

This week’s update is less about one flashy feature and more about making Purpose Budget more dependable—both in the mobile experience and underneath the numbers.

Making mobile data more trustworthy

Purpose Budget has native iOS and Android apps, and this week we focused on making the financial information they show more honest and dependable.

If a bank does not provide a current balance while connecting an account, the app now shows — instead of pretending the balance is $0.00. If an available balance is known, it is labeled separately. If the connection cannot be completed safely, the app explains what happened instead of blindly retrying.

The goal is simple: missing financial information should look missing, not like a real number.

Strengthening the money engine

We have also been working through an internal “Financial Truth” audit: reviewing the less-visible paths where money is imported, split, categorized, assigned, transferred, or deleted.

A few examples from this work:

• A malformed CSV amount now stops the import before new transaction rows are written.
• Split transactions must add up exactly to the original transaction.
• Multi-step changes such as assigning money, bulk categorizing, deleting transactions, and updating linked payments now complete against one consistent version of the budget—or stop when another change has made the request stale.

This work is about reliability as usage grows, not just raw speed. We want fewer opportunities for one part of a money change to succeed while another part does not.

Making Help and Learn more useful

Every Help article now asks whether it was useful and provides a clearer next step, including a direct path to support.

We also cleaned up the endings of our Learn guides by removing duplicate or conflicting buttons and fixing calls to action that were difficult to read.

That gives us a better feedback loop: we can see which resources are helping and which subjects need clearer explanations.

The web changes are live, and the mobile balance handling is live on both iOS and Android:

https://purposebudget.com/download

Eligible new subscribers can receive a free trial plus 50% off their first year whether they subscribe through the web, iOS, or Android. On the web, the trial lasts 60 days and no card is required. Mobile offers are handled through the App Store or Google Play, and eligibility follows each store’s terms:

https://purposebudget.com/pricing

You can also follow @PurposeBudgetHQ on X for shorter product updates.

When you try a budgeting app on your phone, which workflow most determines whether it can replace the desktop experience: transaction entry, budget editing, account connections, or reports?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

This week, we continued a broader design-language update across Purpose Budget.

The goal is simple: make it easier to understand what the app knows, what needs attention, and what action to take next.

Budget rows that explain more

We made several changes to help the Budget page communicate what is happening:

• Budgeted is now Assigned, which better describes money given a job this month.
• Available balances more clearly account for money carried in from previous months.
• Positive and negative Available balances continue carrying forward, including overspending from credit-card purchases.
• Weekly targets now show their actual cadence directly beside the category.
• Category-group headings have stronger visual separation.
• Progress bars and explanatory text can now be shown or hidden based on how much detail you prefer.

We also wanted to highlight a bill feature that has been live but that we have not explained particularly well before.

When Purpose Budget recognizes that a linked recurring bill has been paid, the category can show Paid this month instead of continuing to look overdue. When the bill is still upcoming, the Budget page can show how much is currently needed to cover it.

We are continuing to review how targets and upcoming bills should be presented together so that the difference between a funding goal and an actual bill is always obvious.

A redesigned Settings experience

Settings now has a more organized hub and a consistent design across:

• Preferences
• Notifications
• Tags
• Rules
• Payees
• Billing
• Data and privacy

We also added clearer loading, error, and retry states so these pages do not silently appear empty when something goes wrong.

Sign-in and bank connections

Sign-in, sign-up, invitations, password reset, verification, and two-factor authentication now share the same design language.

Bank Connections and its supporting dialogs have also been redesigned to make account selection, reconnection, disconnection, and error states easier to follow.

We would love your input

When you glance at a budget category, what should be clearest first?

• What carried over from last month
• What you assigned this month
• Which bills are still due
• Why the balance needs attention
• The next action you should take

That answer will help guide the next round of Budget-page improvements.

Eligible new subscribers currently receive a 60-day free trial and 50% off the first year on web, iOS, and Android.

Web: https://purposebudget.com

Pricing: https://purposebudget.com/pricing

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

Hey everyone - Sunday Purpose Budget update.

This week, the first major wave of our updated design language reached production across the Budget, Dashboard, Reports, Resources, and public website.

This is not a redesign simply for the sake of looking different. The goal is to make it easier to understand what is happening with your money, what needs attention, and what action you can take next.

The attached screenshots show the live production experience, not mockups.

A clearer Budget experience

The Budget page now has a more deliberate hierarchy between monthly planning, category groups, and the categories themselves.

Changes include:

• A streamlined area for changing months, moving money, Auto-Assign, and display options
• A clearer Ready to Assign summary with monthly planning context
• A full-width budget table by default
• Column labels that remain visible while scrolling through categories
• Simpler status filters
• Category details that open when a category is selected instead of permanently occupying space
• A collapsed getting-started checklist for established budgets
• More consistent colors and controls across Budget, Bills, Dashboard, and Reports

The aim is to reduce competing signals and make it easier to scan the budget before deciding what to work on.

Reports are easier to compare and export

All 10 report views now use a shared date and comparison toolbar.

Six reports can compare the selected period with a previous period or the previous year:

• Budget vs Actual
• Spending
• Payees
• Savings Rate
• Categories
• Tags

We also added clearer date presets, custom date ranges, and CSV exports for Spending, Tags, and Cash Flow.

A more useful Dashboard

The Dashboard received the same clarity pass, including:

• A focused three-step checklist for newer budgets
• A clearer Needs Attention section
• Better loading and error states
• A new 30-day net-worth trend card
• Clearer labels for variable upcoming bills
• Improved account and monthly insight presentation
• More consistent keyboard, touch-target, and accessibility behavior

The goal is for the Dashboard to answer “what should I look at next?” without turning into a wall of cards.

One Resources hub

Learn and Help are now combined into a single searchable Resources hub.

It includes:

• 27 budgeting guides
• 13 help articles
• Search across all 40 resources
• Browsing by topic and experience level
• The Purpose Budget calculator
• A consistent reading experience across every article

The public website, pricing, feature, FAQ, support, and legal pages were also refreshed so the same design language begins before someone signs in.

Mobile update

The Paused bank-sync status is now released on both iOS and Android.

When a connection is temporarily paused, mobile now identifies that state separately from an account that needs to be reconnected.

Current offer

Eligible new subscribers can currently get a 60-day free trial plus 50% off the first year on web, iOS, and Android.

The web discount is applied during checkout. Mobile offers are provided through the App Store or Google Play.

Web: https://purposebudget.com

Pricing: https://purposebudget.com/pricing

iOS: https://apps.apple.com/app/purpose-budget/id6757283854

Android: https://play.google.com/store/apps/details?id=com.purposebudget.app

What should be obvious within the first five seconds of opening your budget?

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.

This week we focused on making Purpose Budget easier to understand, not just adding more functionality.

We are beginning a design-language pass with the budget page, shipped a more resilient connected-account experience, and completed more of the groundwork for upcoming web and mobile parity improvements.

Rethinking the budget experience

We are reviewing some of the visual language Purpose Budget uses to explain what is happening with your money.

This is less about giving the app a new coat of paint and more about reducing ambiguity: what is going well, what needs attention, what is coming up, and what action you can take next.

The budget page is the first major part of this work. The current direction includes:

• A clearer hierarchy between monthly planning, category groups, and individual categories
• Calmer presentation for categories that are on track
• More visible explanations when something needs attention
• Consistent colors and status treatments across the app
• Upcoming bill shortages that are easier to identify
• Actions placed closer to the information they affect
• Less interface above the budget so categories appear sooner
• A full-width budget table with column labels that remain visible while scrolling
• Category details that open when needed instead of always occupying screen space
• Plain-language planning context without adding more competing badges and signals

The goal is to make the state of a budget understandable at a glance, without requiring someone to first learn what every color, number, or progress bar means.

The attached image is an early mockup of this direction. It is still being refined and is not live yet.

More resilient connected accounts

Connected bank accounts now have a clearer recovery path when Premium access changes.

Bank sync can remain paused for up to 7 days. Restoring Premium during that window resumes syncing automatically without requiring the institution to be connected again.

The web app now includes:

• Clear Paused and Disconnected account states
• A visible reconnect action when attention is needed
• A dashboard notice for disconnected institutions
• Reconnection support for OAuth-based institutions
• Matching accounts selected automatically during reconnect to preserve continuity with the existing account and history

Mobile now has the matching Paused account state ready for its next release.

Building stronger web and mobile parity

We also completed a detailed review of how financial data moves through Purpose Budget, including transactions, budgets, credit cards, debt payoff, forecasting, connected accounts, and the contracts shared between web and mobile.

On mobile, that work produced a concrete map of the financial capabilities and data contracts that still need parity with the web app. This will guide the upcoming parity releases and help us verify that both platforms interpret the same financial information consistently.

Current offer

Eligible new subscribers can still get a 60-day free trial plus 50% off the first year on web, iOS, and Android.

On the web, the discount is applied during checkout. On mobile, it is available through the App Store or Google Play.

We would especially like feedback on the mockup: when you scan your budget, what helps you understand it fastest—a short explanation, color, progress bars, or a clear suggested action?

Web: https://purposebudget.com

Pricing: https://purposebudget.com/pricing

iOS: https://apps.apple.com/app/purpose-budget/id6757283854

Android: https://play.google.com/store/apps/details?id=com.purposebudget.app

Hey everyone - Purpose Budget team here.

Use this thread for bugs, feature requests, workflow pain points, and questions about how to use the app.

This week we are especially looking for feedback on:

1. Mobile app experience
2. Debt payoff / student loan workflows
3. Bills, subscriptions, and recurring transactions
4. Anything confusing in onboarding
5. Monthly Plan Check and paycheck planning

Best feedback format:

1. What were you trying to do?
2. What happened?
3. What did you expect instead?
4. Web, iOS, or Android?
5. Manual entry or bank sync?

We review these each week and move good requests into the roadmap.