How to Replace an Excel Approval System in Malaysia

To replace an Excel approval system, start by preserving the approval rules. Map the request fields, approvers, value limits, exceptions, attachments, and final actions. Move new requests into a controlled data store, then add permissions, routed decisions, reminders, and a time-stamped history. Pilot one workflow, migrate open requests, and keep the old workbook as a read-only archive.

This guide is for Malaysian business owners and operations, finance, HR, or procurement teams whose approval process now spans a spreadsheet, email, and WhatsApp. It covers the controls your replacement needs, the main platform choices, and a seven-step cutover plan that keeps day-to-day work running.

Contents

• Why Excel approval systems become difficult
• Seven signs that your spreadsheet needs replacing
• Can Power Automate extend the current process?
• What the replacement system should include
• How to choose the right platform
• How to replace the workflow in seven steps
• A purchase request before and after
• PDPA and security controls
• How to measure the result
• Timeline and budget

Why Excel Approval Systems Become Difficult

Excel remains an excellent tool for calculations, analysis, and reports. Microsoft 365 also supports co-authoring for Excel files stored in OneDrive or SharePoint, so several people can work in a modern .xlsx file. That solves part of the shared-file problem.

An approval process carries more responsibility than a shared list. Someone must assign each request to the right approver, enforce value limits, preserve comments and attachments, handle leave cover, chase overdue decisions, and prove who approved what. In many offices, Excel stores the row while email or WhatsApp carries the decision. Staff then copy the result back into the workbook.

That split creates gaps. A manager can approve an old attachment. A staff member can overwrite the status. An auditor may need to search a mailbox for the decision. Management cannot see the current queue without asking the workbook owner to clean the data first. The business needs one record that holds the request, the routing, and the decision history together.

Seven Signs That Your Spreadsheet Needs Replacing

A spreadsheet can serve a small process for years. These signs show that the approval workload has outgrown the file:

• Staff ask which workbook or tab contains the current version. Copies circulate through email, shared drives, and personal folders.
• Requesters chase managers by message because the spreadsheet cannot assign a due date or send a reminder.
• Approval limits vary by amount, department, branch, project, or request type. Staff keep the rules in a separate SOP or in one person's memory.
• Several people edit the tracker, and someone must repair duplicate rows, overwritten cells, or broken formulas.
• The evidence for one request sits across the workbook, an email thread, chat messages, and an attachment folder.
• File access gives users more information than their role needs. A requester may see salary, supplier, customer, or budget data for other teams.
• The process slows down when the workbook owner takes leave because no one else knows the macros, formulas, or manual follow-up routine.

Several of these signs justify a short process audit. The audit should identify the real source of delay before anyone buys software. A slow approval can come from unclear authority, missing information, or a poor system. Software fixes the system part and enforces the rules that management agrees to.

Can Power Automate Extend the Current Excel Approval Process?

Power Automate can add an approval action around Excel, and it can work as an interim solution for a low-volume internal process. The workbook must sit in supported Microsoft 365 storage, use a defined table, and follow a controlled editing pattern. The team also needs someone who owns the flow when fields or approval rules change.

The Excel Online (Business) connector documentation lists a 25 MB file limit, possible file locks of up to six minutes, and a warning against simultaneous connector and manual changes because they can create merge conflicts or inconsistent data. These constraints matter when staff continue editing the workbook while an automated flow updates the same rows.

A stronger Microsoft 365 design uses Microsoft Lists or SharePoint as the request store and Power Automate for routing. Microsoft's approval workflow example starts from a SharePoint list, sends the request to an approver, and writes the decision and comments back to that list. Microsoft also recommends Dataverse for approvals that may run longer than 30 days.

Choose this route when your team already uses Microsoft 365, the users sit inside one organisation, and the rules fit the platform. Move to a dedicated or custom application when the workflow needs complex budget checks, external suppliers, customer access, deep ERP integration, or screens designed for a specific operational role.

What the Replacement Approval System Should Include

Treat the current spreadsheet as a starting specification. Its columns, formulas, status values, and lookup tabs show what the team uses today. The replacement should add the controls that the file and surrounding messages cannot manage as one process:

• A controlled request form with required fields, validation, reference numbers, and attachment rules.
• Named user accounts and role-based access for requesters, approvers, finance staff, administrators, and auditors.
• Serial or parallel routing with amount thresholds, department rules, substitute approvers, and separation of duties.
• A clear status model such as Draft, Submitted, In Review, Changes Requested, Approved, Rejected, and Cancelled.
• Notifications, due dates, reminders, escalation, and delegation when an approver takes leave.
• Comments and attachments stored with the request version that the approver reviewed.
• A time-stamped history of submissions, field changes, decisions, comments, and administrative actions.
• Search, dashboards, exports, backups, retention rules, and integration with the systems that act on an approved request.

Keep Excel as an output where it helps. Managers may still want a spreadsheet for analysis, pivot tables, or a board report. The workflow application should hold the master record, while authorised users export a controlled snapshot when they need one.

How to Choose the Right Approval Workflow Platform

Start with the system that already owns the business transaction. An accounting, HR, procurement, or ERP platform may include the approval function you need. Extending that module can reduce duplicate data and give the approved action a direct path into the ledger, payroll, purchase order, or employee record.

• Existing business system: Best when the request belongs inside an ERP, HRMS, document system, or procurement platform and its built-in rules cover the process.
• Microsoft Lists and Power Automate: Best for straightforward internal workflows in a Microsoft 365 environment, with SharePoint or Dataverse holding structured records.
• SaaS approval platform: Best for a standard workflow that needs a fast rollout and can adapt to the vendor's forms, permissions, integrations, and subscription model.
• Custom web application: Best when approval matrices, budget controls, external users, multilingual screens, reporting, or integrations follow business-specific rules.

