What’s new in v1.8
v1.8 upgrades Money recommendations, transaction inspection, and business-date consistency.
- Money cards and panels use a richer recommendation structure with situation, consequence, practical actions, one decision-changing caveat, and supporting evidence.
- Recommendation imagery comes from a shared catalogue so card and detail presentation remain aligned.
- Targeted follow-up answers stay attached to the relevant recommendation and can personalise the displayed result after refresh or regeneration.
- Transaction views preserve canonical row identity, use cleaner counterparty labels, handle connected transfers more accurately, and show longer table values without clipping.
- Money charts and transaction-backed views use Narrative-provided business dates for better consistency across UK reporting windows and daylight-saving boundaries.
What’s new in v1.5.13
v1.5.13 refreshes Money actions so users can scan value and next steps faster while preserving action state more reliably.
- Money action rows use concise titles, fact lines, value chips, time or effort context, and a clear route into the detail panel.
- Detail panels keep the title, value, timing, next steps, decision controls, and supporting reasoning in one consistent structure.
- Saved, snoozed, dismissed, question-gated, and completed states stay attached to the right action across refresh and regeneration.
- Question-gated actions behave more predictably, including overflow handling and expiry for stale gated actions.
- Generated card and detail content is shaped for the refreshed UI so recommendations remain understandable and trustworthy.
What’s new in v1.5.12
v1.5.12 extends Money to same-currency multi-account users.
- Cash balance, money in, money out, and transaction views can reflect combined data from multiple connected accounts in the same currency.
- Internal transfers between the user’s own connected accounts are excluded from income totals, expense totals, spending ratios, and related recommendations.
- Connecting a new same-currency account starts a data reload, with user-facing processing guidance and a completion email when the new data is ready.
- Duplicate account connections are prevented, and different-currency account connections are rejected before their data is saved.
What’s new in v1.5.11
v1.5.11 connects Money actions to the journey and makes follow-through clearer.
- Money action detail panels use a primary action bar with “Worth pursuing”, “Not for me”, and “Later”.
- Bookmarked actions move into a follow-through state with “Mark as done”, “Snooze”, and “Remove”.
- Distinct Money action responses contribute to journey progress, so repeated interaction with the same card does not satisfy progress requirements by itself.
- Coach and journey prompts can bring users back to bookmarked Money actions when follow-through is needed.
What’s new in v1.5.10
v1.5.10 makes Money actions more specific, better researched, and easier to act on.
- Action cards focus on one clear point, with named counterparties or categories where available.
- Recommendations show quantified impact when the data supports it, usually as an estimated range rather than a guaranteed saving.
- Research-enriched actions can include named alternatives, pricing or comparison context, estimated savings, and source links.
- Detail panels are structured around current cost, alternatives or findings, estimated saving, how to act, and source context.
- Money and Growth recommendations are separated more clearly: cost-saving and money-protection items stay in Money, while revenue-growth ideas belong in Growth.
What’s new in v1.5.9
v1.5.9 makes Money recommendations more practical and better qualified.
- Recommendations are more focused, with clearer action framing, named specifics, quantified impact where supported, and concrete next steps.
- Some recommendations can ask targeted follow-up questions when transaction data alone cannot confirm eligibility or usage.
- Subscription value review helps users assess recurring software and service spend when usage is unclear from bank data alone.
- New transaction-pattern recommendations can surface conservative idle-cash opportunities, late or deteriorating expected payments, and debt cost review opportunities.
- Recommendations that rely on inferred timing, rates, or balances include caveats so users understand the basis for the suggestion.
What’s new in v1.5.8
v1.5.8 gives users more control over Money insights and improves first-load reliability after onboarding.
- Users can snooze Money insights when an action is relevant but not right for today.
- Snoozed items are retained across refresh cycles and can resurface later through the prioritisation flow.
- A dedicated snoozed-items view lets users review and manage recommendations they chose to revisit.
- Newly onboarded users are less likely to see unavailable Money metrics or actions when fresh metrics already exist.
- Optional dismissal reasoning can be captured when users dismiss an insight, improving the feedback loop for future recommendations.
- Scheme-type insights can be surfaced when research into grants, tax reliefs, public finance programmes, and similar SME support opportunities identifies relevant support for the business.
Functional flow
1. Load the latest available Money context
1. Load the latest available Money context
Let the SDK present the latest available Money context on first load, including all connected same-currency accounts where available. Preserve explicit dated flows only when the user has intentionally arrived from a dated context.
2. Render summary metrics first
2. Render summary metrics first
Load top-level metrics before deeper drill-downs so users get immediate financial context.
3. Present the action queue
3. Present the action queue
Show prioritised recommendations as scannable rows and preserve stable status semantics across refresh cycles.
4. Resolve recommendations that need more context
4. Resolve recommendations that need more context
Ask only for the extra context needed to decide whether a recommendation should be shown as a confirmed action.
5. Persist user intent
5. Persist user intent
Apply pursue, snooze, dismiss, remove, or completion transitions only after server confirmation and keep local UI state synchronised.
6. Resurface snoozed items when relevant
6. Resurface snoozed items when relevant
Treat snooze as a positive “later” signal rather than a permanent dismissal, and make snoozed items manageable from a dedicated view.
Integration considerations
Reflect status changes only after confirmation, or include a safe rollback path when optimistic updates are required.