Sector guide

ERP for pharmaceutical companies: GxP, validation, traceability, serialisation and the platforms that fit

Pharmaceutical ERP carries records an inspector can ask for years later, so the system, the configuration and the validation evidence are bought together. Here is what MHRA and the EU and US rules expect, what the platforms offer, and how I would choose ERP for pharmaceutical companies.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

What the regulator actually expects of a pharmaceutical ERP

An ERP in a pharmaceutical manufacturer or wholesaler becomes a GxP computerised system the moment it holds a record the regulations require: a batch record, a material release, a supplier approval, a temperature excursion, a returned goods decision. From then on the questions on inspection are not about features but about whether the data can be trusted.

The MHRA’s GxP Data Integrity Guidance and Definitions, revision 1 of March 2018, is the clearest statement of the standard. Data must be attributable to the person generating it, legible and permanent, contemporaneous, original or a certified true copy, and accurate, and the governance around it must keep it complete, consistent, enduring and available throughout its lifecycle. Audit trails should be switched on, users should not be able to amend or switch them off, and routine data review should include a documented audit trail review where a risk assessment calls for it. Two sentences in that guidance shape every ERP decision I make in this sector. Systems should be validated for their intended purpose, and vendor supplied validation data is not acceptable in isolation of system configuration and intended use; the supplier’s test pack does not validate your process. And the effort and resource applied to assure data integrity should be commensurate with the risk to the patient, which permits proportion rather than validating every field in the general ledger.

So the specification for ERP for pharmaceutical companies starts with a map of which records in the system are GxP, who owns them and what evidence will prove they were controlled. Everything else, the platform included, follows from that map.

Computerised system validation: GAMP 5, Annex 11 and Part 11, and what is changing

Three documents set the method. ISPE’s GAMP 5 second edition, published in July 2022, keeps the first edition’s risk based lifecycle but asks for critical thinking by experienced subject matter experts rather than template driven paperwork, adds appendices on cloud, open source software, artificial intelligence and blockchain, and discusses the FDA’s computer software assurance thinking. EU GMP Annex 11 on computerised systems is being rewritten: the European Commission’s consultation on a revised Chapter 4, a revised Annex 11 and a new Annex 22 on artificial intelligence ran from 7 July to 7 October 2025. The draft Annex 11 applies quality risk management across every step of the lifecycle and tightens the requirements on system requirements, supplier and service provider oversight, data integrity, audit trails, electronic signatures and security. UK sites should plan on the revised text.

In the United States, 21 CFR Part 11 sets the criteria under which the FDA accepts electronic records and signatures as equivalent to paper. The FDA’s 2003 scope and application guidance says the agency interprets Part 11 narrowly and exercises enforcement discretion on validation, audit trails, record retention and copying, while the predicate rules stay fully in force. In September 2025 the FDA finalised its guidance on computer software assurance for production and quality system software, a risk based approach that supersedes section 6 of its general principles of software validation, written for device manufacturers but read closely by pharmaceutical quality teams.

What this means for an ERP programme is simple to state and hard to do. Classify each function by GxP risk, test the high risk ones hard with your own data, document the rest proportionately, and keep the evidence maintainable, because the vendor will change the software underneath you. Our ERP testing and go live page covers how we run that evidence trail.

Batch and lot traceability, quality management and electronic batch records

The operational core is the batch. Every material lot received, every intermediate, every finished batch and every pack shipped must be traceable forwards to the customer and backwards to the supplier, with expiry, retest dates, quarantine status and quality results attached, because a recall or a deviation investigation will test that chain under time pressure. Quality management has to sit in the same data: specifications and results, deviations, out of specification handling, CAPA, change control and supplier approval, each with electronic signatures and an audit trail.

