ERP validation

ERP validation for pharma and medical device manufacturers From business process to release

For ERP systems used in GxP-relevant processes, we work with your team to define the scope, plan the tests and provide your QA team with the evidence it needs for its release decision.

  • We test GxP-relevant processes within the defined scope.
  • Include relevant extensions, interfaces and data migration.
  • You decide on release under your own quality procedures.
Video in German · Read the English summary

Daniel explains how the team can support an implementation with a fixed go-live date. You agree the scope, roles, milestones and release decisions. The team carries out the agreed validation work and reports progress through to handover.

Integrated Validation Execution. We manage the project and deliver the agreed work.

  • SAP, Business Central, Sage and other ERP systems
  • Annex 11 and Part 11 where applicable
  • Fixed pricing is possible once scope is clear.
  • Project enquiries: we reply by email

At a glance

How do you scope and validate an ERP system?

Identify the processes where ERP data can affect product quality, patient safety or data integrity. Trace a business decision such as a stock hold or a change of batch status through the configured workflow. Define the requirements and risks, select tests and record the evidence supporting release for that use.

  • Define scope from the processes, data and decisions in actual use.
  • Standard functions, configuration, extensions and interfaces may need different evidence.
  • Use supplier and partner documentation after assessing its suitability for your intended use.
  • After release, maintain the validated state through change control and periodic review.
Read the essentials of computer system validation

What we deliver

  • Define GxP processes, system boundaries and interfaces with your process owners, IT and QA.
  • Clarify requirements and risks and assess supplier and partner evidence.
  • Develop the test plan and implement the agreed strategy, including migration tests.
  • Prepare and hand over documentation using your SOPs and templates and train your responsible staff.

Your team’s responsibilities

  • Operational knowledge and requirements
  • Business decisions during the project
  • Formal release under your own quality procedures

GxP scope

Which ERP processes are GxP-relevant?

An ERP combines commercial and quality-related activities. For validation, identify where the system supports, implements or records a quality decision.

Start with a decision. Who uses which information to authorise material use, dispatch a batch or block stock? Where the ERP holds or transfers that information, or enforces the decision in the warehouse or at dispatch, include the affected process in the validation scope.

Module names help locate functions and owners but do not reliably divide relevant from irrelevant uses. A commercial hold, for example, may interact with a logistics release. Record the rationale for excluding a use.

We developed the table as a scoping aid. It illustrates common links and questions. It is not a regulatory classification.

Where common ERP functions may affect GxP processes
ERP areaPotential GxP connectionQuestion for scoping
Procurement and material masterMaterial identity, specification and intended useWhich data affect acceptance or use?
Batches and quality statusBlocking, releasing or changing the status of a batchWhich system makes the decision and which enforces it?
Warehousing and dispatchStatus, assignment and actual material movementWhich routes must enforce a block?
ManufacturingInstructions, starting materials and records of executionWhich data control or provide evidence of manufacturing?
Quality controlResults, assessment and quality decisionsWhich errors could lead to an incorrect decision?
TraceabilityAssignment of batches, serial numbers or product identifiersCan users trace the record forwards and backwards?
Finance and billingPotential shared data or linked holdsIs there a relevant dependency or do the functions simply share the ERP?
IT operationsAccess, data transfer and recoveryWhich supporting functions does the process need?

Sources: [1] [4]

ERP systems

Which ERP system are you validating?

The approach is vendor-neutral, while the checks depend on the product. These guides contain test cases for the individual systems.

Is your ERP missing from this list? The IT systems directory contains further guides.

Send an enquiry

What to test

What should the team test in an ERP?

Standard functionality, configuration, extensions and interfaces raise different questions. Set the depth of testing from the risk in each workflow.

Separate three questions. What evidence covers the standard product? How is your solution configured or extended? Does it work for the intended process? Include the connections to other systems and any extensions provided by implementation partners.

