Functional testing of the channel

1. Regulatory Concept & Core Standards

This video's topic is functional testing of the channel. By the end, you should be able to test receipt, response and protective safeguards. We will connect the information available, the criterion guiding the decision and the action that must be recorded. Follow the case and compare your answer with the proposed response. Audit compares criteria with evidence and reports findings within a defined scope. This course proposes an internal verification approach. It is not official certification or a guarantee that no wrongdoing exists. Access to reports must remain limited and justified during audit. Section 37’s three-year review concerns designated external authorities. Within Decree 50/2013, the integrity adviser cannot simultaneously be the internal auditor.

A working homepage does not establish the complete process. Submission, follow-up, secure communication and actual notification are distinct functions supporting sections 22 and 24. Use authorised fictional data and test both permitted actions and access denial.

Apply the following rule: A written internal report must be acknowledged within seven days of receipt. Investigate as quickly as circumstances allow and at most within 30 days of receipt. A particularly justified extension requires simultaneous notice of reasons and expected completion. Even then, investigation and section 24 information must not exceed three months. Separate authority channels acknowledge within seven days subject to section 35 exceptions. Sections 36 and 3 generally require handling within 30 days, with a reasoned notified extension capped at six months. Do not combine the two procedures.

2. Practical Implementation & Procedure

Prepare identified and anonymous scenarios according to available methods. Define expected results. Test messages, configured deadlines, cover and conflicts. Check attachment and export permissions. Capture no real case data in evidence. Functional testing is not a full cybersecurity assessment of the product. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.

3. Case Study & Compliance Action

Submission works, but the follow-up code cannot reopen messages. Testing finds a failure that checking the homepage alone would miss. The team records impact and requests correction and retesting of the affected journey. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.

The exercise is as follows: Is checking that the form opens enough to establish that the channel works? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.

No. Test the complete journey and relevant safeguards. The homepage is one point. The report must identify tested routes and results.

One mistake to avoid is: submitting uncoordinated fictional cases that can be mistaken for genuine reports.

Now apply the national rule to a second decision. The platform uses a fixed 90-day period for every country, starting when someone opens the message. Can this setting be retained?

Not without validating the local rule. Use the correct starting event and unit, distinguish acknowledgement from follow-up and allow only permitted extensions. Test receipt outside working hours, month-end dates and the responsible person's absence. Opening a message does not automatically change the legal date of receipt.