AL Processing Charge

AL Processing Charge lets you sell items that go through a light pre-delivery processing-sharpening, coating, grinding, finishing - and have the revenue of the processing tracked separately from the revenue of the item itself, automatically, inside Microsoft Dynamics 365 Business Central. The processing is declared on the sales line; on release of the order a matching Item Charge line is generated and assigned automatically, so item revenue and processing revenue stay distinct in posting, reporting and margin analysis - with no SKU duplication and no custom accounting code.

Key capabilities

• Configurable processing types - a dedicated setup list (sharpening, coating, grinding, finishing, ...), each bound to a standard Business Central Item Charge that governs posting groups and accounting.
• Sales-line tagging with default price - pick a processing type on any Item line (quote, order, invoice, blanket, return, credit memo); the configured unit price is proposed and stays overridable line by line, and can also be fed from a sales price list.
• Automatic Item Charge on release - the matching charge sales line is generated, quantified and assigned to its item line automatically; item revenue and processing revenue stay on separate lines.
• Synchronized, self-healing lifecycle - the charge line follows the item line through quantity-to-ship, warehouse shipment and partial invoicing, and re-aligns or removes itself when the processing type changes before posting.
• Item defaults - an item can carry a default processing type, filled in automatically when it is sold.
• Optional production integration - each setup can reference a Routing and Production BOM and request self-consumption of the output item; when a sales order is planned, AL Processing Charge dispatches one Project Order per distinct processing type plus an Item Order per plain line, injecting the configured routing and components.

Why it matters

• Clear revenue separation - pure margin analysis of each processing operation, independent of the item's own margin.
• No SKU explosion - the same item code is used before and after processing; no parallel item hierarchy to maintain.
• Standard accounting - everything posts through the standard Item Charge engine: no custom G/L logic, nothing new to audit.
• Less manual effort and fewer errors - the charge line is generated and re-aligned by the system; users only choose the processing type on the line.

Built for

SMEs and mid-market manufacturers, distributors and trade-services companies - mechanical workshops, tooling and abrasives, precision finishing, surface treatment, custom packaging and any "buy-and-rework-then-sell" model - that resell items after a light pre-delivery operation and need the real marginality of every processing, a clean item master, and standard Business Central accounting ready for audit.

What makes AL Processing Charge different

• Built on the standard Item Charge engine - consultants already know where the postings land and how to reconcile them; there is no parallel posting framework to learn or to audit.
• One item code, many processings - the processing is a property of the sales line, not of the item; adding a new type is a configuration change, never an item-master change.
• Production integration is opt-in - pure distribution uses the revenue-tracking side alone; manufacturers get the dispatch into Project Orders (one per processing type) without rewriting planning logic.
• Quote-to-credit coverage out of the box - the processing follows the business document everywhere, with consistent UX on each subform.

How it works

On a sales Item line you pick a processing type; its unit price is proposed from the setup (or fed from a sales price list). On Release, AL Processing Charge creates and assigns the matching Item Charge line - item revenue on the item line, processing revenue on the charge line. If the type references a routing, planning the order generates one Project Order per processing type with the routing (and optional Production BOM / self-consumption) already injected; the linked production status is shown on a factbox beside the sales line.

Requirements

• Microsoft Dynamics 365 Business Central online (SaaS), version 28.0 or higher.
• Languages - English (en-US) and Italian (it-IT); more on request.
• Dependencies (installed automatically) - AL Foundation App, AL License and Trial Management, AL Message Passing and AL Role Center, all from AppLibra.