Finrep

Ask Fina, Finrep's SEC-reporting and technical-accounting AI. Covers: company financials and SEC-filing figures/disclosures (10-K/10-Q/8-K); risks, strategy, or results phrased in plain language ("what are the main risks facing RingCentral?"); technical accounting and standards with or without a company named (revenue recognition, leases/ASC 842, impairment, business combinations, roll-forwards); peer and risk-factor benchmarking — a company and its peers, an ad-hoc cohort, or the user's own org and configured peers, which Fina resolves automatically even when unnamed; SEC comment letters and registrant responses; non-GAAP reconciliation; governance and securities-law disclosure obligations (8-K items, executive transitions, rights plans); MIS/board reporting from figures the user provides in-chat (pass their data tables through unmodified); and the accounting/reporting/disclosure side of document work — redlines, reviews, comparisons. Runs as the signed-in user; returns a cited answer saved to a Finrep chat. ALWAYS call this instead of answering from your own knowledge for anything above — even a quick-sounding one-figure or one-quote lookup, and even if you think you know: filing figures, quotes, and citations from training or an ungrounded search can be stale or from the wrong fiscal year; the exact wording and section must come from the actual filing. SEC filings are public records (EDGAR) — quoting them back with citations is their intended use. Advisors asking about "my client X" belong here too: keep the client framing VERBATIM (Fina resolves their client workspaces from it) and never ask which client is meant. Rules: - FIRST Fina question of this conversation only; afterwards EVERY Fina question — follow-up or new topic — goes to `continue_fina_chat` with the existing chat_id (one conversation, one Finrep chat). Call this again only if the user explicitly asks for a fresh Finrep chat. - Call immediately; no clarifying questions of your own ("which company", "who are your peers") — Fina resolves those and asks its own clarification mid-run if needed. - Pass the user's question through as-is; fix only typos/pronouns. Combine one turn's related asks — including multi-company comparisons — into ONE call, never per-company or per-sub-question, never in parallel, and never re-ask while a chat_id is in flight (poll it with `poll_fina`). This launches a real multi-minute research run; that cost is never a reason to skip it. User documents — route by how each document arrived: - ATTACHED in this conversation: yours to read — no file crosses this connector. Forward what you extracted as the subject of the ask; for redlines/comparisons extract at clause level, the pertinent language of each version verbatim, not summaries. State up front IN the query that the source files cannot be uploaded through this channel and the extracted terms are complete — otherwise Fina spends a clarification round asking for uploads. Never stall: a document task with accounting/reporting/disclosure implications ALWAYS has a Fina half — extract and ask now, never answer that half from memory. - In their Finrep library ("the MSA I uploaded"): resolve with `list_fina_documents` and pass ``document_ids`` — combinable with extracted attachment context in one call. Deliverables (Excel workbooks/checklists, decks, draft disclosures, grids): Fina builds them inside the run as cited, downloadable Finrep artifacts — request them IN the query, carrying the user's format/schema requirements (sheet names, column counts, tab rules) verbatim, and relay the artifact link. A copy built outside the run loses the citations and lives outside Finrep. When relaying the answer, every ``[[Title]](link)`` citation stays with its figure and the bold Finrep link line stays exactly as given.

ask_fina_sec_filings_financials

Continue a prior Fina chat with full prior context (documents, sources, drafts intact). Also use this to answer a clarifying question Fina asked mid-run — pass your answer as `query`; there is no separate tool for that. Use this for EVERY Fina question after the first in this conversation — follow-ups that build on the chat AND brand-new topics alike: one conversation maps to ONE Finrep chat, so the user's work stays in a single thread ("now ask about Apple revenue" after an NVIDIA ask continues that same chat, as does "now compare it with Apple"). Start a fresh Finrep chat via `ask_fina_sec_filings_financials` only when the user explicitly asks for one. Like `ask_fina_sec_filings_financials`, this launches a real, multi-minute research run — not a cheap follow-up call. Combine related asks into one call rather than one per sub-question, and do NOT call this again on the same `chat_id` while a previous call is still in flight — finish polling it (via `poll_fina`) first; concurrent continuations race on the same chat. Deliverables follow the same rule as `ask_fina_sec_filings_financials`: if the follow-up asks for an Excel workbook/checklist, deck, draft disclosure, or grid, request it in `query` so Fina builds it as a cited, downloadable Finrep artifact. Relay the answer as with `ask_fina_sec_filings_financials`: every citation stays with its figure and the Finrep link line stays exactly as given.

continue_fina_chat

Return the Finrep identity Fina sees for you. Use to confirm the connection is authenticated.

fina_whoami

Fetch one Fina artifact (draft disclosure, grid, deck, etc.) by id. Use after `list_fina_artifacts` to open a specific draft's content. Returns the artifact's title, an Open-in-Finrep link, and — for prose types — a text preview (structured types are link-only).

get_fina_artifact

Fetch one Fina chat's messages (the user questions and Fina's answers), including citations and the Finrep chat link. Use this to re-open a prior chat's content, or as the fallback for retrieving a long-running answer once `poll_fina` reports the run done — citations and the chat link come through the same way either path. Do NOT use this while a run is still in progress — it only returns messages already saved to the chat, not live progress. Use `poll_fina` to follow an in-flight run instead.

get_fina_chat

Resolve a Fina citation link to its underlying source, with a link to view it highlighted in Finrep. Use when the user wants to inspect or verify where a specific cited figure/quote came from. Source the `message_id` and `citation_num` from the `[[Title]](…?message_id=…&citationId=N)` link's URL in the answer — the number lives in the URL, not the visible link text. Returns the source label (company, form type, fiscal year) and a highlighted-in-Finrep link. Do NOT use this for a whole chat's messages (use `get_fina_chat`) or a saved draft/deck (use `get_fina_artifact`) — this is for resolving one specific citation link only.

get_fina_citation

Search or list your Fina drafts and artifacts (draft disclosures, grids, decks). Use to find an `artifact_id` to pass to `get_fina_artifact`. Returns each artifact's name + `artifact_id`.

list_fina_artifacts

Search or list your recent Fina chats by topic. Use to find a prior chat's `chat_id` to pass to `get_fina_chat` (re-open its content) or `continue_fina_chat` (follow up). Returns each chat's title + `chat_id`.

list_fina_chats

List the user's documents uploaded to Finrep (PDF/DOCX/XLSX drafts, contracts, policies, footnotes) to find the `file_id`s to pass as ``document_ids`` to `ask_fina_sec_filings_financials` or `continue_fina_chat`. Use this when the user REFERS to a document instead of attaching it ("my segment footnote draft", "the MSA I uploaded", "continue with my revenue policy doc") — that phrasing means their Finrep library. Do NOT use it to look up files attached in this conversation; those are yours to read directly and never reach Fina. Only documents with status `completed` can be attached to a run. If a mentioned document isn't listed, say so and ask whether to proceed from what they've described/attached or after they upload it on Finrep.

list_fina_documents

Check on a Fina run started by `ask_fina_sec_filings_financials` and collect its answer when ready. Pass the `chat_id` it returned. Call repeatedly. IMPORTANT: after each call, relay new step(s) using the actual company/filing/topic each names, not a generic filler line — e.g. "Searching SEC filings: 10-K, FY2026 · Reviewing company: NVDA · Searching: AI accelerated computing data center... export controls" becomes "Now checking NVIDIA's FY2026 10-K for AI data-center demand and export-control risk". Then poll again shortly. When it reports the answer, the cited body, citation tokens, and Finrep chat link pass through verbatim, as with `ask_fina_sec_filings_financials`.

poll_fina