One GAMP category for the whole ERP cannot settle these questions. Standard functions, configuration, custom extensions and interfaces may need different evidence. Use the table to plan. Select tests and their depth from the risks identified.

Areas to cover in ERP validation
AreaQuestion to resolvePossible evidence
Configuration and master dataWhich rules, units and status values are actually configured?Compare the setup with business requirements.
Roles and permissionsWho can change a quality status, maintain master data or lift a block?Test allowed and denied actions with representative roles.
Change historyWhich changes to relevant data are recorded and who reviews them?Records of relevant changes identifying who, when and why.
Extensions and industry modulesWhat does the extension do in the quality-relevant process?Inventory with origin, version and assessed effect.
InterfacesHow are assignments, errors and repeat transfers handled?Compare defined source and target values, including failure cases.
Data migrationWhich data and relationships must reach the target intact?Reconcile what the data mean. Do not rely on record counts alone.
Reports and labelsWhich outputs support a quality decision or identify a product?Compare outputs with the approved data.
Updates and operationsWho assesses supplier changes and decides what to retest?Defined assessment with an owner and a justified test scope.

Sources: [1] [3]

Responsibilities

Who does what in an ERP project?

The implementation partner, operating company and validation team contribute different expertise. Resolve gaps in responsibility before the project starts.

The implementation partner can provide technical information and tests. Assess what they demonstrate against your requirements. Give an external validation team access to the relevant system version and results.

The allocation of work varies by company. Identify the actual contact and decision-maker for each task.

Dividing responsibilities in an ERP project
AreaImplementation partner's contributionOperating company's contribution
ConfigurationExplain actual settings and dependencies.Define the expected business rules.
ExtensionsDescribe version, function and the effect of changes.Assess relevance to processes and records.
InterfacesProvide mapping, error handling and technical evidence.Define meaning in the process and acceptance criteria.
TestsProvide suitable technical evidence and support for the test environment.Establish intended use and assess the results.
MigrationDocument the technical route and transfer results.Assess data mapping, exceptions and future use.
OperationsProvide agreed maintenance and change information.Assign responsibility for assessment and approval.

We plan validation, assess existing evidence and carry out the agreed tests with your team. You define the business rules and authorise release.

Sources: [1] [5]

Which responsibility is unresolved in your ERP project? Tell us where you stand.

Ask about ERP validation

Working with us

How we deliver ERP validation

Before the project starts, agree what we will deliver and who needs to participate. Each week you can see completed work, risks and decisions coming up.

IVE
Integrated Validation Execution

Project management and delivery from one team.

  1. Project management

    Commission the project and agree the scope

    You commission the project and we begin with scoping. We document system boundaries, deliverables, assumptions and the work expected from each side.

  2. Involve the responsible people

    Process owners, system owners, QA, IT and the supplier agree who is responsible for requirements, decisions and approvals.

  3. Make progress visible

    We maintain one agreed status for each system. The weekly report shows completed work, risks and upcoming decisions.

  4. Delivery

    Qualify and validate

    We prepare the agreed documents and evidence under your SOPs and templates, with testing and technical review as defined in the project.

  5. Hand over the evidence and knowledge

    We hand over the documentation, record open points and their owners and prepare your team to maintain the system in operation.

Computer system validation at a glanceExplore IT GxP consulting

Deliverables by project phase

What your team receives

Each phase produces evidence the next phase can use. We agree responsibilities with the operating company.

PhaseQuestions to resolve togetherDeliverable
ScopingProcesses, boundaries, extensions and interfacesJustified scope with named exclusions and open decisions
PlanningRequirements, risks and supplier and partner evidenceTestable requirements and a justified evidence plan
ExecutionSystem version, test data, execution and findingsLinked results with assessed deviations
MigrationData mapping, exceptions and reconciliationDocumented migration results with discrepancies resolved
Decision on useAssessment of results and operating prerequisitesDocumented decision under the company's quality procedures
OperationsUpdates, changes, review and data accessNamed responsibilities and applicable operating procedures

