1. Home
  2. Platform
  3. Prove
Prove · module 3

Show that it works

Your regulatory framework linked directly to your control testing.

Prove links every test to the control, the obligation and the article it counts for. Your compliance requirements and your actual controls then match. When a requirement lapses, so does the test. The lineage runs from the evidence back to the regulatory obligation, for the second line, the third line and the supervisor.

comply24 · test · test plan
Test plan with the tests of the current year
Prove · Test plan: per year which test definitions are tested, by whom and when. Demo environment, fictitious institution.

What changes

A test plan that follows the law, not last year’s plan.

The test plan

Grows every year.

New requirements are added. What lapsed stays because nobody knows where it came from.

additions only

The evidence

Collected just before the audit.

What is missing only shows when the auditor asks for it.

too late

The rationale

A report per audit.

Why a control is tested, and with which sample, has to be explained again every time.

every time

Benefits

What Prove gives you.

Prove records the test result against the obligation. For each article you see what is covered and what demonstrably works.

01

Testing according to plan

Frequency, testers, reviewer and due dates per year, with tasks and reminders per owner.

02

Evidence on time and complete

For every test you see which evidence is in and what is missing. Missing evidence shows up before the audit.

03

One workflow for owner, tester and reviewer

The tester does not review. The reviewer sees the evidence. Four eyes, without exception.

04

Requirements and controls match

The test result is recorded against the control, the obligation and the risk. For each article you see what demonstrably works.

05

Always current: a framework that can also shrink

When an obligation lapses, the control and the test leave the test plan. You test what the law asks now, not what was added over the years.

06

Lineage from evidence back to the regulatory obligation

Sample, evidence, conclusion and review can be traced back to the article. The second line, the third line and the supervisor see why a control exists and that it works.

In four screens

From control to tested evidence in four steps.

The tester does not review. The reviewer sees the evidence. Every step records who did what.

1

Test creator: a test definition per control

The Test creator proposes a design test and an operating test per control from the Control library. You confirm or edit.

Prove · Test creator
2

Test plan: who tests what and when

One plan per year: per test definition the testers, the reviewer, the frequency and the due date.

Prove · Test plan
3

Test: design and operation

The testers assess the evidence, record the outcome per sample item and conclude. The platform proposes a conclusion.

Prove · Test
4

Evidence: per test, with versions

Upload or SharePoint link. A test keeps the version it used. The test report is frozen.

Prove · Evidence

Try it

One test, one conclusion.

The platform proposes a conclusion based on the results and the evidence. The tester validates, a reviewer approves. A test that fails becomes a gap in Trace.

  • Two conclusions per test: design and operation
  • The sample draw is recorded and repeatable
  • The result counts only after the review
Illustrative exampleTest T-2026-052 · CR-12 · Q3

Sample of 25 obligors: for two, the review was recorded after the deadline. What is your conclusion on operation?

Proposal: Not effective. The evidence covers the flag, but for 2 of the 25 obligors the review within five working days is missing.
  • Decision
  • ByYou, tester · review by the second line
  • Time
  • Then

Back from the evidence

From the evidence back to the article, link by link.

An auditor or supervisor starts at the evidence and works back: test, control, obligation, provision. Every link shows what was approved, by whom and when.

Illustrative example with sample data. No client data.

Swipe sideways for all eight links.

Law

Regulation (EU) No 575/2013 (CRR)

Capital Requirements Regulation as amended by Regulation (EU) 2024/1623. Loaded per article and paragraph, including versions. A new version shows the difference per provision.

Source
EUR-Lex
Reason in scope
Bank, Wft licence
Module
Signal

Provision

Article 178(1)(b)

A default occurs when the obligor is more than 90 days past due on a material credit obligation.

Part
Part Three, Title II
Status
In force
Module
Signal

Obligation

Treat an obligor as defaulted after 90 days past due

Derived from the provision with the citation attached, merged with the same requirement from the EBA guidelines and approved by the expert.

Priority
Tier 1
Approved by
Credit Risk expert, 14 Oct 2026
Module
Trace

Control

CR-12 · Daily flag of 90 days past due

The system flags obligors more than 90 days past due. The workout team reviews them within five working days.

Type
Preventive, automated
Owner
Head of workout
Module
Trace

Risk

R-CR-03 · Default recognised too late

From your own risk register. The gross risk is high. The net risk follows from the test result of the control, not from its description.

Gross
High
Control
CR-12
Module
Trace

Policy

Credit risk policy v3 · § 4.5 Default and arrears

The policy provision that covers the obligation. A new version of the law affects this provision only, not the whole document.

Linked to
OBL-CRR-178 · CR-12
Approved
Management board, 12 May 2026
Module
Trace

Test

T-2026-052 · Design and operation of CR-12

Sample of 25 obligors from the third quarter. Two conclusions, design and operation, and a review by the second line.

