What should a business system do that a spreadsheet can't?
A spreadsheet keeps what people type. A business system built around your process also makes sure each step happens: one record, access by role, checks before anything goes out, approval of an exact version, and a record of who did what. Research on spreadsheet errors points at people, not at the software.
The errors come from people.
Raymond Panko of the University of Hawaiʻi reviewed the research on spreadsheet errors. Intensive audits of 85 working spreadsheets found errors in 94% of them. In lab studies, 3.9% of cells held an error on average. When people inspected spreadsheets for errors, they found about 60% of them. His conclusion: the programs are not error-prone, people are.
A spreadsheet can hold checks and permissions, but nothing makes anyone use them. A system built for the process can require them.
SOURCE — Raymond R. Panko, University of Hawaiʻi · What We Don't Know About Spreadsheet Errors Today · EuSpRIG 2015
Enter it once.
In a system, each fact is entered once and every screen reads from that one record. The desk and the phone show the same figures, because there is only one set.
Each role sees what it needs.
OWASP, the web application security nonprofit, says to give each user only the minimum access their job needs, and to deny access by default so new access has to be granted on purpose. So staff, management, a client and a partner can each see a different view of the same record.
Opening a restricted record is an event worth logging. OWASP lists access to sensitive data among the things an application should record, and warns that without access logging, violations can go undetected or stay unattributable.
Checks run before anything goes out.
Reading a record over is not a check. In the same research, people found about 60% of spreadsheet errors, and some errors were found by fewer than one in ten. A system can run written rules every time, and keep a record as a draft until every rule passes.
A rule only catches what someone wrote it to catch. That is why the first questions are about what must be checked first.
SOURCE — Raymond R. Panko, University of Hawaiʻi · What We Don't Know About Spreadsheet Errors Today · EuSpRIG 2015
One version. One approval.
When a record changes after approval, the approval should not quietly carry over. The approver is shown the exact version and what changed since the last one, and the approval belongs to that version.
Approving also asks for a fresh sign-in. OWASP's guidance is to ask for current credentials again before a sensitive transaction, because someone with a stolen session or brief access to the user's browser could otherwise act as them.
SOURCE — OWASP · Authentication Cheat Sheet
Every step is on record.
OWASP says each logged event should record when, where, who and what. Where the agreed scope includes an audit record, entered, checked, evidenced and approved can be separate entries, each with a time and a person.
Where file evidence is in scope, the build can record a SHA-256 hash. A hash is a short fingerprint of a file. NIST's Secure Hash Standard defines SHA-256, and these fingerprints are used to detect whether a file has changed since the fingerprint was made.
No record is beyond question. OWASP notes that a log's trustworthiness often rests on whoever keeps it being audited properly, and says access to the logs should itself be restricted and recorded.
Part of Sri Lanka's data law starts on 1 January 2027.
A gazette order dated 13 July 2026 and published on 22 July 2026 sets 1 January 2027 for section 2, section 3, Part I and Part III of the Personal Data Protection Act, No. 9 of 2022. Part I covers the processing of personal data. It puts duties on controllers, the organisations that decide how personal data is used. Section 8 requires accurate data. Section 10 requires integrity and confidentiality, through appropriate technical and organisational measures, and the Act lists access controls among them. Section 12 requires controllers to maintain duly catalogued records of how they meet these duties.
Act No. 22 of 2025 amended the Act. It left sections 8 and 10 unchanged and repealed only subsection (2) of section 12.
Whether the Act applies to a business depends on section 2 of the Act. This is a plain summary, not legal advice.
SOURCES —
Government of Sri Lanka · Gazette Extraordinary No. 2498/16 · 22 JULY 2026Government of Sri Lanka · Personal Data Protection Act, No. 9 of 2022 · 2022Government of Sri Lanka · Act No. 22 of 2025, amending the Personal Data Protection Act · 2025Check your own process in 10 minutes.
- Where does the work start? Find the one place each record is first entered. If it is typed again anywhere else, mark it.
- Who sees it, and who acts? List who can open each record and who can change it.
- What must be checked first? Write down the rules a record must pass before it goes out.
- Who approves each version? Check that you can show which version they approved.
- What stays on record? See whether you can say who changed a figure, and when, without asking anyone.
Every "no" is a gap. Five answers on one page is the start of the conversation.
When a spreadsheet is enough.
One person, no approvals, nobody else who needs to see it, and no personal data about customers or staff: keep the spreadsheet. The five questions start to matter when a second person, an approval or personal data enters the process.
Vantaris by Tecblitz is supply chain intelligence, built on Intelligent Operations Software. A scoped build still starts from a process the company already has. Replay on your own history is the first paid stage. The build and the subscription are agreed in writing after that.
Checked 23 October 2026.