Introduction In Purchase & trade agreements in D365 – Part 1 & 2 blog we have gone through overview of Purchase & trade agreements in D365 & how to setup different types of Purchase agreements in D365. In this blog will go through how to setup Trade agreement for Purchase price & how to setup different types of Trade agreement of line discount in D365. i.e. Fixed amount, percentage discount or for quantity range. Problem statement – In this scenario we need to setup different types of trade agreements for vendor. Solution steps – 1 – Will setup trade agreement for purchase price 1.1 Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names 1.2 New -> Name -> Pur Price -> Description -> Purchase price Trade agreement -> Relation -> Price (purch.) -> Save. 1.3 Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount 1.4 Enable all parameters for Price. Item parameter Yes for Vendor means It is to enable price for specific vendor for specific Item. Item parameter Yes for Vendor group means if price is same for item for group of suppliers (based on vendor group) then need to enable this parameter. Item parameter Yes for All vendors means if item has same prices for all suppliers then need to enable this parameter. 1.5 Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals 1.6 Create new journal – Name -> Pur price (Created in step 1.2) -> click on Lines to add details 1.7 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000009 -> Unit -> Pcs -> Amount in currency -> 3000 -> Save. 1.8 Validate -> Validate all lines 1.9 Post. 1.10 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000009). Purchase price will be reflected as per set in Trade agreement. 2 – Will setup trade agreement for Line discount for Fixed amount 2.1 Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names 2.2 New -> Name -> Pur Disc -> Description -> Purchase discount -> Relation -> Line disc. (purch.) -> Save. 2.3 Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount Enable all parameters for Price. Item parameter Yes for Vendor means It is to enable price for specific vendor for specific Item. Item parameter Yes for Vendor group means if price is same for item for group of suppliers (based on vendor group) then need to enable this parameter. Item parameter Yes for All vendors means if item has same prices for all suppliers, then need to enable this parameter. 2.4 Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 2.2) -> click on Lines to add details 2.5 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000009 -> Unit -> Pcs -> Amount in currency -> 100 -> Save. 2.6 Then validate & post the journal. 2.7 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000009) discount will be reflected as defined in Trade agreement. 3 – Will setup trade agreement for Line discount for discount % 3.1 As we have created already journal name & enabled parameters in solution 2, we can directly create journal. Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 2.2) -> click on Lines to add details 3.2 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000010 -> Unit -> Pcs -> Discount percentage 1 -> 10 -> Save. Then validate & post. 3.3 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000010) discount % will be reflected as defined in Trade agreement. 3.4 There is one more field available at Trade journal Discount percentage 2. Define Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000011 -> Unit -> Pcs -> Discount percentage 1 -> 10 -> Discount percentage 2 -> 5 -> Save. Then validate & post. If both Discount percentage 1 & 2 is defined, then on Purchase value 1st discount in field 1 is applied & then on that value % of field 2 is applied. i.e. if amount 100 & disc 1 -10 & disc 2 – 5 then final % will be 100*.1=90*.05=85.5 so total discount will be 14.5%) 3.5 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000011) discount will be reflected as defined in Trade agreement. In this blog we completed how to setup Trade agreement for Purchase price & line discount fixed amount & discount percentage. In next blog (Part 4) will cover setup of trade agreement line discount for quantity range & next flag. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction How effectively are you tracking your company’s environmental impact? As sustainability becomes a growing priority, businesses need the right tools to monitor and manage their emissions. Dynamics 365 Business Central offers powerful features like the Chart of Sustainability Accounts (CoSA) and the Sustainability Ledger to help organizations streamline their sustainability efforts. In this guide, we’ll take a deep dive into how you can leverage these tools to enhance your environmental performance. What is the Chart of Sustainability Accounts (CoSA)? The Chart of Sustainability Accounts (CoSA) in Dynamics 365 Business Central is a specialized framework designed to manage emissions data, similar to a traditional chart of accounts but tailored for sustainability metrics. Key Features: Question: Have you already identified the key areas of your business that contribute to emissions? Think about where CoSA can help you focus on reducing your environmental impact. Managing Sustainability Accounts – Adding and Modifying Accounts Tip: Be cautious when deleting accounts. If they have existing ledger entries, you’ll need to resolve those before deletion to maintain data integrity. Interactive Element: Understanding Account Categories – Purpose and Setup Pro Tip: If your organization needs specific calculations, you can create custom formulas. This ensures that emissions are tracked accurately, even for complex or unique activities. Calculation Foundations The system uses different methods to calculate emissions based on the emission type and category. Here are some examples: Interactive Question: Have you considered which scope of emissions contributes the most to your environmental footprint? Scope 1, 2, or 3? Account Subcategories – Purpose and Setup Did You Know?: You can also set up renewable energy-related subcategories. By marking the Renewable Energy field, you can easily track the impact of renewable energy use in your operations. Interactive Element: Have you considered using renewable energy in your business? Start tracking it separately in CoSA to measure its impact on your emissions. Sustainability Ledger Entries – Purpose and Management Correcting Errors Once data is posted, it cannot be deleted. To correct errors, simply post a reverse transaction with the same details but a negative amount. Interactive Tip: Worried about data entry mistakes? Start with a test entry in the ledger to familiarize yourself with the system before posting live data. Conclusion The Chart of Sustainability Accounts and Sustainability Ledger in Dynamics 365 Business Central are invaluable tools for businesses aiming to reduce their environmental impact. By properly configuring CoSA, setting up categories and subcategories, and using the sustainability ledger, you can gain deeper insights into your emissions and improve your sustainability practices. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Managing financial transactions accurately and efficiently is crucial for any growing business. The process of ledger settlements can be time-consuming and prone to errors when done manually. To address this, Microsoft Dynamics 365 Finance version 10.0.31 introduces the ability to automate ledger settlements, helping businesses streamline their financial processes. In this article, we’ll walk you through the steps needed to enable and optimize automatic ledger settlements in Dynamics 365, so your organization can save time, reduce errors, and improve financial reporting. Automating ledger settlements is a significant improvement over the manual process. The automated process works by comparing debit and credit transactions in your general ledger. It automatically matches transactions with identical accounting currency amounts, simplifying reconciliation efforts. However, it’s important to note that this feature does not support partial matching of transactions. Before enabling the Automate Ledger Settlements feature, it’s crucial to first activate the Awareness feature between Ledger Settlement and Year-end Close. This step ensures the process runs smoothly without impacting your year-end financial closing. Steps to Enable Automatic Ledger Settlements Step 1: Identify Relevant Primary Accounts Step 2: Create a Rule for Process Automation Step 3: Set up Criteria for Automation Step 4: Manage the Created Rule Once the rule has been created, you can view or modify it at any time. This flexibility allows you to adapt the automation process to changing business needs. Step 5: Verify the Automation Batch Job Ensure that the automation batch job is running correctly. Go to System Administration > Inquiries > Batch Jobs to check the execution status. Step 6: View Scheduled Executions and Results You can monitor the status of your scheduled automations and the results of settled transactions for full visibility into your financial processes. Step 7: Access Settled Transactions To view finalized ledger settlements, navigate to General Ledger > Periodic Tasks > Ledger Settlements. Conclusion By automating the ledger settlement process in Dynamics 365 Finance, businesses can reduce manual effort, minimize errors, and optimize financial workflows. It’s essential to follow the steps outlined above to ensure smooth implementation and operation. By automating your ledger settlements, your organization can save time and improve financial reporting accuracy. Take the Next Step If your organization is looking to optimize financial workflows, start by automating your ledger settlements today. For more detailed assistance or to explore additional financial automation features, feel free to contact us.

