Introduction  

Account structures in Dynamics 365 Finance use a main account and financial dimensions to create a set of rules that determine the order and allowed values when entering account numbers in transactions. Once an account structure is defined, it must be activated. Historically, the account structure activation process has been time consuming. It was also difficult to view the activation progress or to view any errors with the new configuration. If an account structure configuration change caused an error, a user could not find the root error message on the account structure page, but rather needed to dig through batch job logs to find the error message to understand the problem with the new account structure configuration.  

Feature details  

In order to solve these problems, we have recently released an enhancement to the account structure activation process in application release 10.0.31. This performance enhancement lets you activate account structures more quickly by allowing multiple transaction updates to happen at the same time. An added benefit of this new feature enhancement is allowing the structure to be marked as active immediately after it is validated and before the remaining unposted transactions are updated to the new structure configuration. This allows transaction processing to continue while the existing unposted transactions are updated to the new structure.  

To view the status of the activation, select View activation status above the grid on the Account structures page. You can also view the activation status by selecting View on the Action Pane and then selecting Activation status on the drop-down menu. 

Enable the feature 

In order to use this new functionality, enable the feature “Account structure activation performance enhancement” from within feature management.  

Learn more

More information about this feature can be found at this location: Account structure activation performance enhancement – Finance | Dynamics 365 | Microsoft Learn 

The post Account structure activation performance enhancement  appeared first on Microsoft Dynamics 365 Blog.

A key component of the Subscription billing feature is the Recurring contract billing module. Recurring contract billing allows customers to manage their recurring billing contracts through billing schedules which contain the financial details of a contract. Recurring billing contracts can be managed across one or many customers based on how a contract is drafted. The new feature Customer split allows Dynamics 365 Finance users to split billing schedules across multiple customers based on a percentage of the invoice. This feature reduces the risk of incorrect billing, as a single billing schedule can manage the billing for all customers that are to be billed.

What is Customer Split

Customer split allows a single billing schedule to be billed across multiple customers. For example, let’s consider a scenario where a contract should be billed to two customers: one is responsible for 60% of the bill and the other is responsible for 40%. Customer split allows users to configure a scenario such as this and reduce additional manual entry as well as reduce risk of inaccurate billing. 

The feature is enabled by setting the Customer split parameter in Recurring contract billing parameters page to Yes. 

 
Once the Customer split feature has been enabled in the Recurring contract billing parameters, the customer split can be set up on a billing schedule. The billing schedule header contains the primary customer responsible for the invoice, including the Bill to address on the Address tab. 

The Customer split option under Billing schedule in the action pane can be used to add additional customers and their responsibility for the bill at the header level. Customer split can also be added on a line-by-line basis.  

When creating the record for the customer split, the billing schedule parent customer will get billed the remainder of what is not defined. In our example, that will be 60%. When defining the customer split a start date, end date, customer reference, customer requisition, end user account, end user name, delivery address, and bill to address can be entered. 

When generating invoices for a billing schedule that has customer split defined, a sales order will be created for each customer defined in the customer split as well as the billing schedule header customer. 

Customer split is available on a billing schedule or billing schedule lines when: 

• Billing schedules have an Invoice transaction type of Sales order
• Billing schedule line is a service item 
• Billing schedule is not linked to a project 
• Billing schedule line is not configured for unbilled revenue

How to get started 

This functionality is available in 10.0.29 and later of Dynamics 365 Finance.  
Read the documentation for a more detailed look at the feature: Customer split on billing schedules.

The post Split recurring contract billing across multiple customers  appeared first on Microsoft Dynamics 365 Blog.

One aspect of Dynamics 365 Field Service’s adaptability lies in the flexibility of its ‘status’ functionality, driving a meaningful work order lifecycle tailored to each organization. Field Service helps manage work orders and bookings across diverse use cases. This blog series explores critical status concepts: 

• System Status and Substatus for Work Orders 
• Booking Status and Field Service Status for Bookings 
• Booking Status Impact on Work Orders Across Single and Multi-Booking Scenarios 

Grasping these concepts allows organizations to leverage the solution’s functionality, optimize field service processes, and ultimately provide better customer service. 

This blog will expand upon many of the concepts discussed in the existing work order and booking status documentation: Work order life cycle and statuses – Dynamics 365 Field Service | Microsoft Learn 

Work Order Status Concepts: System Status and Substatus 

System Status 

Work orders in Dynamics 365 Field Service have a column called System Status which helps organizations manage their field service processes efficiently. There are six values available for System Status: 

• Unscheduled: Work order has been created, but resources have not been assigned. 
• Scheduled: Work order has resources assigned and is ready for execution. 
• In Progress: Work order is currently being executed by the assigned resources. 
• Completed: Work order has been executed and finished. 
• Posted: Work order has been invoiced and is now closed. 
• Cancelled: Work order has been cancelled and will not be executed. 

As the documentation highlights, an organization must use this field as is because these values allow the FS solution to interpret the current state of the work order record and apply appropriate behaviors and validations. If this list is changed, it could cause many issues both immediately and unanticipated, down the line. New values in this list would not be interpretable by the solution. However, the Field Service solution has a powerful related concept that provides infinite flexibility which can be mapped directly to these System Status values. 

Substatus 

In Dynamics 365 Field Service, the Substatus table plays a crucial role in providing organizations with the ability to create meaningful states that are mapped to System Statuses. One noteworthy feature of the Substatus table is the option to define a “Default” Substatus for each mapped System Status. This default Substatus will be automatically applied when a work order transitions into the corresponding System Status through the out-of-the-box (OOTB) logic.  

