Money is the day-to-day financial operations surface for end users. It helps users quickly understand cash movement (balance, money in, money out), then act on prioritised recommendations so they can address the most important cost, cashflow, or operational issues without losing context.Documentation Index
Fetch the complete documentation index at: https://docs.narrativebanking.com/llms.txt
Use this file to discover all available pages before exploring further.
What’s new in v1.5.7
v1.5.7 improves the Money experience for both quick review and deeper follow-up.
- Mobile summary cards are more compact and easier to scan.
- Change indicators use clearer visual direction cues.
- Cash balance, Money In, Money Out, and action detail panels have been aligned for a more consistent reading experience.
- Users can request a curated financial report from the Money area, delivered by email.
- Recommendations are better at retaining high-value items across refreshes, so useful actions are less likely to disappear unexpectedly.
- Period comparisons are more consistent, helping users understand month-to-month or quarter-to-quarter changes.
- Transaction patterns can contribute to richer business context over time.
- New users are less likely to see stale or unavailable Money data immediately after onboarding.
- Quick-action chips are expected to remain readable and tappable on narrow mobile screens.
- Bank connections are limited to one account while full multi-account support is being prepared.
Functional flow
1. Establish one snapshot context
1. Establish one snapshot context
Use one shared as-of context per page so all cards, actions, and details remain aligned.
2. Render summary first
2. Render summary first
Load top-level metrics before deeper drill-downs so users get immediate financial context.
3. Load action queue second
3. Load action queue second
Present prioritised recommendations tied to the same snapshot context.
4. Persist status transitions
4. Persist status transitions
Apply user actions only after server confirmation and keep local UI state synchronized.
Integration considerations
| Area | What to preserve | Why it matters |
|---|---|---|
| Snapshot discipline | One consistent time context | Prevents mismatched metrics and action detail |
| Action ordering | Stable priority and status semantics | Keeps user focus on highest-impact items |
| Update confirmation | Server-acknowledged status changes | Avoids drift between UI and backend state |
Reflect status changes only after confirmation, or include a safe rollback path when optimistic updates are required.