Introduction Are you looking to enhance your business’s sustainability efforts? Dynamics 365 Business Central’s Sustainability Management feature helps businesses monitor, manage, and report their environmental impact, with a focus on greenhouse gas (GHG) emissions. With this tool, you can track your emissions across various scopes to align with your company’s sustainability goals. But how can you ensure this tool is properly configured to maximize its benefits for your organization? Key Features and Capabilities 1. Emission Tracking Imagine being able to track emissions across multiple dimensions. Here’s how the tool categorizes them: Tip: Start by listing all the potential sources of emissions in your business. Can you think of ways to reduce emissions in Scope 1 or 2 right now? 2. Setup and Configuration Setting up this feature correctly is key to getting meaningful data. Pro Tip: If you’re unsure where to begin with emission factors, consider consulting with a sustainability expert to ensure you’re using accurate numbers. 3. Data Management Question: Which areas of your business could benefit most from detailed emission tracking—your supply chain, your operations, or perhaps both? 4. Reporting and Insights Call to Action: Ready to see how these reports can help streamline your sustainability goals? Schedule a demo today to explore the full reporting capabilities! Benefits Still wondering if this feature is right for your business? Here’s what you stand to gain: Example: One of our clients reduced their Scope 2 emissions by 15% after better understanding their energy consumption patterns using Business Central’s data management features. Step-by-Step Setup Guide To configure the Sustainability module in Dynamics 365 Business Central, follow these steps carefully. Don’t worry if you’re not familiar with all the terms—we’ll guide you through each section: 1. General Fast-Tab Configuration Tip: Choosing the right level of precision can make a big difference in how your data is interpreted. 2. Calculations Fast-Tab Configuration Pro Tip: If your emissions are mostly related to transportation, focus on fine-tuning the distance and fuel data. 3. Reporting Fast-Tab Configuration (Note: This section is for future reporting capabilities) Did you know? Although this feature isn’t available in version 24.0, it will be in future updates. Stay ahead by configuring the settings now! Conclusion The Sustainability Management feature in Dynamics 365 Business Central provides critical tools for managing your environmental footprint. By configuring units of measure, decimal places, and reporting parameters, you can tailor the system to meet your business’s sustainability goals. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Seamless integration between systems is essential for efficient operations and data accuracy. One of the common integration challenges is syncing data between Customer Relationship Management (CRM) systems and Finance and Operations (FNO) systems. Traditionally, dual write has been a solution for this integration, but it comes with limitations. In this blog, we’ll explore a real-life business use case where we replace dual write with Azure Logic Apps to enable real-time data synchronization between CRM and FNO systems. Understanding Dual-Write Dual write is a framework provided by Microsoft that ensures data consistency between Dynamics 365 Finance and Operations (FNO) and Dynamics 365 Customer Engagement (CRM) applications. It facilitates real-time and bi-directional data synchronization, maintaining records of table and field mappings between FNO and CRM. This ensures that any change made in one system is reflected in the other, providing a unified experience across the enterprise. However, dual-write has its limitations, such as complex setup, limited customization options, and potential performance issues in high-transaction environments. These limitations prompt businesses to seek more flexible and scalable integration solutions. The Business Use Case: Replacing Dual-Write with Azure Logic Apps Scenario: A manufacturing company uses Dynamics 365 CRM to manage customer interactions and Dynamics 365 FNO to handle finance and operations. The company relies on dual write to keep customer data synchronized between the two systems. However, they face issues with the dual-write setup, including occasional synchronization lags and difficulties in customizing data mappings. To overcome these challenges, they decide to implement Azure Logic Apps for real-time data synchronization between CRM and FNO. Objective: Create a Logic App that enables real-time data synchronization between CRM and FNO, replacing the existing dual-write setup. This Logic App will ensure that any changes in customer data in CRM are immediately reflected in FNO and vice versa, without the complexities and limitations of dual write. Steps to Implement the Solution Benefits of Using Azure Logic Apps Conclusion By replacing dual write with Azure Logic Apps, the manufacturing company can achieve a more reliable and customizable integration between their CRM and FNO systems. This solution not only enhances data consistency and real-time synchronization but also provides the flexibility to adapt to future business requirements. Azure Logic Apps empower businesses to streamline their operations, improve data accuracy, and ultimately deliver better customer experiences. In our next blog, we will explore in detail how this business use case can be fully implemented using Azure Logic Apps. Stay tuned for a step-by-step guide on setting up the Logic App, configuring connectors, and ensuring seamless real-time data synchronization between CRM and FNO. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Purchase & trade agreements in D365 – Part 1 blog we have gone through overview of Purchase & trade agreements in D365 & how to setup different types of Purchase agreements in D365. In this blog will go through how to setup purchase agreement of type Product category value commitment & Value commitment. To give brief overview of Purchase & trade agreements in D365, for those who have not gone through part 1 of this blog. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. & Trade agreement can be used to create discounts generally for short period for specific vendor or vendor group. In D365 there are different types of Purchase agreement & trade agreements. Below are different types of Purchase agreements based on commitment in D365 – Product category value commitment is setup when there is commitment to buy fixed amount of specific category of goods from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy Travel luggage bags category SKUs from vendor A worth 10million over next 1 year then vendor will offer 20% discount for same. Value commitment when there is commitment to buy fixed amount from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy from vendor A worth 15million over next 1 year then vendor will offer 20% discount for same. Below are different types of Trade agreements based on relation in D365 – Problem statement – In this scenario we need to setup purchase agreement of type Product category value commitment & Value commitment for vendor. Solution steps – 1 – Will create purchase agreement for Product category value commitment 1.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements 1.2 Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000002) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product category value commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 1.3 Fill the respective details of Item/Category name – Spinner, Net amount – 100000, Discount percent – 15 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 1.4 Then create new Purchase order, select Purchase agreement to link 1.5 Add any Item with category mentioned in purchase agreement, in this case it is “Spinner” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 1.6 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.7 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Value commitment 2.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements -> Click on New -> Vendor account ->  Select respective vendor (In this case it is VEN-000005) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Value commitment -> Effective date ->  Select respective date (In this case it is 1 Aug 24) -> Expiration date ->  Select respective date (In this case it is 1 Aug 25) -> Ok 2.2 Fill the respective details of Item/Category name – can select highest category in this case it is Bags, Net amount – 500000, Discount percent – 20 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 2.3Then create new Purchase order, select Purchase agreement to link 2.4 Add any Item with category mentioned in purchase agreement in this case it is “Bag” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 2.5 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. In this blog we completed purchase agreement types. In next blog (Part 3) will cover setup of trade agreement. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction  In this blog post, I’ll walk you through the process of transforming JSON to JSON using Azure Logic Apps and the Liquid Template Language. This step-by-step guide will demonstrate how you can use Azure Integration Services to achieve your transformation goals.                                      What is Liquid Template Language?  The Liquid Template Language (commonly referred to as “Liquid”) is a flexible, open-source template language developed by Shopify. It is widely used to render dynamic content in platforms such as Shopify themes, Jekyll websites, and web applications. Liquid uses placeholders, loops, and conditional statements to pull dynamic data into a web template, making it an effective tool for JSON transformation.  Prerequisites  To complete this tutorial, you’ll need:  Sample Input JSON  We will use the following sample JSON file for this tutorial:  {    “FirstName”: “Deepak”,    “LastName”: “Ch”,    “Add1”: “T square, Saki Vihar Road, Andheri East”,    “Add2”: “Mumbai”,    “Landmark”: “Near Car Showroom”,    “PhoneNo1”: 9812727261,    “PhoneNo2”: 2121233322  }  Desired Output JSON  The client’s requirement is to transform the input JSON into the following format:  {    “Full Name”: “Deepak Ch”,    “Address”: “T square, Saki Vihar Road, Andheri East, Mumbai, Near Car Showroom”,    “Phone”: “9812727261, 2121233322”  }  Step-by-Step Guide –   Step 1: Create a Free Azure Integration Account  Step 2: Add the Liquid Template Map  Step 3: Create a Logic App  Step 4: Transform JSON to JSON using Liquid  Here’s the Liquid template used for this transformation:  {    “Full Name”: “{{content.FirstName}} {{content.LastName}}”,    “Address”: “{{content.Add1}}, {{content.Add2}}, {{content.Landmark}}”,    “Phone”: “{{content.PhoneNo1}}, {{content.PhoneNo2}}”  }      Step 5: Test with Postman  Final Output  The output JSON will be:  {    “Full Name”: “Deepak Ch”,    “Address”: “T square, Saki Vihar Road, Andheri East, Mumbai, Near Car Showroom”,    “Phone”: “9812727261, 2121233322”  }  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In today’s business environment, Companies must adhere to various financial reporting standards. These standards are essential for fostering investor confidence, ensuring regulatory compliance, and supporting international expansion. Depending on their operational scope, some organizations are required to comply with multiple reporting frameworks, often necessitating the maintenance of multiple books of accounts. Companies need to comply with Financial Reporting Standards – IFRS, UK GAAP, US GAAP, Ind AS, Local GAAP due to reasons like: Compliance with the reporting standards is mandatory for some companies while others may follow them as best practice. There can be scenarios where a company must maintain multiple books of accounts to comply with multiple reporting standards. Example: Company listed on multiple stock exchanges like Infosys, ICICI Bank, TCS (India and US stock Exchange) must prepare financial reports as per Ind AS and as per IFRS. Microsoft Dynamics 365 Finance has the capabilities to meet the financial reporting requirements. How D365 Finance supports Financial Reporting Standards: Thereby, a company can utilize D365 Finance to maintain separate books for Financial Reporting. Conclusion Compliance with various financial reporting standards is not just a regulatory necessity but also a best practice that can enhance investor confidence and facilitate global operations. Microsoft Dynamics 365 Finance simplifies this process by enabling organizations to maintain multiple charts of accounts, set up parallel posting layers, and customize financial reports to meet different regulatory standards. By leveraging the comprehensive capabilities of D365 Finance, businesses can efficiently manage their financial reporting requirements, ensuring compliance across multiple jurisdictions and fostering transparency in their financial operations. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Are You Quick Enough with Your Decision-Making? 73% of Businesses Say No. In today’s data-driven landscape, a whopping 73% of businesses confess they find it tough to make quick, informed decisions because their reporting tools are outdated or just not cutting it. Are you in the same boat? If yes, it might be time to rethink your strategy for gaining business insights. Meet Microsoft Dynamics 365 Business Central—a real game-changer for companies looking to turn their data into actionable insights. While many ERP systems come with basic reporting options, Business Central shines with its customizable reports that offer real-time data, greater flexibility, and predictive insights. In this blog, we’ll take a look at five standout reports in Business Central that not only provide essential insights but also empower your business to make quicker, smarter decisions. These reports are crafted to keep you ahead of the competition and help you hit your business targets—without the hassle of complicated customizations. Let’s jump in and see how these powerful reports can revolutionize your operations! 1. Dimension-Based Reporting: Custom Insights Without the Complexity Business Central makes that easy with dimension-based reporting. It allows you to slice and dice data across custom dimensions such as department, product line, project, or location. You don’t have to adjust your chart of accounts for every new need—you just define dimensions and filter reports accordingly. Imagine the insights: Want to know how profitable a particular product line is in a specific region? Or how a department is performing across multiple locations? With dimension-based reporting, you can quickly analyse performance across all these areas. 2. Account Schedules: Build Custom Financial Reports Without External Tools If financial reporting feels rigid or limited with your current system, then you’ll love Business Central’s Account Schedules. Picture this: You’re able to customize income statements, balance sheets, or cash flow reports to match your exact business needs. Whether you want to compare actuals vs. budgets by department or break down profitability by project, Account Schedules gives you the flexibility to design these reports yourself. 3. Seamless Integration with Power BI: Turn Data Into Visual Dashboards Are you tired of static reports that don’t tell the full story? Business Central’s seamless integration with Power BI allows you to transform raw data into rich, visual dashboards that offer deeper insights. You can create interactive, real-time dashboards that not only display your data but also allow you to drill down for detailed analysis. 4. Embedded Excel Integration: Collaborate and Update in Real-Time Do you find yourself constantly exporting data to Excel, only to struggle with re-importing it back into your system? Business Central solves that with its embedded Excel integration. Imagine this scenario: You export your financial data to Excel, update it with your team, and then push the updated data back into Business Central—with no data loss or formatting issues. The integration keeps all your financial and operational reports intact, so collaboration is seamless. 5. Cash Flow Forecasting with AI: Predict the Future of Your Finances How accurate are your cash flow forecasts? With Business Central, you get AI-driven cash flow forecasting that goes beyond simple historical analysis. The system uses machine learning to predict future cash flows based on past data, outstanding receivables, and planned expenses, giving you a clearer picture of your financial future. Ready to See These Reports in Action? These reports are just the beginning. With Microsoft Dynamics 365 Business Central, you have a powerful tool that helps you make smarter, quicker decisions and stay ahead of the competition. Interested in learning how Business Central can transform your reporting? Reach out to us today for a personalized demo or consultation at transform@cloudfronts.com, and let’s explore how we can tailor these reports to fit your business’s unique needs.

