Back to the blog
auditcompliancetraceabilityinternal control

What your auditor will ask for (and your Excel can’t prove)

Basis Network

Seeing your data isn’t enough for an auditor. They want the supporting documents, who changed what and when, and the full history of every record. Here’s how that goes with Excel, and how it goes with Basis.

It’s nine in the morning. The auditor is already in the boardroom, laptop open, nursing a coffee someone poured a while ago. You have everything “ready.” They open a folder, pick a random invoice from March and ask: “Can you show me the supporting documents?”

And that’s where it starts.

Having the data isn’t enough for an auditor. They take that for granted. What they want is for you to prove that the data is true and that nobody touched it along the way. It sounds like the same thing, but it isn’t, and plenty of companies find that out too late, with the auditor sitting across the table.

Here are four things they’re almost certain to ask for. And what happens when the answer lives in an Excel file, a paper folder or a system that anyone with permissions can edit.

1. “Show me the supporting documents”

It’s the oldest question in auditing. Every figure needs a document behind it: the invoice, the purchase order, the minutes, the signed work order.

Now picture this: the document exists, but it’s sitting in the inbox of someone who no longer works for you. Or in a server folder named “FINAL_v3_for_real_this_time.” Or in a box at the back of the warehouse. While your team digs for it, the auditor waits. And takes notes.

That “we’re still looking” turns into an audit finding very fast. And a document that shows up days later, with yesterday’s modified date, raises more questions than it answers.

2. “Who changed this, and when?”

This is where Excel runs out of answers. Anyone with access can open, change and save an Excel file. Sometimes it keeps the name of the last person who saved it, sure. But it doesn’t keep what it said before, or who touched it the time before that, or why.

Now picture the scene nobody wants to live through. Management spots an odd figure in the month-end close report and asks who changed it. Silence. Nobody knows. Or worse: everybody knows, but nobody can prove it.

Your usual system has a similar problem. Many keep a change log, that’s true. The catch is that the log is managed by the same people who might have a reason to erase it. A user with admin rights can fix a figure and, if they want, its trail too. The auditor knows this. That’s why a screenshot won’t convince them.

3. “Walk me through this record’s full history”

The auditor doesn’t only care what a record looks like today. They want to see it from the day it was born: when it was created, what changes it went through, who approved them and how it ended up as the figure in the report.

Put a face on the problem. “Only Carlos handles that” is something you hear at a lot of companies, and it’s a ticking time bomb. The day Carlos goes on vacation, gets sick or quits, that record’s history walks out the door with him.

On paper it’s even worse. A sheet gets lost, gets wet or gets swapped for another one “that says the same thing.” And nobody can prove which one was the original.

4. “Why doesn’t this add up?”

Inventory discrepancies are the classic. The physical count says one thing, the system says another, and at the close, manual adjustments show up that nobody can quite explain. It could be a data-entry error or it could be shrinkage. With data anyone can correct, you have no way of knowing. Neither does the auditor, so it goes in writing.

The opposite also sets off alarms. A cash count that comes out exact every single day, for months, smells wrong to any seasoned auditor. In real life there are always differences. When everything comes out “balanced by hand,” the question changes: who balanced it, and how?

From there, it’s a short step to an audit finding. If the statutory auditor sees it as serious, it can end up as a qualified opinion in the audit report, which is exactly what no board of directors wants to read.

The same audit, but with Basis

Back to the boardroom. Same auditor, same coffee, same March invoice. The difference is that this time every operation in your company was recorded on Basis Network the moment it happened.

Here’s what that looks like:

  • The record is where it should be. Every operation sits in your database and is also sealed on the blockchain, so you don’t depend on someone remembering where they saved it.
  • Nobody fixes anything behind your back. Whatever is sealed on the blockchain can’t be altered afterward.
  • The history doesn’t depend on one person. It lives on the network, not in Carlos’s head or his inbox.
  • The auditor verifies it independently. They can check the proofs without you giving them access to your systems. They no longer have to take your word for it: they check it themselves.
  • You show them who recorded what, and when. And that nobody touched it afterward.
  • If someone touches a record, it shows. What your database says has to match what was sealed. If it doesn’t, you know where to look before someone else finds it.

And your team doesn’t have to learn anything strange. Basis doesn’t replace your ERP or your applications: it complements them, and people keep working the way they always have. Your company’s data lives on its own private subnet, so nobody else sees it. You don’t buy tokens or pay per transaction. It’s a monthly subscription, and we take care of the technical side.

Codesa and Grupo SuperGiros chose Basis Network: they have their own subnet, and we developed their gaming-ticket traceability system for them. In that sector, every ticket has to stand up to scrutiny.

Run the test before the auditor does. Take our audit check: seven yes-or-no questions, and at the end you’ll know where your company stands. If the result gives you pause, book 20 minutes with us and we’ll go through these four questions together, using your real operation.