Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Why growth exposes the weaknesses in financial processes

How to fix them before they cause problems.

[Photo: Getty Images]

Profile photo of Philipp Schloter

President & CEO · ABUKAI Inc

Growth rarely breaks a financial process overnight. More often, a process that worked for years becomes harder to manage one exception at a time. A new office uses a different approval path. An acquired business keeps its accounting system. A regional team needs different tax documentation. Finance teams respond with spreadsheets, email checks, and manual corrections. Each adjustment makes sense on its own, but together they create a process that is difficult to see and even harder to control.

The usual response is to standardize everything. That sounds sensible, but it can make the problem worse. A company can spend months forcing every business unit onto one workflow, only to discover that the workflow does not reflect how several parts of the business operate.

The mistake is assuming that scalability requires every part of the organization to work the same way. Often, what needs to be standardized is the outcome and the controls—not every step used to get there.

GROWTH EXPOSES HIDDEN DEPENDENCIES

Smaller organizations often run on shared context. An employee knows which manager to ask about an unusual expense and the manager knows when an exception is reasonable. Finance knows the history behind a transaction. Few of those decisions are written down because the people involved can resolve them quickly.

That informal knowledge does not scale. As transaction volume rises and teams spread across locations, finance sees more submissions without the context needed to evaluate them. Managers begin interpreting the same policy differently, and employees receive corrections after the fact even when they believed they followed the process.

The visible symptom may be slower processing, but the underlying problem is not speed. The actual problem is that the company has never separated true requirements from habits that developed around a particular team, office, or system.

ACQUISITIONS MAKE THE TRADE-OFF CLEARER

We recently worked with a company that has grown through several acquisitions. The parent company uses one enterprise resource planning and expense workflow, while the acquired businesses use different accounting systems, approval structures, and regional policies. Leadership wants consolidated reporting but does not want to interrupt operations by replacing every local system at once. This creates a common dilemma: achieving consistent financial control without forcing every acquired operation through an immediate systems migration.

A rigid standardization project might require every acquired company to change systems, coding structures, and approval routines immediately. That can create retraining, integration work, delayed reporting, and team resistance from those whose existing processes are functioning. The organization may end up adding temporary workarounds to protect business continuity, leaving it with more complexity than it started with.

A more useful approach is to standardize the information and controls the company needs while allowing the collection process to vary where there is a legitimate business reason. Every transaction might need an approval, currency, receipt, identified employee, business purpose, tax treatment, and general ledger code. How each business unit captures or routes that information does not need to be identical. What matters is that those different processes ultimately produce consistent, structured financial data that downstream accounting, ERP, and reporting systems can use.

STANDARDIZE OUTCOMES BEFORE WORKFLOWS

Finance leaders can begin by identifying the result that must be consistent. This includes the data required for accounting, the evidence required for audit, the approval authority required for policy, and the timing required for reporting. Those are control points. They should not be confused with preferences, such as which screen an employee uses or whether every country follows the same sequence of steps.

For example, two regions may have different receipt or value-added tax requirements. Treating those differences as process failures leads to repeated exceptions. Building the regional requirements into the process produces consistent compliance without pretending the requirements are the same.

The same principle applies to approval levels. A field services team may need project or work-order information that a corporate traveler does not. The company can require the same financial controls while collecting additional information only where it is relevant.

AUTOMATION DEPENDS ON CLEAR DECISIONS

Automation can reduce repetitive work, but it cannot decide which inconsistencies are intentional. If policies are vague, automation either passes questionable transactions or creates a larger queue of exceptions for finance to review. Adding technology before defining the rules often makes the confusion move faster.

Before automating a process, I recommend looking for three things: decisions that finance makes repeatedly, information that employees are asked to correct after submission, and exceptions that occur often enough to be predictable. Each one points to a rule, data requirement, or workflow choice that can be made explicit.

This does not require eliminating judgment. Some transactions will always need human review. The goal is to reserve that judgment for unusual cases instead of using it to compensate for an undefined process.

BUILD A FINANCIAL PROCESS THAT CAN ABSORB CHANGE

A scalable financial process should make it possible to add a location, business unit, or system without redesigning the entire operation. That requires a clear core of shared data and controls, plus defined room for local requirements.

Growth does not create most process problems. It reveals assumptions that were manageable when the company was smaller. Finance leaders who distinguish required outcomes from unnecessary uniformity can improve control without disrupting the parts of the business that already work.

The most scalable financial process is not necessarily the most standardized one. It is the one that is clear about what must be consistent—and flexible about what does not.

Philipp Schloter is president and CEO of ABUKAI.