Dynamics 365 for Chemical & Process Manufacturing

Process vs. Discrete Manufacturing in Dynamics 365

The fundamental difference between process and discrete manufacturing affects how you configure Dynamics 365:

Discrete Manufacturing produces distinct units. A laptop assembly line manufactures individual laptops. Each product has a bill of materials (BOM) listing exact component quantities. Production follows a make-to-order or make-to-stock logic centered on finished good units.

Process Manufacturing transforms raw materials through chemical or physical processes. A paint manufacturer mixes base resins, pigments, solvents, and additives in precise proportions to create paint batches. A pharmaceutical company dissolves active ingredients in carriers and excipients. Output is measured in liters, kilograms, or gallons – not discrete units.

In Dynamics 365, this distinction appears in how you define production formulas, manage potency, handle yield variance, and track by-products.

Dynamics 365 Finance & Operations includes a dedicated Process Manufacturing module that extends core production capabilities:

• Formula versioning: Maintain multiple formula revisions with start/end dates, allowing staged recipe updates
• Potency tracking: Define ingredients with variable strength; the system scales quantities to achieve target potency
• Catch-weight products: Products sold by weight or volume with inherent variance (e.g., 1 kg ± 5%)
• Parallel processing: Run multiple steps in parallel rather than sequential assembly
• Continuous flow: Model production lines that run continuously, not discrete batches

Business Central, by contrast, uses a simpler BOM/assembly model. It works for small chemical manufacturers with straightforward formulas and low regulatory overhead, but lacks potency tracking, advanced batch attributes, and the audit-trail depth required for FDA or REACH compliance.

Formula and Ingredient Management

A chemical formula is the recipe: which raw materials, in what quantities, under what conditions, produce the desired end product. In Dynamics 365 Finance & Operations, formulas are the foundation of process manufacturing.

Key formula capabilities:

Feature	Purpose	Example
Formula lines	Specify each ingredient, quantity, unit, and planning percentage	Polyol: 100 kg, Isocyanate: 45 kg, Catalyst: 2 kg
Potency	Define ingredient strength; system scales to target potency	Pigment supply is 80% pure; formula expects 95% purity
Formula versions	Maintain multiple revisions with effective dates	Q1 formula vs. Q2 formula (supplier ingredient change)
Co-products & by-products	Define secondary outputs beyond primary product	Paint manufacturing yields both paint and solvent recycle stream
Planning percentage	Adjust ingredient quantities for process loss/yield	Input 100 kg resin; expect 5% evaporation loss in process

In practice, a chemical manufacturer maintains a centralized formula library in Dynamics 365. Each formula links to:

• Product item master (finished good)
• Ingredient item masters (raw materials, solvents, catalysts)
• Unit of measure conversions (kg to L for liquid ingredients)
• Standard cost (roll-up from ingredient costs and process overhead)
• Approval workflows (QA sign-off before production use)

When a production order is created for 1,000 kg of paint, the system pulls the formula, scales the ingredient quantities by 1,000, applies potency adjustments, and accounts for planning percentages. The result is a bill of materials unique to that batch – a bill that may differ from the formula if catch-weight variances occur.

Batch Attributes and Potency Tracking

Chemical products are rarely uniform. Two batches of epoxy resin produced from the same formula may have slightly different viscosity, color, or cure time due to raw material variation, temperature, or equipment differences. Dynamics 365 Finance & Operations addresses this with batch attributes.

Batch attributes are custom fields attached to inventory batches:

• Concentration: Actual % of active ingredient (target 98%; measured 97.8%)
• Viscosity: Measured in cP (centipoise); quality range 50–60 cP
• Color: Visual or spectrophotometric measurement against standard
• Shelf life: Days or months until expiration based on stability data
• Potency: Bioassay or chemical test result for pharmaceutical actives
• Catch weight variance: Actual weight vs. nominal for catch-weight items

During quality testing (after production), lab personnel record these attributes. The batch is held until QA approves. Once released, inventory is tagged with these attributes, and the system enforces quality holds if attributes fall outside specification.

Potency tracking is a specialized use case. In pharmaceuticals, a batch of API (active pharmaceutical ingredient) might have 98.5% purity instead of the target 100%. When this ingredient is used in a tablet formula, the system scales the quantity upward to compensate: if the formula expects 100 g of 100% API but the ingredient is 98.5% pure, the system uses 101.5 g of the actual ingredient to achieve the target potency in the final tablet.

This automation is critical for pharmaceutical, dietary supplement, and high-performance chemical industries where off-spec ingredients must be used (at higher cost) or rejected entirely.

By-Products and Co-Products

Many chemical processes yield multiple outputs. Refining crude oil yields gasoline, diesel, kerosene, and fuel oil. Manufacturing polyurethane foam produces foam waste and excess liquid resin that can be recycled. Dynamics 365 handles this through by-products and co-products.

Co-products are planned, intentional outputs with equal economic value. A rendering plant processes animal byproducts to produce meat meal, bone meal, and tallow – each with market value. You define multiple "output" lines in the formula, and production orders produce all of them simultaneously.

