IT systems · Practical guide

Validating CSB-System: linking material status to the correct weight

Choosing a raw material weight in CSB-System depends on the recipe, batch, assessed potency, quality status and connection to the balance. In a human medicinal product GMP example, a mathematically suitable substitute batch may still be ineligible for use. Test the material decision and check that supplier evidence covers the actual configuration.

Table of contents

At a glance

How do you validate CSB-System for a GxP-relevant production process?

Trace data and material from the test request through the assessed result and permitted batch to the recipe instruction and actual weight. Identify the CSB package, version, modules, balances and interfaces. Test status changes, substitute batches, calculation rules and interruptions. Use supplier evidence where it covers your configuration and requirements. A pharmaceutical product label alone does not demonstrate that the customer installation is validated.

  • The industry ERP, factory ERP, and actual plant equipment integrations collectively define the system boundary.
  • The analysis result, material status, and formulation status are separate pieces of information that collectively influence usage.
  • An independent expected quantity reveals retained old values and unauthorised batch changes.
  • Supplier documentation, customer testing, and operating procedures must align with their actual scope of coverage.

1. First, determine the package, documentation route, and scope of application

CSB-System SE describes its pharmaceutical industry solution as Industry ERP for the entire company and as Factory ERP for plants with connection to a higher-level Group ERP. The public package matrix also distinguishes Basic ERP. Therefore, do not transfer the complete pharmaceutical scope or Group-ERP connection unchecked to any installation. Capture ordered functions and actually used components separately.

Depending on the process, validation may cover recipe management, quality control, container stock, production confirmations, CSB-Rack and the balance interface. For Factory ERP, include data exchange with the leading enterprise system. Identify where the quality status is set, where quantity is calculated and which system posts actual consumption. A shared interface alone does not establish those relationships.

The regulatory scope of this guide applies to the manufacture or associated quality processes of human medicinal products under EU GMP. Annex 11 is the relevant GMP guideline for computerised systems. Medical devices, dietary supplements, or purely commercial activities do not fall within this scope solely due to the product name.

Sources: [1] [3] [6] [5]

2. Separate manufacturer functions from the actual version status

The currently publicly available pharmaceutical brochure states the date of May 2023. It describes a multi-stage compounding management with history, active ingredient balancing based on analytical parameters, and scale integration via CSB racks. These statements establish specific testing areas. However, they provide neither evidence of an up-to-date build of your installation nor a defined rounding algorithm, status code, nor an automated locking mechanism.

Prepare a configuration sheet prior to review: product package, software version, customer-specific modifications, database, employed modules, terminals, scales, and interfaces. Supplement with relevant release information and supported device combinations. A previously described update schedule from an older brochure is insufficient to determine current maintenance windows or patching policies.

CSB identifies pre-prepared risk assessments, test cases, and test plans as supportive documentation. Request the available materials for your project and align them with your specific requirements. A fully executed, appropriate manufacturing test can be valuable. Conversely, an unreviewed package or a general qualification statement does not substitute for a detailed comparison of version, configuration, and usage.

Sources: [2] [4] [6]

3. Clarify material status and data ownership at each transfer point

An existing inventory addresses a quantity question. A measured value describes a tested characteristic. The quality status and the intended decision determine whether the material may be used for a specific purpose. Do not combine these data into a single green screen field. Your requirements should specify which combinations are permissible for use and define the action to take when conflicting information is present.

The following work matrix translates the documented functional areas into individual verification questions. In the project, additionally specify the primary system, the responsible role, and the location of evidence. Particularly relevant is the timing between planning and actual sample withdrawal: information deemed appropriate at an earlier stage may be superseded by a newly assessed finding.

Own work matrix: from goods receipt to weighing-in
TransitionRelated informationSpecific evidential question
Goods receipt → Quality control Supplier batch, package, quantity, inspection task Does the inspection task specifically relate to the received material?
Quality Control → Compounding Evaluated analysis result, unit, batch, allowable use Does the correct analysis and decision logic achieve the calculation?
Recipe → balance Recipe version, expected quantity, container and work order Was is the same specification being executed that was professionally approved?
Factory ERP ↔ Group ERP Leading status, inventory level, takeover time point Is a discrepancy identified and addressed prior to the affected usage?

Sources: [2] [1] [6]

