Practical guides · Practical guide

FAT and SAT in CSV: which tests can support IQ and OQ?

The supplier has tested cases your team is now being asked to repeat. Before starting another test campaign, identify exactly what the supplier's evidence establishes and what changes at your own site.

Table of contents

At a glance

Can FAT and SAT tests replace IQ and OQ evidence?

Selected tests and document reviews can be reused with justification where the requirement, tested version, environment, execution and result match. Demonstrate site-dependent functions separately. Annex 15 discusses reuse in qualification. For computerised systems, also consider the requirements of Annex 11.

FAT, SAT, IQ, and OQ are distinguished by their statement.

FAT stands for Factory Acceptance Test: a verification conducted at the supplier's site prior to delivery. SAT refers to the inspection performed upon arrival at the site. IQ and OQ evaluate installation and operational functionality within the intended qualification context. These terms represent different perspectives, not four mandatory, identical test suites for every computerized system.

For a system with control, FAT and SAT can be specifically linked to transportation, setup, and connection activities. In a pure SaaS application, this physical workflow is not directly applicable. In such cases, appropriate supplier documentation can be utilized without necessarily requiring artificial FAT or SAT phases.

The key question therefore is: Which requirement is demonstrated under what conditions? A Functional Acceptance Test (FAT) may demonstrate extensive functionalities yet provide no insight into future user management or connectivity to the customer network. A System Acceptance Test (SAT) may be site-specific and still fail to cover critical process flows.

Sources: [1] [2]

What does Annex 15 actually say regarding reuse?

Annex 15 section 3.6 allows certain FAT tests or document reviews to be used without repeating them during on-site IQ/OQ where this is appropriate and justified and transport and installation do not affect the function concerned. Section 3.7 addresses the possible addition of SAT.

This is not a blanket exemption from site qualification tests nor a requirement to repeat every supplier's test. The suitability of foreign protocols is also assessed. For the computerized component, particular attention is given to system status, configuration, data flows, and risk-based validation evidence.

The following decision-making steps serve as our working guidance. They do not expand regulatory requirements to include a fixed document list. In the project, clearly define which applicable conditions apply and which terminology is being used. Otherwise, disputes regarding test names may arise, even though the actual absence of a test statement should have been clarified.

Sources: [2] [1]

Evaluate the acceptance in seven questions

First: Is the own requirement truly identical to the verified one? Second: Is the tested software, hardware, and configuration state known? Third: What environmental conditions affect functionality? Fourth: Were the acceptance criteria appropriate and defined prior to execution?

Fifth: Are the execution, actual results, and findings sufficiently traceable? Sixth: What changes exist between the supplier's test and on-site operations? Seventh: Who evaluates and authorizes the transfer according to their own quality system? Only through these answers can a sound decision be made.

Refer to specific test cases and results. "Supplier is qualified" is a different statement from "Test F-18 confirms our requirement URS-12 under unchanged functional conditions." A supplier assessment supports the decision of trust but does not replace the technical assignment of evidence.

Own acceptance matrix: decide per requirement
Requirement and Supplier ScenarioTransfer validation checkDecision in the example
URS-12 · Computational Algorithm · F-18 Identical approved software version; independent required state; no location parameters Transfer may be considered upon assessment
URS-21 · Roll binding · F-31 Supplier used local accounts; Site employs its own identity system Complement site test
URS-25 · Measurement value transfer · F-44 Simulator replaces the actual laboratory device End-to-end test at the site
URS-32 · Restoration · F-52 Alternative backup procedure and other infrastructure Own restoration justification
URS-40 · Alarm limit · F-63 Customer boundary adjusted after FAT Investigate affected cases anew

Sources: [1] [2]

Example: a laboratory setup with computerized data evaluation

A supplier evaluates the data analysis algorithm of a laboratory system using defined input values. The software version is documented, the expected results are independently determined, and all relevant cases have been successfully completed. At the site, this algorithm remains unchanged. This evaluation statement can be accepted as valid following a suitability assessment.

In the same FAT, local users are created. At the site, logins are performed via the enterprise administration. This has altered the conditions for access and role assignments. The FAT documentation covers the supplier environment but does not verify actual identity binding. It is referenced and supplemented with targeted site-specific incidents.

The equipment passes results to a LIMS. Only a simulator was connected during the FAT. Site evidence must therefore cover the actual mapping, units, error handling and repeat transmission. Reusing the FAT evidence avoids unnecessary repetition of suitable tests. It does not remove any of the process questions the evidence must answer.

Sources: [1] [2]

Three decisions are better than simply transferring or repeating.

Result one: retain unchanged, provided the required statement is supported in the appropriate context and under transferable conditions. Document the rationale and the exact source reference. Future auditability must not depend solely on a temporarily accessible supplier portal.

