Cortex sector summary
Bank and financial institution
All the work surrounding core banking in a single system
Accounts, loans, cards and accounting remain in the core banking system. The work surrounding these decisions — findings, committee decisions, controls, complaints, branch requests, suppliers, personnel and litigation — is handled at most banks today through e-mail, Excel and separate programs. Cortex brings this layer into a single system.
- 5
- finding sources in a single pool: inspection, internal control, compliance, external audit, BDDK (Turkey's banking regulator)
- 3 months
- Audit Committee reporting period — the package is prepared in a single step
- Same day
- time within which an operational loss event at a branch becomes visible at head office
Executive summary
What changes in this sector, in six points.
The direction set by the general manager reaches the units
The direction is recorded as targets and distributed to units, branches and individuals. Achievement is consolidated from the bottom up. A unit that deviates is reported to senior management while there is still time to intervene.
The Audit Committee package is prepared in a single step
Findings from inspection, internal control, compliance, external audit and BDDK are monitored in a single pool. The quarterly report is not compiled by hand. Closure without evidence is not accepted.
Overdue findings are reported by the system
The person responsible receives a reminder. If no response is received, the matter is escalated to the next level, and from there to the level above. The general manager is informed before the deadline expires.
Operational losses are visible at head office the same day
An incident at a branch is reported from where it occurred. Events above the threshold are automatically escalated. Tasks are created for indicators that exceed their threshold.
Board decisions are not left without follow-up
Each decision is assigned an owner and a deadline. Open decisions are carried over to the next agenda automatically. Delays are reported to the committee chair.
The morning briefing is a single paragraph
Where the bottleneck is, which unit is deviating and what keeps recurring are presented to the general manager without the need to ask. The decision is made by a person.
Work handled in Cortex in this sector
22 topics. Each one states why it requires tracking — most are tied to a deadline, a piece of evidence or a sanction.
- 01
The direction set by the general manager: strategy, targets, units, individuals
The annual budget, branch targets, transformation programme and strategic projects must reach units and individuals with the same clarity. Cortex records the direction as targets, distributes it and makes deviations visible upwards.
- 02
The head office view and the role of AI
Senior management's question is clear: where is the bottleneck, which unit is deviating, what keeps recurring. The answer must arrive without being requested, comparative across units and on time.
- 03
Tracking board of directors and committee decisions
The owner, deadline and status of every decision must be visible before the next meeting. Decision tracking must not remain in the minutes; it must become a workflow.
- 04
Audit findings and Audit Committee reporting
Findings come from five sources: inspection, internal control, compliance, external audit and BDDK. The regulation requires findings to be monitored through a single finding tracking system and reported to the Audit Committee at least once every three months.
- 05
Operational risk events and the loss database
Loss events must be collected consistently, classified and recorded with their amounts. An incident at a branch is expected to reach head office the same day.
- 06
Compliance: legislation, policies, mandatory training, personal data protection
Legislation changes frequently; it must be tracked which policy, process and unit each change affects. Mandatory training and the statutory deadlines for personal data requests are tracked on the same calendar.
- 07
Information systems: changes, incidents, access, continuity
The answer to "who approved this change" must be in one place and backed by evidence. Changes are made approved and traceable, incidents are recorded, access rights are managed and continuity is tested.
- 08
Tracking credit processes: files, collateral, appraisal, committee
The credit decision and its accounting reside in the core system; Cortex does not hold them. What surrounds the decision requires tracking: file preparation, missing documents, collateral documents, appraisal, insurance renewals, committee conditions.
- 09
Customer complaints and statutory deadlines
Complaints arrive through branches, the call centre, e-mail and the consumer arbitration committee channels; each has a different response deadline, and exceeding it leads to sanctions. A complaint whose root cause is not identified recurs.
- 10
Support services and supplier management
For outsourced services, risk assessment, an audit right in the contract and continuous monitoring are mandatory. Contract end dates and the currency of risk assessments are monitored from one place.
- 11
Internal control: daily, weekly and monthly controls
Whether a control was performed, to whom an exception was escalated and whether it was closed must be monitored on a single calendar; the results are reported to the Audit Committee.
- 12
Legal: litigation, enforcement and contract opinions
Hearing dates, power of attorney validity periods and opinion requests are tracked on a single calendar. A missed date turns directly into a loss.
- 13
Personnel: rotation, authorisation certificates, from hiring to departure
Rotation, signing authority, mandatory training and the revocation of access on departure go together; all of them are tracked on a single calendar.
- 14
Call centre and help desk: calls, voice recordings, quality evaluation
Every call is a record: the voice recording is retained, a written transcript is produced and its quality is evaluated. Waiting time and the first-call resolution rate are measured.
- 15
Corporate customer relations
Cortex does not hold the account; it holds the relationship. Who visited, what was discussed and what was offered are on record. Even if the customer representative changes, the history stays with the bank.
- 16
Software development and TFS
The answer to "what happened to this request" is given by showing code activity and the business request in the same place.
- 17
Procurement, contracts and asset assignment
When request, quotation, approval, contract and asset assignment are not tracked in a single flow, the trail of spending is lost.
- 18
Operations centre: correction requests, documents, archive, cash
The transaction is carried out in the core system. The tracking of requests, deadlines, documents and errors surrounding the transaction runs in Cortex.
- 19
Branch openings, refurbishment and real estate
A branch opening is a project involving several units, field work, a budget and a tight schedule. Lease contracts and permits require a calendar of their own.
- 20
From branch request to head office
This is the most frequently repeated flow in a bank: the branch makes a request and head office resolves it. Every step must be on record, and the branch must be able to see the status without asking.
- 21
ATMs and hardware: from fault to resolution
Fault reporting, field assignment, on-site resolution and recurrence analysis are tracked in a single record. Device replacement decisions are based on data.
- 22
Security, occupational safety and employee well-being
When physical security, occupational safety and employees' mental health are monitored separately, the overall picture is not visible. Cortex monitors them in a single system, in line with authorisation and confidentiality rules.
What lies outside the scope of Cortex
This section of the presentation is reproduced as it stands. A buyer who does not know what a product does not do will not trust what it does either.
It is not core banking
Account, loan, card, payment and accounting transactions are not carried out in Cortex.
It does not declare regulatory compliance
The infrastructure is in place; how each article is met is assessed specifically for each institution.
It does not make decisions
AI produces suggestions; it does not make credit, allocation, personnel or spending decisions.
It does not connect to every system out of the box
An integration layer is available; the scope is defined specifically for each project.
Legal basis
The sector headings, deadlines and figures on this page are taken from the Cortex product team's sector presentation dated September 2026. The legal bases are listed below; how each obligation is met is assessed specifically for each institution.
- Bankaların İç Sistemleri Hakkında Yönetmelik (Regulation on the Internal Systems of Banks)
- Bankaların Bilgi Sistemleri ve Elektronik Bankacılık Hizmetleri Hakkında Yönetmelik (Regulation on the Information Systems and Electronic Banking Services of Banks, 15.03.2020)
- Operasyonel Riskin Yönetimine İlişkin Rehber (BDDK guideline on operational risk management)
- Kredi Tahsis ve İzleme Süreçlerine İlişkin Rehber (BDDK guideline on credit allocation and monitoring processes)
- Bankaların Destek Hizmeti Almalarına İlişkin Yönetmelik (Regulation on the Procurement of Support Services by Banks)
- MASAK (Turkey's financial intelligence unit) obligations · KVKK (Turkish Personal Data Protection Law)
Frequently asked questions
How long does it take to learn?
It does not need to be learned. A Cortex trainer is always at the employee's side. The user says or writes what they want to do; the trainer opens the relevant screen, shows it step by step and, if necessary, does the work itself. It provides training according to the person's authorisation and the work they will do.
Does it integrate with our existing systems?
There is an interface layer for connecting with external systems. Scope and duration are defined specifically for each project, according to the capabilities the other system provides.
Can our existing data be transferred?
Data can be transferred from Excel and similar sources; the duration depends on the data volume and how well the source data is organised.
Does the AI make decisions?
No. It produces summaries and suggestions; the decision to act belongs to the user, and the person who approves is recorded. It handles routine work itself and brings decisions to you for approval.
Is there a separate charge for AI?
No separate subscription is required. If the institution prefers to connect its own provider account, the cost arises in that account.
Let us review together what changes in your sector
The full product — 19 module groups, 396 screens — is described on the Cortex page. This page covers only one sector: Bank and financial institution.