When we use GxPsuite, we draft these documents from your templates in the application. How we work with GxPsuite

Effort and costs

What drives the effort to validate an ERP?

We estimate the work once we have agreed the scope and objectives of your project.

Explore computer system validation costs

Send an enquiry

Checklist

What to establish before starting ERP validation

Use these twelve points to assess the proposal, plan and target date. An unanswered question can be a valid assumption if you make it visible and assign a next step.

System and intended use
Data and interfaces
Team and planning

How we work

Every project follows the same quality framework.

Reliable validation depends on who leads the work, which standards the team follows and how the results are checked before they reach QA. We establish the same controls on every project.

Daniel Herrmann provides technical oversight on every project. The team uses consistent procedures, templates and quality checklists so that quality does not depend on one individual.

We specialise in the life sciences: pharmaceuticals, biotech, medical devices and laboratories. Our focus on these sectors gives our team the GxP experience it brings to your project.

  1. Technical oversight

    Provided by Daniel Herrmann on every project.

  2. Consistent procedures

    The same procedures and templates across projects.

  3. Quality checklists

    Defined checks on every project.

  4. Continuous improvement

    We incorporate proven improvements into our procedures and checklists.

GxPsuite, our documentation system

Prepared automatically. Reviewed by experts. Approved by you.

For documentation for your ERP validation we use GxPsuite. It brings together your sources and automatically prepares a draft from your templates. Your team can review the draft and see which details still need to be supplied or checked.

Our experts begin their review with a draft prepared from your templates. This reduces manual preparation and helps us produce consistent documentation across projects.

The AI cites the source it used when answering a technical question. Our experts review the draft. Your team checks its relevance to the actual system and makes approval decisions under your quality procedures.

People make the technical decisions.

GxPsuite is a product of traqx GmbH, co-founded and managed by Daniel Herrmann.

Learn more about GxPsuite at gxp-suite.com

  1. 01 / Starting point

    Your sources and templates

    Your procedures, system documentation and a clearly defined task.

  2. 02 / Preparation

    A draft ready for review

    Documents and answers cite their sources and identify outstanding questions.

  3. 03 / Decision

    Experts review. You approve.

    Technical review and approval follow your existing quality procedures.

Personal project experience

Experience relevant to your project

HMS Analytical Software · Daniel Herrmann’s personal project experience

Build CSV processes into an existing quality management system

“Daniel kept our company’s particular circumstances in mind throughout and scaled the processes accordingly.”

Elisabeth Kohm · translated from the published German text
Read the published testimonial

SAP rollouts at Boehringer Ingelheim · Daniel Herrmann’s personal project experience

Coordinate validation management across SAP projects

“Daniel brings tremendous value through his expertise and commitment to validation and compliance.”

Jens Fuellbier · translated from the published German text
Read the published testimonial

ERP implementation at a pharmaceutical company · Daniel Herrmann’s personal project experience

Build CSV capability during a large ERP project

“A patient expert who exceeds expectations and successfully completes even the most complex projects.”

Heidelinde Hecher · translated from the published German text
Read the published testimonial

Daniel Herrmann’s own project work.

Three common misconceptions

What makes ERP validation defensible?

Common assumption01

“Our ERP is standard software. There is little to validate.”

The standard product does not establish how your company configures or uses it. Interfaces, migration and business rules can also need evidence.

What matters in practice

Assess actual use and the suitability of existing records.

Common assumption02

“The implementation partner tested it. That is our validation.”

Partner tests can contribute substantially. Assess their relevance to your requirements and system version.

What matters in practice

The operating company retains responsibility for business rules, assessment of results and release.

Common assumption03

“Validation is complete at go-live.”

Go-live is an important milestone. Updates, new roles and new interfaces can change the system afterwards.

What matters in practice

Assess changes and review the system periodically to maintain the validated state.

