# T-NEX: procurement overview and product assessment worksheet

Version 1.0 · 11 September 2026 · Publisher: T-NEX GmbH

This worksheet summarises publicly described functions and their documentation basis. Use the editable fields to prepare a product demonstration, technical assessment or proposal. The product pages provide further detail; your project establishes the scope of the actual installation and its operation.

## 1. Your project

| Field | Your team’s entry |
|---|---|
| Institution and department | [complete] |
| Contact and role | [complete] |
| Workflow to support | [complete] |
| Expected result for users | [complete] |
| Existing systems and authoritative data sources | [complete] |
| User groups and required permissions | [complete] |
| Important dates and business dependencies | [complete] |
| Assessment reference and date | [complete] |

Describe the goal as a testable workflow: “A project manager requests capacity for a work package. The line manager checks available capacity and decides. The project plan shows the committed resource.” This gives the demonstration a shared basis for assessment.

## 2. Documented offerings and suitable assessment cases

### T-NEX Controlling

**Purpose:** IT cost planning, analysis and internal cost allocation.

- **Inputs:** Accounting data, provider invoices, cost objects, contract values, quantities and planned values.
- **Results:** Allocated cost records, planning views, planning previews and traceable reports. Actuals, open commitments, budgets, operational IT planning and the multi-year financial plan remain distinguishable.
- **Roles in the assessment:** IT controlling, planning owners and administration; permissions are defined for the installation.
- **Assessment task:** Import a known invoice, identify missing allocations, trace an amount to its source and inspect a planning run before execution.
- **Documentation basis:** Controlling manual, 25 August 2026, edition 3, 286 pages. It describes a specific institutional installation. “Edition 3” is the manual revision, not a common software version.
- **Scope boundary:** The displayed allocations do not post entries to the authoritative accounting system. Interfaces and account assignments require their own agreement.

