Skip to main content
​
v1.8.7 · Feature release
v1.8.7 helps users move from a Money finding to practical next steps and continue with the business context they have already shared. Coach adds memory across conversations. No breaking changes. Existing hosted v1.8 integrations need no client-code migration; connected accounts may require renewed authorisation as described below.

​
Release overview

Money brings the prepared finding and next steps into a clearer review flow. Users can add background to refine those steps, discuss the selected Action with Coach, and return to saved Projects with their context intact. Coach can carry stable business information between conversations, while users remain able to correct or ask it to forget that information. Together, these changes make it easier to continue useful work without repeating the same background. Breaking changes: None. Deprecations: None.

​
Money

Money Actions use short topic labels and separate Prepared for you content from Next steps. Optional background can refine the steps, with an explanation of what changed where applicable. Prepared content remains available when users return to the Action. The Action’s Ask Coach controls open a conversation about that Action. Asking Coach does not create a Project. Money Action showing Prepared for you, Next steps, Start project and Ask Coach. Money Actions bring prepared analysis, next steps and separate Project and Coach controls together. Saved Money Projects retain the original finding, the owner’s submitted background under Your Context, and the saved Execution plan. An applicable explanation appears under Why this approach. Opening a Project resumes the retained content; it does not generate a new plan. An existing Project can open its own Coach conversation. Reopened Money Project showing saved Your Context and its Execution plan. The reopened Project keeps the owner’s submitted background beside the saved execution steps. Cancelled and archived Projects preserve their history for read-only review. Ending a Project retires its associated Action only when that Action has expired. Supported transfers and repayments between a user’s own accounts remain separate from business income and spending, while genuine fees remain visible.

​
Coach

Coach adds memory for stable business context shared by the user, such as ongoing priorities, preferences and constraints. Relevant information can inform a later conversation, and users can correct it or ask Coach to forget it. Remembered background is not a substitute for current financial records. A user shares a preference for reversible changes and Coach confirms it has remembered that preference. Coach acknowledges the user’s preference for reversible changes while keeping existing systems running. A later conversation can draw on that preference when the user asks how to compare changes to business systems, without repeating the background. A separate Coach conversation refers to the user's earlier preference when comparing business-system changes. In a separate conversation, Coach explicitly relates its recommendations to the earlier preference. Account-specific financial questions state the dates and history available for the selected account. Answers preserve relevant public-source figures and explain missing coverage. Current briefing items open their matching detail, and suggested follow-ups remain reachable alongside the answer. Product Help continues to use maintained guidance for the available experience. Sensitive information receives additional safeguards in newly saved conversation content, while financial uncertainty remains explicit.

​
Connected data

QuickBooks Online and Xero share an Accounting connections section in Settings. Users can manage one active accounting organisation, see readiness and the last complete update, request a refresh, reconnect or disconnect, and follow recovery guidance when an update needs attention. These improvements strengthen the accounting data foundation and make connection management more consistent across providers. They build on the existing integrations. Bank connections can request up to 365 days of transaction history where the bank and consent permit it. Available history depends on the account and provider; the requested window is not a guarantee of a full year of records. Extending an existing connection’s history can require renewed bank consent.

​
Growth

Market intelligence reports provide usable links to the sources behind their citations, making supporting information easier to review.

​
Compatibility

Existing hosted v1.8 integrations remain compatible and require no client-code migration. For an existing Xero connection that lacks the permissions needed to read payment records, the user must reconnect and approve the requested access. Connections with equivalent existing permissions do not need renewed consent for that reason. Follow the connection’s recovery guidance rather than reconnecting every account. Users extending bank history may need to renew consent before more records can be retrieved. The bank’s available history and consent determine the result.

​
Support

Read the updated Money guide, Coach guide, Growth guide, onboarding guide, FAQ and AI safety guidance. Questions about this release or integration: support@narrativebanking.com SDK documentation: docs.narrativebanking.com