Threads

Threads are comment conversations attached to a specific accounting object — a transaction, journal entry, invoice, bill, vendor, or customer. The discussion stays on the record it's about, so your team sees context exactly where the work happens instead of digging through email. Each thread also carries a review status, turning comments into a lightweight workflow advisors can work and clear across every client business.

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 (superusers can edit/delete any)
• 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 (status: 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

1. Open the Threads page from the sidebar, or open any record and use its comment/thread control.
2. 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.
3. Click a thread to open it — the detail panel shows the full comment history with author names and timestamps.
4. Type in the composer and press Enter to post (Shift+Enter for a newline). Comments are limited to 10,000 characters.
5. Click Mark reviewed when the question is settled, or Reopen to send a Reviewed thread back to Pending review.
6. Click View {object} (e.g. "View Transaction") to open the underlying record in context.
7. Use Summarize on a row or in the detail to get an AI recap with key decisions and action items.
8. Hover a comment and use the trash icon to delete it (your own comments, or any comment if you're a superuser).

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

A thread can attach to any of the supported object types, and the first comment on an object creates its thread automatically — you never create threads explicitly. Supported object types and where "View" sends you:

Commenting on any other object type isn't supported.

Statuses

Status is a two-state review flag, not a per-comment field.

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.

Creating, editing, and deleting comments

• Ownership — comments belong to a thread and an author.
• Creating — auto-creates the thread if needed and stamps the author's display name.
• Editing / deleting — restricted to the comment's author or a superuser; anyone else is denied.
• Deleting — removes the comment from the thread, so use edits for fixes you want to keep visible.

Permissions

• Reading and commenting — business-scoped; you must have access to the business the thread belongs to.
• Changing status — additionally requires write permission on that business; read-only roles (e.g. firm viewer) can read and even comment per their access, but cannot mark threads reviewed or reopen them.
• Superusers — can update any thread.

Advisor cross-business listing and filters

The Threads page runs in two modes:

• Business in context — scopes to that business.
• No business — returns threads across every business you can access, typically all of an advisory firm's client businesses.

The list is paginated and supports:

• Filters — author, object type, status, and an updated-on date range.
• Total count — optional and more expensive.
• Summary rows — business name, latest-comment author and preview, comment count, and last-updated time, so you can triage without opening each thread.

AI assistance

Two AI helpers work on a thread's contents, both on-demand — you stay in control of what actually gets posted:

• Summarize — returns a concise summary plus extracted key decisions and action items.
• Draft reply — proposes a response with a suggested tone.

Edge cases

• There's exactly one thread per object — commenting again always appends to the same thread.
• Comment text must be 1–10,000 characters.
• A brand-new thread with no comments returns an empty comment list rather than an error.
• Deletions are permanent; prefer editing when you want to preserve the record.