Result
Effective
Reviewer
Second line, not the tester
Module
Prove

Evidence

EV-0412 · Arrears report Q3 and sample file

Recorded with version, source and time. The test report is frozen. From the evidence you can trace back to the article it relates to.

Recorded
3 Oct 2026, 10:42
Report
Frozen
Module
Prove

What lineage gives you

  • For every priority the basis is written out: legal weight, supervisory attention, risk.
  • Every judgement has a rationale, a citation, a name and a time.
  • A change in the law reaches only the links it affects.
  • One export answers the supervisor’s question, per article.

Prove on screen

Test what the law requires now, not what was added over the years.

Test definition

The test is tied to the article

Every test definition shows its lineage: the provision, the obligation, the control and the line in the test plan. So you know for every test which requirement it counts for.

  • One definition can serve controls in several control frameworks and is tested once
  • For each definition: the tests, the versions and where it is used
The test is tied to the article
Prove · Test definition. Demo environment, fictitious institution.
Test

A change in the law reaches the test

When an impact alert on an obligation is confirmed, the test definition of the control gets the status Check needed. The next test waits until the testers have checked the definition.

  • When an obligation lapses, the control and the test leave the test plan
  • Keep or edit: both decisions are in the versions and the audit trail
A change in the law reaches the test
Prove · Test. Demo environment, fictitious institution.
Test · Sample

Sample with an outcome per item

The platform draws the sample from the population the control owner provides. For each item the tester records Pass or Exception. An exception requires a note.

  • The sample size follows the frequency of the control
  • The draw can be repeated by reviewer and auditor
Sample with an outcome per item
Prove · Test · Sample. Demo environment, fictitious institution.
Test results

Results per framework, instrument and quarter

Test results shows the share of controls tested effective, what was not effective and what is still in progress. A row opens the tests behind it.

  • Not effective raises a gap; the next test shows whether it is resolved
  • The test report of a closed plan no longer changes
Results per framework, instrument and quarter
Prove · Test results. Demo environment, fictitious institution.
Compliance status

Tested effective per obligation

The compliance status shows, per article, the obligation, the control, the policy provision and the test result. Requirements and actual controls are in one list.

  • Filter by tested effective, not effective or not tested
  • Export per instrument for the supervisor
Tested effective per obligation
Prove · Compliance status. Demo environment, fictitious institution.

Who it is for

For the second line, the third line and the control owner.

You choose

Prove builds on Signal and Trace. Together they close the chain.

Each module is a complete product. You choose your own modules and expand when you are ready.

Signal

Know what changes

Signal supplies the changes that trigger a check of a test definition.

Starts with the regulatory change teamFrom € 5,500 a year

Signal + Trace

Direct the change

Trace supplies the controls and obligations that every test is tied to.

Starts with compliance and riskFrom € 17,500 a year

Signal + Trace + Prove

Show that it works

With all three you show, per obligation, that your controls work.

Starts with risk, internal audit and the boardFrom € 24,000 a year

Trace builds on Signal, and Prove on Trace. Your setup stays in place when you expand. Starting prices are for the Small tier, excluding VAT.

Calculate your price

Price

A fixed annual price, per tier.

Prove comes with Signal and Trace. The tier follows the number of named users in the platform and does not depend on the number of tests. You set up the first test plan yourself, or together with our experts.

Prove

Small

€ 6,500

up to 15 named users

Medium

€ 18,000

up to 40 named users

Large

€ 50,000

unlimited named users

Per year, 2026 list prices, excluding VAT. With Signal and Trace. Ten extra named users: € 1,500 a year.

Questions

Frequently asked questions about Prove

Can we use our existing test definitions?
Yes. You record them in the Control library, or let the Test creator propose them from the control description and adjust them.
How does the platform handle samples?
The sample size follows the frequency of the control. The draw is recorded so that a reviewer or auditor can repeat it.
What happens when a control is not effective?
A gap is created in Trace, with an owner and a deadline. The next test shows whether the gap is resolved.
What happens to a test when the law changes?
When an impact alert is confirmed, the test definition gets the status Check needed and the next test waits for the check. When an obligation lapses, the control and the test leave the test plan.
Can Prove run without Trace?
No. Prove tests the controls from Trace and records the result against the obligation.

The first step

Try it free for two weeks. Or start with a demo.

Try the platform for two weeks with real legislation, news and alerts. Or see in thirty minutes what it does with a law from your own scope. For either, contact us.

Cookies

Cookie settings

This site only uses necessary storage, so there is nothing to give consent for. Below you can see what the site does and does not do.

Your language choice and your cookie choice, stored in your own browser. Without this storage the site forgets your language and the cookie notice returns on every visit.

  • c24consent
  • c24lang

This site does not measure visits. No statistics service is loaded.

This site sets no marketing cookies and does not follow you on other sites.

Read the cookie policy