The mainstream platforms have moved a long way here. Dynamics 365 Supply Chain Management offers electronic batch records built, in Microsoft’s words, to meet 21 CFR Part 11 requirements: a master manufacturing record documents the permitted methods and measurements, a batch production record captures the actual method, actual quantities, substituted ingredients and the quality orders generated automatically from the master record, and approving a bill of materials version, approving a route, posting the report as finished journal and validating a quality order can each demand an electronic signature backed by a cryptographic certificate and a reason code. Oracle announced in February 2026 that Fusion Cloud SCM gained formula, recipe and batch synchronisation, lot grade capture, a block on expired materials in production, automatic finished goods expiry from ingredient shelf life, and electronic batch record approval with electronic signature. Infor’s M3 Graphical Lot Tracker traces from raw materials to finished goods so affected product can be isolated and recalled. IFS Cloud adds a quality management product for deviations, nonconformances, audits and corrective actions. BatchMaster, built for process manufacturers, offers version controlled formulations, electronic batch records, pass or fail quality workflows, certificates of analysis and audit trails, and runs on top of QuickBooks, SAP Business One, Business Central or Sage.

For the wider process manufacturing requirements, our process manufacturing ERP guide goes deeper.

Serialisation and the Falsified Medicines Directive position after Brexit

Serialisation in the UK changed on 1 January 2025. Under the Windsor Framework the MHRA now licenses medicines on a UK wide basis, packs certified on or after 1 January 2025 must carry a UK Only label, and the EU Falsified Medicines Directive safety features regime was disapplied across the whole UK from midnight on 31 December 2024. The MHRA’s explainer puts it plainly: the European FMD safety features requirement no longer applies in Great Britain, and it no longer applies in Northern Ireland either. Two dimensional barcodes and serial numbers remain permitted, but any code the EU verification system would recognise must be removed or covered, and anti tamper packaging is encouraged rather than required.

That does not make serialisation optional for anyone who exports. Packs placed on the EU market still fall under the EU’s own rules, and other markets carry theirs, so a manufacturer or contract packer selling into Europe or beyond still needs a serialisation repository, aggregation of serials to cases and pallets, capture of events from packaging lines and country specific reporting. SAP Advanced Track and Trace for Pharmaceuticals, which runs on S/4HANA Cloud private edition, is the reference example: a corporate serialisation repository, sequential and randomised serial number management, an object and event repository, and country compliance packages for regulatory reporting. BatchMaster generates serial numbers for items and pallets where a customer requires them. Whichever route you take, decide early whether serialisation lives in the ERP, in a dedicated serialisation system the ERP feeds, or at the contract packer, because each choice changes the interfaces you have to validate.

The platforms that fit, by size and type of business

Shortlists in this sector depend less on features than on validation posture, so I group platforms by how much of the compliance burden they carry for you.

  • Large manufacturers and groups: SAP S/4HANA, with Advanced Track and Trace for serialisation, remains the default for complex multi site manufacturing, and Oracle Fusion Cloud SCM is now a credible process manufacturing alternative after its 2026 batch and electronic record additions. Our SAP consultancy page covers the S/4HANA route.
  • Mid sized manufacturers: Dynamics 365 Supply Chain Management with a life sciences partner, noting that Microsoft publishes GxP guidelines for Dynamics 365 and the Power Platform but states there is no GxP or Part 11 certification for cloud providers and the customer must validate its own applications. IFS Cloud, which names pharmaceutical compliance, batch tracking and quality control among its life sciences uses. Infor M3 for process manufacturers who need lot traceability and recall. And QAD, whose Qualified Environment for Life Sciences gives each site a dedicated production, test and development instance with installation qualification documentation and electronic record assessments, citing GAMP 5 second edition.
  • Smaller manufacturers, packers and wholesalers: BatchMaster on Business Central, SAP Business One or Sage, where a process layer with batch records and signatures sits on a finance system you already trust.

On the finance side I have implemented or delivered Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access over 19 years, and the lesson for pharma is that the ledger is rarely the validation problem; the batch, quality and distribution records are. For the platforms beyond that list, PEF’s practitioners have led and analysed the choices made before, during and after migrations onto them. We hold no reseller or referral agreement with any of these vendors and take no implementation revenue from them, which matters when a partner’s own template is being sold to you as the only safe option.