4. Test the analytical value, unit and recipe history together

During active ingredient balancing, a computationally plausible result alone is insufficient. The origin of the analytical value must be defined, including its assignment to the specific batch, its unit of measure, and its professional assessment. It must also be verified whether the value is based on the referenced reference value. A percentage value and a differently referenced content must not be implicitly assigned the same computational meaning.

Create the expected result independently of the specific application being evaluated. Document the allowable formulation, conversion factors, rounding rules, and quantity resolution in such a way that a peer specialist can trace and verify the invoice. Then, select targeted edge cases: missing analysis result, invalid unit, revised value based on order planning, or a batch no longer suitable. The appropriate response arises from your process, not from a predefined or artificial standard menu.

A recipe history should clearly illustrate the executed status. Distinguish the currently maintained master list from the original specification underlying an already initiated order. A subsequent modification must not create the impression during reconstruction that the prior order was executed according to the new specification.

Sources: [2] [6] [7]

5. Example of calculation: Replacement batch with other active substance content

The following example is a self-developed audit aid, not a manufacturing instruction and not a completed CSB test. An order is to yield a total mass of 100 kg with 10 kg active ingredient. Batch A contains 20% active ingredient, Batch B contains 25%. The remaining excipient in this example contains no active ingredient; losses, additional components, and rounding effects are explicitly excluded.

Before each error case, the same documented initial state is restored. The technical suitability of a substitute batch is a separate requirement. The table specifies a required standard for this example; it does not claim that CSB technically prevents every unauthorized action.

Sample calculation: Soll matrix with independent mass balance
Incident and Initial StateInvoice or errorExpected evidence
A is authorized for the order; 20 percent share 10 kg ÷ 0.20 = 50 kg A; 100 − 50 = 50 kg Carrier 50 × 0.20 = 10 kg active ingredient; total mass 100 kg.
A is locked for this purpose upon calculation. The old invoice remains mathematically correct Suspension until formal decision is made; provide evidence of technical or organizational implementation.
B is available; substitution is not yet authorized 10 ÷ 0.25 = 40 kg of B, with 60 kg of carrier. Calculating alone does not allow substitution; no use without the intended decision.
B is authorized for the order. 40 × 0.25 = 10 kg; 40 + 60 = 100 kg B, Analyte value, decision basis, specified and actual weighed amount are consistent.
Error: Previous usage value of 50 kg will be transferred to B 50 × 0.25 = 12.5 kg; Additional quantity 2.5 kg = 25 percent of the active ingredient target quantity Even at a total mass of 100 kg, the intended active ingredient quantity is not achieved; detect and evaluate the deviation.
Error: Correct quantity, but wrong pack size for Batch A instead of B 40 × 0.20 = 8 kg; shortfall of 2 kg = 20 percent of the active ingredient quantity required Verify material identity; the correct number alone does not fulfill the requirement.

Sources: [2] [6]

6. Include the actual scale and feedback pathway

The brochure describes the online integration of balances via CSB racks. However, the actual data exchanged by your system combination must be demonstrated through the appropriate equipment and interface documentation. Review the path from the input instruction to the displayed quantity and back to the recorded data. This includes, for example, in the selected process: material identity, unit, target value, measured value, and order reference.

A reasonable exception case involves an interruption following partial weighing. Prior to proceeding, define the amount already physically available, the amount recorded in the system, and designate who has authority to approve the resumption of the process. Subsequently, compare the actual material present, the displayed processing progress, and the documented consumption. The mere reconnection of a system does not constitute valid evidence of a technically correct restart.

In addition, check delayed or repeated messages with the Group-ERP connection. It is crucial whether an outdated quality information or double feedback could unnoticed create a wrong process state. Call for described error handling and comprehensible events; do not imply automatic repeat security or a specific technical blocking type.

Sources: [2] [1] [6]

Further reading:

7. Combine decisions, authorizations, and records

Determine who takes over analytical results, professionally evaluates them, modifies formulations, authorizes exceptions, and has actual authority to release materials. The required authorizations follow your established process. This does not result in a universal requirement for QA approval of every ERP action. Similarly, every status change is not automatically considered an appropriate electronic signature.

