MAINSYSTEMS 
identify controls needed after supplier selection
1. Regulatory Concept & Core Standards
This video focuses on how to identify controls needed after supplier selection. Follow the sequence of decisions in the example rather than simply memorising a list. Notice who is involved, what information is needed and the expected result. These points help turn the content into a practice that another person can verify. Risk can arise when defining needs, selecting suppliers, changing contracts and paying invoices. The course distinguishes public procurement under Pzp from private purchasing. A warning sign calls for verification but is not alone proof of corruption or an automatic exclusion ground.
Contract management compares delivery with approved terms, acceptance evidence and payments. Where Polish public procurement law applies, changes require assessment under Articles 454 and 455 Pzp. A convenient commercial agreement is not by itself a sufficient legal basis for changing the contract.
Apply the following rule: Distinguish records and recipients. Articles 8(8), 29(5) and 46(4) provide three-year retention linked to the end of the relevant calendar year and completion of follow-up or resulting proceedings, as applicable. The Commissioner’s forwarded-report personal data and documents instead have the 12-month rule in article 8(7). Article 8(9) requires deletion/destruction on expiry, with the exception in 8(10) for documents forming part of specified investigation or court files. Clearly irrelevant personal data are deleted within 14 days after their irrelevance is established under article 8(4). Do not use receipt as the universal starting date.
2. Practical Implementation & Procedure
Match contract or order, receipt evidence and invoice. Review changes and approvals. Check duplicates and unusual payments. Confirm bank changes independently through a previously verified contact under the procedure. Do not rely only on contact details in the change request itself. Record exceptions and authorisation. 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
After selection, the contract scope is substantially expanded without a Pzp assessment. The manager’s signature does not establish permissibility. The team checks the legal basis and performance records. 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: Does management approval alone legalise a public-contract change? 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. The applicable statutory basis and conditions must be demonstrated. Financial review and organisational approval do not replace that assessment.
One mistake to avoid is: relaxing controls because of urgency or an established supplier relationship.
Now apply the national rule to a second decision. The system deletes every case five years after receipt regardless of record type and proceedings. Is that appropriate?
No. Polish law distinguishes entity data, registers, RPO forwarding and procedural files. Identify the appropriate three-year or specific twelve-month period and the relevant event and calendar-year end. Irrelevant information must not await the end of the whole case. Record the basis, deletion date and any applicable exception.