Model of financial control maturity: self-evaluation for medium-sized companies

Table of contents

The financial control maturity model for medium-sized companies proposed in this guide is a qualitative self-assessment of five dimensions: governance, reconciliations, authorizations, technology, and reporting. It serves to identify practices and gaps, and to prioritize them; it is not a statistical benchmark or a professional diagnosis of a company.

What does this model measure and what are its limits?

In this guide, financial control is understood as the set of practices that govern how a company's financial transactions are authorized, recorded, reconciled, analyzed, and communicated. Therefore, reviewing it involves more than simply verifying accounting records: it also entails observing who is responsible for the controls, what evidence is retained, how the systems are used, and how discrepancies or exceptions are handled.

Maturity describes the consistency and traceability with which these practices are designed, implemented, reviewed, and adjusted. It does not equate to the absence of errors or risks, nor does it, on its own, measure a company's overall performance. A practice may be documented but not applied consistently; conversely, useful controls may rely too heavily on one person's knowledge rather than a shared process.

The model presented here is a methodological proposal for this guide. It was not developed using a sample of companies or statistical data, and it does not allow for the calculation of averages, percentiles, or rankings relative to a sector. Its dimensions and levels are qualitative: they aim to facilitate internal dialogue and highlight questions that should be answered with evidence. They do not constitute a certification or a universal normative criterion.

This exercise can serve as a starting point for an internal control assessment and a more structured self-evaluation of accounting processes. However, its scope is limited: an organization's internal control may include other processes, risks, and responsibilities not covered by this matrix. Applicable obligations also depend on each company's context and must be verified separately; this guide does not offer a legal, tax, or regulatory conclusion for any particular case.

When the organization needs to delve deeper than an initial review, the page of Amézquita's internal control assessment It is a reference related to this topic.

The five dimensions of financial control maturity

The dimensions can be reviewed separately. The intention is not to require an identical structure in all medium-sized companies, but to adapt the questions to the size, complexity of operations, systems used, and distribution of responsibilities.

Government and responsibilities

This dimension examines whether responsibilities for designing, implementing, and reviewing financial controls are clear. It is important to identify who approves policies, who implements them, who monitors their operation, and how exceptions are escalated. It is also useful to observe whether responsibilities are clearly defined in practice or rely on informal agreements. When segregation of duties is not feasible, the self-assessment can document what compensatory review exists and who performs it.

Conciliations

Reconciliations compare balances or transactions between accounting records and their supporting documentation to identify discrepancies that require explanation. The review may include, depending on the company, bank accounts, accounting balances, related-party transactions, or other relevant records. Rather than simply verifying that a file exists, it's important to observe who prepares and reviews the reconciliation, whether it's performed at a defined frequency, how outstanding items are documented, and how they are tracked until resolution.

Authorizations

This dimension considers how transactions such as payments, purchases, adjustments, or accounting entries are requested, approved, and recorded. The central questions are who has the authority to authorize, how it is verified that the approval corresponds to the transaction, and what happens in the event of an exception. A useful review allows one to distinguish verifiable approval from informal or subsequent acceptance. It also examines whether the criteria are understood and whether changes in responsibilities or permissions are documented.

Technology and data

The focus is on the controls associated with the systems and files involved in financial processes, not on purchasing a specific tool. It's possible to review who has access to the information and whether those permissions are related to their roles; how relevant changes to data or configurations are identified; and what controls exist over spreadsheets, interfaces, or transfers that feed reports. The practical question is whether the organization can explain the origin of the information, recognize changes, and detect errors that affect records or analyses.

Financial reports

This dimension examines how reports are prepared, reviewed, and used to manage finances. It's important to ask whether the periods, definitions, and criteria are consistent, whether the figures can be traced back to their sources, and who reviews relevant variances. What happens after a report is issued is also crucial: who interprets the results, how decisions are documented, and how agreed-upon actions are monitored. Simply submitting a report does not, in itself, demonstrate that the information has been reviewed or used.

Self-assessment matrix for medium-sized companies

The following matrix translates the dimensions into observable questions. For each question, it is preferable to gather examples of how the process operates and review the available evidence, rather than simply answering based on what should happen. The questions are guidelines and can be adapted to the processes relevant to each organization.

Proposed matrix for reviewing financial control

Dimension Guiding question Evidence that can be observed
Government Are the responsibilities for execution, review, and escalation assigned? Communicated roles, identifiable responsible parties, and an example of how an exception was handled.
Conciliations Are the records compared with their sources and are discrepancies tracked? Reconciliations prepared, documented review, outstanding items identified and their resolution status.
Authorizations Is it possible to verify who requested and approved a transaction, and under what criteria? Approval records, defined responsibilities, and evidence of exception review.
Technology Is it possible to identify who accessed or modified information relevant to the process? Reviewable permissions, available logs, and controls over files or transfers that affect data.
Reports Is it possible to track the figures and check how the variations were reviewed? Sources identified, consistent criteria, review comments and follow-up actions.