For decision-critical changes, you need a clear and traceable link: What was changed, by whom, when, and if applicable, with what rationale? Annex 11 addresses audit trails on a risk-based approach. Therefore, establish which events are relevant to your process and how they are appropriately reviewed. A complete printout of any history list does not by itself prove adequate coverage.

Verify the retrospective reconstruction of a closed order using the original analysis, dispensing, and decision status at the time of closure. Chapter 4 requires traceable records and controlled changes. The required data volume may therefore extend beyond a single result PDF. The electronic source data and relationships that must remain available are to be defined for the specific documentation purpose.

Sources: [6] [7]

8. Hosting, Recovery, and Controlled Changes

CSB describes cloud offers and local installations. The public service conditions designate services and limits; the concrete contract decides on your agreed scope. Check who operates application, database, device connection and backups. A general backup description does not replace the agreed recovery goal or any proof that the required process data can be used afterwards.

Separate backup, restoration, and professional retention. Annex 11 addresses the protection of stored data, the verification of restoration and archiving as interrelated but distinct activities. Therefore, a copy designated as an archive under contractual agreement must be verified for its intended retention purpose, access, and readability.

Assess changes based on their impact. A patch to the recipe calculation affects other validations differently than a purely cosmetic adjustment. New balances, interface modifications, and role changes can also be significant. Leverage existing tests strategically and supplement relevant transition phases. Neither every change nor every new release automatically necessitates a complete revalidation.

Sources: [4] [2] [6]

Further reading:

9. What preparatory steps make the project feasible

For a realistic cost estimation, you need more than just the number of users. Develop an actual process flow, a components list, a suitable example formulation, data sources, and existing documentation. Responsible personnel must be able to justify which material states are acceptable and how deviations are handled. IT and suppliers support the technical implementation.

Effort arises particularly due to multiple leading systems, customized calculations, changing analytical sources, scale integrations, and poorly reconstructible original orders. Unclear responsibilities lead to additional coordination, even when the software functionality is simple. Therefore, prioritize the transitions at which a wrong value or status could influence a quality decision.

Discuss with the supplier the documentation and test records available and the specific questions they can address. At the end-user level, particular attention should be given to the intended use, technical specifications, and the decision on appropriate validation evidence. The assignment of specific tasks may be defined on a project-specific basis; a rigid role assignment cannot be inferred from the product name.

Sources: [6] [2]

10. Checklist prior to use of the validated process

Use the list as a reference tool for specific usage decisions. A checkmark indicates an available and evaluated evidence, not merely a promised function. Document open points with their implications, responsible party, and decision status. Critical uncertainty regarding material identity or actual usage cannot be resolved through a well-composed closing report.

  • Package, build, module, scales, and interfaces are documented with their actual usage.
  • Material status, analytical source, and permitted use are professionally defined; conflicting statements are subject to a defined decision procedure.
  • Recipe formulation, unit, conversion, and rounding are clearly traceable; independent target values are available.
  • Risk-appropriate evaluation conducted for batch replacement, batch substitution, incorrect packaging, and interruption.
  • Supplier documentation is assigned to the actual configuration; remaining gaps are evaluated.
  • Permissions and relevant change information support the intended decisions.
  • Order data remain readable within the required context; storage and restoration have been addressed.
  • Operational responsibility, change evaluation, and handling of open investigation results are defined prior to use.

Sources: [6] [7]

Project experience and collaboration

Trace material status across module boundaries

Your process owners trace a CSB material flow through production, batch management and quality assessment. We establish which actions a status actually controls in your configuration. A critical handover may be tested separately first. If several modules are involved, we map the data paths, owners and available records before defining the evidence needed. The test approach relates to your configured solution and its permitted uses.

Frequently asked questions about CSB-System

Is the CSB system as Pharma-ERP already validated?

A pharmaceutical industry solution and appropriate supplier documentation can provide essential foundations. However, this does not imply a one-size-fits-all validation of your implementation. Key factors are the specific process, configuration, and existing validation evidence. When evaluating proposed risk assessments and test plans, verify that they cover the relevant version, features, and test conditions. Suitable documentation may be utilized; unaddressed customer requirements must be adequately supplemented.

Sources: [2] [6]

What differences between Industry ERP and Factory ERP are relevant for validation?