[T-NEX Controlling](https://t-nex.de/en/institutions/products/ai-controlling-hub/)

### T-NEX Dynamic AI Reporting

**Purpose:** Natural-language data questions and editable reports.

- **Inputs:** Connected data sources, business descriptions of the data and a specific analysis question.
- **Results:** Draft reports and visualisations that can be reviewed, edited and shared with authorised people.
- **Roles in the assessment:** Report authors, authorised readers and administration.
- **Assessment task:** Ask for a known metric from a defined source, compare its calculation and filters with the source analysis, then check sharing with a reader.
- **Documentation basis:** T-NEX product presentation of 2 July 2026 and the reporting and permission sections of the Controlling manual of 25 August 2026. Actual data integration is installation-specific.
- **Scope boundary:** A generated report needs business review. Data access, model configuration and permitted functions are part of setup.

[T-NEX Dynamic AI Reporting](https://t-nex.de/en/institutions/products/ai-reporting/)

### T-NEX Compliance, including requirement extraction

**Purpose:** Connect regulations, requirements, assessments, gaps, remediation and audits.

- **Inputs:** Versioned external regulations and internal control documents.
- **Results:** Clauses with source references, approved requirements, assessments, assigned remediation and a report for the defined audit scope.
- **Roles in the assessment:** Editing, assessment and approval with separate functional permissions.
- **Assessment task:** Check a clause against the original, approve its requirement, review a proposed assessment and create an assigned remediation action. Then check the difference between a report draft and an issued report.
- **Documentation basis:** Compliance functional manual, 30 August 2026, application version 15.23.0, 58 pages. Documented sample workflows establish the described functional scope.
- **Scope boundary:** Requirement extraction is part of this workflow. It does not promise arbitrary invoice or credit-file processing. A software status does not determine the institution’s legal compliance.

[T-NEX Compliance](https://t-nex.de/en/institutions/products/ai-compliance-hub/) · [Requirement extraction](https://t-nex.de/en/institutions/products/document-extraction/)

### T-NEX PPM

Programme functionality is disabled by default in the documented release and is not yet fully developed. Its intended scope is assessed separately.

**Purpose:** Projects, programmes, portfolios and resource decisions.

- **Inputs:** Project brief, work packages, dates, roles, resource needs and planning states.
- **Results:** Work breakdown structures and Gantt plans, baselines, resource requests and commitments, status reports and portfolio views.
- **Roles in the assessment:** Project management, PMO and line management; the functional documentation distinguishes seven system roles.
- **Assessment task:** Record a need in the project plan, submit a resource request, decide as the line manager and trace the effect on planning and status. Review AI suggestions before adopting them.
- **Documentation basis:** PPM functional documentation, 30 August 2026, frontend 0.8.5, server 15.23.0, 107 pages.
- **Scope boundary:** Requested capacity is not yet a committed resource. Roles, organisation structure and interfaces are configured for the project. The documented version is not a blanket version for all T-NEX applications.

[T-NEX PPM for institutions](https://t-nex.de/en/institutions/products/ai-project-management/) · [T-NEX PPM for companies](https://t-nex.de/en/companies/products/project-portfolio-management/)

### T-NEX Fraud Detection

**Purpose:** Rule-based transaction monitoring and AI-assisted case triage.

- **Inputs:** Agreed transaction and context data, plus a configured ruleset.
- **Results:** Matches grouped into cases, supporting transactions, an AI assessment, analyst decisions and an audit trail. The documentation describes nine rule types and retrospective rule testing.
- **Roles in the assessment:** Analysts, team leads and administration with the required permissions.
- **Assessment task:** Work through an unusual and a routine sample case, explain the rule trigger and record the analyst’s decision. Also test a failed AI call and continued manual handling.
- **Documentation basis:** Fraud Detection functional manual, 30 August 2026, application version 15.23.0, 23 pages.
- **Scope boundary:** An anomaly does not establish a crime. Payment blocking, external suspicious-activity reporting, production volumes and detection quality are separate assessment items.

[T-NEX Fraud Detection](https://t-nex.de/en/institutions/products/fraud-detection/)

### T-NEX Banking Platform and custom extensions

**Purpose:** Connect business applications, permissions and additional tasks in a configured environment.

- **Inputs:** Required module selection, data models, user groups and workflows to integrate.
- **Results:** A module combination configured for the engagement. App Studio supports applications with their own interface, data and permissions.
- **Assessment task:** Define the data model, interface, permissions and import/export needs for a limited extension. Then test the workflow through different roles.
- **Documentation basis:** Controlling manual, 25 August 2026, particularly module selection, administration and chapter 29.4 on App Studio. The MONTEE user documentation of 29 August 2026 also describes embedded platform administration in a customer-specific business application.
- **Scope boundary:** Applications and products do not automatically share a database, version or enabled module selection. Custom development has its own service scope and acceptance criteria.

[Banking Platform](https://t-nex.de/en/institutions/products/banking-platform/) · [Regulated custom development](https://t-nex.de/en/institutions/services/regulated-software-development/)

### T-NEX AI Risk Manager

**Purpose:** Risk register, controls, incident links and textual scenario assessments.

- **Documented state:** Product demonstration from the T-NEX presentation of 2 July 2026. It shows functions using sample data and does not establish an institutional deployment.
- **Assessment task:** Derive a risk proposal from a recorded incident, trace its associated controls and examine the assumptions behind a textual scenario assessment.
- **Scope boundary:** Scenario analysis is not a validated quantitative stress test. Applying it to an institution’s own workflow is assessed as a project.

[T-NEX AI Risk Manager](https://t-nex.de/en/institutions/products/ai-risk-manager/)

## 3. Assessment matrix for your demonstration

Copy rows for additional cases. Record observations and open questions separately from commitments.

| ID | Your requirement | Mandatory/Optional | Expected evidence | Observation or document version | Met/Open/Not met | Owner and next step |
|---|---|---|---|---|---|---|
| F01 | [specific workflow] | [select] | [demonstration/document/test] | [complete] | [complete] | [complete] |
| F02 | [data source and connection] | [select] | [import/interface test] | [complete] | [complete] | [complete] |
| F03 | [roles and restricted access] | [select] | [check using two roles] | [complete] | [complete] | [complete] |
| F04 | [error or exception case] | [select] | [failure and continued handling] | [complete] | [complete] | [complete] |
| F05 | [export, report or handover] | [select] | [sample file and criterion] | [complete] | [complete] | [complete] |

## 4. Define integration and operations

| Topic | Record for your project |
|---|---|
| Module selection and version | [products, enabled functions, configuration] |
| Data sources and interfaces | [authoritative system, fields, format, frequency, error handling] |
| Permissions and identities | [roles, sign-in, administrative access, changes] |
| AI processing | [purpose, permitted content, model/service, human review, failure handling] |
| Infrastructure and data locations | [account owner, environment, storage and backup locations, connected services] |
| Operating tasks | [maintenance, monitoring, incidents, responsible people, support hours] |
| Backups and recovery | [scope, retention, desired objectives, agreed verification] |
| Contract and data protection documents | [required documents for the actual parties and data flows] |
| Costs and changes | [setup, licences, infrastructure, support, additional scope] |
| Export and provider transition | [formats, access, documentation, rights, handover steps] |
| Acceptance | [test cases, participants, result and remaining points] |

## 5. Assessment result

- Selected solution scope: [complete]
- Assessed version and configuration: [complete]
- Evidence used and assessment results: [complete]
- Open business or technical questions: [complete]
- Agreed next step, owner and date: [complete]

This document is a public summary and worksheet. The cited manuals are not being provided as a complete public download collection. Available project-specific evidence and operational commitments are identified for the procurement exercise.

[Technical evidence](https://t-nex.de/en/institutions/evidence/) · [Hosting and operations](https://t-nex.de/en/institutions/services/secure-hosting/) · [Discuss your project](https://t-nex.de/en/institutions/contact/)