Prior to the Wave 1 2020 release, the allocation of charges capability was available only on the Purchasing side of F&O processes. In this blog, we’ll review the Current State process and share some exciting news about Future State process.
Did you know that Dynamics 365 for Finance and Operations offers certain pricing advantages to customers? Because not all organizations have enough users to qualify for reduced pricing structures and negotiations, the concept of agreements presents a more competitive market to mid- and small-sized companies. In today’s blog, we’ll explain how to use these agreements to leverage your loyalty and gain a competitive advantage.
When planned correctly, these agreements can positively influence buying power if categorized and combined with either quantity or similar product offerings. In both the Sales and marketing and Procurement and sourcing modules, agreements are offered to maintain a log and track transactions specific to any type of commitments made. And since these are offered on the Sales side and Purchase side, as shown below, you can use them not only for your customer base to potentially gain additional market share, but also for commitments you want to issue with your own suppliers!
Once a new agreement is started, you must select a classification, as shown below. As with other areas within Dynamics 365, these classifications are intended to allow you to group agreements together for reporting and analytics. You can choose whatever classifications you like, but here are a few recommendations:
Again, the classifications are limitless by design, to offer flexibility for all users.
After classifying your agreements, the next step is to define validity dates. When defining an Effective date and Expiration date, the agreement and any releases created in conjunction with a specific record are restricted to these dates. Unlike other dates within Dynamics 365, these dates offer a firm period in which purchase orders and sales orders can be issued. This can benefit either party in each transaction by ensuring no offer is extended further than desired.
Next, a Default commitment type must be selected. Each option is defined below, but generally speaking, an agreement needs to differentiate between value (price) and quantity.
Now that the prerequisites are selected, the lines can be defined as to what item(s), categories, or amounts should be considered against the defined commitment type. Various fields will be available upon selection of these types, but the required definition must be within each line.
In addition, within Line details, added functionality can be used to further control the limits within the agreement. Comparable to the dates, the optional elements below will hinder the flexibility among the value or quantity defined, which is inherent when left excluded.
The fulfillment for each agreement can likewise be viewed within the Line details. Ultimately, this is what drives the Fulfillment Report found within each module’s area page. The report can be filtered by commitment type, item, customer, vendor, etc., but the values reported are intended to provide a quick view into all these values.
With all required inputs entered, the agreement can then be confirmed to formalize into Dynamics 365 and create a journal that can be sent to the other party. This confirmation step is necessary because by default, agreements have a Status of On hold:
After confirming, you’ll have the option to either mark the agreement as effective or leave it On hold. Since approvals may need to be incorporated through workflows, effectivity may come later. However, once active, the agreement can be transacted upon as long as the validity period is current.
To maintain tracking and keep calculations related to the appropriate agreements, each release order must be created directly from the agreement. As released, they are transacted upon almost identically to standard sales and purchase orders, excluding the relationship that is held on the release to the commitment type. The added benefit of linking them occurs when releases are made or updated. The requirements from the agreement are cross-checked against the release order or changes; if they don’t align, an error and hard stop occurs.
Example 1: release order attempting to be made outside of validity dates (note error at top of screen).
Example 2: Quantity change exceeds max of agreement (note dialog box).
In summary, agreements offer additional functionality for many users, customers, and vendors alike. Loyalty can be leveraged for smaller organizations with minimal spends, larger corporations with limited buys, and a variety of others. Don’t let size or breadth define your buying power. Influence your pricing and control your destiny!
Happy Dynamics 365’ing!