Frequently asked questions

Questions about ERP validation

Still have a question?
Send us your question.

Send a project enquiry
Must the entire ERP be validated?

Scope follows use. Identify where the ERP influences a decision about product quality, patient safety or data integrity. Describe those processes and test them according to risk. Give reasons for exclusions and consider dependencies between excluded functions and relevant processes.

Sources: [1]

Which rules apply to ERP validation?

Intended use determines applicability. EU GMP Annex 11 covers computerised systems used in GMP-regulated activities. For electronic records or signatures within FDA scope, consider 21 CFR Part 11. Article 10(9) of the EU MDR addresses medical device manufacturers' quality management systems. We use ISPE's GAMP 5 as methodological guidance. It is not legislation.

Sources: [1] [2] [6] [3]

Are the manufacturer's or implementation partner's validation documents enough?

They can contribute evidence. Assess them against your own requirements and use. Identify the system version each document covers, what it actually establishes and which gaps remain. Local configuration, extensions, data flows and operating procedures may need additional evidence.

Sources: [1]

How should we handle cloud ERP updates?

Assign an owner to assess announced changes and determine which checks are needed before or after activation. Use the supplier's information, your scope and the risk of the processes affected. Annex 11 requires controlled changes to a computerised system in accordance with a defined procedure.

Sources: [1]

When should validation begin in an ERP project?

Start by defining the processes before configuration and migration. This brings requirements and risks into the design and lets the implementation partner plan tests whose results you can assess as evidence. For a project already under way, start with the actual system and existing records.

Our ERP has been operating for years with incomplete evidence. Where do we start?

Review actual use and existing documentation. Missing documents do not invalidate every existing record, but years of use cannot establish suitability on their own. A gap assessment identifies the requirements and tests to add and their priority.

What does ERP validation cost?

The effort depends on process scope, extensions, interfaces, data migration and existing evidence. A fixed price is possible once scope is clear. A day rate can suit targeted advice.

Do you also validate SAP?

Yes. We have a dedicated SAP validation service for SAP S/4HANA and SAP ERP. The same approach to processes, data and decisions applies.

Sources and review date

Sources behind this guide

Sources were checked on 12 November 2026. The regulatory references cover computerised systems in GMP-regulated activities under EU GMP Annex 11 and, where applicable to intended use, 21 CFR Part 11 and medical device manufacturers’ quality management systems. We developed the overviews, test topics and checklist. The linked system guides provide product-specific information.

Daniel Herrmann
Life sciences compliance specialistSources checked: Updated:
  1. European Commission, EU GMP Annex 11: Computerised Systems, January 2011 revisionThe Principle and section 1 cover scope and risk. Sections 3 and 4 address suppliers, validation and data transfers. Sections 5 and 9–12 cover data exchange, change recording, change control, periodic evaluation and access.
  2. eCFR, 21 CFR Part 11: Electronic Records and Electronic SignaturesSection 11.1 defines scope. Applicability depends on the use within FDA jurisdiction.
  3. ISPE, GAMP 5 Second Edition, public description of the guideIndustry guidance on risk-based validation. It provides a methodology and has no legislative status.
  4. ICH Q9(R1), Quality Risk Management, official text hosted by the European CommissionRisk-based decisions and appropriate formality. The overviews here are our implementation suggestions.
  5. European Commission, EU GMP Chapter 7: Outsourced ActivitiesSuitability, responsibilities and agreements for outsourced GMP activities.
  6. EUR-Lex, Regulation (EU) 2017/745 on medical devicesConsolidated text of 19 July 2026. Article 10(9) addresses manufacturers' quality management systems.

Services

Computer system validation · Explore this service →

Your project enquiry

Tell us about your ERP project

Tell us about your ERP project, your target date and the support you need.

Send an enquiryTell us about your project · We reply by email
Daniel Herrmann
Daniel HerrmannWe start with your situation.