Comments and Review, Attached to the Actual Numbers

Review of a financial model usually happens somewhere other than the model. A comment in an email thread, a note in Slack, a question typed into a shared doc that has drifted three versions out of sync with the numbers it’s about. By the time someone finds the discussion again, the figure it referred to has often changed, and nobody is quite sure if the comment is still relevant.

Rexfin puts the conversation on the number itself, not next to it.

Why this matters for a finance team

A question like “did we confirm this DPO jump with the customer?” is only useful attached to the specific working-capital figure it’s about, in the period it’s about. Detached from that context, it’s a stray note competing for attention in an inbox. Attached to it, anyone opening that statement row later sees the question and the answer without having to go hunting.

The second thing that matters is who sees what. Internal back-and-forth about a number, is this real, did we double check the source, is not something you want visible the moment you send a board member or an auditor a share link. But some of that discussion, once resolved, is exactly the context an external reviewer should see. Getting that boundary wrong in either direction is a real cost: too permissive and internal debate leaks out, too restrictive and reviewers lose useful context.

How it works

Comments attach to a specific cell, wherever that cell lives, a statement row, a KPI or per-share card, a what-if slider. A small indicator marks where a discussion exists, and it only appears on pages an owner is actually looking at; a read-only shared view never shows it, because the affordance is built to not render at all outside that context. Threads are one level deep: replies flatten under the original comment and inherit its anchor, so a conversation stays legible instead of turning into a nested tree.

The anchor itself is built to survive the data underneath it changing. It’s tied to the entity and a semantic key, the specific cell, KPI, or driver, rather than a row position, so re-running a model or refreshing a period doesn’t orphan a comment that was pointing at something real.

Each thread can be resolved and reopened, the kind of lightweight sign-off state a spreadsheet gives you natively but a lot of collaboration tools skip. Every comment and activity event, threads created, resolved, share links generated or viewed, also rolls up into one interleaved timeline on each company’s activity page, so a reviewer coming back after a week can see what happened in order rather than piecing it together from separate feeds.

The part worth being direct about: visibility is explicit, not inferred. A comment is marked internal or shared, and that marking is what a share link actually honors, a shared view only ever renders threads marked shared, and internal discussion never crosses that line. If a shared reply happens to sit under an internal parent comment, it’s promoted to display as its own item rather than exposing the internal thread it was replying to. And on a shared view specifically, comments are labeled as unverified annotations without attaching an author’s name to them, so nobody looking at a share link can mistake a comment for something Rexfin itself is asserting.

That last point connects to a harder rule: comments are annotations, never data. They do not appear in cited PDF and Excel exports, not even as an appendix, and nothing in the calculation engine ever reads them. Discussion about a number and the number itself are kept structurally separate, so a comment thread can never quietly influence a figure that’s supposed to be deterministic.

Who this is for

This is built for the ordinary friction of reviewing numbers with other people: an analyst flagging something for a controller, a CFO leaving a question on a KPI ahead of a board meeting, a reviewer coming back to check whether last week’s question got answered. It’s most useful for teams already working inside team workspaces who want review to happen where the numbers live, and it pairs directly with the insights feed: a detected anomaly is exactly the kind of thing worth a thread. When it’s time to bring in someone outside the team, the same visibility split is what makes auditor share links safe to send without a separate cleanup pass first. See the Rexfin product tour for how the pieces connect.