VERSICH

ERP Risk Assessment: Single-Point-of-Failure Audit

erp risk assessment: single-point-of-failure audit

Single-Point-of-Failure Audit for Your ERP 

A single point of failure is any one person, account, system or vendor whose failure stops a business process. Every ERP has several, and nobody notices them until one breaks. The Microsoft 365 outage on 12 and 13 November 2026 exposed one of the most common: approvals and invoices that only move by email. Our live coverage of the Microsoft 365 outage shows how far that failure reached. 

This ERP risk assessment focuses on single points of failure: the seven areas where one failure stops a business process, with what to check and how to fix each one.

How to Run the ERP Audit 

Run the ERP risk assessment in one working session with your ERP administrator, finance lead and IT lead. Go through each area below and record every “yes” as a risk. Score each risk, then fix the highest scores first. 

1. People 

Check: Does one person hold all the administrator's knowledge? Does only one developer understand key integration or customization? 

Fix: Keep at least two trained administrators, document every workflow, script and integration, and cross-train before holidays and handovers. 

2. Sign-In and Access 

Check: Does everyone sign in through one identity provider with no tested fallback? Are multi-factor authentication codes tied to one person’s phone? 

Fix: Keep documented emergency administrator access that does not depend on single sign-on. In NetSuite, the Administrator role cannot sign in through SAML single sign-on, so confirm at least two people hold it and can sign in directly. 

3. Integrations 

Check: Is any integration authenticated with a named employee account? In NetSuite, token-based authentication tokens belong to a specific user and role, so deactivating that employee breaks the integration. Do integration failures alert only by email? 

Fix: Run every integration under a dedicated integration user and role, send failure alerts to a second channel, and document how to retry failed records. Our API development team rebuilds fragile integrations on this pattern. 

4. Email and Notifications 

Check: Do approvals move only by email? Do vendor bills arrive through one forwarded mailbox? 

Fix: Put approval queues on approvers’ ERP dashboards and send vendor bills straight to the ERP’s email capture address. Set up this way, approvals and bills keep moving when email is down. 

5. Data and Reporting 

Check: Is there a copy of master data and open transactions outside the ERP? Do all reports depend on one data pipeline or one analyst’s spreadsheet? 

Fix: Schedule exports to storage control and document the reporting pipeline from end to end. Our data and technology team builds pipelines with no single owner and no single route. 

6. Vendors and Payments 

Check: Does the business rely on one bank feed, one payment gateway or one shipping integration with no alternative? Who renews the company domain, DNS and security certificates? 

Fix: Map every ERP vendor dependency, set up a second payment route for critical collections, and keep a renewal calendar with two named owners. 

7. Customizations 

Check: Are there undocumented scripts, scheduled jobs nobody owns, or changes tested only in production? 

Fix: Keep a script inventory with an owner for each item, test every change in a sandbox first, and log each release. 

Score and Prioritize 

Impact 

Likelihood 

Action

High 

High 

Fix this month 

High 

Low 

Document a workaround this quarter, fix at the next upgrade 

Low 

High 

Fix when the area is next changed 

Low 

Low 

Review at the next audit 

Keep Your ERP Resilient 

ERP resilience is not a one-off project. Repeat the ERP risk assessment every year and after every major change: a new integration, a new subsidiary, a system upgrade or the departure of a key person. Our NetSuite managed services team runs this audit for clients and fixes the risks it finds. 

Conclusion 

A single point of failure stays hidden until the day it stops your business. One working session finds most of them, and the fixes are small: a second administrator, a dedicated integration user, an alert outside email. Talk to our ERP team and we will run a single-point-of-failure audit on your ERP and deliver a prioritized fix list.

Frequently Asked Questions

What is the single point of failure in an ERP?

A single point of failure is any one person, account, system or vendor whose failure stops a business process. Examples include one administrator, an integration that runs under one employee login, or approvals that only move by email.

How often should we run an ERP risk assessment?

Run an ERP risk assessment every year and after every major change: a new integration, a new subsidiary, a system upgrade or the departure of a key person.

Who should take part in the audit?

Your ERP administrator, your finance lead and your IT lead, plus the owner of each major integration. Together they cover the people, systems, and vendors that the ERP depends on.

What should we fix first?

Fix the risks that score high on both impact and likelihood first. Start with single-administrator setups, integrations running under a named employee account, and approvals that depend on email: each one stops a process the day it fails, and each fix is small.

Why should NetSuite integrations run under a dedicated user?

NetSuite token-based authentication tokens belong to a specific user and role. When that employee leaves and their access is removed, every integration using their tokens stops. A dedicated integration user with its own role keeps integrations running through staff changes.