A custom build carries the most value when the approval process forms part of a larger operational system. GRITC's Excel-to-web application service converts the trusted fields and rules into a secure multi-user application. Our business process automation service covers the routing, notifications, and integrations around that data.

How to Replace an Excel Approval System in Seven Steps

Plan the change around one real request from submission to completion. Include a rejection, a missing approver, and an exception. These cases expose more useful requirements than a clean happy-path diagram.

• Step 1: Map the current process. Record who submits, who checks, who approves, which channels they use, how long each stage takes, and what happens after approval. Mark every manual copy, message, and handoff.
• Step 2: Document the workbook logic. List each field, formula, lookup, macro, status, amount threshold, approver rule, attachment, and report. Ask the workbook owner to explain repairs and exceptions that never reached the SOP.
• Step 3: Define controls before screens. Agree on named roles, minimum access, separation of duties, approval evidence, retention, backups, and administrative rights. Give each control an owner in the business.
• Step 4: Select the platform. Match the option to user count, process complexity, external access, Microsoft 365 usage, integration needs, support capacity, and total cost over several years.
• Step 5: Build one representative pilot. Use a request type that includes common rules and one exception. Let real requesters and approvers test it with sample data, then correct the form and routing before migration.
• Step 6: Migrate active work and run UAT. Clean duplicate records, map old statuses, import open requests, and test submission, changes, rejection, delegation, escalation, export, and permission boundaries. Preserve required history in a read-only archive.
• Step 7: Cut over and assign ownership. Stop new edits in the old workbook, direct users to the new form, train each role, publish a support contact, and review failed or overdue requests during the first weeks.

Avoid a long parallel run with two master records. A short, controlled overlap can confirm results, but staff need one clear place for every new request. Set the cutover date, name the system of record, and document how the team will handle a request that started before that date.

Example: A Purchase Request Before and After

Consider an illustrative purchase approval. A staff member enters the supplier and amount in Excel, emails a quotation, then messages the manager. The manager replies with approval. Finance checks the workbook later, asks for the approval message, and updates the status. A change to the quotation can leave the final amount out of sync with the decision.

In the replacement workflow, the requester submits one form with the quotation attached. The system checks required fields and applies the agreed matrix. A request above RM 5,000 goes to the department manager and finance; a request above RM 20,000 also goes to a director. Each approver sees the same version, adds a comment, and records a decision under a named account.

After the last approval, the system notifies the requester and creates the next task for purchasing or finance. The record keeps the submitted values, attachment version, routing steps, timestamps, comments, and final status. Management can see pending value and overdue work without rebuilding a report from messages.

PDPA and Security Controls for Malaysian Businesses

PDPA compliance depends on the complete process: the personal data collected, its purpose, access, disclosure, protection, accuracy, retention, and disposal. The Malaysian Personal Data Protection Commissioner's Personal Data Protection Standard 2015 addresses security, retention, and data integrity. Use those obligations when you define the replacement system and its operating procedure.

The Commissioner's 2026 Data Protection by Design guideline describes flexible, risk-based measures across the data lifecycle. It covers data minimisation, access limitation, security, retention, backups, breach management, and attributable records. The guideline gives design guidance; your organisation must assess the law and sector requirements that apply to its data.

• Collect the personal data the approval needs and remove fields that serve no defined purpose.
• Use named accounts, strong authentication, minimum access, and regular access reviews.
• Log approval decisions and sensitive administrative actions with the user and timestamp.
• Set retention periods for requests, attachments, exports, backups, and logs, then enforce disposal.
• Document backup, recovery, vendor, hosting, and data-location responsibilities.
• Assign owners for access requests, corrections, incidents, system changes, and periodic control reviews.

How to Measure the Result

Capture a 30-day baseline before cutover when the request volume allows it. Use the same definitions after launch so management can see whether the new workflow reduces delay and manual work. Track median approval time, the overdue-request rate, manual follow-up messages, duplicate or reworked requests, and the percentage of completed requests with full approval evidence.

Review the exceptions as well as the averages. One request that waits ten days for a substitute approver can reveal a missing delegation rule. A high rejection rate can point to unclear form fields or missing guidance. Give one process owner responsibility for the measures and the backlog of improvements.

How Long Does an Approval System Replacement Take?

A focused approval workflow can fit a fixed-scope sprint when the team has agreed on the fields, roles, rules, and integrations. GRITC's typical automation engagements run for 2 to 3 weeks and cost RM 8,000 to RM 15,000. Complex approval matrices, data cleaning, ERP integration, external portals, or several departments increase the scope.

Start with a free automation audit. Bring the workbook, the approval matrix or SOP, two recent request examples, and the people who operate the process. GRITC can map the current flow, recommend Microsoft 365, SaaS, an existing business module, or a custom approval web application, then provide a fixed written scope.

Turn the Approval Rules Into a Controlled Workflow

A project to replace an Excel approval system should carry forward the rules that staff trust and remove the manual gaps around them. Keep one record for the request, the reviewed attachment, each decision, and the final action. Give the process owner live visibility instead of another spreadsheet to reconcile.

Choose the smallest platform that meets the workflow, security, reporting, and support requirements. Start with one representative approval, measure the result, and extend the system after the team proves the design. Book a free automation audit if you want GRITC to map the current file and recommend the right path.

Read Next

• Excel to Web Application Development Malaysia explains how columns, tabs, formulas, and macros move into a secure multi-user system.
• Business Process Automation Malaysia covers approval routing, reminders, reporting, and integration beyond the spreadsheet.
• Budget Management System Malaysia shows how budget controls and approval workflows work together.