Table of contents
At a glance
How do you validate Sage 100 add-ons in a GxP project?
Assess a GxP-relevant add-on together with the affected Sage 100 processes and data flows. Define suppliers, versions, interfaces and responsibilities. Test the business handover between the core system and extension, including failures, retries and status changes. Release of an individual module does not demonstrate suitability of the whole combination.
Scope and Applicability
Sage offers various partner and add-on solutions. The contribution does not assume any specific function within each add-on. Required features, such as logging or lock logic, must be demonstrated for the specific product and its version.
Inventory the actually used solution
Sage 100 can be used with add-on solutions and custom enhancements. The product name alone does not adequately describe your quality-relevant application. Therefore, capture the manufacturer, version, and purpose of each relevant module, as well as any customizations. A general Sage certificate or description of the base system does not automatically cover these components.
Start with the business process. Which module modifies batch information, calculates quantities, generates labels, or transmits results? What decision is based on this? Supplement database objects, interfaces, and manual transfers, as required to support the assertion. The system boundary should reflect actual data processing.
A manufacturer overview of add-on solutions serves as an entry point for inventory assessment, not as evidence of the specific installed behavior. Request appropriate documentation from the respective supplier. Explicitly identify missing information. An unknown module should not be implicitly classified as a standard function.
Assess dependencies between base, module, and interface
An add-on module can utilize data from the base system while simultaneously introducing its own fields or rules. A change to a common master record can impact multiple downstream outputs. Therefore, establish a simple dependency overview: source, processing, target, and responsible supplier. This overview also supports troubleshooting efforts.
Separate supplier documentation from internal process validations. A module test can verify certain functions, but cannot confirm your configuration, roles, or connected systems. Assess transferability based on version, scope, and prerequisites. Inappropriate documentation is not sufficiently valid merely by inclusion in the validation package.
| Component | Information to be captured | Question to investigate |
|---|---|---|
| Sage-Basis | Version and relevant configuration | Which master data and actions are used? |
| Add-on module | Supplier, Version, and Purpose | What additional quality-related logic is added? |
| Own customization | Status and Responsible Party | Who understands and maintains the rules? |
| Interface | Data objects, Mapping and error path | Is processing traceable through to the recipient? |
| Output | Report, label, or file | Which decision is based on the result? |
Example: An add-on module alters the unit logic
The base system processes quantities in kilograms, while an add-on module generates output in grams. For 0.25 kilograms, a output of 250 grams is expected. After a change, an unintended second conversion factor is accidentally applied. The output contains a plausibly formatted but incorrect value. A test focusing solely on the input mask does not detect this issue. This example does not describe a defect in Sage 100 or a specific add-on module, and it is not a completed product test.
Document the original value, unit, transformation rule, and target output. Verify a normal value, a low limit value, and an invalid or missing unit. The independent setpoint is calculated prior to execution. Test the actually installed combination of base, module, and output pathway.
Upon a failure, investigate where the transformation occurs—this may be within the module, in a mapping, or already in the source dataset. Manual correction of the generated document does not address the root cause. After adjustment, affected cases and other dependent outputs are reviewed. The selection remains focused on assessed risks.
| Test case | Input or situation | Expected evidence |
|---|---|---|
| Normal case | 0.25 kilograms | 250 grams in the correct target context |
| Small amount | Designated low amount | Defined accuracy and rounding |
| Missing unit | Value without required unit | No unexplained further professional processing |
| Repetition | Repeat the same action again. | Selected repetition rule remains traceable |
| Module change | Review new setup with reference cases | No unintended second factor |
| Other edition | Check dependent label or report | Common logic operates consistently |
Clarify supplier roles and responsibilities in writing
With multiple suppliers, each one may only understand a portion of the overall process. Identify who evaluates the baseline, module, customization, and interface, and who integrates the overall picture. A disruption should not circulate among suppliers due to ambiguity in the primary data rule. The responsibility of the regulated company for its own usage remains intact.
Grant access to required documentation and support for changes. Which versions are supported? How are known defects communicated? Who provides justification for a custom adaptation if the original developer is unavailable? These questions impact long-term maintainability and are part of a reasonable supplier assessment.
Document the limits of available evidence. A marketing description is weaker than a specific functional or test validation basis for the installed system. Missing evidence may necessitate additional internal assessments or an alternative solution. A general "the manufacturer is responsible" statement does not close this gap.
Updates apply to the entire combination.
An update to the core system may affect an unchanged add-on module. Conversely, a module update may alter the handling of existing data. Assess compatibility and impact on the process jointly. Technical startup of the application constitutes only part of the validation evidence.
Maintain a small set of critical end-to-end scenarios. It should encompass data intake, transformation, rights management, and output. Upon a change, justify which scenarios require re-execution. A complete test of every financial function is not automatically required; a simple login test is insufficient for critical quantity logic.
Obtain a traceable configuration state with all relevant versions. The designation "Sage 100 current" is ambiguous and insufficient for future reconstruction. Link test report to the actually used combination. This enables the team to specifically identify the changed component in a subsequent investigation.
Share responsibility for updates and outages together
Clarify responsibility for changes. A Sage update and an add-on update may have separate timelines and point of contact, even though they modify the same process. Without coordinated compatibility and validation planning, a combined scenario exists that has not been collectively evaluated by any of the involved parties.
Even an incident requires a shared understanding. A scanner can locally confirm a process step, while the booking in the ERP is rejected. The team needs a clearly identifiable failure point, controlled reproducibility, and reconciliation against duplicate bookings. These evidences form part of the process and not merely part of a technical interface test.
Operate and handover in accordance with understandable rules
Do not provide only installation files—also convey the technical significance of key configuration settings. An internal system owner should be able to explain the pathway of a critical value from its source to its final output. A hands-on exercise involving a unit transformation or a status change demonstrates whether this linkage is fully understood.
Define the approach to errors and manual corrections. Who assesses affected data, who modifies the rule, and who confirms the correct downstream processing? Obtain the original finding and its linkage to the correction. A revised label without explanation may obscure the underlying root cause.
Assess long-term dependence on the add-on module. If a supplier discontinues support, data access, required documentation, and potential replacement must be evaluated in a timely manner. An active license alone does not constitute a complete operational or retention strategy.
Worksheet for tracing a value through the base system, extension and output
Describe a critical data chain with unique identifiers. In the example, a quantity is recorded in the base system, transformed by an add-on module, and displayed on a label. Name each transformation step. If two components perform the same conversion, a systematic error may occur, even though each interface appears plausible.
The submission is also suitable for coordination among multiple suppliers. Each supplier should specify the portion they provide and the assumptions they undertake. The overall responsible party shall integrate these statements. An ambiguous interface between suppliers must not be obfuscated by a general affirmation of the baseline system.
When an observation is identified, the manufacturer and customer should evaluate the same referenced data instance. This facilitates differentiation between source errors, transformation errors, and display errors. A manually corrected output may be necessary in the short term, but does not automatically address the flawed common rule.
| Kettenfeld | Example entry | What the test establishes |
|---|---|---|
| Source | 0.25 kilograms with known article identification. | The original value and unit are unambiguous. |
| Extension | Module referenced with documented version. | The location of the conversion is known. |
| Rule | One kilogram is converted once into grams. | Target value 250 grams, independently derived. |
| Output | Label or report for the correct procedure. | Value, unit, and reference are consistent. |
| Failure scenario | Missing or inappropriate unit. | No unexplained further processing. |
| Change | Base or module update with the same reference. | Compatibility and professional efficacy jointly evaluated. |
Next steps
- Document system boundaries and data-modifying functions.
- Evaluate supplier compatibility and provide evidence from both suppliers.
- Perform common normal and failure cases.
- Define ownership for updates and failures for the combination.
Project experience and collaboration
Verify data transfer between Sage and the add-on module
With the process owners, IT and the extension provider, we trace a value through Sage 100, its add-on and the final output. We identify changes in units, status or responsibility and the record that covers each handover. One add-on may need only a targeted addition to existing validation. If several extensions are being redesigned together, we first map their dependencies. We then agree tests for faults, retries and subsequent updates.
Frequent Questions about Sage-100 Enhancements
Can the add-on module be validated independently?
Is the release of the implementation partner sufficient?
What should be included in the system description?
Can we validate Sage 100 only and exclude additional modules?
No, if these modules influence the intended quality-related processes. The system boundary follows data and decisions. A module that performs unit conversions or generates batch information should accordingly be included in the evaluation. Purely independent, non-critical functions may be categorized differently; the demarcation should be clearly justified.
Does a module supplier’s compatibility release suffice following an update?
It can serve as a valuable basis. However, verify its current status and scope of coverage. Additional documentation may be required for your configuration, customizations, and connected systems. Appropriate end-to-end scenarios should be validated to confirm that critical functional processing continues to operate correctly within your actual system combination.
Which add-on modules should be included in the system inventory?
Capture those components that influence the intended quality-related process or its validation evidence. This may include partner solutions, customizations, and interfaces. The installed product name alone does not adequately describe the actual solution. Justify excluded independent functions based on their impact.
How do we prevent gaps in accountability among multiple suppliers?
State the source, processing, and destination, together with the responsible party for each. Agree on who will coordinate the overall case and provide the required evidence. A supplier validation for a component does not substitute the assessment of system interaction. Specific responsibilities should remain clearly defined in the project and operational model.
Sources and review date
The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.
- 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.
- Sage: Add-on solutions for Sage 100Supplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.
Sources checked: .
So your team can safely plan the next step.
We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.
- 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.