By-products are secondary outputs, often with lower value, or waste streams suitable for recovery. If a paint batch yields 10,000 L of usable paint and 150 L of solvent recycle stream, the 150 L by-product is tracked separately and may be reprocessed or sold.

In Dynamics 365:

• Define by-product and co-product items in the formula with planned output quantities
• Assign scrap, loss, or standard cost reduction to by-products to adjust costing
• Track actual yield variance: if a batch produces 10,100 L instead of 10,000 L, the system records the 100 L overage
• Report yield analysis to identify process improvements

This capability is essential for optimizing profitability. If a chemical manufacturer can recover and resell a by-product instead of disposing of it, the formula costing and production P&L reflect that value immediately.

Hazardous Materials and Regulatory Compliance

Chemical manufacturers operate under strict environmental and safety regulations:

REACH (EU) – Registration, Evaluation, Authorization, and Restriction of Chemicals. Companies must register chemical substances, assess hazards, and maintain compliance documentation. Non-compliance carries fines up to €5,000 per day per substance.

EPA (USA) – The Environmental Protection Agency regulates chemical manufacturing under the Clean Air Act, Clean Water Act, and Resource Conservation and Recovery Act (RCRA). Facilities must file hazard reports, manage waste streams, and maintain emission records.

OSHA (USA) – Occupational Safety and Health Administration requires hazard communication, training, and incident reporting for employees exposed to hazardous chemicals.

Dynamics 365 Finance & Operations integrates hazard tracking into inventory management:

• Item hazard classification: Flag raw materials and finished products as hazardous; store GHS (Globally Harmonized System) classification, flash point, and toxicity data
• Safety data sheet (SDS) management: Attach and version control SDS documents; track expiration and required updates
• Batch-level hazard tracking: Record hazard properties for specific batches (e.g., this batch of solvent contains 5 ppm residual monomer)
• Shipping & compliance: When an order ships, the system validates hazmat classification, packaging requirements, and labeling
• Waste stream tracking: Monitor disposal of off-spec batches, solvents, and by-products to ensure RCRA compliance
• Audit trails: All hazard data changes are logged with user, date, and reason – essential for regulatory audits

Integration with a dedicated EHS (Environmental, Health, and Safety) system – such as Intelex or Sphera – amplifies Dynamics 365’s capabilities. The ERP system becomes the master for material and batch hazard data, feeding compliance workflows in the EHS platform.

Quality Control and Testing Workflows

In chemical manufacturing, nearly every batch undergoes testing before release. A paint manufacturer tests viscosity, color, gloss, and cure time. A chemical intermediate supplier tests purity, water content, and acid number. Testing results determine whether a batch is approved for sale, reworked, or scrapped.

Dynamics 365 Finance & Operations includes Quality Management functionality:

• Quality orders: Automatically generated when a batch is produced; linked to the production order
• Test specifications: Define which tests apply to which products and materials; specify acceptance criteria (min/max values or categorical pass/fail)
• Test results recording: Lab personnel enter measurements; system validates against specification limits
• Conditional release: If results fall outside spec but within tolerance, QA can release with conditional approval (e.g., customer accepts off-color paint at discount)
• Hold & disposition: Failed batches are held; QA assigns disposition (scrap, rework, return to supplier, alternative use)

For advanced analytics, integrate with Statistical Process Control (SPC) tools. Plot test trends over time; detect drift toward specification limits; trigger corrective action before batches fail. This proactive approach reduces scrap and rework costs significantly.

Batch Record Generation and Audit Trails

In pharmaceutical manufacturing, FDA 21 CFR Part 11 requires electronic batch records (eBRs) that are legally equivalent to paper records. In chemical manufacturing, REACH and EPA audits demand complete documentation of what was produced, by whom, when, and how it performed. Dynamics 365 provides the foundation, but implementation often requires third-party ISV solutions.

Batch record components:

Component	Captured In
Formula & ingredients used	Production order & formula lines
Lot/batch numbers of raw materials	Inventory transactions with batch tracking
Equipment used & dates/times	Resource scheduling or manual entry
Personnel & approvals	Workflow history, audit logs
In-process measurements (temperature, pressure, pH)	Manual entry or sensor integration
Quality test results	Quality management module
Deviations & corrections	Incident management or custom module
Final batch disposition	Inventory release, scrap, or hold

Dynamics 365 captures much of this natively, but chemical manufacturers typically implement an ISV solution like Insight Works xRx (for eBR) or Progressus Pharma Solutions to format and digitally sign batch records according to regulatory standards. These tools extract data from Dynamics 365, assemble it into a regulated eBR document, enforce electronic signatures, and maintain an immutable archive.

Audit trail integrity is enforced at the database level in Dynamics 365: every data change is logged with a timestamp, user ID, and old/new value. This immutability is critical for regulatory compliance.

Business Central vs. Finance & Operations for Chemical Manufacturers

Choosing between Dynamics 365 Business Central and Finance & Operations is a strategic decision for chemical manufacturers.

