The auditor's report of findings and recommendations must be translated into concrete actions, assigning responsibilities, setting deadlines, and providing evidence of completion. Once the observations are received, the company needs to determine which require priority attention, how to respond to them, and what follow-up will demonstrate that they have been addressed. Properly managing this stage prevents recommendations from becoming mere formal commitments without any real changes to the processes.
The strategic value of addressing the findings
When management receives a finding from the auditor, the first step is to understand what happened, what the associated risk is, and what implications it may have for the organization. The goal should not be to respond quickly to consider the report addressed, but rather to determine the root cause of the situation and what action would allow for its sustainable correction.
A finding may be related to a regulatory deviation, a control deficiency, a document inconsistency, or an operational risk. Its significance will depend on the potential impact, recurrence, financial, legal, or reputational exposure, and the company's ability to resolve it promptly.
It is also necessary to define who needs to be informed about each issue. Some observations can be handled directly by the process owner, while others require involvement from management, the audit committee, or the board of directors due to their criticality, the resources required, or the scope of the decisions that need to be made.
The auditor's report of findings and recommendations gains greater value when it ceases to be treated as a document that simply needs to be answered and begins to be used as a tool to prioritize decisions, allocate resources, and reduce risks.
How to interpret the auditor's report of findings and recommendations
Before issuing a formal response, management should review each observation with the relevant departments and validate the supporting facts. To do this, it is advisable to identify the situation encountered, the associated risk, the possible cause, and the recommendation made by the auditor.
When an issue involves multiple processes, the analysis should not be limited to a single area. An observation about payments, for example, may simultaneously involve treasury, accounting, purchasing, and technology, so an isolated response might only resolve part of the problem.
It is also necessary to distinguish between an isolated incident and a recurring weakness. A reconciliation submitted late due to an exceptional absence does not have the same impact as several reconciliations delayed for months without evidence of independent review. In the latter scenario, the response will likely need to involve changes in responsibilities, supervision, or controls.
Organizations seeking an independent function capable of identifying and communicating these types of situations can evaluate the statutory auditing service from Amézquita.
Validate facts without turning the response into a controversy.
The company may supplement or technically challenge a finding when it has sufficient evidence. If there is documentation that was not considered, additional information that modifies the analysis, or a situation that has already been corrected, it should be presented clearly and with supporting documentation.
However, validating the content should not automatically become an attempt to eliminate the observation. Even when there is a difference of opinion regarding the proposed recommendation, management can acknowledge the identified risk and propose an alternative that addresses it appropriately.
The result of this review should be a clear position: accept the finding, accept it with clarifications, or technically support a different interpretation, always leaving defined what treatment the risk will receive.
Classification of findings to define priorities
Once the issue is understood, its priority must be established. Not all findings require the same speed of response or the same resources, so it is advisable to use consistent criteria related to impact, probability, recurrence, regulatory urgency, and the number of processes affected.
A critical issue may require immediate attention, senior management involvement, and temporary controls while the final solution is implemented. High-priority findings should have clear accountability and enforceable deadlines, while medium- or low-priority issues can be incorporated into normal improvement cycles as long as they remain documented and monitored.
The ranking should be supported within the matrix to avoid relying solely on the perception of the responsible department. This way, the organization can explain why certain issues received more attention and how available resources were allocated.
From observation to an action matrix
The auditor's report of findings and recommendations can be transferred to a monitoring matrix that allows each observation to be converted into manageable commitments, without replacing the original document.
| Element | Management question | Expected result |
|---|---|---|
| Classification | What is the impact, the urgency, and the recurrence? | Defined and supported priority |
| Plan of action | What needs to be changed to address the cause? | Concrete and verifiable action |
| Responsible party and deadline | Who will carry out the action and when? | Responsibility and due date |
| Evidence and closure | How will it be proven that the measure worked? | Supported closure and validation of effectiveness |
In addition to these elements, the matrix can incorporate the identified cause, the management's response, the status of the commitment, and the necessary support to subsequently validate its implementation.
How to respond to the auditor's letter of recommendations
The auditor's letter of recommendations should receive a concrete and verifiable response. Each observation needs to clearly state whether management accepts the finding, what cause it identified, what action it will take, who will be responsible, and the expected completion date.
When the proposed recommendation is not feasible under the stated terms, the company may propose an alternative, provided it adequately addresses the risk. The important thing is not to reproduce the auditor's suggested solution verbatim, but to demonstrate that the organization understood the issue and defined a technically sound response.
For example, when faced with recurring delays in reconciliations, simply stating that “the process will be strengthened” is insufficient. A clearer response could establish a monthly schedule, assign responsibilities for each account, implement an independent review, and set a deadline for preparation and approval.
Define actions that address the cause
Addressing only the identified issue may leave the underlying situation unresolved. If files are incomplete, completing the missing documents corrects the immediate problem, but it's also necessary to determine why the process allowed it to continue without those supporting documents.
The cause may lie in inadequate policies, ambiguous responsibilities, technological configurations that allow for exceptions, lack of oversight, or operational capacity that no longer matches the workload. Action should be focused on correcting these underlying causes to reduce the likelihood of recurrence.
When several observations show related weaknesses or structural problems, it may be pertinent to evaluation of the internal control system for companies. This type of review has a different scope than the treatment of an individual finding and can delve into policies, responsibilities, authorizations and controls when the situation warrants it.
Assignment of responsibilities and governance of the plan
Each action should have an identifiable person responsible and with the actual capacity to carry it out. In cross-functional matters, there may be a main person responsible, supported by various departments, especially when the solution affects processes, systems, or decisions involving more than one function.
Senior management should intervene when the plan requires investments, policy changes, technological developments, or decisions that exceed the authority of the operational manager. Similarly, the organization should differentiate between those who implement the measure and those who monitor it, so that there is an objective review of progress and the reported evidence.
When a closing date needs to be changed, the change should be justified within the same tracking process. The company can document the reason for the delay, the new deadline, the risk that remains, and any temporary measures taken while the final solution is being implemented. This prevents dates from being pushed back indefinitely without visibility into the consequences of the postponement.
Follow-up, evidence and validation of closure
A finding should not be considered closed simply because the committed activity was carried out. The organization needs to verify that the measure was implemented and that it consistently works against the risk it sought to reduce.
If a policy was modified, there should be evidence that the responsible parties began implementing it. If access privileges within a system were changed, it should be verified that incompatible profiles have been effectively removed. If a new review process was created, it should be verified that it is being implemented with the planned frequency and evidence.
The supporting documentation will depend on each case and may include system reports, transaction samples, reconciliations, approvals, minutes, training records, or subsequent indicators. For this reason, it is useful to differentiate between an action implemented, which confirms that the measure already exists, and an action closed, which implies having also verified its effectiveness.
Measure effectiveness after closure
In critical or recurring findings, it may be necessary to observe the performance of the measure over several periods before considering that the risk is sufficiently controlled.
If the problem was related to late payment approvals, for example, simply updating a procedure is not enough. It should be subsequently verified whether authorizations are being made within the timeframe, whether exceptions are supported, and whether monitoring is ongoing.
Indicators can help with this validation, but it's not necessary to create overly complex dashboards. What's important is having metrics directly related to the issue, such as the frequency of exceptions, overdue commitments, timely reconciliations, or the percentage of transactions that comply with the new control.
Turning the findings into a culture of improvement
Post-audit management can become a source of learning when the observations generate real changes and are not limited to producing administrative responses.
When a finding reappears after it has been closed, the company should review both the cause and the effectiveness of the previous action. Recurrence may indicate that the solution focused solely on the effect, that there were implementation difficulties, or that process conditions subsequently changed.
In this context it may be useful to review the Common errors in statutory auditing that can affect the company to identify practices that hinder the relationship between management and auditing. However, once a finding has been issued, the focus should remain on the response, follow-up, and evidence of closure.
The auditor's letter of recommendations is most valuable when the organization can demonstrate what decision was made, what action was taken, and what changes were subsequently made. This traceability allows management and governing bodies to focus their attention on issues that still require intervention, rather than on observations that should already be resolved.
From an open discovery to a verifiable improvement
The auditor's report of findings and recommendations should not be considered fulfilled simply because management sent a response or met a deadline. The process ends when there is clarity regarding the risk, a defined action, a responsible party, and sufficient evidence to demonstrate that the implemented measure is effective.
Quality management also depends on prioritization. Critical issues require closer monitoring and escalation, while less impactful observations can be incorporated into routine plans without losing traceability. When a finding resurfaces, the organization should review the cause and effectiveness of the previous solution before simply setting a new deadline.
Managed in this way, the auditor's letter of recommendations ceases to be a formal response document and becomes a tool to reduce recurrences, strengthen the company's reaction capacity and give management and governing bodies concrete information about the risks that still remain open.
Frequently asked questions about findings management
? What is the difference between a finding and an opinion of the statutory auditor?
A finding corresponds to a specific situation identified during the work, while the opinion expresses a professional conclusion on the financial statements within the corresponding scope.
- Example: There may be observations regarding reconciliations, supporting documentation, or controls without necessarily changing the opinion on the financial statements.
- Recommendation: analyze each finding according to its risk and avoid assuming that all observations have equivalent consequences on the opinion.
? What should the administration's response to a finding include?
The response should indicate the administration's position, the identified cause, the measure to be implemented, the responsible party, and the expected completion date.
- Example: Stating that “the procedure will be strengthened” does not allow for subsequent verification of what changed or who was supposed to implement it.
- Recommendation: Use a common format that allows each finding to be linked to a specific action, responsible party, deadline, and expected evidence.
? What happens if the company disagrees with a recommendation from the auditor?
Management can provide technical support for a different position or propose an alternative measure. The important thing is to demonstrate that it assessed the identified risk and that the decision made is supported by sufficient evidence.
- Example: The company may consider that the suggested control is not viable and propose another mechanism that mitigates the same risk proportionally.
- Recommendation: document the difference of opinion, the chosen alternative, and the reasons why it is considered appropriate.
? When can a finding by the statutory auditor be considered closed?
When there is evidence that the action was implemented and, when the nature of the matter so requires, that it works effectively against the identified risk.
- Example: Updating a policy demonstrates implementation, but it may be necessary to review subsequent operations to confirm that the new procedure is being applied.
- Recommendation: Define from the beginning what evidence will be necessary to validate the closure and prevent it from depending solely on meeting a date.
? When should a finding be escalated to the board of directors or the audit committee?
When their criticality, recurrence, regulatory exposure, financial impact or difficulty of resolution require decisions that exceed the capacity of the responsible area.
- Example: A critical finding that has passed its deadline may require additional resources, policy changes, or decisions that only senior management can authorize.
- Recommendation: Establish escalation criteria beforehand so that relevant matters reach the decision-making body in a timely manner.
