Lesson 1 of 6
Regulated contexts
13 min
In most SAP programs, testing answers a business question: does the system do what we need? In a regulated company, testing must also answer a second question, asked by someone outside the program: can you prove it? That someone may be an external auditor reviewing internal control over financial reporting, or an inspector from a health authority reviewing a manufacturer's computerized systems. This course is about producing evidence that answers both questions at once. It is not legal advice; your compliance, quality and audit functions decide how the rules apply to your company.
Two regulatory families
| Aspect | Financial controls (for example SOX) | Life sciences (GxP) |
|---|---|---|
| What is protected | Reliability of financial reporting | Product quality, patient safety and data integrity |
| Typical frameworks | Sarbanes-Oxley Act section 404; COSO Internal Control framework; PCAOB standards for auditors | FDA 21 CFR Part 11; EU GMP Annex 11; ISPE GAMP 5; FDA computer software assurance guidance |
| Who checks | Internal audit and the external financial auditor | Internal quality assurance and regulatory inspectors |
| Unit of focus | Controls over financial reporting, including IT general controls | Computerized systems and the GxP records and processes they support |
| Typical SAP scope | Order to cash, procure to pay, record to report, access and change management | Batch management, quality management, stock status, master data with quality impact, electronic records |
Financial controls in brief
Under section 404 of the Sarbanes-Oxley Act, management of a US-listed company assesses its internal control over financial reporting, and for many companies the external auditor attests to it. Most companies use the COSO Internal Control - Integrated Framework (updated in 2013), whose five components are control environment, risk assessment, control activities, information and communication, and monitoring activities. In SAP terms, the controls fall into two groups: application controls inside business processes (for example the tolerance check when an invoice is matched to a purchase order and goods receipt) and IT general controls (ITGCs) that keep those application controls reliable (user access, change management, and computer operations such as job scheduling and backups).
GxP in brief
GxP is shorthand for the "good practice" regulations in life sciences: good manufacturing, laboratory, clinical and distribution practice. Where a computerized system supports GxP processes or holds GxP records, regulators expect it to be validated for its intended use. In the US, 21 CFR Part 11 sets requirements for electronic records and electronic signatures, including secure, computer-generated, time-stamped audit trails. In the EU, Annex 11 to the GMP guidelines covers computerized systems. ISPE's GAMP 5 guide (second edition, 2022) is the industry's main practical framework for a risk-based approach.
When both apply
A US-listed pharmaceutical or medical device company is subject to both regimes, often in the same SAP processes. A goods receipt that moves a batch into quality inspection stock is a GxP event and an inventory valuation event. Do not run two separate test programs with two evidence standards. Agree one evidence standard that satisfies the stricter of the two, tag each requirement or control with the regimes it falls under, and let the risk assessment decide the depth. Internal audit and quality assurance should both approve that standard before testing starts.
- TagMark each requirement or control as SOX, GxP or both
- Set one standardOne evidence standard that satisfies the stricter regime
- ApproveInternal audit and quality assurance both sign the standard before testing
- Assess riskThe risk assessment sets test depth per requirement
- Test onceOne program, one evidence set, serving both auditor and inspector
What "validation" means
Computerized system validation (CSV) is documented evidence that a system does what it is intended to do, consistently, and remains in that state through change. Financial auditors use different words (design and operating effectiveness of controls), but the core idea is the same: defined requirements, risk-based testing, attributable evidence and controlled change. Both reject the idea that a vendor's product is "validated" out of the box. SAP provides a configurable product; each customer must show that its configuration and use are fit for its intended use.
What would you do?
Contoso's CFO asks whether the S/4HANA program can skip control testing because "SAP is a standard, widely audited product." What should Priya answer?
- Regulated testing must answer "can you prove it?" for an auditor or inspector.
- SOX focuses on internal control over financial reporting, including application controls and ITGCs; COSO is the common framework.
- GxP expects validated computerized systems; Part 11, Annex 11 and GAMP 5 are the key references.
- Validation is evidence that the customer's configured system is fit for intended use and stays so through change.
Check your understanding · not graded
Lesson check
1. Which is an IT general control relevant to SAP?
2. What does 21 CFR Part 11 address?
3. Why can't a company rely on SAP being "validated out of the box"?
4. Which framework do most companies use for SOX internal control?