The matrix is not an identical list of requirements for all companies. A company may need different evidence depending on its processes, systems, and responsibilities. If a practice is outlined in a document, but there are no examples of its implementation, it's important to note this discrepancy rather than assuming the control is fully operational. If the control is in place, but support is informal, this is also a relevant observation: dependence on a single individual can affect the continuity and the ability to review the process.

How to assign a qualitative level

Assign a level to each dimension separately. The assessment should be based on practices that can be described and substantiated, not on a general impression that the area is functioning well. The four levels proposed below are guidelines for this guide; they do not correspond to a statistical scale or an external rating.

Initial

Activities rely primarily on individual knowledge or informal agreements. Useful controls may exist, but evidence is scattered, it's not always clear who should review them, or it's difficult to explain how exceptions are handled. At this level, the exercise helps identify which practices depend on a single person and what information is needed to understand the process.

In development

The company has identified relevant controls, and some may be documented or implemented regularly. However, their application is not uniform, reviews may not be recorded, or follow-up on discrepancies depends on each department. The next step is usually to clarify responsibilities, criteria, and evidence of implementation, without assuming that simply documenting a practice is enough to make it work in all cases.

Definite

Responsibilities, frequency or execution criteria, and expected support are described clearly enough to allow for repetition. It is identified who reviews the process and how exceptions are recorded. A defined control does not need to be fully automated; what is important for this assessment is that its operation is understandable, verifiable, and reasonably consistent.

Integrated

Controls are integrated with the processes and information that feed into financial management. Relevant exceptions are recorded and tracked, process changes are considered, and the results of reviews help refine practices. Integration is not demonstrated solely through technology or a written procedure; it requires the ability to explain how those responsible, the evidence, and the decisions are connected.

If the evidence varies between teams or periods, document the variation rather than masking it with an average rating. A strong dimension should not compensate for another with a significant gap: well-prepared reports, for example, do not in themselves demonstrate that authorizations are clear. If the practice falls between two levels, document what evidence supports the assessment and what aspect remains to be confirmed. In this way, the maturity of financial controls is represented as a profile of strengths and opportunities, not as a single score for comparing companies.

How to turn findings into control improvements

The value of self-assessment depends on what happens next. A list of gaps without accountability or follow-up may describe a situation, but it doesn't help to organize the work. To turn the findings into action, the company can follow these steps:

  1. Define the process and the period reviewed. Identify which entities, areas, or operations are included in the exercise and which are excluded. This prevents interpreting a single observation as a conclusion about the entire organization.
  2. Describe the gap with evidence. Indicate what was expected to be observed, what evidence was found, and what aspect requires confirmation. Separating facts from hypotheses makes it easier to discuss the finding with those responsible for the process.
  3. Prioritize according to the context. Consider the potential financial or operational impact, the frequency with which the situation occurs, the complexity of the operation, and the information needs to make a decision. The maturity label alone does not determine priority: two gaps at the same level can have different impacts.
  4. Define an action and how to verify it. Document who will be responsible, what practice is expected to be adjusted, what evidence will allow for observing the change, and when to review progress according to the company's schedule. Avoid defining actions that depend on a new tool if the main problem is a lack of clear responsibilities or criteria.

For example, if reconciliations exist but the status of discrepancies is not easily known, one possible action is to establish a common record that identifies the item, the person responsible, the outstanding explanation, and the resolution status. The company can later review whether the record facilitates follow-up. This example illustrates one way to turn an observation into action; it does not prescribe a mandatory format nor guarantee a specific outcome.

In companies with foreign capital or operations linked to an international group, this self-assessment can be complemented by a broader review of the local context. Related reading is available in the following: Guide to operating in Colombia for foreign companies. The matrix in this article does not replace the verification of the conditions and obligations that correspond to each company.

Frequently Asked Questions

Is this model a statistical benchmark?

No. It is a qualitative proposal to guide a self-assessment. It is not based on a sample of companies and does not allow for comparison of results with averages, percentiles, or sector rankings.

What evidence should be gathered before starting?

You can review documentation related to responsibilities, reconciliations, approvals, access permissions, reports, and exception tracking. It's also helpful to look at operational examples. The specific evidence required will depend on the processes and systems used by each company.

How is the level of the five dimensions consolidated?

Evaluate each dimension separately and describe the evidence that supports your assessment. There's no need to average them into an overall score; a profile for each dimension allows you to recognize differences that a single number might obscure.

Does an initial level mean that the company is failing to meet an obligation?

No. This self-assessment does not, by itself, determine regulatory compliance or establish obligations for a company. To evaluate a specific case, it is necessary to consider its circumstances and compare them with the applicable regulations.

Does adopting a technological tool automatically increase maturity?

No. Technology can support traceability and analysis, but it doesn't replace clarity of responsibilities, authorization criteria, review, and monitoring. Maturity is assessed by observing how practices and evidence work together, not just which system the company uses.

This article has been verified by
Humberto González,
Public accountant
Recent Publications
Categories

Search