The Default Substatus feature within the Substatus table allows organizations to streamline their work order management process by automatically applying a predefined Substatus when a work order moves into a particular System Status using the out-of-the-box logic. This helps ensure consistency across work orders while still allowing for customization and adaptability when needed.

For example, if your organization has a default Substatus of “Pending Customer Confirmation” for the System Status “Scheduled,” any work order that moves into the “Scheduled” System Status due to the standard logic will automatically be assigned the “Pending Customer Confirmation” Substatus. This helps maintain consistency and simplify the management of work orders, especially when dealing with a high volume of work orders. 

It’s important to note that if a work order already has a different Substatus applied within the same System Status, the default Substatus will not be applied. This means that, if an organization adds custom logic to set a substatus, the default logic will not override it. The existing Substatus will remain in place, allowing organizations to maintain flexibility and customization for specific work order situations. It is also worth noting that any custom logic is still subject the allowed System Status validations (for example: the Work Order cannot be forced into a Scheduled System Status if there are no bookings). 

Further, direct updates to the Substatus field will drive updates to the work order’s System Status, within the allowable System Status changes. For example, using some of the Substatus records proposed below, if a work order is in the “Technician Assignment Pending” Substatus, which maps to the Unscheduled System Status, a user could change the Substatus directly to “Customer Canceled” which will immediately move the System Status of the work order to Canceled. It is worth noting that the default form UI should filter the available Substatus values to allowed changes, based on the current state of the work order and the mapped System Status of the Substatus. In this example, none of the Subtatuses which mapped to the Scheduled or In Progress System Statuses would have shown up in the UI. They would have been dynamically filtered out so that a user couldn’t make a choice that wouldn’t have been allowed. 

Example: Substatus Records with Mapped System Status 

The following are an example set of possible meaningful Work Order Substatuses. These Substatuses will be mapped to the appropriate System Status to help drive actions and behaviors in the system while communicating meaningful information to anyone who looks at the work order in Dynamics 365 Field Service. 

Conclusion

While these are examples of Substatuses which may be valuable, each organization can create their own, set the defaults that make sense, and map them to relevant System Status values. 

Next up in the blog series –

Part 2 – Booking Status Concepts: Booking Status and Field Service Status
Part 3 – Booking status impact on work orders across single and multi-booking scenarios 

The post Status-Driven Success: Managing Your Work Order Lifecycle through Statuses – Part 1   appeared first on Microsoft Dynamics 365 Blog.

Continuing our 3-part series exploring Dynamics 365 Field Service’s adaptability using critical status concepts. We have viewed the following concept Work Order Status Concepts: System Status and Substatus  in our last blog.

This blog explores the concept of:

• Booking Status and Field Service Status for Bookings 

Grasping these concepts allows organizations to leverage the solution’s functionality, optimize field service processes, and ultimately provide better customer service. 

Booking Status Concepts: Booking Status and Field Service Status 

Before delving into the concepts of Booking Status and Field Service Status, it is important to understand the distinction between a work order and a booking in Dynamics 365 Field Service.  

A work order represents a scope of work to be performed for a customer. It includes the required services, the location of the work, type of resources, and other relevant information to complete the job. It also serves as a document which tracks how the scope of work is closed including what products and services were required, what tasks were completed, and other relevant information which someone may want to know about the work. Work orders are essential for organizing and managing service delivery, and their status changes as they progress through various stages, from creation to completion. 

On the other hand, a booking is a scheduled appointment or time slot that is associated with a work order. It is an essential component of the scheduling process, as it assigns a specific technician or resource to perform the services outlined in the work order. While work orders focus on the overall service request, bookings represent the individual appointments which are intersection of the specific time and duration of individual appointments and the assigned resource needed to fulfill the request. Each work order can have multiple bookings, allowing for more complex jobs to be split across multiple appointments or technicians. 

Booking Status 

Bookings for work orders in Dynamics 365 Field Service also have two critical status concepts. The first is Booking Status, which is a record that allows organizations to define their own meaningful statuses for bookings. By customizing Booking Status, organizations can better reflect their specific field service workflows and processes. 

Field Service Status 

The second critical concept for bookings is the Field Service Status value on Booking Status records. This status allows organizations to map their custom meaningful statuses to one of the six key values that the Field Service solution can interpret while driving important solution logic.  

These six key values are: 

• Scheduled: The booking has been scheduled, and the resources are assigned. 
• Traveling: The field service resources are en route to the job site. 
• In Progress: The booking is currently being executed by the assigned resources. 
• On Break: The field service resources are taking a break during the booking. 

• Completed: The booking has been successfully executed and finished. 
• Cancelled: The booking has been cancelled and will not be executed. 

By mapping their custom Booking Status values to the Field Service Status values, organizations ensure seamless integration between their unique processes and the overall Field Service solution. 

Example: Booking Status Records with Mapped Field Service Status 

For a Booking Status to be usable on a Booking which is related to a Work Order, the system expects the Booking Status to have a Field Service Status value. The following are an example set of meaningful Booking Status records. These Booking Statuses will be mapped to the appropriate Field Service Status to help drive actions and behaviors in the system while communicating meaningful information to anyone who looks at the booking in Dynamics 365 Field Service. 

This blog expands upon many of the concepts discussed in the existing work order and booking status documentation: Work order life cycle and statuses – Dynamics 365 Field Service | Microsoft Learn 

Next up in the blog series –

Part 3 – Booking status impact on work orders across single and multi-booking scenarios 

The post Status-Driven Success: Managing Your Work Order Lifecycle through Statuses – Part 2   appeared first on Microsoft Dynamics 365 Blog.