Capability	Business Central	Finance & Operations
Process manufacturing module	No	Yes
Potency tracking	No	Yes
Formula versioning	Limited (via assembly BOMs)	Full version control with effective dates
Batch attributes	No	Yes
Quality management	Basic	Advanced (test specs, SPC integration)
Multi-site batch reporting	Limited	Consolidated views across sites
Regulatory compliance tools	Minimal; rely on third-party	Built-in audit trails; ISV integrations available
Cost per user/month	$70–$150 (Team Member licensing available)	$165–$180 (plus activity-based licensing)

Choose Business Central if:

• You manufacture simple products with straightforward formulas
• Regulatory requirements are light (no FDA, REACH, or EPA oversight)
• You have fewer than 10 production SKUs and limited batch tracking needs
• You want to minimize licensing and implementation costs

Choose Finance & Operations if:

• You manage complex formulas with potency, by-products, or catch-weight products
• You operate in regulated industries (pharma, fine chemicals, specialty coatings)
• You require comprehensive batch record capability and audit trail depth
• You operate multiple manufacturing sites with centralized formula governance
• You need advanced quality management and SPC integration

Most mid-to-large chemical manufacturers choose Finance & Operations because the process manufacturing and quality capabilities are essential for competitiveness and compliance.

Frequently Asked Questions

Q: Can Business Central handle catch-weight products?
A: Business Central can store catch-weight variance at the item level, but lacks potency-based scaling and advanced batch attribute tracking. For chemical manufacturers managing potency-adjusted ingredients or multiple batch attributes, Finance & Operations is required.

Q: How do I integrate real-time sensor data (temperature, pressure) into production orders?
A: Dynamics 365 does not natively ingest sensor data. Common approaches: (1) IoT Hub integration via Power Platform, capturing sensor readings and writing them to a custom table; (2) MES (Manufacturing Execution System) integration, where the MES records process conditions and the ERP imports batch-level summaries; (3) third-party API connectors (Insight Works, Dassault Systèmes 3DEXPERIENCE) that bridge sensors and the ERP.

Q: What is the difference between a formula and a recipe?
A: In Dynamics 365 terminology, a formula is the ERP object defining ingredients and quantities. A recipe is a broader concept that may include processing instructions, equipment, temperature profiles, and time sequencing. Formulas are ERP data; recipes are typically documented in MES or quality systems.

Q: Can I version control formulas and track which version was used in each batch?
A: Yes, Finance & Operations supports formula versioning with start and end dates. When you create a production order, the system defaults to the active formula version as of the order date. The batch record links to the specific formula version used, enabling full traceability.

Q: How do I handle waste & scrap in chemical manufacturing?
A: Define waste and scrap items in the item master; include them in formulas as planned by-products or loss percentages. When a batch is produced, the system accounts for both good output and scrap in inventory and costing. You can also define a scrap percentage on production order lines to adjust expected good output.

Q: Is Dynamics 365 suitable for continuous manufacturing (e.g., a paint mixing line running 24/7)?
A: Dynamics 365 Finance & Operations includes a continuous flow production type in addition to batch. However, most chemical manufacturers use batch-oriented production orders even for high-volume lines; they simply run shorter batch cycles (e.g., 2-hour batches instead of daily batches). For true continuous production with real-time sensor integration, a dedicated MES (Wonderware, Invensys) is often paired with Dynamics 365 for costing and compliance tracking.

Q: What ISV solutions complement Dynamics 365 for chemical manufacturers?
A: Insight Works offers xRx for eBR and quality; Progressus Pharma provides batch record and deviation management; Aptean TraceLink handles supply chain traceability; Augmento Labs offers AI-driven quality prediction. Most enterprise implementations combine Dynamics 365 with at least one ISV layer.

Methodology

Dataset: This guide synthesizes insights from Dynamics 365 product documentation (Business Central and Finance & Operations release notes through March 2026), ISV partner case studies (Insight Works, Progressus, Aptean), regulatory guidance from the FDA and ECHA (European Chemicals Agency), and interviews with five Dynamics 365 implementation partners specializing in chemical and pharmaceutical manufacturing.

Analytical approach: We structured the guide around the five core challenges faced by chemical manufacturers: (1) formula management, (2) batch quality and testing, (3) regulatory compliance, (4) by-product and co-product handling, and (5) multi-site operations. For each challenge, we documented the Dynamics 365 capabilities, limitations, and ISV extension points.

Limitations: This guide covers general-purpose Dynamics 365 capabilities as of March 2026. Highly specialized use cases (e.g., semiconductor chemical manufacturing, nuclear materials processing) may require custom development or dedicated ISV solutions not covered here. Implementation timelines and costs vary significantly based on formula complexity, regulatory scope, and legacy system integrations.

Data currency: All product capabilities and pricing reflect Dynamics 365 as of March 2026. ISV solutions and regulatory frameworks are accurate as of the same date; regulatory updates are published continuously, and implementation partners should verify current guidance with regulatory bodies.