IT systems · Practical guide

Business Central: testing batch traceability

An ERP record contains the batch number, but a recall list may still omit partial quantities, returns or open transactions. In Business Central, test the full chain of records and identify the limits of each tracing function.

Table of contents

At a glance

How do you test batch traceability in Business Central?

Define the backward and forward searches required by the actual process. Test known batch chains through partial quantities, production, transfer, sale, return and open transactions. Compare results, quantities and relationships against an independently defined reference package. Microsoft Item Tracing and Find Entries serve different purposes. A single result list does not establish that the entire recall population is covered.

Traceability begins with the question about the process

Define the user's required information in an emergency situation. "Where was raw material batch R-18 used?" is a forward-looking query. "Which incoming batches are contained in finished product batch F-42?" is a backward-looking query. For a recall, additional information such as recipient details, quantities delivered, remaining inventory, and previously returned goods must be included. These queries overlap but are not identical. A complete list of all documentation remains insufficient as a clear and actionable response.

This guide refers to Microsoft Dynamics 365 Business Central with the specific article tracking and, if necessary, extensions. The GxP evaluation concerns your actual process. A batch function in the standard is not a flat-rate proof of regulatory suitability. Document version, booking paths, interfaces and leading data sources. If an external warehouse or MES manages relevant relationships, its transition to the observed detection chain also belongs.

Sources: [1] [2]

Item Tracing and Find Entries differ

Microsoft describes item tracing for forward and backward tracking of booked inventory transactions. The display is based on balanced transactions. Therefore, due to multiple accesses to the same batch, the view cannot be considered a complete list of all activities without further investigation. Find Entries enhances the search capability and can display both booked entries and open records. The appropriate combination depends on your specific query.

In addition, evaluate display options and existing relationships. A simplified view may hide subordinate information that has already been tracked elsewhere. The user must understand this to avoid mistaking the absence of a visible branch for the absence of data. Conversely, the mere presence of an additional search function shall not be considered valid evidence of its proper use. The operating procedure and training must accurately reflect the actual research pathway.

Sources: [1]

Build a known chain of evidence for test data

Before test execution, create a reference package with known relationships. It shall include the relevant inbound quantities, consumption quantities, conversion factors, outbound deliveries, and remaining balances. Separate booked activities from open orders or deliveries. Define which of these are required for the specific decision. The "should" is derived from the described process and underlying documentation, not from a copy of a subsequent ERP report.

Intentionally vary the cases. Use the same batch number across multiple accesses, multiple batches within a single production run, and partial quantities in different deliveries. Include a return and a relevant correction entry. At multiple locations, account for transfers and local designations. A simple batch with a single access and a single sale can demonstrate the core functionality, but it does not address the typical limitations of subject-matter investigation.

Sources: [2] [1]

Example with quantity reconciliation

In this example, a 100 kg raw material batch R-18 is used. Of this, 60 kg is incorporated into finished product batch F-42, 30 kg into batch F-43, and 10 kg remains in inventory. From batch F-42, 40 units are shipped to Customer A and 20 units to Customer B. Two units from Customer B are returned. Additionally, a shipment from batch F-42 to Customer C has been scheduled but not yet booked. The quantities are intentionally simplified; actual formulations, yields, and unit volumes must be considered separately in the project.

The proof of target connects R-18 with both batches. For F-42, the search shows the original deliveries and the subsequent withdrawal without confusing them with each other. An open further delivery belongs to an additional consideration depending on the callback question. Do not add unnoticed stock and sales volumes with different units. Check each quantity relationship in the appropriate business object and explain which population actually covers the recall list.

Own work aid – Example with quantity reconciliation
Assessment questionExpected relationshipAdditional boundary case
R-18 forward F-42 and F-43 available Repeated receipt of the same batch
F-42 backward Right entrance racks Blending of multiple raw material batches
Recipient F-42 A and B with supply reference Partial and consolidated deliveries
Withdrawal Reference to the original shipment Resale or blocked stock
Remaining warehouse stock Correct location and status Transfer between locations
Open process Detectable outside authorized chain Search with supplementary procedure

Sources: [2]

Status, units, and corrections verified

Traceability requires not only IDs but also their meaning. Verify article number, batch number, quantity, unit, location, and relevant status. A converted quantity may be numerically plausible yet based on an incorrect packaging unit. Define conversion rules and rounding limits. For split or consolidated transactions, the relationships must be preserved and clearly understood.

Corrections and reversals change how users see transaction history. Where an assessment depends on that history, a reversed transaction must remain traceable. Check how the original, reversing entry and subsequent transaction appear. Changes to master data can also affect historical output. Decide which names or addresses from the time of the transaction must remain available for a recall and how the report identifies them.

Sources: [2] [3]

Include interfaces and extensions in the detection

When batch information originates from a WMS, MES, or external portal, verify the complete data transmission pathway. Which identity is transmitted? When is the booking considered accepted? What occurs in the event of a failure? A successful technical response can only confirm the receipt of a message. The actual inventory or production booking may still be missing. Therefore, reconciliation must reflect the true final state of the destination system.

