AI, in your work.

Three improvements to an existing foundation

Microsoft lists three subcontracting improvements as generally available in the BC29 release notes: carrying instructions into purchase orders, simplifying setup, and using inventory put-aways and picks.

The 28.3 release notes already listed subcontracting capabilities as generally available. BC29 therefore extends an existing workflow; presenting the entire process as new would misrepresent this update's scope.

The extended capabilities belong to the Microsoft-published Subcontracting extension, which must be installed. Manufacturing is part of the Premium experience; selecting that experience does not assign licenses. Assessing availability for a particular company requires checking its version, application, license and permissions.

The assisted setup guide provides configuration guidance, but does not verify that every vendor, location, price, production BOM or routing is ready for use.

Materials: three distinct workflows

The component documentation distinguishes three supply methods. The final column contains Nexo's proposed checks for preparing a functional validation.

Instructions that accompany the purchase

Operation comments become zero-quantity text lines on the purchase order, whether created from the production order or the subcontracting worksheet. This behavior is described in the ordering guide.

Routing attachments reach the purchase line when Document Flow Production and Document Flow Purchase are enabled. Files added manually to the production order line do not follow that path. Microsoft explains these conditions in its attachment setup guidance.

As a proposed check, review the document and files the vendor will receive: current specification, drawing revision and acceptance criteria. The presence of a comment or attachment does not establish that its technical content is correct.

Receipt and work in progress have different limits

At receipt, an intermediate operation records capacity; the final operation also records output. Serial or lot tracking applies to final-operation output, not intermediate operations. The receipt guidance distinguishes these cases.

Work-in-progress transfers—WIP—receive different treatment: quantities are recorded in a dedicated ledger, without item, value or warehouse entries. Their lines support neither serial nor lot numbers. These restrictions appear in the WIP transfer documentation.

That guide also recommends transfer routes with an in-transit code between warehouse and subcontractor locations. Direct transfers have restrictions depending on movement direction and warehouse configuration. The proposed validation should cover material returning as well as being sent out.

Prices and additional charges

Prices consider vendor, item, work center, dates and quantity, among other criteria. Selection uses the highest qualifying minimum-quantity tier, without guaranteeing the lowest price. A minimum amount can increase the applied unit cost. Microsoft explains these rules in its pricing guide.

Transport or packaging costs can be assigned as item charges to subcontracting receipts. These charges link to capacity ledger entries and the production order, according to the additional-cost documentation.

The service must be invoiced from the subcontracting order itself, without retrieving its receipts on a separate invoice. This documented restriction should be considered when designing the administrative workflow.

Fictional example: external machining of 60 parts

Imagine a company commissioning a workshop to perform a machining operation for an order of 60 parts. The following workflow is Nexo's proposed test scenario, with no associated implementation results.

• Before shipment, identify which components will be transferred, which are held on consignment and which the workshop supplies. Record expected quantities at each location.
• When preparing the purchase, check the instructions and drawing that will accompany the order, together with the price and any minimum amount.
• Test a delivery of 58 parts with two outstanding. Check which quantities and documents remain open, distinguishing receipt of an intermediate operation from the final operation.
• Before closing, reconcile materials, consumption, receipts, the service invoice and additional charges. Also test the return of unused components.

Nexo's interpretation

The practical value of these improvements lies in connecting documentation, movements and receipt within the same external operation. For consultants and manufacturing leads, validation should assess the consistency of the complete workflow: where material is located, which instructions the vendor receives and what is recorded when it returns. Documentation establishes features and restrictions; each implementation's results require testing with its own configuration and exceptions.