Introduction In many businesses purchase is common & important function. & for purchase department, agreement is important feature. In D365 we have different types of agreements. i.e. Purchase agreement & Trade agreement. Both agreements have its benefits. In this blog will go through overview of purchase & trade agreements in D365 & setup of Purchase agreement in D365 of type Product quantity commitment & Product value commitment. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. Whereas Trade agreement can be used to create discounts generally for short period for specific vendor or vendor group. In D365 there are different types of Purchase agreement & trade agreements. Below are different types of Purchase agreements based on commitment in D365: Product quantity commitment is setup when there is commitment to buy fixed quantity of item from specific vendor over fixed period, so vendor will provide special purchase price for that quantity over defined period. For example, purchaser have committed to buy 1000 quantity of 1 SKU of luggage bag from vendor A over next 1 year then vendor will offer special price of 2000 instead of original price of 3000. Product value commitment is setup when there is commitment to buy fixed amount of specific item from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy 1 SKU of luggage bag from vendor A worth 1million over next 1 year then vendor will offer 15% discount for same. Product category value commitment is setup when there is commitment to buy fixed amount of specific category of goods from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy Travel luggage bags category SKU’s from vendor A worth 10million over next 1 year then vendor will offer 20% discount for same. Value commitment when there is commitment to buy fixed amount from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy from vendor A worth 15million over next 1 year then vendor will offer 20% discount for same. Below are different types of Trade agreements based on relation in D365: Trade agreement for Purchase price is used to define purchase price of item from specific vendor or group of vendors. The price defined in trade agreement will be reflected in purchase order automatically. Trade agreement for Line discount for purchase is used to define discount on purchase price of item. can setup different types of discounts i.e. Fixed amount, percentage discount or for quantity range. Trade agreement for Multiline discount for purchase is also used define discount on purchase price of item but in multiline discount system will consider quantity of specified item available on multiple lines in purchase order to decide discount percentage. For example, If we have same range for line & multiline discount of 5% for 1-101 & 10% for 101-501. When Purchase order has 2(or multiple lines) of same item. i.e. 1st line has 50pcs & 2nd line has 70pcs. So, in case of Line discount each line will get discount of 5% even though total quantity is greater than 100. But in case of Multiline discount, discount applied will be 10% as total is greater than 100, as it considers total of multiple line. Trade agreement for Total discount for purchase is used to define discount percentage for total purchase order level & not at line level. Also note that, if both purchase agreement & trade agreement are defined for same combination of vendor & item, then Purchase agreement gets precedence / priority over trade agreement. Problem statement: In this scenario we need to setup Product quantity commitment & Product value commitment type of purchase agreement for vendor. Solution steps: 1 – Will create purchase agreement for Product quantity commitment 1.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements 1.2 Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product quantity commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 1.3 Fill the respective details of Item number – P-000003, Quantity – 1000, Unit price – 3000 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. 1.4 Confirm purchase agreement. 1.5 Now create new purchase order. Go to Procurement & sourcing -> All purchase orders 1.6 New -> Select Vendor -> Select above created Purchase agreement -> Ok. 1.7 Add Item mentioned in purchase agreement, in this case it is P-000003 & required Quantity 500 in purchase order, price will be automatically taken from purchase agreement. 1.8 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.9 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Product value commitment 2.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements -> Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product value commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 2.2 Fill the respective details of Item number – P-000003, Net amount – 50000, Discount percentage – 10 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link … Continue reading Understanding Purchase & trade agreements in D365 – Part 1 →