Why Finance Teams Still Rely on Spreadsheets in Business Central

Where spreadsheets re-enter Business Central workflows

In practice, spreadsheet dependency tends to show up in very specific places. Crestwood most often sees it re-emerge in workflows that span people, approvals, and timing rather than transaction entry.

Accounts Payable approvals
Before Business Central, invoices were routed by email or shared drives. After go-live, invoices are entered into the system, but approvals still happen in a spreadsheet or email chain. The spreadsheet becomes the coordination layer. It answers questions like who approved what, which invoices are waiting, and which ones are exceptions.

Accounts Receivable tracking
AR teams may post invoices in Business Central, but collections notes, disputed balances, and follow-ups are often tracked outside the system. A spreadsheet becomes the living document that reflects reality as the team sees it, even though the ledger technically holds the data.

Month-end close coordination
Business Central closes the books, but the close itself is managed elsewhere. Teams rely on spreadsheets to track task ownership, timing, dependencies, and sign-offs. The system records results. The spreadsheet manages the process.

These patterns are common across organizations of different sizes and industries. They persist even in well-implemented environments.

Why this happens even with a modern ERP

Spreadsheet reliance in Business Central environments is rarely about missing functionality.

It is about workflow design.

Most finance teams adopted spreadsheets long before ERP systems were in place to solve coordination problems, not accounting problems. Spreadsheets are flexible, fast, and easy to adapt when processes evolve.

When Business Central is implemented, the focus is often on configuration, data migration, and reporting. Less attention is given to how finance teams actually move work forward day to day. As a result, the ERP records transactions accurately, but the workflows that guide approvals, exceptions, and follow-ups remain informal.

This is not user resistance. It is a rational response to gaps between system structure and real-world behavior.

Finance teams are optimizing for visibility and control. When they cannot see exceptions clearly inside the workflow, they recreate that visibility externally.

What Crestwood sees in underutilized Business Central environments

In post go-live optimization work, Crestwood frequently sees Business Central environments that are technically sound but operationally underutilized.

Two anonymized patterns appear often:

First, AP teams use spreadsheets to manage invoice queues because approval workflows do not reflect how decisions are actually made. The system captures approvals, but it does not surface stalled invoices or priority exceptions in a way that matches how managers think.

Second, close processes rely on spreadsheets because task sequencing and accountability live outside the system. Business Central holds balances, but the close calendar, handoffs, and sign-offs are tracked manually.

In both cases, spreadsheets are compensating for workflows that were never fully designed. The ERP is working. The process around it is not.

This is where Business Central finance automation often stalls. Not due to lack of capability, but due to misalignment between system workflows and team behavior.

Reframing spreadsheets as a workflow signal

Spreadsheets are not the problem. They are the signal.

When a spreadsheet becomes essential, it usually indicates one of three things:

• Exceptions are not clearly visible
  • Ownership is not clearly defined
  • Timing and sequencing are not enforced by the workflow

Before Business Central, spreadsheets handled all three. After go-live, they should not disappear overnight. Instead, they should inform where workflow optimization is needed.

Consider a before and after view:

Before
AP approvals tracked in Excel. The spreadsheet shows status, approver, and urgency.

After optimization
Business Central workflows surface pending approvals, stalled invoices, and exceptions automatically. The system reflects how work moves, not just that work exists.

The goal is not to eliminate spreadsheets. It is to remove the need for them as a control mechanism.

From transaction volume to exception-based workflows

As finance teams scale, automation success depends less on processing speed and more on exception handling.

Business Central already handles transaction volume well. Where teams struggle is managing the small percentage of items that do not follow the happy path. These exceptions are what drive spreadsheets back into the process.

Effective Business Central workflows are designed around these moments. They surface what needs attention, route decisions appropriately, and provide visibility without manual tracking.

When workflows are built this way, spreadsheets naturally fade into the background. They become analysis tools again, not operational lifelines.

A calmer path forward

Spreadsheet dependency does not mean your Business Central investment missed the mark.

It means your finance team is doing what it has always done. Finding practical ways to maintain control and clarity.

The opportunity lies in stepping back and asking where workflows can better reflect how decisions, approvals, and exceptions actually happen. Not by adding complexity, but by aligning system behavior with real finance operations.

Crestwood regularly works with finance teams who are past go-live and ready for this next phase. The most effective improvements come from small, focused workflow adjustments that reduce friction without disrupting what already works.

If this resonates, you may find value in our upcoming Finance Automation Deep Dive webinar. It is a practical discussion focused on real AP, AR, and close workflows, not a product demo. We explore where spreadsheets tend to re-enter, why, and how teams are redesigning workflows around exceptions rather than volume.

Sometimes the path to automation starts with understanding why Excel never really left.