When an accounting system automatically converts a signed incoming invoice into a financial liability, the company risks paying for unauthorized or unrendered services. To protect cash flow, a financial controller must ensure every document passes a business logic filter before account balances are adjusted. If expense initiators have direct access to posting or if the accounting department trusts the incoming flow without additional validation, budget control is lost. The solution lies in setting up an isolated registry to record approval steps and clearly delineating responsibilities between operational units and the finance department. This approach requires implementing four mandatory verification stages: completeness of details, authorization confirmation, absence of duplicates, and compliance with accounting policy.
Symptoms of the Gap Between Receipt and Accounting
When an accountant receives a certificate of completion via an electronic document management system with valid signatures, the standard reaction is to create a posting to close the period. However, the legal correctness of a file does not confirm its economic validity. If expense initiators are managers of operational units, the financial risk of erroneously recognizing liabilities falls on the accounting department without proper internal control. An electronic signature only confirms that the document was sent by the stated counterparty, but it does not prove that the work was performed with quality and in full.
The consequences of directly reflecting unverified data manifest during plan-fact analysis or reconciliation at the end of the reporting period. Consider an illustrative example: the CFO discovers that the company recognized a liability for marketing services in the amount of 150,000 UAH, even though the marketing director has not yet accepted these works due to significant deficiencies. Another symptom is double recognition of expenses. A supplier may send a paper original by mail and, a week later, duplicate it electronically through an exchange platform, changing the number format (e.g., from 'Invoice 45' to 'Invoice 45/1'). If the accounting system lacks strict entry barriers, both versions become separate accounts payable.
Error Mechanism and Creating a Digital Buffer Zone
Erroneous postings arise from the conceptual mixing of two different processes: registering incoming correspondence and recognizing a business transaction. The error mechanism is triggered the moment a document becomes available for payment solely based on its upload into the system. Under the pressure of month-end deadlines, specialists skip the stage of clarifying details with initiators. Accounting systems are designed for recording financial transactions and building reports, not for flexibly managing complex approval routes for every individual delivery.
To break this chain, the company must create a digital buffer zone. Companies use specialized solutions to receive primary documents. For example, the Deals product, which is part of the Intecracy Group ecosystem, provides EDI functions, e-Signature application, and electronic document management (EDM). In such an isolated environment, the file exists as a draft or an approval request. In this zone, the document does not yet affect the financial result, change account balances, or form a tax credit. Returning to the illustrative example: the 150,000 UAH invoice is uploaded via the EDM system, but its current status technically blocks the generation of an accounting entry. The document awaits review by responsible persons according to the configured route.
The transfer of data to the General Ledger requires passing control stages to reduce legal, managerial, operational, and methodological risks. A configured workflow allows for the consistent verification of details, authorization, and accounting parameters. To assess the efficiency of the current process, a financial controller can test the system's ability to detect duplicates and block postings until the initiator's approval is obtained.
Sources: [2]
Decision-Making Matrix for Four Checks
Each control stage requires a clear definition of acceptance criteria, responsible persons, and evidence of execution. The separation of responsibilities is a basic rule of internal control. An accountant does not confirm the volume of services provided for software development or advertising setup, and an expense initiator does not define accounting accounts. This matrix serves as an instruction for configuring access rights and routing in the process management system.
The proposed table demonstrates the distribution of functions between human and algorithm, as well as the compromise between processing speed and reliability. Involving the cost center manager in authorization verification slows down the document flow cycle because it requires time for review. However, this step is an effective way to avoid paying for poor-quality or partially unrendered services. If the initiator rejects the invoice, the process stops, and the supplier receives a notification about the need for correction.
The table shows that no role has full control over the entire document lifecycle. Duplicate checking removes routine operational burdens from the employee, shifting them to the system. At the same time, final control of the accounting policy remains the exclusive competence of the finance department. Such a distribution reduces the risk of conflict of interest and forms the basis for setting up an automated digital route.
| Control Stage | Acceptance Criterion | Responsible Role | Evidence of Execution |
|---|---|---|---|
| Completeness of details | Presence of mandatory fields (date, number, amount, signatures) | Primary documentation accountant | Completed document card without empty critical fields |
| Authorization confirmation | Compliance of volume and quality with actually received services | Cost center manager (initiator) | Electronic approval visa in the workflow |
| Duplicate control | Absence of matches by combination of vendor TIN, date, and amount | Automated system algorithm | System log of verification completion with no matches found |
| Accounting policy | Correct definition of accounts, period, and tax purpose | Chief accountant or financial controller | Generated and unlocked accounting entry |
Practical Method for Configuring the Approval Route
Implementing the four checks requires a task routing tool that operates before a financial record is created. The UnityBase platform allows for visually configuring new applications, which reduces the need for manual coding when setting up verification logic. This means that business users and analysts can adapt the solution to a changing organizational structure and new cost centers without lengthy specialized training.
The process begins with the automatic reading of details. When the illustrative 150,000 UAH invoice enters the system, the algorithm checks for the presence of mandatory fields. Next, the system generates a task for the marketing director. They review the document in their workspace and click the approval button, confirming the fact that the work was performed. With this step, the business owner takes responsibility for the expediency of the expense, and the system records their decision.
In the next step, the algorithm searches for matches by amount, date, and vendor identification code in the database of already processed documents. If a potential match is found, further movement is blocked until circumstances are clarified. Only after successfully passing these three stages does the document reach the chief accountant. The accountant verifies the correctness of the cost center definition, tax purpose, and period, after which they approve the final entry. UnityBase generates its own APIs for organic integration with core accounting systems, passing an already verified array of data there for the formation of entries.
Sources: [1]
Recording Results and a Controlled Audit Trail
Successful completion of the approval route must be reliably documented. A file signed by the counterparty does not in itself prove that the company's internal controls were followed. Proper evidence is a system record of who exactly, when, and on what basis made a decision at each of the four stages. Without such a record, an internal check turns into a formality that cannot be verified during an audit.
The built-in automatic recording system (audit trails) in UnityBase helps track any changes to data or processes. With proper configuration, the audit trail records defined user actions. During a tax audit or internal audit, the company can provide an export that clearly shows the chronology: from the moment the invoice was uploaded to the final approval by the chief accountant. The platform also contains an effective version control system for the processes themselves and related documents.
The presence of such a controlled trail reduces the risk of blurred responsibility. If it turns out a year later that marketing services were not provided in full, the CFO will be able to pull up the approval history and see that it was the cost center manager who authorized this transaction on a specific date at a specific time. Thus, implementing the four checks reduces the risk of errors in cash flows and supports transparent discipline in liability management at all levels of the company.
Sources: [1]
Action checklist
- Compile a comprehensive list of mandatory fields for recognizing and validating an incoming document.
- Assign cost center managers to authorize services and configure their access rights.
- Configure the duplicate search algorithm based on a combination of vendor TIN, exact amount, and document date.
- Define routing rules for exceptions, for example, when discrepancies in amounts are detected or a duplicate is suspected.
- Verify the preservation of the approval history (audit trail) before configuring integration with the ERP system.
Questions and answers
What should be done if the cost center manager is on vacation and delays document approval?
Configure automatic task delegation to a deputy or escalation to the financial controller after a specified time (e.g., 48 working hours). This reduces the risk of delaying the financial period closing process.
Does a qualified electronic signature (QES) of the supplier replace authorization verification?
No. An electronic signature only confirms the legal integrity of the document and the identity of the signatory on the counterparty's side. Internal verification must collect and record evidence of acceptance, authorization, and volume.
How should documents received after the official closing of the financial period be handled?
The document goes through a controlled route. The chief accountant determines the period and method of reflection according to current standards, accounting policy, materiality, and the closing status. The decision and basis must be documented.