User guide & release roundup · November 3, 2026
ThirdNexa user guide
ThirdNexa brings vendor records, due diligence, contracts, findings, incidents, and examination evidence into one workspace. This roundup covers the major capabilities built into the platform to help financial-services teams organize oversight work and preserve the records behind their decisions.
The platform serves SEC- and FINRA-regulated firms, including investment advisers, broker-dealers, hybrid firms, hedge funds, private equity firms, and asset managers, as well as consultancies supporting those organizations.
This is a cumulative feature guide, not a list of changes made on a single day. Availability depends on your plan, role, and workspace configuration.
The firm makes every decision.
ThirdNexa organizes records, highlights follow-up work, and assists with extraction and summaries. It does not provide legal advice, determine whether a regulation applies, approve vendors automatically, or judge whether an examination response is adequate.
New in this release
AI Use Register
Where to begin
- Ask ThirdNexa support to turn the register on for your firm.
- Then open AI use under Risk & reporting.
- Explore the fictional sample workspace first, no sign-in.
What it is
The AI Use Register is a record of how your firm uses AI: each tool, who uses it and why, what data it touches, where its output goes, and its approval status. A checklist records firm-level and per-use-case oversight items with notes and evidence links, a coverage view shows what is on file, and a dated evidence pack (PDF or CSV) summarizes the register, status changes and approvals for any period. The register records what your firm enters. It does not judge whether any AI use is appropriate, and it never changes a record on its own.
Availability
The register is off for every firm by default. ThirdNexa staff turn it on per workspace; firm administrators cannot switch it on themselves. Until it is on, the AI use pages show a “not available” notice and the menu item stays hidden. To begin, contact support and ask for the AI use register to be enabled for your firm.
Once it is on
- An AI use item appears under Risk & reporting. Add a use case with the short form, or start from an existing vendor so the page shows that vendor's AI answers, latest review and Reg S-P clause status live.
- Contributors and Reviewers add and edit Proposed and In use records. Only a Firm Administrator can move a use case to Approved, Restricted or Retired, each with a short written note; who changed it and when are stamped automatically. An approved use case can be retired but never deleted.
- The coverage view shows firm-level items and a grid of use cases by checklist item. It shows what your firm has recorded; it does not assess whether your controls are adequate.
- Reports gains an AI use evidence pack, and the Annual evidence pack can include an optional AI use section. Every download is recorded in the activity log.
- Use-case review dates appear on the Calendar, and turning the register on adds a yearly “Review AI use inventory” item.
The detailed sections AI use register, checklist and coverage and evidence pack appear in the guide below.
At a glance
What is in this release.
45 capability areas, each with the place to start in the application.
- New: AI Vendor Oversight (controlled rollout, turned on per firm by ThirdNexa staff) — record each vendor's AI systems, run AI risk assessments, send the AI due diligence questionnaire, record AI decisions with follow-up, and log AI changes.
- New: AI oversight dashboard with filters, ready-to-use and saved views, a personal default view, audited CSV exports and export history.
- New: AI contract review, clause by clause, with cited source text and labeled regulatory references.
- New: dated AI decision history, evidence, remediation and reassessment dates in examination-ready reports.
- New: an AI column and Yes/No/Unknown filter on the Vendors list.
- Improved: questionnaires are answered against the exact version sent, with required and conditional answers checked on submission.
- Improved: QuickBooks vendor-list exports import with columns recognized automatically.
- An optional AI use register: record each AI tool your firm uses, its approval status, checklist evidence and a dated evidence pack.
- A centralized vendor inventory with business and compliance ownership.
- Reviewed imports from spreadsheets, PDFs, Word documents, pasted lists, and images.
- Customizable due diligence questionnaires with conditional questions and exception flags.
- AI-assisted contract extraction, vendor oversight briefs, and assurance-report analysis.
- Contract renewal tracking and a Regulation S-P clause checklist.
- Incident workflows, findings, remediation conditions, and assigned tasks.
- Examination request tracking and a permanent production log.
- Deficiency response workflows with linked remediation steps and evidence.
- A compliance calendar with recurring obligations and existing oversight deadlines.
- Day One vendor summaries, annual review evidence packs, and source-record indexes.
- Multi-firm consultancy access, role-based permissions, and account security controls.
- Expanded Help Center guidance and Ask AI answers with inline citations and article previews.
- Questionnaire versions, exact sent-version links and previewable audit packets.
- Internally attested answers with citations and pre-download provenance warnings.
- Firm-branded PDF exports, workspace archives and explicitly approved departure deletion.
Contents
01
Vendor inventory and ownership
Where to begin
- Vendors → Add vendor.
One record for each service provider
Maintain vendor details, services, contacts, business ownership, compliance ownership, risk information, customer-information access, and supporting records in a single place. Contracts, reviews, documents, findings, and incidents remain connected to the vendor they concern.
Business owner and Compliance owner selectors show teammates with their roles and membership status, helping your team distinguish an active colleague from an invited teammate.
Risk information with a recorded rationale
Record customer-information access, service criticality, and other oversight details. Risk tier labels are Critical, Standard, Low and Unclassified, not a configurable High/Moderate scale. ThirdNexa can suggest a tier; your firm reviews it and records a reason when overriding it. Scored risk assessments retain the factors behind a classification.
The Add vendor form identifies unanswered required questions before saving, including “Accesses customer information?” Your team can answer Yes, No, or Unknown rather than leaving the field blank.
Fill from website
Enter a vendor’s website and use Fill from website to suggest identifying details such as its name, legal name, type, description, and services. The tool fills empty fields without overwriting what you entered and reports which fields it populated.
Some websites block automated reading. When a clearly recognized company is identified using general knowledge instead, the tool discloses that basis. Suggested information still requires review.
Required documents and outstanding work
A vendor's Documents tab flags required evidence as received, missing, expiring or expired. Firm administrators can override the per-tier checklist in Settings; missing items never block saves. W-9 is its own category and never substitutes for financial statements. A newly missing requirement after a tier change can create a task due in 30 days, high priority for Critical vendors; imports do not create these tasks.
Dashboard status and tier counts open filtered vendor lists. Exam readiness shows outstanding evidence and overdue work, not a compliance conclusion. Reports → Exam readiness by vendor supports tier, gap and began-date filters, firm-shared saved views and CSV export. What's due combines recorded deadlines with Past due, 30/60/90-day, 6-month and 12-month horizons; consultants can switch between this firm and all authorized client firms.
02
Imports that keep your team in control
Where to begin
- Vendors → Import (or select “Import contracts instead” / “Import everything at once”).
More ways to bring in vendor information
Import vendor lists from CSV and Excel files, PDFs, Word documents (.docx), and supported images such as screenshots. Use Paste a list for clipboard text rather than creating a file first.
The full import tools are available after a workspace is created. The initial signup vendor step remains CSV-only.
Review, verify, and reconcile before saving
The three-pass import workflow preserves source values alongside proposed values, checks for missing or conflicting information, and reconciles the outcome before commit. Your team can:
- Inspect original values beside normalized or edited values.
- Review mapping confidence and flagged issues.
- Resolve likely duplicates without automatic merging.
- Accept records, merge selected values, keep records separate, retain existing values, or skip rows.
- Explicitly clear an existing field when intended; incoming blanks do not silently erase existing information.
- Confirm that every source row is accounted for before saving.
Spreadsheet commits are all-or-nothing for the reviewed import scope. Multi-worksheet workbooks review and save vendors first, then process the contracts worksheet against the vendor inventory. Each worksheet has its own commit and audit entry.
Contract documents and batch retries
Upload several contract PDFs for AI-assisted extraction and review. Check the extracted terms, resolve the vendor match, and approve the contracts you want to create. Contract imports link to vendor records; they do not silently create new vendors.
Each PDF batch receives an Import audit entry listing its files, outcomes, and failures. Retry failed saves without re-uploading the batch or saving successful contracts again. Unreadable files can be re-read, and retries receive their own audit entries.
Combined document imports extract vendor details only. Use the contract import workflow for contract documents.
A permanent import record
The Import audit records counts, reconciliation results, row or file outcomes, and relevant source-to-value changes. Export audit details as CSV for later review.
03
Due diligence reviews and questionnaires
Where to begin
- Questionnaires to manage templates; Reviews to start due diligence.
Structured initial and recurring reviews
Use reviews to collect vendor responses, examine supporting evidence, record issues, and preserve the firm’s final decision. Reviews retain their status and decision context rather than treating a completed questionnaire as automatic approval.
Customizable questionnaires
Start from the financial-services questionnaire library, copy a template, create one from blank, or upload questionnaire questions from a spreadsheet. Organize questions into sections and configure question types, required responses, help text, and applicable risk tiers.
Questionnaires support Draft, Active, and Retired states. Drafts remain editable before use; Active questionnaires are available for new reviews; retiring a template does not remove answers from historical reviews.
Conditional questions and exception flags
Conditional questions appear based on prior answers, reducing irrelevant follow-up questions. Exception rules help reviewers identify responses that need attention, including unknown answers and missing required evidence.
Vendors respond through secure links without creating a ThirdNexa account. Section assignments help organize questionnaire work and follow-up.
04
AI assistance with human review
Where to begin
- Open a vendor for the AI brief; open its Documents area for report analysis.
Vendor oversight brief
Generate a plain-English brief from a vendor’s existing oversight records, including reviews, findings, incidents, contracts, and documents. Copy the brief for internal discussion or use it as a starting point for a review.
The brief summarizes recorded facts. It is not a vendor approval, risk acceptance, or regulatory conclusion.
SOC and assurance-report analysis
From a vendor’s Documents area, use Analyze report to extract information from an assurance report, including:
- Report type, auditor, reporting period, and stated opinion.
- Scope and relevant criteria.
- Complementary user entity controls (CUECs).
- Auditor testing exceptions and stated management responses.
- Named subservice organizations.
Your team records its response to each CUEC, with who recorded the status and when. Existing CUEC sign-offs are preserved when a report is analyzed again. Create a finding from an extracted exception when your team decides follow-up is needed.
AI extraction may omit or misread information. Review the original document before relying on an extraction or summary. Identifying a subservice organization in a report is not the same as continuously monitoring that organization.
05
Contracts and Regulation S-P oversight tools
Where to begin
- Contracts for individual records; Reg S-P clauses for the checklist view.
Track contract terms, renewal dates, notice periods, and cancel-by dates alongside the vendor record. AI-assisted document extraction provides proposed terms for review rather than silently accepting them.
The Regulation S-P contract checklist records clause status and supporting context. Its revised notification description reads:
Vendor notifies the firm within 72 hours of becoming aware of unauthorized access to or use of customer information.
The checklist records your team’s assessment of contract language. It does not decide whether the rule applies or whether a contract satisfies a regulatory requirement.
06
Incidents, findings, and remediation
Where to begin
- Open the vendor’s incident or finding records; use Tasks for assigned follow-up work.
Incident response records
Record vendor incidents, response activity, decisions, and notice information. The incident workflow organizes assessment, containment, decision-making, notices, and closure, with notice timers to help track recorded dates.
The firm must determine applicability, relevant timing, recipients, and required actions. A timer is a tracking aid, not a legal determination.
Findings and follow-up work
Create findings with severity, ownership, due dates, remediation conditions, and supporting context. Track the lifecycle from investigation and remediation through verification, closure, or recorded risk acceptance.
Assign tasks to teammates and preserve the rationale behind material decisions. Findings, tasks, and related deadlines remain connected to the oversight record.
07
Examination request tracker and production log
Where to begin
- Exams → select or create an exam → add requests and production log entries.
Keep every request visible
Create an exam and enter each request with an owner, due date, and status. Link the vendor records, contracts, reviews, findings, and documents supporting the response. Past-due highlighting helps your team identify requests needing attention.
Record what was sent
The production log preserves what your firm sent to examiners, when it was sent, the delivery method, the associated request, scope notes, and the person who recorded the entry.
Production log entries cannot be edited or deleted. Export the log as CSV for a consolidated record of submissions.
The log records submissions entered by your team; it does not itself transmit materials to regulators or prove receipt.
08
Deficiency response and supporting evidence
Where to begin
- Exams → select an exam → Deficiency response → Generate evidence pack (PDF).
When a deficiency letter arrives, use the exam’s Deficiency response section to:
- 1Record each deficiency as stated, with an owner, due date, and status.
- 2Add remediation steps with their own owners, due dates, and progress.
- 3Link documents, findings, reviews, contracts, or vendors to the deficiency or a specific step.
- 4Record the firm’s written response.
- 5Generate a PDF evidence pack summarizing deficiencies, remediation steps, and linked evidence.
Step completion records the completion timestamp, and generating the pack is recorded in the activity log. The pack organizes the firm’s records; it does not judge whether remediation or a response is adequate. Referenced evidence is listed in the pack rather than represented as a guarantee that every original file is embedded.
09
Compliance calendar and recurring obligations
Where to begin
- Calendar.
Bring recurring obligations together with deadlines already recorded in vendor oversight.
The calendar includes vendor review dates, contract renewals and cancel-by dates, document expirations, findings, tasks, conditions, and exam request deadlines. Add custom recurring obligations with owners and due dates. Completing a recurring obligation schedules its next occurrence automatically.
Dates drawn from existing records remain governed by those source records. The calendar does not independently determine which filings, certifications, training, or reviews your firm is legally required to perform.
10
Reports and evidence packs
Where to begin
- Reports → Day One summary.
- Reports → Annual evidence pack.
Day One vendor summary
Export a concise, one-page summary of active key service providers and their oversight details as PDF or CSV. Optionally include critical and high-risk vendors. Vendor relevance flags determine which key providers appear, so review those flags if the report is empty.
Annual review evidence pack
Select a year to summarize vendor reviews, findings, incidents, and decisions. The evidence index links to source records and supporting documents; the PDF includes an index appendix, and CSV provides the corresponding record list.
This pack supports gathering evidence for the firm’s annual review. It is not the annual review itself and does not establish that the review meets a regulatory requirement.
Broader oversight reporting
Exam evidence packs and Service provider oversight reports bring together inventory, risk tiers, customer-information access, contract clause status, incidents, review coverage, and activity. Vendor evidence packs organize an individual vendor’s record for internal review or examinations.
Report downloads are recorded in the activity log. Links to source records remain subject to workspace access permissions.
11
Consultancy workspaces, permissions, and communications
Multi-firm work without mixing records
Consultants can work across authorized client workspaces from one account. The workspace switcher identifies which firm is open, while firm-level access boundaries govern the records available there. Final vendor approval authority remains with the client firm’s administrators.
Firm Administrator, Reviewer, Contributor, and Read Only roles support different responsibilities. Two-step verification adds an account security control.
Messages, reminders, and branding
Use customizable message templates, merge fields, and previews for supported communications. Staff work summaries help organize assigned work, including cross-client summaries for consultants. Vendor-facing reminders are opt-in.
Supported emails use a “Name via ThirdNexa” sender display with replies directed to the sender. Eligible plans can customize email sender names, signatures, and footers; this is not a connection to the sender’s Outlook or Gmail mailbox.
Settings → Message templates offers due-diligence outreach, recurring review and overdue-request starters, merge-field previews and suggested wording. Recurring and overdue starters require their checklist to pass before saving; outreach checks are advisory. Consultancy owners and managers may share templates across managed clients; client firms can use shared templates but cannot edit or delete them.
Firm PDFs apply the saved firm logo and accent with a ThirdNexa fallback and retain Powered by ThirdNexa. Email sender, signature and footer branding follows firm Growth-and-above and consultancy Practice-and-above entitlements. Custom sending domains and full white-labeling are not currently available.
Plan access and account security
Plan & billing belongs to the open workspace and is managed by its administrators. New firm trials last 30 days without a card. Without a plan or active trial, access locks to Plan & billing; failed renewals allow a 14-day grace period from the first failure. Upgrades apply immediately, downgrades at renewal and cancellation at the paid period's end. Vendor limits warn without blocking entry; consultancy plans cover their client firms. Consult the live pricing page rather than a copied historical price.
Every account uses authenticator-based two-step verification. Use Settings for team invitations and role changes, and My workspaces to distinguish direct membership from consultancy access. Firm admins record final vendor decisions and risk acceptance; a reviewer cannot verify their own assigned finding. A missing control may reflect role, plan or module access, not a broken workflow.
Notifications now open the related oversight record where available, helping recipients move directly from an alert to the work needing attention.
12
Help Center and Ask AI
The expanded Help Center covers imports, vendor setup, reviews, contracts, incidents, exams, reports, calendars, AI tools, roles, billing, and troubleshooting.
Ask AI answers application questions using Help Center guidance. Inline numbered citations identify supporting articles beside specific claims or steps. Citation previews let users inspect an article without leaving the answer, with an option to open the full article.
When guidance is insufficient, the support path remains available. Ask AI is application assistance, not legal or regulatory advice.
For a vendor explanation, name the vendor. Ask AI receives limited recorded fields and findings plus firm-level open-finding and overdue-task counts, not every uploaded file. Unsupported questions and requests for a human can be sent to support with an email acknowledgement. Do not enter passwords or sign-in codes; check original records and article citations before relying on an answer.
Connect Claude or ChatGPT
The public Connect Claude or ChatGPT guide explains the read-only MCP connection. Sign in and approve access; the tools search vendors, show a vendor risk profile, upcoming reviews, open findings and recorded Reg S-P clause status within your permissions. Queries are activity-logged. This connector does not expose every app feature, edit records or approve vendors.
13
Change log and firm responses
Where to begin
- Change log.
Open Change log to record regulatory or business changes, source links, discovered and effective dates, an owner and your firm's response. Link affected vendors and track status. The record describes what the firm did; ThirdNexa does not judge its adequacy.
14
AI Vendor Addendum, AI system details and diligence age
Where to begin
- AI oversight
Each AI system on a vendor page now records model name and version, hosting model (vendor hosted, third-party cloud, model provider API, on premises or unknown), hosting region, zero data retention (yes, no or unknown) and its basis, retention period, new-feature notice, whether public sharing is possible and whether an administrator can turn sharing off. Blank answers stay Unknown or Not reviewed and are never treated as No. The AI systems card has an Export CSV button with every field.
To ask the vendor, open a review, send a questionnaire, choose the shared AI Vendor Addendum template and pick the AI system. ThirdNexa staff maintain the template; firms can copy it before editing. Its questions map one-to-one to the AI system fields plus the vendor's model-change notice.
After the vendor submits, the review's Questionnaire section lists each mapped answer next to the current value. Vendor answers never change your records automatically. A reviewer clicks Apply to AI system for each answer the firm accepts. Every apply is saved in a permanent history with who, when, the old value and the new value, and also appears in the vendor's activity history. Only answers from the version that was sent, and only valid choices, can be applied.
Diligence age shows the last verified date for each AI system. It shows Not reviewed since <date> (or Not yet verified) when the last verification is more than 12 months old, or when a new-feature, model or retention-policy change was logged for that system after its latest AI risk assessment. This is a neutral reminder, not a pass, fail or adequacy determination.
Filter by it with Diligence age: Needs a fresh look on the AI systems card, or the Diligence age view (and the ready-made AI systems not reviewed recently saved view) on the AI oversight dashboard. Dashboard CSV exports include those rows when that view is selected.
15
AI Vendor Oversight: what it is and how to turn it on
Where to begin
- AI Vendor Oversight overview
AI Vendor Oversight covers AI used by your vendors (for example, a CRM or custodian that uses AI on your data). It is separate from the AI use register, which records AI your own firm uses.
It is in a controlled rollout and is turned on per firm by ThirdNexa staff. Choosing or changing a plan does not turn it on. Contact support to discuss availability. When it is on, vendor pages show the AI cards described in these articles and an AI oversight item appears in the menu.
The workflow is: record the vendor's AI systems, run an AI risk assessment, send the AI due diligence questionnaire, record an AI approval decision with follow-up, record later AI changes, and review everything on the AI oversight dashboard and in examination-ready reports.
AI decisions never change the vendor's ordinary approval status, risk tier or billing. ThirdNexa records what your firm decides; it does not decide whether a vendor's AI is appropriate and does not give legal advice.
16
Record a vendor's AI systems
Where to begin
- Vendors
Open the vendor and find the AI use card. Answer whether the vendor uses AI (Yes, No or Unknown), then add one entry per distinct AI system: name, what it does for your firm, data it touches (including customer NPI), model provider, internal owner and next review date.
Blank or unanswered items stay Unknown and are never treated as No. Existing No answers are preserved.
The Vendors list has an AI column showing AI in use, Unknown or No and the number of active AI systems. The Uses AI filter offers Yes, No and Unknown, and the vendor CSV export includes the AI system count.
Every change is stamped with who and when in the vendor's history.
17
AI risk assessment for a vendor
Where to begin
- Vendors
On the vendor page, open the AI risk card and start an assessment. Answer the six categories: data privacy and customer information; information security; model transparency and reliability; regulatory and compliance exposure; AI subprocessors and third-party dependencies; and operational resilience and human oversight. The rating is calculated the same way every time from your answers and the saved weights, shown on screen.
Safeguards you have not confirmed count as unknown rather than in place. High ratings require a documented review. A reviewer can override the rating only with a written justification, and the original calculation is kept.
The AI rating is separate from the vendor's ordinary risk tier and never changes it. Assessments are saved in the vendor's risk history and appear in reports.
18
Send the AI due diligence questionnaire
Where to begin
- Questionnaires
Start a review for the vendor and choose the AI Vendor Due Diligence questionnaire (10 sections, 31 questions). Follow-up questions appear only when they apply, for example extra questions when the vendor handles customer NPI.
You can link the request to one of the vendor's AI systems; the system must belong to the same vendor and firm. Shared templates are read-only: copy one to your firm before editing.
Sending, reminders, versions and the audit packet work the same as any other questionnaire.
19
Questionnaire submission safeguards
Where to begin
- Questionnaires
Each request is locked to the template version that was sent. If you edit the template later, the vendor still sees and answers the original questions.
Final submission is checked on the server: every required question that applies (including conditional follow-ups that are switched on by earlier answers) must be answered. The vendor sees which questions are missing.
Answers to questions that are not part of the sent version are rejected. If an answer cannot be saved, the vendor sees an error instead of a silent loss, and nothing is partly submitted. Two people submitting at once cannot overwrite each other.
A few older requests sent before versions were recorded cannot be validated safely; they show an error and must be resent.
20
Record an AI approval decision and follow-up
Where to begin
- Tasks
From the vendor's AI card, a firm reviewer records a decision for an AI system with a written rationale, links supporting evidence (questionnaire answers, documents, assessments), and can add conditions, findings, owned follow-up tasks and a reassessment date on the calendar. Everything saves together or not at all.
Decisions are permanent history: a new decision supersedes but never deletes the old one. The AI decision is independent of the vendor's approval status and billing.
Follow-up tasks get the normal reminders and appear on the vendor's monitoring panel and the AI oversight dashboard.
21
Record vendor AI changes and track alerts
Where to begin
- AI oversight
On the vendor page, open AI changes and click Record change. Choose the AI system, category (for example New AI feature, Material model change, New AI subprocessor, Model training policy or AI security incident), materiality, a firm reviewer, required action and due date. Attach up to 50 of the vendor's documents as evidence.
Saving creates the linked follow-up task (with reminders), an optional reassessment calendar item that also updates the system's next review date, and a notification to the reviewer, all at once.
A change can be closed only after its linked tasks are complete. Changes cannot be deleted and their links cannot be altered. Open, overdue and upcoming items show as alerts here and on the AI oversight dashboard.
22
AI oversight dashboard, saved views and CSV export
Where to begin
- AI oversight
Open AI oversight from the menu. Cards show recorded changes, open alerts, overdue follow-ups and items due within 30 days. Filter by search, vendor, system, owner, status, category, materiality, date range and view (All, Changes, Alerts, Overdue, Follow-ups). Rows link to the vendor record.
Ready-to-use reports: AI vendor changes, Open AI alerts and Overdue AI follow-ups. Use Save a copy to keep one as a firm view. Firm saved views are shared with your firm; save, replace or delete them if you can edit records. Choose a view as your own default; links that already include filters always open as linked.
Export CSV downloads exactly the filtered rows for your firm. Before the file is released, the export is recorded permanently with who exported, when, the filters and row count; if that record cannot be saved, the download does not happen. The Export history panel shows those records.
23
AI contract review and regulatory references
Where to begin
- Contracts
Open a contract and find AI contract review. For each of the ten AI clauses (customer data and model training, data retention and deletion, AI subprocessors, material AI functionality changes, information security, incident notification, data ownership and confidentiality, human oversight, audit rights, and termination and data return), record a status: present, absent, ambiguous, not applicable or not reviewed, with a rationale of at least 20 characters and the source document.
Read AI provisions can read the contract file and suggest quoted text. Suggestions never set a status or verification; a person confirms each one. If reading fails, your draft is kept.
You may map a clause to up to seven reference sources. Each is labeled as a binding rule or voluntary guidance, with an official link. Mappings are reference only, not legal conclusions. You can optionally link an existing verified finding. Every review is permanent history.
24
AI history in examination-ready reports
Where to begin
- Reports
The vendor examination-ready report and the evidence pack (PDF, CSV and ZIP) include a dated history of AI decisions with approvers, previous and new statuses and justifications, linked evidence, remediation status and reassessment dates.
Historical decisions and current remediation or schedules are labeled separately so an examiner can tell what was decided then from what is open now. Reports show only your firm's records.
25
AI use register: record how your firm uses AI
Where to begin
- AI use register
Open AI use under Risk & reporting. The menu item appears only when ThirdNexa has turned the AI use register on for your firm; ask support if you do not see it.
Click Add AI use case and fill in the short form: a name, the AI tool, who uses it and why, what data it touches and where the output goes. Use Start from a vendor to link a tool to an existing vendor. Everything else (tool type, use case type, owners, model name and version, human review, prompt and output retention, review dates) can be completed later on the use case page.
Yes / No / Unknown answers start as Unknown or Not reviewed. A blank answer is never treated as No.
Contributors and Reviewers can add and edit Proposed and In use records. Only a Firm Administrator can move a use case to Approved, Restricted or Retired, and each of those needs a short written note. Who changed it and when are stamped automatically. An approved use case can be retired but never deleted. Every change appears in the use case's activity history.
When a use case is linked to a vendor, its page shows the vendor's AI answers, latest review and Reg S-P clause status read live from the vendor record. The dashboard tile 'Vendors reporting AI use with no recorded use case' lists vendors whose record says they use AI but have no linked use case. Review dates appear on the Calendar, and turning on the register adds a yearly 'Review AI use inventory' calendar item.
ThirdNexa records what your firm enters. It does not judge whether any AI use is appropriate.
26
AI use checklist and coverage view
Where to begin
- AI use coverage
The checklist has firm-level items (for example, an AI use inventory on file and written policies covering AI use) and per-use-case items (for example, testing, prompt and output logging, model version and human review). Agent items appear only for agent tools, and items about client or public statements appear only when the output goes to clients, marketing or a regulatory filing. Items that do not apply are hidden.
Each item can be Recorded, Not recorded, Not applicable or Not reviewed. Not applicable needs a note explaining why. Recorded needs a note or at least one evidence link: a web link, a document already on file, or an obligation from your obligations register. Who updated it and when are stamped automatically.
Each item shows its reference with section and page. These are reference only: they come from regulator-published considerations and exam priorities, such as the 2026 FINRA Annual Regulatory Oversight Report and the SEC Division of Examinations' fiscal year 2026 priorities, not from rules. They are not legal or regulatory advice.
Open Coverage from the register to see firm-level items and a grid of use cases by item, with counts per status and a CSV export. The view shows what your firm has recorded. It does not assess whether your controls are adequate or whether your firm meets any rule.
27
AI use evidence pack
Where to begin
- AI use evidence pack
Open Reports and choose AI use evidence pack, then pick a period. The PDF and CSV include the register as it stood at period end (rebuilt from the audit trail), status changes and approvals made in the period with who, when and the note, the checklist records, an evidence index linking each record to its source, and a page listing what has not been recorded yet. That page is a list of items not on file, not findings.
The AI use register can also be added as an optional section to the Annual evidence pack. Every download is recorded in the activity log.
28
Obligations register: turn your policies into tracked obligations
Where to begin
- Obligations
Open Obligations under Risk & reporting. Upload your vendor management policy, WSPs or incident response plan. ThirdNexa reads it and lists each thing the policy says your firm must do about vendors, with the exact quote, section, tiers it applies to, how often, and where the evidence would live in ThirdNexa.
Every extracted item starts as Awaiting approval and does nothing until approved. Click Review to check the wording against the quote, edit it, pick an owner from your team, set the next due date, and choose where the evidence lives (for example Reviews or Contracts) or paste a link.
Only a firm approver can approve or reject, and must write a short note explaining the decision. Approval requires an owner. Who decided and when are stamped automatically and every change goes to the activity log. Active obligations can later be retired, never silently deleted.
The summary tiles show items awaiting approval, active, overdue, and active without evidence. Export CSV gives an exam-ready register. ThirdNexa only reports what your policy says; it never judges whether the policy is adequate.
29
What ThirdNexa automates, and what stays your decision
Where to begin
- Setup status
- Dashboard
- User guide
In plain terms: ThirdNexa does the busywork, you make the calls. It reads contracts, SOC 2 reports, policies and spreadsheets, fills in suggested values with the exact quote it used, calculates due dates, builds task lists, sends reminders to your staff, tracks what is missing, and assembles reports and evidence packs.
It never acts for you. It does not approve or reject vendors, set a risk tier without you saving it, answer a questionnaire for the vendor without your confirmation, email vendors unless you choose to, or say a vendor or your firm is compliant. Every suggestion waits for a person to check and save it, and the activity log records who did.
Automated today: contract and document reading with citations, new vendor setup from a signed contract (vendor, contract, onboarding tasks, first review), default reminder schedules, review due dates from your tier frequencies, overdue and due-soon alerts, required-document gap checks by tier, policy rule extraction, AI-drafted cited answers for internal attestation, questionnaire version snapshots, and report, CSV and evidence pack generation.
To see which automations are switched on for your firm and what needs attention, open Setup status in the menu. It lists each workflow as set up, needs attention or optional, with the next step and a link.
Always yours: the risk tier, the final review decision and its rationale, confirming each AI answer against its source, accepting policy rules, deciding when to contact a vendor, and judging whether evidence is adequate. ThirdNexa gives no legal advice or regulatory conclusions.
30
How review due dates are calculated
Where to begin
- Settings
Each vendor's next review date is worked out for you. ThirdNexa takes the date the last review was completed and adds a number of months. Which number? First a frequency set on that vendor, then your firm's default for the vendor's tier (Settings, Oversight defaults), then the built-in cadence: Critical 12, Standard 24, Low 36 months.
The vendor's Overview shows a Review schedule card with the frequency, where it came from, the last review and the next due date. Every page (vendor, Dashboard, Calendar, Reports, What's due) uses the same calculation, so they always agree. If a month is shorter, the date lands on its last day (Feb 29 plus 24 months is Feb 28).
Change a tier default and every vendor in that tier updates at once; nothing needs editing by hand. A vendor never reviewed keeps its originally recorded due date. Changes to frequencies are recorded in activity with before and after values.
31
Due-soon and overdue alerts, review chart and review exports
Where to begin
- Dashboard
- Reviews
The Dashboard shows a red banner when reviews are overdue and a yellow one when reviews fall inside your due-soon window (7, 14, 30, 60 or 90 days, set in Settings, Oversight defaults; default 30). Counts are split by tier, and the banner opens the What's due queue.
The Review activity chart shows reviews completed on time, completed late and upcoming, by tier, from the past 12 months to the next 6. Click any bar section to open Reviews already filtered to that month, tier and status.
On Reviews, save a set of filters as a named view, and use Export CSV with the Columns picker to choose what goes in the file. Your column choice is remembered in this browser for the workspace. Alerts and charts only point to work; they never complete a review.
32
Risk assessment and tier changes
Where to begin
- Vendors
Open a vendor's risk assessment and score the factors. Scores start at values matching the current tier so saving without changes keeps it. ThirdNexa calculates a suggested tier and shows a yellow notice if it differs from the current one.
Guided option: open Setup status and choose Assign tiers next to Risk tiers recorded. Pick an Unclassified vendor, answer four questions (customer information, systems access, critical function, continuity), and ThirdNexa shows a suggested tier with its reasons. Each tier card shows how often the vendor would be reviewed, where that frequency comes from, the next due date, and which documents would be required. Choose a tier, write a short reason and save; a task is created for any newly required documents.
Lowering or raising an existing tier needs a short written reason, kept for exams. Giving an Unclassified vendor its first tier does not. Changing tiers can add a follow-up task (30 days, high priority for Critical) and changes required documents and review frequency automatically. You save the tier; ThirdNexa never sets it alone.
33
Set required documents and review frequencies from your vendor policy
Where to begin
- Settings
In Settings, under Required documents by risk tier, choose Set from our vendor policy and upload a PDF, Word or text file. ThirdNexa reads it and lists the document requirements and review frequencies it states, each with the exact quote and section.
Compare each suggestion with your current settings and tick only what you agree with. Nothing changes until you choose Apply. Provisions it cannot map are shown for reference. It only reports what the policy says, never judges whether the policy is adequate, and every applied change is logged.
34
Adjust, review and retry contract reminders
Where to begin
- Contracts
On a contract page, the Reminders section lets you choose Adjust renewal reminders to set your own days, reset to the default or turn them off. Each linked task has its own on or off choice, with a reason shown when it cannot send (no due date or nobody assigned).
Reminder delivery history lists each reminder as Sent or Failed with the reason. Retry resends a failed one and records it as a manual retry. Reminders go to your staff only, never the vendor.
35
Flag an unhelpful or outdated answer
Where to begin
- Help Center
Under an open Help article or a finished Ask AI answer, choose Flag as unhelpful or outdated, pick a reason and add a note if you like. ThirdNexa staff review the flags and correct the guidance. Flags do not change any of your records.
36
Set up a new vendor from a signed contract
Where to begin
- New vendor from contract
Go to Contracts and choose New vendor from contract. Upload the signed PDF, Word or text file and choose Read contract. ThirdNexa reads it three times and fills in only the values the readings agree on; check and correct every field before creating anything.
Reg S-P clauses found in the contract are pre-ticked with the supporting quote. Confirm each against the contract; unticked clauses stay not reviewed. This records what the contract says, not a compliance conclusion.
Creating adds the vendor as Onboarding with no risk tier, the contract with you as owner, the signed file in the vendor's documents, four onboarding tasks (SOC 2, W-9, certificate of insurance, risk assessment) due in 30 days, and an initial due diligence review due in 30 days. Each can be switched off first.
Reminder emails go only to you: 7, 3 and 1 days before each task is due, and 90, 30 and 7 days before the contract's cancel-by date (or renewal date when no notice period is set). Nothing is emailed to the vendor. If the vendor already exists, use Upload contract PDFs instead.
37
See which contracts still need reminders
Where to begin
- Contracts
- New vendor from contract
Contracts opens with a Reminder coverage panel: contracts with renewal reminders on, contracts with task reminders on, contracts that still need each, and contracts with no tasks linked yet. Renewal reminders go 90, 30 and 7 days before the cancel-by date (or the renewal date when no notice period is set); task reminders go 7, 3 and 1 days before a task is due.
Use the Reminders filter to list only the contracts that still need them. With write access, Enable renewal reminders switches the default schedule on for every contract that has a cancel-by or renewal date and none yet, and Turn on task reminders switches the default schedule on for the open, assigned tasks of each contract whose open tasks send none.
Reminder emails go to firm staff only, never the vendor. A contract with no tasks linked has nothing to remind on until a task is added, and an open task with no due date or nobody assigned cannot send a reminder until it is filled in. Contract CSV export carries the renewal and task reminder state for each row.
38
AI-use import review and source-to-record provenance
Where to begin
- Import vendors
- Import audit
During import review, Artificial intelligence use shows the source column, original answer and proposed Yes, No or Unknown value. Show flagged only focuses on ambiguous, unreadable or Unknown answers; Show all includes the rest. Choose a correction for a row or Export CSV to review the mappings. Nothing is saved until the import is committed.
Corrections flow through the normal review and verification checks and are recorded as reviewer edits alongside the original source value. Blank input must not be treated as a confirmed No. After saving, the Import audit preserves source-to-value changes and CSV exports for later review.
Where a record has stored AI provenance, View AI proposal opens the proposed-versus-saved comparison. It distinguishes what AI proposed from what a reviewer saved; it is not proof that the source was accurate. Check original files before using the imported fact in a decision.
39
AI assistant connection diagnostics
Where to begin
- AI assistant diagnostics
- Connect Claude or ChatGPT
Open AI assistant diagnostics and click Run diagnostics. It checks that the connection address refuses unsigned requests, confirms your sign-in, runs the same read-only Reg S-P query used by the assistant tool, compares returned firms with active memberships, and writes and reads back diagnostic mcp_query activity entries for the firms touched.
The test does not change vendors, contracts or findings, but it does create diagnostic activity history. It is an app-side check, not proof that your external Claude or ChatGPT connection completed successfully. Verify that separately by asking the connected assistant a supported read-only question and checking the resulting activity.
If a check fails, read its displayed detail and contact support rather than assuming it proves a data leak or granting broader permissions. Accounts using consultancy access may need support to interpret a membership-based scope result.
40
Questionnaire version history, comparisons and vendor previews
Where to begin
- Questionnaires
- Requests
Open Questionnaires, select a questionnaire and scroll to Version history. Saving creates an immutable numbered snapshot with author, timestamp and optional change reason. Compare versions to see changed questions and settings; export the history as CSV. Existing questionnaires receive a baseline on their first tracked save; earlier edits are not reconstructed.
Use Preview as vendor to test current edits before saving or sending, including conditional questions and required-answer progress. An archived version's preview is read-only and does not send a request or change the live questionnaire. Draft questionnaires cannot be sent; activating makes a questionnaire available for new reviews but does not email vendors.
When a questionnaire is sent, changed questions are saved as a version first and the request is linked to that snapshot. Requests, the review's request history and Version history show the recorded version. Select that version link to open its read-only preview. Older requests without a recorded version show not recorded; do not assume today's questions were what those vendors received.
Version history also lists requests sent with each version, including recipients, status and send or response dates. Editing today's questionnaire does not rewrite these historical snapshots.
41
Preview and download a questionnaire audit packet
Where to begin
- Questionnaires
Open Questionnaires, select a questionnaire, then in Version history choose Preview audit packet. The preview groups version summaries and change notes with the requests linked to each version. Check the vendor, request status, question, submitted answer, respondent and response time, and supporting-document metadata.
Choose Download PDF in the preview to generate the packet from those loaded records. The packet keeps author and date information, version changes and version-linked request history. No answer means no submitted answer is recorded for that question; it must not be treated as a yes or a satisfactory response.
Supporting documents are listed by their recorded metadata; their original files are not embedded in the PDF. Review-level documents can appear under more than one questionnaire on the same review. Download originals separately when needed. Requests predating version tracking are not silently linked to a guessed version.
42
Complete a questionnaire internally from vendor documentation
Where to begin
- Reviews
- Exam evidence pack
Upload the vendor's supporting documents first. Open its review and choose Complete internally from vendor documentation. Select up to six of that vendor's uploaded documents to draft answers with AI, or enter answers manually.
For each answer, check the original document and review or edit the cited document, page, section or control and quoted passage. If the documents do not address the question, record that rather than inventing an answer. Nothing is saved until you confirm that you checked the answer against the cited passage.
Saved internal answers retain the reviewer, acceptance timestamp, citations and whether AI drafted the answer or the reviewer authored it. They remain separate from the vendor's submitted responses; internal completion must not be represented as the vendor's own attestation.
Reports → Exam evidence pack includes internally attested answers in its preview and PDF, CSV and ZIP exports, with citations and reviewer/time provenance. Check the provenance-gap summary before downloading; it links to reviews containing affected answers. Internal answers are not automatic approvals or legal conclusions.
43
Evidence pack preview and internal-answer provenance gaps
Where to begin
- Exam evidence pack
- Reviews
Open Reports → Exam evidence pack and review the selected records before downloading. The Internally attested questionnaire answers preview shows each answer, full citations, reviewer, timestamp and authorship information.
When gaps exist, an amber summary counts missing citations, missing reviewer information or an unmatched reviewer profile, and missing timestamps. It lists affected answers by vendor, questionnaire and question; clean answers show no warning. An answer can have more than one gap.
Select the link beside a gap to open the review containing that answer. Check the original documents and the recorded attestation before correcting it through the internal-completion controls. Never invent a reviewer, backdate acceptance or add a citation that does not support the answer. If historical provenance cannot be established, preserve the limitation and contact support.
The summary is a review warning, not an adequacy determination or a guarantee that downloads are blocked. An answer with no citations is labeled Not addressed in vendor documentation. PDF, CSV and ZIP exports preserve the recorded provenance, not a replacement for checking the originals.
44
Full data export and post-departure retention
Where to begin
- Settings
A firm administrator opens Settings → Full data export → Download full export. The ZIP contains CSV and JSON for the included firm-scoped record types, organization settings as JSON, original uploaded vendor files that could be downloaded, and manifest.json. It includes vendors, reviews, questionnaires and versions, responses, contracts, findings, tasks, exams, team, activity and supporting records the administrator is permitted to read.
Check the manifest after every export: it lists counts, included files and partial reads or files that could not be downloaded. Large workspaces may take several minutes. Tokens, passwords, secrets and hashes are omitted, and downloading is recorded in the Activity log. This archive is not an automatic restore tool or a guarantee that every system record is included.
Under Export availability after your firm leaves, enter a whole number from 30 to 365 days and click Save. The initial value is 90 days. Changes are logged; the manifest records the current setting. Download and inspect your archive before starting departure and before the scheduled removal date. Your firm is responsible for retaining the archive according to its own obligations.
Starting departure sets the scheduled date using the retention period saved at that moment. Changing the setting afterward does not recalculate an existing departure date. Expiry makes removal eligible for staff approval; it does not automatically delete records or guarantee continued sign-in if other access or billing restrictions apply.
45
Start or cancel firm departure and permanent removal
Where to begin
- Settings
Firm administrators open Settings → Full data export → Leave ThirdNexa and remove data. Download and inspect the archive first, set the retention period, type the displayed firm name exactly and click Start departure. This schedules when removal becomes eligible; it does not immediately remove records.
Every member sees an in-app departure warning, and active firm administrators receive a notification telling them to export before the scheduled date. Countdown reminder emails are not currently implemented. The warning is not proof that an email was delivered.
A firm administrator can click Cancel departure in the same section before permanent removal. Starting or canceling is recorded in activity. Removing a team member or the last person leaving a firm is different: that closes or ends access without itself requesting permanent deletion.
After the export window, ThirdNexa staff must explicitly approve removal. The firm administrator cannot perform that final step. Permanent deletion removes the firm's records and uploaded files and keeps a staff-visible deletion record. It cannot be undone in the app; download your records first and contact support about access problems before the deadline.
Rollout
A practical rollout checklist.
For a firm adopting these capabilities, in the order the work usually happens.
- 1Review team roles and assign vendor business and compliance owners.
- 2Import the vendor inventory and resolve flagged rows before committing.
- 3Record customer-information access and review risk classifications.
- 4Attach contracts and assurance documents; verify AI-extracted information against originals.
- 5Configure questionnaires and schedule recurring due diligence.
- 6Assign findings and tasks, then review upcoming dates in Calendar.
- 7For an examination, create requests and record submissions in the production log.
- 8Link remediation evidence to any deficiencies and export the relevant evidence pack.
- 9Generate the annual pack for the selected year and review its evidence index.
Scope and availability
What this guide covers, and what it does not.
This guide describes implemented product capabilities, not a promise that every feature is included in every subscription. Consult current pricing and workspace permissions for availability.
The read-only Claude/ChatGPT MCP connection and Change log are implemented. A documented customer read/write API with configurable webhooks, self-service SSO/SCIM, mock exam mode and full white-label custom domains are not current capabilities. Employee personal-trading surveillance and code-of-ethics monitoring remain outside vendor oversight. Departure countdown reminder emails are not implemented; warnings are in-app.
ThirdNexa’s analysis of a vendor’s SOC report should not be read as a statement that ThirdNexa itself holds SOC 2 certification.
Keep vendor oversight work, examination requests, and supporting evidence connected—while your firm retains control of every decision.
ThirdNexa is a software platform provided by ThirdNexa LLC. ThirdNexa does not provide legal, regulatory, or compliance advice, and use of the platform does not guarantee compliance with any law or regulation or any particular examination outcome. Each firm remains solely responsible for establishing and maintaining policies, procedures, supervision, controls, and oversight appropriate to its regulatory obligations. ThirdNexa LLC is not affiliated with or endorsed by the SEC, FINRA, or any other regulatory authority.