Validation effort, cost and how to choose

Budget for validation as a line in its own right, not a percentage buried in the integrator’s estimate. The cost drivers are the number of GxP functions in scope, how far you configure rather than customise, how many interfaces touch regulated data and, above all, how you will keep the system validated when the vendor updates it. One Microsoft partner that implements Dynamics 365 in pharma, Cegeka, describes handling validation and testing across the system’s whole life, especially when Microsoft launches platform releases twice a year, and working with a specialist computerised system validation firm so that project deliverables line up with GAMP 5 outputs. Every SaaS platform you shortlist needs the same answer: who performs release impact assessment and regression testing, how often, and with what evidence.

Three questions decide most selections. First, can the vendor or partner show a validated implementation method and a sample validation pack for the functions you will use, and does it fit your own quality procedures rather than replace them? Second, where will serialisation and your quality management system sit, and how many validated interfaces does the candidate ERP add? Third, what happens to the validated state at each release, in writing, with named responsibilities? Then run your own risk based testing on your own data before you sign. Our ERP vendor selection and data migration pages set out how we run both, and our fees are published plainly on the pricing page.

Related reading: Process manufacturing ERP, ERP for food and beverage manufacturers, ERP for aerospace and defence suppliers, ERP testing and go live, ERP data migration: what goes wrong, SAP consultancy.

Common questions

Does a pharmaceutical company need a validated ERP?

Yes, for the parts of it that hold GxP records such as batch records, material release, quality results and distribution history. The MHRA expects computerised systems to be validated for their intended purpose and says vendor supplied validation data is not acceptable on its own without your configuration and intended use. Functions with no GxP impact, such as parts of the general ledger, can be documented proportionately.

What is GAMP 5 and does it apply to ERP?

GAMP 5 is ISPE’s good practice guide for GxP computerised systems, now in its second edition from July 2022. It gives a risk based lifecycle approach to specifying, testing and maintaining systems, and it applies to any ERP that holds regulated records. The second edition stresses critical thinking over paperwork and covers cloud, open source software, artificial intelligence and the FDA’s computer software assurance approach.

Is the Falsified Medicines Directive still in force in the UK?

No. The MHRA states that the EU FMD safety features system was disapplied UK wide from midnight on 31 December 2024, covering Great Britain and Northern Ireland, and packs certified from 1 January 2025 must carry a UK Only label. Two dimensional barcodes remain permitted but must not be recognised by the EU repositories system. Packs you place on the EU market still follow EU rules.

Which ERP systems are used in the pharmaceutical industry?

SAP S/4HANA with Advanced Track and Trace dominates large manufacturers, and Oracle Fusion Cloud SCM added electronic batch record approval in 2026. Mid sized firms use Dynamics 365 Supply Chain Management with a life sciences partner, IFS Cloud, Infor M3 or QAD, which offers a qualified cloud environment. Smaller manufacturers and packers often run BatchMaster on Business Central, SAP Business One or Sage.

How much does ERP validation cost for a pharmaceutical company?

There is no standard figure, because cost follows the number of GxP functions in scope, how much you customise, how many interfaces carry regulated data and how you keep the system validated through vendor releases. Treat validation as its own budget line, ask each vendor who performs release impact assessment and regression testing and with what evidence, and price that recurring effort over the contract term.

Need an ERP your inspector will trust? We specify, assure and deliver GxP ERP programmes for pharmaceutical manufacturers and wholesalers, independent of every vendor and partner, with fees published plainly.

Book a confidential conversation

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving

ERP advice from PEF

Independent, client side help across ERP implementation: vendor selection, project management, testing and go live, health checks and programme recovery, on SAP, Oracle, NetSuite, Dynamics 365, Sage, IFS, Odoo, Epicor, Infor and more. Fees are shown plainly on our pricing page.

CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.