The industry ERP system describes the entire organisation, including MES functionalities, with a factory-level ERP implemented for plants under a group-level ERP. This configuration may alter potential system boundaries and data transfers. For factory-level ERP, it is particularly important to clarify which system manages quality status and inventory. The package designation alone does not indicate which interfaces, devices, and customisations are actually installed.

Sources: [1] [3]

What CSB version status must we document?

Document the actual current application status and the relevant components of your target configuration. The public pharmaceutical brochure from May 2023 does not include the current build number of your installation. Supplement with appropriate release and compatibility documentation for modules, database, scales, and interfaces. A manufacturer brochure or an outdated release cycle is insufficient to definitively establish the verified and subsequently operated state.

Sources: [2] [6]

How can we test that an unsuitable quality status prevents batch use?

Review, for each known batch and quality status, which bookings and usages are actually permitted. Predefine allowed and restricted actions, and incorporate exception pathways, time-delayed status information, and authorized decision-making. The mere display of a status designation does not constitute an effective lock in the subsequent process.

Sources: [2] [6]

How do we verify active ingredient balance independently?

Calculate the required amount outside of application for a technically appropriate test case and document all assumptions. In the simplified example presented in this article, 10 kg of active ingredient at a 25% content results in an application amount of 40 kg. For actual processes, the reference quantity, units, additional components, rounding, and technical suitability must be clearly defined. The manufacturer's note on active ingredient balancing does not specify a particular algorithm.

Sources: [2] [6]

Must every replacement batch always be electronically signed off by QA?

Not on a general basis. Specify within the applicable quality procedure who is authorized to assess a substitute batch for a specific order, what form of approval is required, and how the decision linkage is maintained. Required authorities and documentation shall align with the process and its defined scope. If an electronic signature is used, its suitability for this decision must be independently evaluated.

Sources: [6] [7]

Is calibration of the connected scale sufficient?

The metrological suitability of the scale does not answer whether CSB transmits the correct specification or assigns the actual value to the correct order. Therefore, check in addition the actual data path, units, material identity and fault cases. Validation of the application and the appropriate qualification of its IT infrastructure remain related to the intended use according to Annex 11; device documents do not replace this transitional test.

Sources: [2] [6]

Does CSB-Cloud-Hosting automatically cover GMP retention requirements?

No, a general hosting or backup description does not fully demonstrate the specific retention purpose. Clarify the contractual scope, required data relationships, readability, access, and recovery capabilities. Public terms serve as a starting point; your individual contract and actual evidence are decisive. A backup can contribute to data availability without necessarily fulfilling all professional archiving requirements.

Sources: [4] [6] [7]

Does 21 CFR Part 11 automatically apply to every CSB pharmaceutical project?

No. Applicability depends on the specific FDA record-keeping or submission context and the underlying requirements. The FDA Guidance on Scope and Application clarifies this distinction. Neither a pharmaceutical product name nor a general compliance statement determines it. First, determine which electronic records and, if applicable, signatures are involved in your regulated process.

Sources: [8]

What should we prepare for an initial validation meeting?

Provide the component list, process flow diagram, a sample recipe, analytical method sources, status rules, and existing supplier documentation. Identify the subject matter experts responsible for material usage and production, as well as the technical point of contact. This enables the identification and limitation of critical transfer points and missing evidence. The effort and approach can then be tailored to your specific configuration, without deriving general time or cost commitments from the product name.

Sources: [6] [2]

Sources and review date

Sources were checked on 6 October 2026. They include public CSB feature pages, service terms and the pharmaceutical brochure D | 5.2023. These sources do not confirm a specific current customer release number or services under an individual contract. The regulatory references are EU GMP Annex 11 and Chapter 4 for human medicinal products, both January 2011 versions. Assess FDA applicability separately. The figures and expected workflows are our own worked examples.

  1. CSB: ERP System for the pharmaceutical industry
  2. CSB Industry-ERP Pharma – Brochure
  3. CSB BASIC ERP: Comparison of ERP Packages
  4. CSB System SE: Software and Cloud Service Terms
  5. European Commission: EudraLex Volume 4
  6. EU GMP Annex 11: Computerised Systems
  7. EU GMP Chapter 4: Documentation
  8. FDA: Part 11 — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Define their CSB process specifically

We support you in integrating existing supplier evidence, technical requirements, and real-world data transfers into a traceable approach.

  • 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 →