* Manufacturing Cloud & Rebate Mgmt *

Hi @Brijesh Tekrawala

• Manual/Excel still common, especially where plants ran separate AP pre-consolidation. No audit trail, biggest pain point.
• Homegrown Flow + Apex - Flow for routing, Apex for 3-way match logic. Breaks down on: plant-specific approval matrices (hardcoded → brittle), no native OCR (bolt-on needed), multi-currency/GL mapping gets messy.
• AppExchange AP tools (your category) - wins when: multiple ERPs across plants, need line-level tolerance matching, want standard AP reporting out of the box.
• Middleware + ERP-as-source-of-truth - larger manufacturers often let SAP/NetSuite do the matching, sync status to Salesforce for visibility only.

Universal pain points regardless of approach:

• Plant-level approval matrices as hardcoded logic vs. data-driven config
• Partial receipts/partial invoicing against a PO
• Vendor invoice format variance across plants
• GL/cost center mapping drift when a plant's chart of accounts changes

 I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

You may also want to explore GLOVIA.  

Based on the requirements you've mentioned, it's one of the strongest AppExchange solutions available. While it is lighter on the financial capabilities side however it offers robust functionality for inventory management, order management, warehouse management (WMS), and procurement.  

Additionally, it is a 100% Salesforce-native solution, which makes implementation and integration within the Salesforce ecosystem much simpler. 

I ended up creating some customization for this. I created a custom object called "Large Sales Agreement," and a flow screen tied to an action on the Sales Agreement called "Extend Sales Agreement." 

When selected, I collect a little information from the user, but it works very similar to Renewing, except my flow creates a Large Sales Agreement record, and adds the two Sales Agreements together as child records to it. 

Then I displayed a flow screen component on that Sales Agreement that displays a datatable of the two Sales Agreements and their totals, allowing my user to see the total Sales Agreement value of any Sales Agreements tied to my Large Sales Agreement. 

If the user chooses to extend again, then the third Sales Agreement gets added and so on.

You can leverage Action Plans and Assessment Tasks to manage and capture inspection data. Action Plans can be used to capture high-level inspection information, while Assessment Tasks

can represent the individual activities or step-by-step checks performed during the inspection process. 

Additionally, if inspections are executed as part of a planned onsite or remote engagement, Visits can be utilized to align the inspection with an overall visit plan and provide better scheduling, tracking, and execution visibility.

Hi @Jerome Devemy

The claim object in Manufacturing Cloud is primarily used for warranty claims. It represents a warranty claim submitted by a partner to a manufacturer or a supplier recovery claim submitted by the manufacturer to a supplier.  

This object can also be configured to allow customers to submit claims directly via an Experience Cloud site. This involves setting up related objects like Claim, Claim Item, Claim Coverage, Claim Coverage Payment Details, and Claim Participant. Manufacturers can also create claims on behalf of partners if needed. 

For more details, refer: 

Capture Warranty Claims

The "Partner Fund Claim" is a separate concept used in the context of Market Development Funds (MDF). It allows partners to submit claims for reimbursement of marketing expenses or other fund-related activities.  

Partner Fund Claims are managed through the Partner Central Experience Cloud site. Channel Account Managers (CAMs) or financial departments can approve and reimburse these claims.

For more details, refer: Configure Partner Fund Claims

Key Differences:

• The Claim Object is used for warranty or supplier recovery claims, while the Partner Fund Claim is specific to Market Development Funds and partner reimbursements.
• Both can be configured for use in Experience Cloud, but their purposes and workflows differ.

Hope this helps. Thanks!