Result two: adopt and extend. An existing test can validate an algorithm, while customer-specific limits or interfaces may be missing. Clearly define this extension. Thus, the entire test sequence does not need to be repeated unnecessarily, merely because a single condition differs.

Result three: do not accept. Reasons can be an unknown state, insufficient raw evidence, unexplained deviations or a substantially different environment. "Not overacceptable" does not mean that the supplier has worked badly. It is said that this document does not carry the concrete own test statement sufficiently.

Sources: [1] [2]

Monitor findings and changes between FAT and site control

Capture any relevant changes to the considered site following the FAT. This includes software corrections, parameters, hardware components, and interface configurations. A general note such as "minor adjustments" is insufficient if the change could affect a previously validated function.

Evaluate open FAT findings prior to acceptance. A test failing a criterion shall not be considered passed solely by signature. Clarify the impact, corrective actions, and required retesting. For findings deemed irrelevant, provide a clear and justifiable rationale for the lack of relevance.

Maintain the temporal chain: verified supplier status, subsequent changes, adopted site status. Only with this chain can a later reviewer understand why an older test date may still represent current validity. If the chain is missing, it must be clarified prior to the team deriving a release justification from the documentation.

Internal assistance tool for transfer between testing locations
Transfer pointTo ensureConsequence of deviation
FAT completed Version, Configuration, Results, and Findings No blanket acceptance of unclear cases
Delivery of the software Change list compared to FAT Assess the impact on accepted statements
Installation Actual site location and connections Purposefully evaluate deviating conditions
SAT/Site Test Enhanced customer-specific justifications Link requirements to gaps
Closure Rationale for Transfer and Remaining Limitations Only evidenced scope

Sources: [1] [2]

Keep documentation concise and sufficient for a decision

A useful reuse matrix links the requirement, supplier evidence, tested version, relevant differences, findings and decision. Reference the precise section of the test report so reviewers can find the supporting result without copying the whole report.

In addition, review the use of evidence within your own workflow. Who verifies the documentation? Who accepts the additional site tests? What changes trigger a revised assessment? Provide specific roles and decision points. A supplementary list containing the same information in different wording is not helpful.

The value lies in a clear chain of accountability. The team identifies what is already substantiated and what additional testing remains pending. The remaining work can then be planned technically, rather than being driven by the number of test packages or document pages.

Sources: [1] [2]

Project experience and collaboration

Map supplier tests to your own requirements

If you have FAT or SAT records, we examine an executed test with the owners. What did it demonstrate, on which version and under which conditions? We map that finding to your requirement. Transferable evidence can be included in the plan. Site-specific conditions and uncovered handovers require separate tests. If the results are missing or the tested setup differs, we record the gap. The name of the supplier document does not establish acceptance.

Frequently asked questions about Using FAT and SAT evidence

Must a completed FAT at the site be fully repeated?

Not automatically. Evaluate, for each required test statement, whether the conditions and settings are transferable. Annex 15 outlines a justified use of specific tests without repetition. Site-specific functions or relevant changes require additional supporting evidence. The decision is documented, rather than inferred from the test name.

Sources: [2]

Is SAT the same as OQ?

The terms may overlap in scope but represent different perspectives. SAT refers to a decline at the site; OQ evaluates functionality within a qualification context. Key factors are requirements, criteria, and results. A document titled SAT does not inherently cover all required OQ statements.

Sources: [2]

Does every cloud-based application require a FAT and SAT?

No, the physically defined sequence should not be artificially applied to every SaaS application. Utilize appropriate supplier documentation and verify the specific customer configuration and usage. The objective remains a risk-based demonstration of the intended use.

Sources: [1]

Can a supplier certificate replace the acceptance matrix?

A certificate may contribute to supplier assessment. However, it does not automatically demonstrate that a specific requirement within the own system has been verified. For that, you need relevant test-related information or other appropriate evidence, along with a justified determination of suitability.

Sources: [1]

How does one manage a pending FAT finding?

Assess the affected functional scope and its impact on your own application. Document any corrections, additional checks, or justified non-relevance. A professionally relevant finding must not be concealed through a blanket acceptance decision.

Sources: [2]

Can combined protocols be used?

Annex 15 permits appropriate combinations of qualification documentation. Ensure that requirements, prerequisites, acceptance criteria, and decisions remain clearly identifiable. Fewer separated documents do not imply a reduction in required evidence.

Sources: [2]

Sources and review date

Status: October 14, 2026. The takeover assessment is based on the listed regulatory and authority sources. Examples, test matrices, and templates are standalone reference tools; adapt them to your specific application.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. European Commission: EU GMP Annex 15, Qualification and Validation (2015)Qualification and validation, supplemented by the specific framework for computerized systems.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →