Excel is not your tool. It is your confession

When Excel carries your ledger, the cause sits upstream. Read the workbook as a map of the links your systems do not own, and fix them in the order of the chain.

Peter EngelFounder & CEO · 4 min read

The close is in its second day, and the one person who understands the reconciliation workbook is on holiday. Nobody else knows which tab feeds which journal, or why one cell holds an adjustment without a note. So the team waits, or guesses.

Few finance teams ever decide to run their books in Excel. It happens in small steps. A pivot table for a difference that should only appear once. A lookup for a new payment provider. A tab for a marketplace that was meant to be temporary. Years later, the workbook holds the matching rules, the adjustments and the explanations. It carries more of the accounting than the system it was meant to support.

That is not a spreadsheet problem. The workbook is the visible end of a chain that has been patched for years.

How the debt builds up

Infrastructure debt is what you get when the foundation under finance is patched instead of fixed. Each workaround makes sense on its own. An export from the payment provider, a mapping sheet, a settlement file split by hand, a journal template copied every month. Together they become the system. And none of those steps is recorded where the transaction started.

Nobody chooses that. In the short term, working around the system is simply cheaper than changing it.

Read the workbook as a map

Accounting is a chain. A transaction is captured, matched to an order, a settlement and a payout, posted to the ledger, closed by period and reported. The tabs in the workbook cover the links the system does not own. Read it that way, and it shows you where the debt sits.

  • Capture. A payment, an order and a refund describe the same sale in three different ways. Nothing in the source ties them together, so the record exists but nobody can follow it.
  • Matching. The rules live in lookups and in people’s heads. They are right for the cases someone remembered, and silent about the ones nobody has seen yet.
  • Posting. The ledger receives summaries. The detail an auditor needs stays behind in the source, linked by a reference someone typed by hand.
  • Close. The calendar absorbs the gaps. Buffer days get added because the work no longer fits the time the process was designed for.
  • Reporting. Management gets numbers with a caveat nobody wrote down. It lives in someone’s head, or in a comment cell nobody else opens.

Why fixing the matching is not enough

Reconciliation is usually where the chain hurts first. The bank does not match the payment provider, or the settlement does not match the orders. That is the right place to start looking. But a mismatch is a symptom. It means something upstream is not carrying the information the next link needs.

Fix only the matching, and the same problems return next month in a different form. They return when transactions arrive without a stable reference, or when fees are booked in another system than the sales. They also return when the close still depends on a manual journal.

So ask three questions at each link. Where was this record created? Which system holds its status today? Who decides how it is posted? The answers show most of the debt, and which link should own the record.

A safer workbook is still a workbook

Locking the sheet, adding a second reviewer and keeping a change log all lower the risk a little. But the workbook still starts from transaction data that arrives in pieces and is stitched together by hand.

Auditors know this. They do not test a spreadsheet on its own. They test whether a transaction can be followed from source to report. They check that the same question gives the same answer twice, and that every change leaves a trail. A clean reconciliation at the end does not help if a posting cannot be traced to its detail. Nor does it help if a matching rule changed last quarter and nobody recorded who approved it.

Fix it in the order of the chain

  1. Give every transaction a source reference that survives each hand-off.
  2. Bring matching into the system, so the rules are written down and versioned instead of kept in a file.
  3. Post entries to the ledger that can be traced back to their detail.
  4. Let the close and the reporting read from that foundation. The calendar shrinks because the work is already done.

Each step makes the next one cheaper. None of them requires replacing the ERP. Most of them do require agreeing, for the first time, which system owns which record.

Follow one revenue line

Take one revenue line from last month. Follow it from the first record in the source system to its line in the management report. Write down every hand-off, who or what made it, and whether it left a trace.

Each hand-off without a trace is a piece of infrastructure debt. The work starts where the trail goes dark, and for most businesses that point sits further upstream than the spreadsheet. Excel was never the problem. It only shows you where to begin.

In practiceCan you prove to your auditor today that your revenue is complete?

Written by

Peter EngelFounder & CEO