Extensions may alter the data model, booking workflows, and reports. Evaluate them based on the current state. Test a duplicated message, a delayed recall, and a defective batch reference. Expected treatment and retry procedures shall be predefined. The reference population must not consist exclusively of data from the same error-prone report under review. Otherwise, both source and comparison may contain the same error, leading to a false appearance of perfect concordance.

Sources: [2]

Design a recall exercise as a process justification document

Under EU GMP Chapter 8, human medicinal products must enable an immediate recall to be initiated at any time. Its provisions must be regularly assessed for effectiveness, including in off-hours situations; consideration should be given to whether recall drills are necessary. Distribution records must be readily available to the recall responsible party and must enable identification of all distributors and direct customers, including contact details, batch numbers, and shipment quantities. A drill therefore integrates system investigation with accountability: assign a designated employee a known originating batch and verify whether they can fully identify the required recipients and inventory holdings. A separate evaluation of internal time objectives should be conducted; Chapter 8 does not specify a general time limit in minutes.

The system review does not replace a comprehensive regulatory recall assessment. Responsible functions must evaluate affected products, distribution channels, and required actions. The IT evidence provides a reliable data foundation for this evaluation. Document the boundaries: which distribution channels, open processes, or external inventories require additional information? A professional report makes these boundaries visible, rather than issuing an incomplete list as a comprehensive recall outcome.

Sources: [2] [1] [4]

Acceptance and maintenance of traceability capability

Summarize verified audit trails, configurations, reports, deviations, and operating procedures. A suitable qualification decision defines the authorized scope and required enhancements. Review access permissions, particularly in relation to the intended roles of recall responsibility holders. An administrator may view information that is not available to a team member in the recall team. The required information retrieval must be genuinely executable under the intended authorizations.

Define triggers for re-evaluation: changes to product traceability, new production processes, enhancement updates, additional warehouses, or new interfaces. Maintain a reusable reference dataset or its controlled description. This enables targeted verification of relevant relationships after changes. The ability to trace must be retained in operation; a single successful test prior to implementation is not sufficient for ongoing assurance.

Sources: [2]

Project experience and collaboration

Use a known batch history as the test reference

To test traceability, we first assemble a batch chain with independently known records and quantities, together with warehouse staff, production and the process owners. We compare backward and forward searches, including open transactions, against that reference. A gap in one extension or record type may need targeted work. If the population to be recalled is undefined, we clarify it before further testing. This makes clear which conclusion the search can support.

Frequently asked questions about batch tracing in Business Central

Is each batch number in Business Central automatically traceable?

A standalone existing identifier alone does not establish a complete audit trail. Verify article tracking, bookings, relationships, and actually used search paths. Open processes or external systems may require supplementary information. Crucially, the complete response to the specific forward, backward, or recall query must be provided.

Sources: [1]

Why can item tracing not display all expected processes?

Microsoft defines limits through balanced transactions and simplified representation of existing relationships. Review filter settings and display options, and additionally use Find Entries. A missing visible entry must be investigated; it does not automatically indicate data loss or complete search coverage.

Sources: [1]

Should open orders be included in a follow-up list?

Present open orders separately and decide on their handling based on the specific recall action. Finished goods already shipped and pending deliveries require different responses. The target population must therefore be defined in advance. A booked transaction chain must not be considered a complete overview of all potentially affected activities without proper verification.

How are returns and partial shipments verified?

Use known deliveries with defined quantities and associated returns. Verify original reference, quantities, status, and subsequent usage. Returns must not cause the original recipient to disappear from the history. Quantity reconciliations are performed in the correct unit and on the appropriate documentation level.

Is an Excel output sufficient as evidence?

An export can document a test result if the source, filters, time and records included are traceable. Check completeness and content. A manually edited list without a controlled link to the system search does not provide equivalent evidence. The export also does not replace an assessment of the underlying function.

Must the entire traceability be revalidated after each update?

Assess the change and its impact. Booking paths, data models, or reports affected require appropriate validation evidence. A stable reference case supports targeted regression testing. The scope shall be justified; neither a blanket end-to-end test nor a complete test exemption is appropriate for every update.

Sources: [2]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes. Additional source cross-check on October 18, 2026: Chapters 8, Items 8.22, 8.23, and 8.30 relating to recall readiness, sales records, and effectiveness assessment.

  1. Microsoft: Trace item-tracked items in Business CentralForward/Backward Search; only balanced item transaction entries in Item Tracing, Find Entries supplemented with open entries. Reviewed on 14.10.2026.
  2. 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.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  4. European Commission: EU-GMP Chapter 8 – Complaints, Quality Issues and Product Recalls, effective from March 2015No. 8.22, 8.23, and 8.30 reviewed on 18.10.2026. This requirement applies to human medicinal products; the specific design of the system validation is a separate derivation.

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 →