Growth rarely breaks an organization abruptly, it strains it gradually. At Pércimon, the sustained increase in operational volume began to reveal a silent friction in one of its most sensitive processes: electronic invoicing and its internal approval. What had worked for years through email coordination started turning into a structural bottleneck.
The problem, in reality, wasn't invoice issuance itself — it lay largely in the architecture supporting the flow. Every document required individual submissions, successive validations, and manual follow-up between departments. Approvals depended on informal confirmations, and the real status of the process wasn't available from a single point of reference. The operation moved forward, but visibility was fragmented.
As volume grew, so did the risk: accumulated delays, repetitive validations, dependence on specific people, and difficulty identifying where each invoice stood in the cycle. And automating email sending didn't solve the problem — the entire process needed to be redesigned.
Diagnosis before tool
The first stage of the project consisted of understanding the actual operation.
A detailed mapping of the flow was carried out: formal and informal responsibilities, explicit and implicit rules, dependencies between areas, frequent exceptions, and points of greatest friction. This analysis allowed visualizing the process as an interconnected structure and not as a sequence of isolated tasks.
The finding was clear: the bottleneck was in the lack of a flow governed by defined rules and centralized traceability.
From informal coordination to structured architecture
The redesign focused on three fundamental decisions:
1. Centralize the flow under a single operating model.
Issuance, validation, and approval ceased to depend on scattered exchanges and were integrated into a system with defined states, assigned responsibilities, and real-time visibility.
2. Parameterize approval rules.
Instead of validating case by case manually, objective criteria were established according to the type of invoice, supplier, and responsible area. These rules were incorporated into the system to ensure consistency and reduce ambiguity.
3. Guarantee full traceability.
Each intervention was recorded, the process ceased to depend on organizational memory or manual tracking and came to have a verifiable history and structural control. This approach allowed growth to stop amplifying complexity. The volume increased, but the stability of the process was maintained.
Structural impact
The redesign not only reduced operational friction — it also strengthened Pércimon's capacity for growth. With a billing flow that is structured and governed by clear rules, the organization eliminated critical dependencies and gained stability during periods of higher volume. This now allows it to plan the opening of new points of sale with the confidence that the financial process won't become a bottleneck.
Growth stopped being an additional administrative burden because the structure was finally ready to absorb it. Additionally, the centralization and traceability of information significantly improved visibility over supplier billing. The company moved from reacting to deadlines to strategically planning its payments, optimizing financial discounts and strengthening cash flow planning, which made billing a financial management tool.
Now, this transformation impacts three key dimensions:
- Operational scalability: the ability to grow without multiplying complexity.
- Financial control: traceability and predictability in obligations and collections.
- Informed decision-making: reliable data to plan for expansion and liquidity.
Beyond digitization
This case demonstrates a key distinction: digitizing is not redesigning.
Many organizations move their manual validations to a platform without questioning the underlying structure, but unfortunately, the result is a digital version of the same problem.
Effective automation begins with a deeper question:
How should the process work if we designed it today, with a growth mindset?
At Pércimon, the answer involved rethinking the flow before implementing it — technology was the enabler; the architecture was the real transformation. Growth always amplifies the existing structure: if the process is informal, it will amplify the friction; if it's structured, it will amplify the efficiency.
So the question shouldn't be whether your billing works today, but whether it's designed to sustain the volume you plan to reach.