T-NEX Compliance

Turn regulatory requirements into action faster.

T-NEX Compliance connects new regulations with your internal policies, assessments and actions. AI helps explore and compare the content. Your team identifies gaps, assigns tasks and tracks implementation through to the audit report.

T-NEX Compliance: Assess gaps
Original view from the Compliance functional manual, 30 August 2026.
T-NEX Compliance

From a new regulation to the audit report.

Documents, requirements, assessment and implementation stay connected. New regulation versions and scheduled reviews bring requirements back for assessment.

In daily work

How to use the solution.

For compliance leads and business teams that need to work through requirements and make implementation traceable for internal audit.

Regulations, internal evidence and actions remain connected in one workflow. We configure the application with the modules, data access and roles your institution needs for this process.

Functions

How the application supports your team.

01

Version regulations

Clauses belong to a specific document version. Earlier versions retain their links to requirements.

02

Check extraction against the original

The source view places extracted clauses beside the original document.

03

Requirements with provenance

Derived requirements link back to their clauses and receive business review and approval.

04

Separate assessment from approval

AI proposals and manual assessments are handled in a dedicated review step.

05

Track remediation

Approved gaps receive remediation actions and assigned tasks with due dates and progress.

06

Preserve the issued report

The report covers a defined scope and preserves its state after issue.

Overview

Connect requirements with assessment and implementation

T-NEX Compliance maintains external regulations and internal control documents as two distinct starting points. Requirements derived from them are assessed against each other. Identified gaps lead to remediation plans, assigned tasks and a report with a defined audit scope.

Approvals connect these stages: confirmed clauses become available for requirements work, while approved gaps can enter remediation planning. This sequence shows where business review is missing and who needs to approve the next step.

Overview

Identify connections between regulations

A requirement includes its rationale, source reference and expected control measure. Priority, type and ownership support its processing. Mapping requirements to framework controls can connect requirements from several regulations with the same control.

List view supports daily work. Framework view shows common controls; regulation view follows the source hierarchy. Applicability attributes narrow the business scope. The institution records its rationale for deciding that a requirement does not apply.

Overview

Check AI assessments against their basis

Assessment starts by interpreting an external requirement for the institution. The assessment form brings together expected controls, implementation steps and linked internal evidence. An AI proposal can be generated for one requirement or a selected group.

The subsequent review queue is used to assess evidence and results. Fulfilment status, confidence in a mapping and gap severity answer different questions. A high similarity score is therefore not approval. The responsible person can amend or override the assessment and record additional gaps.

Overview

Turn identified needs into concrete actions

For an approved gap, T-NEX Compliance can prepare a plan with remediation tasks, subtasks and estimated effort. The originating requirement and gap rationale remain accessible alongside it. Business owners add dates, priorities and responsibilities.

The gap and its remediation each have a separate approval point. Approved measures then enter task execution. Progress and outstanding work are visible there, while change history associates updates with their time and author.

Overview

Incorporate changes into the workflow

A new edition receives its own version. The earlier edition and derived requirements remain available. Changed regulations and scheduled reassessments can appear as separate work items in the assessment process.

Review can therefore start with specific questions: which clause changed, which requirement depends on it and which assessment needs attention? The document-version reference helps distinguish the current position from earlier review results.

Overview

Keep management and audit informed about implementation

An audit defines a period, external requirements and internal evidence. It can be departmental, recurring, ad hoc or limited to assessment. The report brings together an executive summary, scope, results, gaps, task progress, ownership and recommendations.

While the report is a draft, it follows the working data. Issuing it freezes the figures. Scope, assessments and summary are therefore checked before issue. Reading, editing and approval can be assigned separately across the individual compliance functions.

The workflow

How we introduce the solution.

  1. 01

    Upload regulations and review extracted clauses.

  2. 02

    Add and approve internal policies.

  3. 03

    Derive and approve external and internal requirements.

  4. 04

    Compare requirements, review assessments and approve gaps.

  5. 05

    Plan and approve remediation with subtasks and target dates.

  6. 06

    Assign and complete tasks and monitor progress.

  7. 07

    Define the audit scope and issue the reviewed report.

What needs to be agreed before use

T-NEX Compliance supports documenting, assessing and managing requirements. The institution determines their applicability and interpretation. A software status does not independently establish legal compliance.

FAQ

Questions about the solution

How does this differ from a document repository?

Documents are the starting point. T-NEX Compliance connects their clauses with requirements, assessments, gaps and remediation. Findings can therefore be traced back to their originating requirement.

Can one internal control support several regulations?

Requirements can be mapped to framework controls, making common references visible. Assessment determines whether the internal control actually fulfils each specific requirement.

Does AI approve assessments itself?

AI results are proposals. A person with the relevant permission approves them. Editing and approval are separate permission levels.

Why is a document missing from requirements management?

All preceding clause approvals must be complete. While clauses remain unapproved, the next stage is not enabled for that document version.

Can we start with a gap assessment only?

Yes. The Assessment audit type assesses a defined scope. The broader workflow is used for subsequent remediation and task management.

What does issuing an audit report mean?

The report moves from a changing draft to a fixed reporting position. Its figures are frozen on issue, separately from ongoing work in the module.

Related options

You may also be interested in these.

Requirement extraction · T-NEX Compliance: Review the clause structure

Document extraction

Review regulations as clause trees and derive requirements with source references. Document processing within T-NEX Compliance.

Learn more

Which task would you like to solve next?

Bring a concrete task. Together, we will define what the application needs to do.

See the compliance workflow in a demonstration