Getting Started with Stories
Stories let you group transactions into a named collection that crosses account and statement boundaries. They're useful for building a narrative — "funding the property purchase," "transfers tied to Business X," "expenses for Location A" — independent of which bank or data source the money moved through. A story is just a name, an optional description, and a set of transaction memberships. Once created, you can filter the transactions grid and Visualizations tab to that story, and you can include it as a dedicated section in a Financial Activity Report.
From the Bank Transactions page, click Stories in the toolbar. This opens the Manage Stories dialog showing every story in the engagement.
Click Add at the bottom of the list. Enter a name (required) and a description (optional), then click Create. You'll see a Story Created Successfully toast.
There is no field for account, date range, or transaction count at creation time — those are all handled afterward by tagging transactions into the story.
Tagging transactions into a storySelect one or more transaction rows in the grid. In the per-selection toolbar, click the bookmark-plus icon (internal label "Manage Stories," tooltip may read Manage Transactions to Stories). This opens a dialog titled Manage Transaction Stories showing every story in the engagement as a checkbox list.
Check the box next to each story you want these transactions to belong to, then click Save. You can add a transaction to as many stories as you need — there is no "one transaction, one story" limit. See Story Limits and Membership Rules for how membership actually works and what the limits are.
The dialog pre-checks whatever stories the selected transaction(s) already belong to. For multiple selected transactions with different existing memberships, it pre-checks the union of every story any of them belongs to — it does not distinguish "all selected are in this story" from "at least one is."
Saving computes the difference: newly-checked stories are added, newly-unchecked stories are removed. If you uncheck a story while checking another, you're explicitly removing the transaction from the first story — the dialog does what you tell it to do, so be deliberate about what you uncheck.
Tagging a large number of transactionsIf you need to tag 600+ transactions, the supported path is:
- Narrow the grid using the left-hand filters. Use the dedicated Custom Fields entry in the filter panel to match by a custom field's value (pick the field, type a substring). This is the only way to filter by a custom field's value — the column's own filter menu won't work, even though the column appears filterable.
- Select the narrowed rows. There is no "select all matching the current filter" control, so you'll need to select rows individually or via range-select.
- Tag the selection. Chunking happens automatically in the background (groups of 10 requests in parallel); you don't need to batch the selection yourself.
The grid has no header select-all checkbox configured, so selecting rows is always a manual or range-based action.
Viewing and filtering by storyTo filter the transactions grid to one or more stories, use the Stories section in the left-hand filter panel. Check the box next to each story you want to include, then click Apply.
To see which story a transaction belongs to, hover over the icon in the Story column — a small popup lists every story that transaction is tagged into.
To clear all active filters, click Clear in the left-hand filter panel, then click Apply.
Visualizations and storiesClick the Visualizations tab with a story filter active, and the chart (a Sankey-style sources/uses diagram) narrows to that story's transactions. The chart can be tied to a "visualization category" — if you've assigned Vis Category labels to the transactions in the story, the chart reflects them.
Stories and Vis Categories are independent: you can have one without the other, and assigning a story membership does not assign a Vis Category. They're two separate ways to organize the same transactions.
Including stories in a Financial Activity ReportWhen building a Financial Activity Report, you'll see a toggle labeled Add Stories in the first step. Enabling it advances you to a story selection screen where you can pick which stories to include. There's a Select All shortcut if you want every story.
The FAR's Stories section renders, per selected story:
- Name and description
- An optional chart image (if you've associated a visualization category with that story)
- A data table of that story's transactions: date, account, description, check number (as text), inflow/outflow amount, source page number, and totals
The FAR's Stories section does not include check images. Check images render only in the report's separate Evidence section, which is scoped by account, not by story. There is no way to generate a check-image set limited to exactly one story's transactions. If a client wants the 86 check images from a particular set of transactions, Stories will give them the transaction list and check numbers, but not the images themselves.
See Financial Activity Report: Multiple Accounts and Stories for how the FAR handles multiple accounts and stories together, and for known limitations in that interaction.
Editing and deleting storiesTo edit a story's name or description, click Stories, then View next to the story you want to edit. This opens the Story Summary dialog (labeled View but actually editable). Make your changes and click Save.
The Story Summary dialog includes Prior and Next buttons that let you cycle through all stories one at a time.
To delete a story, click Stories, then click the cancel/x icon next to the story. A Delete button appears. Click it to confirm deletion.
Deleting a story is permanent. There is no restore path — not for you, and not for support. The story's name, description, and all transaction memberships are gone. The transactions themselves are not deleted; only their association with that story is removed.
Who can do what- Engagement Owners can create, rename, delete stories and add or remove transaction memberships.
- Engagement Users can view stories, filter by them, and see which stories a transaction belongs to, but they cannot create, edit, or delete stories, and they cannot change membership.
If a Stories control is greyed out and you have an Engagement Owner role, and a transaction is selected, contact support — that combination should work, and no blocking condition for that scenario was found.