Threads
Threads keep team comments on the record they concern — transactions, invoices, bills, journal entries, vendors, or customers — with Pending review / Reviewed status so close questions do not get lost in email.
Key capabilities
- Comment threads on transactions, journal entries, invoices, bills, vendors, and customers
- One thread per object, created automatically the first time someone comments
- A review workflow — each thread is Pending review or Reviewed
- Posting a new comment auto-resurfaces the thread back to Pending review, so addressed items don't go stale silently
- A centralized Threads page with a split list / detail layout
- Filter by object type and status; an optional total count
- Cross-business view for advisors — omit a business and see threads across every client business you can access
- Edit or delete your own comments
- Each list row shows object type, status, business, author, comment count, latest-comment preview, and last-updated time
- AI thread summary — a recap with key decisions and action items
- AI draft reply — a suggested response in the right tone
- One-click View to jump to the underlying record
- Paginated advisor list, with a permanent audit trail
How it works
Any object can carry a thread. The first comment creates the thread (and sets it to Pending review); each later comment appends and resurfaces it; an advisor marks it Reviewed once the question is settled.
flowchart TD
obj["Object (transaction / invoice / bill / journal entry / vendor / customer)"] --> first["First comment"]
first --> thread["Thread created (Pending review)"]
thread --> more["More comments appended"]
more --> review{"Advisor reviews"}
review -->|"Mark reviewed"| reviewed["Reviewed"]
reviewed -->|"new comment"| thread
thread --> nav["View object / Summarize / Draft reply"]How to use it
- Open the Threads page from the sidebar, or open any record and use its comment/thread control.
- Use the All Types and All Statuses filters in the toolbar to narrow the list (e.g. only Bills that are Pending review). Click Refresh to reload.
- Click a thread to open it — the detail panel shows the full comment history with author names and timestamps.
- Type in the composer and press Enter to post (Shift+Enter for a newline). Comments are limited to 10,000 characters.
- Click Mark reviewed when the question is settled, or Reopen to send a Reviewed thread back to Pending review.
- Click View {object} (e.g. "View Transaction") to open the underlying record in context.
- Use Summarize on a row or in the detail to get an AI recap with key decisions and action items.
- Hover a comment and use the trash icon to delete your own comment.
Pro tips
- Use threads for month-end review questions — the context stays permanently with the record, which is gold during close and audits.
- Lean on the Pending review filter as an advisor worklist: clear questions, mark Reviewed, and let new client comments automatically resurface anything that needs another pass.
- In the cross-business view, filter by object type to batch similar questions (e.g. review every Bill thread at once).
- Run AI summary on long threads before replying so you're not re-reading the whole history.
- Document why a categorization decision was made in a comment — it becomes a durable, audited rationale on the exact record.
In-depth guide
Object types and where View sends you
| Object type | Opens |
|---|---|
| Transaction | Transactions |
| Journal entry | Journal Entries |
| Invoice | Invoices |
| Bill | Bills |
| Vendor | Accounts Payable |
| Customer | Accounts Receivable |
The first comment on an object creates its thread automatically — you never create threads explicitly. Commenting on any other object type isn't supported.
Status workflow
| Status | Meaning |
|---|---|
| Pending review | Has unaddressed activity; default for new threads and whenever a new comment is added |
| Reviewed | An advisor has addressed the thread |
Marking a thread Reviewed is reversible with Reopen. Any new comment on a Reviewed thread flips it back to Pending review so resolved items resurface when there's fresh activity.
Permissions and advisor listing
Reading and commenting require access to the business the thread belongs to. Marking threads Reviewed or Reopening them requires write permission — read-only roles can read and comment but cannot change status.
The Threads page runs in two modes: scoped to one business, or across every business you can access (typical for advisory firms). The list supports filters by author, object type, status, and updated-on date range. There's exactly one thread per object — commenting again always appends to the same thread.
AI assistance
Summarize returns a concise recap plus extracted key decisions and action items. Draft reply proposes a response with a suggested tone. Both are on-demand — you stay in control of what actually gets posted. Comment text must be 1–10,000 characters. Prefer editing over deleting when you want to preserve the record.