Our Company has a unique requirement where we need to order an item in a KIT but we are receiving it's component for Example :-
KIT ITEM Number = CON-KIT-100
Components included in this kit are as below,
CON-ZEA-101 = 2 Qty
CON-ZEA-102 = 2 Qty
We are receiving the invoice from the vendor for the KIT that we order.
I would like to know how to Post an Invoice against this and also we are currently using Invoice Capture for all kind of Invoices so how can we use Invoice Capture for this kind of invoice to be process automatically.
Good morning, afternoon, or evening depending on your location! When dealing with a kit item on a purchase order where you receive an invoice for the kit (even though the components are delivered), the challenge is to have Dynamics 365 Finance and Supply Chain post a vendor invoice against the kit header rather than trying to “explode” the kit’s bill of materials into individual components. This is particularly important when you want to use Invoice Capture to process the vendor’s invoice automatically. Below are some considerations and steps that can help you achieve a solution: 1. Configure Your Kit Item for Kit-Based Invoicing
Kit Setup in Product Information: Ensure that your kit item (‑CON‑KIT‑100) is defined as a kit in the product master and that its invoicing parameters are set to “invoice as a kit” rather than having the system automatically explode the kit into its components. Many organizations have a BOM for kit explosion in production scenarios, but for purchasing, you may prefer the kit to be treated as a single unit.
Purchase Order Line Settings for Kits: When you create the purchase order, verify that the line is flagged as a kit item. This flag tells the system that the pricing and invoicing should remain at the kit level even if internally the kit is composed of components. Check that you’ve configured the item and purchasing parameters accordingly.
2. Mapping Invoices with Invoice Capture
Invoice Capture Mapping Rules: In the Invoice Capture solution you already use for other invoices, verify that the mapping rules are configured to match vendor invoice lines to purchase order lines based on the kit item number. Since the vendor’s invoice image will reference the kit (CON‑KIT‑100) and not list the individual components, ensure that the Invoice Capture configuration isn’t expecting a component-level match.
Custom Field Mapping (if needed): In some cases, you might need to extend or adjust the mapping logic (whether in the prebuilt model configuration or via an extension) so that the kit invoice data is correctly interpreted as relating to the kit purchase order line. This might involve adding conditions for kit items or using custom fields to identify them.
3. Automating the Process via Invoice Capture
Automated Vendor Invoice Posting: Once the kit item and mapping have been configured, when an invoice is captured (via OCR and the AI model), Invoice Capture should create a vendor invoice that matches the kit purchase order line. The vendor invoice will then post the invoice at the kit level, even though the physical receipt process later deals with component specifics.
Review the Routing of the Invoice: Ensure that your Invoice Capture solution’s processing rules for Purchase Order (PO) invoices are aligned with your kit ordering process. Sometimes you need to adjust the derivation rules to bypass any default behavior that might “explode” the kit when the invoice is imported.
4. When Customization is Required
Custom X++ Code or Extension: If out-of-the-box configuration and mapping do not suffice—especially if the system is still attempting to process the kit by its components—you may need to implement a small customization in the vendor invoice posting process.
This extension can detect that the item is a kit and override the standard pooling logic so that the invoice posts only against the kit header.
Custom logic can also be introduced in your Invoice Capture pipeline to flag kit transactions and treat them accordingly.
Testing in a Sandbox: Any customization or configuration change should first be validated in a non-production environment. Verify that the Invoice Capture process, when a kit-based invoice comes in, creates a vendor invoice that matches correctly against the purchase order kit line.
Summary
Post Invoice at the Kit Level: Configure your kit item and purchase order so that the kit is invoiced as a whole, and the kit’s BOM does not automatically trigger a component-level explosion during invoice posting.
Adjust Invoice Capture Settings: Ensure your Invoice Capture mapping and processing rules are set to recognize and process kit items properly. You might need to adjust mappings or add a conditional check specific to kit invoices.
Use Customization if Needed: If system standard behavior cannot meet your requirement, consider implementing a custom extension using X++ to finalize the invoice posting procedure for kit-based invoices.
By aligning your product and purchasing configuration along with your Invoice Capture settings, you should be able to automatically process the vendor invoice for a kit without having to capture each component separately. Please note: I teamed up with CoPilot AI to research and craft the best response to your question! Hope this helps some!
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
6
Share
Report
All responses (
Answers (
