Every company has expenses. Some relate to the supply chain, and others to operating costs like rent, utilities, leasing, food, phone bills, and software subscriptions. These operating costs, known as overhead expenses, are the first focus of the Payables Agent. They are often received as email attachments or through other channels.

Sourcing files and attachments related to purchase of overhead expenses

In the first version, the Payables Agent can source purchase attachments (PDF files) from a Microsoft 365 email account where vendors send their invoices. The agent can also import PDF files from a shared SharePoint folder where the accountant and other employees place files to be processed. These invoice documents are imported into E-Documents in Business Central for further processing. After importing the documents, the agent moves the files to an archive folder.

Processing imported purchase attachment and files

Once files are imported, Azure Document Intelligence processes them using Optical Character Recognition (OCR) technology. The results are stored in Business Central in the E-Document. An updated PDF attachment viewer lets users validate the OCR processing by viewing the attachment in near-full screen with position overlays of captured information like amounts and descriptions.

Creating purchase invoices

When Azure Document Intelligence processes a purchase attachment, the Payables Agent creates a purchase invoice document, ready for further approval and posting. The agent uses various predictors and indicators for creating these invoices, like the company's available purchase history, accounting policies, or others specified when setting up the agent. The goal of the Payables Agent is to streamline the entire flow from identifying and importing purchase attachments, capturing relevant information to categorize the expense, registering the expense correctly in the general ledger, to creating purchase documents.

In the future, the Payables Agent will handle increasingly complex scenarios and company-defined rules, manage supply chain expenses, and match with open purchase orders, while also supporting E-Invoices received through other channels, like PEPPOL and other access points, or vendor invoices pushed into E-Documents via its native API.

Copilot's chat capabilities have been enhanced with the following:

• Users can ask questions about content from installed add-on apps, such as new pages, fields, and business processes.
• Copilot explains and guides based on documentation provided by the apps installed in your Business Central environment.
• The Ask Copilot icon is available in tooltips for custom fields that originate from installed apps.

About security, privacy, and AI

Copilot is built on Microsoft's comprehensive approach to enterprise security, privacy, compliance, and responsible AI. Our philosophy is that your data is your data: customer data in Business Central is not used to train AI models. For more information, go to FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform

Looking for more details?

• Read the preview announcement for Chat with Copilot
• Learn about Chat with Copilot
• AI FAQ for Chat with Copilot

Tell us what you think

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

For greenhouse gas emissions (GHG), Copilot can estimate total emissions based on descriptions and input parameters and adjust emission factors for future use.

To try out this feature:

1. Sign in to your Business Central online environment.
2. Go to the Sustainability Journal page.
3. Enter Sustainability accounts and fill in the Descriptions field with accurate information as well as other inbound parameters, such as Fuel/Electricity, Distance, Custom Amount, Installation Multiplier, or Time Factor.
4. Choose Suggest emissions with Copilot.

Join the conversation

We're excited to have you with us on our Copilot journey.

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at aka.ms/bcIdeas, or join the partner community discussion on the Dynamics 365 Business Central Partner Community Network on Viva Engage (formerly Yammer) to help us shape the future of AI in Business Central.

Copilot in Business Central is already enhancing users’ creativity and productivity with AI in key application scenarios, providing guidance and assistance in working with the product and finding the right data.

With this release, we're expanding the use of AI to enable customers to orchestrate and automate business processes using AI agents. Agents can work autonomously, perform assigned tasks, respond to different events and inputs, reason over the state of data, and overcome errors based on user input and the context of the Business Central user experience. Agents require minimal to no intervention from users, while bringing them in if circumstances require their attention. Agents can act on behalf of a company, department, or team, not just a user.

To enable this capability in Business Central, we're introducing our first out-of-the-box agent, Sales Order Agent, to automate the process of capturing sales orders from email messages.

The agent is configured to manage the full process:

1. Receive item requests from customer emails in a shared company mailbox.
2. Identify the customer from those registered in Business Central.
3. Draft the sales quote with the requested items.
4. Verify item availability.
5. Forward the sales quote to the customer for approval.
6. Receive confirmation, convert the quote into a sales order, and share the order with the customer via email.

The agent operates based on the included instructions and user configuration, and uses AI to identify and carry out the necessary steps to complete this task within the Business Central environment. It seeks user intervention when specific situations arise. For example, when it prepares outbound communications or to provide business approval for key operations. 

Sales Order Agent can only access the parts of the product it needs to perform its duties. It comes with predefined permissions and role (profile), which is automatically assigned when you activate the agent. 

The agent will have a simple configuration experience, where you can define the agent’s name, the channel for receiving requests for sales quotes and orders (shared company email), and select the steps you want to include or exclude in the process of taking orders from the customers.

When activated, the agent is ready to perform the process of capturing sales orders autonomously. The agent is started by an internal email processor in Business Central, which is configured to monitor the company mailbox provided in the agent's configuration.

Actions performed by Sales Order Agent, including navigating Business Central pages, creating and modifying records, and calling actions, are fully transparent so that you can review them in the Copilot pane. The actions show the agent’s user ID and will show up in the same places and in the same way as other users in list views, history, posted documents, notifications, and so on.

Business Central users maintain full transparency and control over the changes made by Sales Order Agent by using additional experiences, which enable the users to:    

• Discover notifications from the agent. For example, when it requires help, or when the process demands human review (such as all inbound and outbound messages, approvals, and adding missing data).  
• Get a better understanding of the task's context and history (“timeline” view), including the key steps displayed in the Copilot pane.  
• Get a detailed review of each entity the agent created (such as sales quotes or sales orders). You can review all changes and suggestions the agent makes for a specific task, so you can adjust these changes if needed and sign off on proceeding with the task.
• Discard the steps performed by the agent, adjust the quote or order as needed, and ask the agent to proceed with the flow.

This feature allows users to configure various Activity Codes, such as trade or service, for use in VAT Settlements. When enabled, Business Central will support posting multiple VAT settlements within the same period, each associated with a different Activity Code. These activity codes will also be recorded in the Periodic Settlement VAT Entry. Once a VAT settlement for a specific period is posted, the system will automatically document the period in the corresponding Activity Codes, ensuring accurate and compliant reporting.

Every six months (biannual), Australian companies with more than $100 million in annual turnover are required to report information on how and when they pay their small business suppliers (annual turnover of less than $10 million).

This feature organizes vendors by size or payment terms and generates reports for them based on the criteria required by local authorities.

• The average agreed payment period.
• The average actual payment term.
• The proportion of invoices paid after the end of the agreed payment period.

You can select the period for which you want to run a calculation and find details based on a grouping you choose. For each of these groupings, you can find sourced entries.

You can use this feature by opening the Payment Practices page and creating a new payment practice. You can also use different types of reporting for vendors, customers, or both, by using the Header Type option. For payment time details and statistics, set up all parameters and choose the Generate action.

The report will be in the required format, and it will categorize details into ranges of time (based on the timing after the invoice was issued):

• less than 21 days
• 21-30 days
• 31-60 days
• 61-90 days
• 91-120 days
• more than 120 days of issue

We're expanding the availability of Business Central to include more countries and regions through partner-led localizations. Our partners create the relevant localization apps and publish them to AppSource. In combination with the built-in language offerings, we're making Business Central online available to serve customers in more than 180 countries and regions worldwide.

The localized version for the UK is now available as a set of extensions on the W1 base app. This includes a data upgrade to ease the transition from the previous localization. This release is a step toward full delocalization, allowing ISVs to reach a broader market. During this process, some features will move to the base app or be delivered as global apps, while others will remain specific to the GB market.

Microsoft announced new IRS 1099 reporting features in 2024 release wave 1. Now, we're providing additional features for 1099 form submissions through API integrations. Integration with the IRIS platform lets you submit IRS 1099 forms electronically, saving significant time and reducing costs. This seamless integration eliminates the need for manual data entry and the associated administrative burden, so you can focus more on other important business activities. The integration with the IRIS platform streamlines the entire filing process, ensuring accuracy and compliance with IRS regulations. You can track the status of your submissions using the IRIS Transmission page.

By leveraging this feature, you can efficiently manage your tax reporting obligations directly within Business Central, enhancing productivity and minimizing the risk of errors or delays. This capability is particularly valuable for businesses that want to optimize operational efficiency and maintain compliance with tax authorities.

The introduction of the ability to encode attachments in the PEPPOL file format in Business Central 2024 release wave 2 provided the benefit of additional automation. You can automate the process of embedding sales document attachments in the PEPPOL file format. When you post a document, Business Central creates a PDF file and embeds it in the PEPPOL format, including both the full XML and a human-readable format. To enable this option, you must select the Embed Invoice PDF to XML field on the E-Document Service page.

During the purchase process, Business Central can process PEPPOL files with embedded attachments (invoices), decompose the embedded file, add it as an attachment to the e-document record, and make it available on the E-Document page for further processing.

If there was a problem with your setup for e-documents, and Business Central didn't create a related e-document when you posted a sales invoice, for example, you can quickly create one yourself. To check whether Business Central created an e-document, open the Posted Sales Invoice page and select the Open E-Document action. If you don't find a related e-document, you can run the Create New E-Document action to generate one based on the workflow rules. If a related e-document does exist, you can't use the action.

Business Central won't create new incoming e-documents if you import a batch that contains duplicates. Duplicates are documents with the same vendor, external document number, and date.

If a duplicate or incorrect e-document already exists in Business Central, administrators can delete them by running the Delete Related Document action. However, you can't delete e-documents that are already processed and are connected with purchase documents.

Previously, you couldn't create e-documents for reminders and finance charges. Now, the PEPPOL format accepts financial values from issued finance charges and issued reminders.

To activate these types of documents, on the E-Document Service page, run the Supported Document Types action. Add the finance charge and reminder document types on the E-Document Service Supported Source Document Types page. Business Central can then generate a file that's formatted as an invoice and contains the financial values from these documents.

When you receive an incoming e-document from an external service or manually upload one, it's typically in XML or similar format that can be difficult, if not impossible, to read. For example, if you aren't technical and don't understand the XML format, it'll be hard to thoroughly review an invoice before you process it. To make it easier for everyone to review incoming e-documents, invoices and credit memos have an E-invoice Lines FastTab that displays details from the imported file, such as line and header information, in a way that's easy to understand.

This feature is only available for invoice and credit memo types of incoming e-documents.

Previously, you could either choose to send e-documents through a connector service or download the file and send it by email. You now have more options for handling e-documents in sales.

If you choose the Post action from the Sales Order, Sales Invoice or Sales Credit Memo pages, Business Central posts the document as usual, but it can also trigger a workflow to create an e-document. That requires you to have an e-document workflow configured for the customer. But, if you choose Post and Send, Business Central does the same but also sends the e-document via email as an attachment.

Depending on whether you enable the e-documents workflow, you can choose one of the following models for sending documents in the sales process:

• Use the Post action from the document and Service Integration is enabled on the E-Document Service page. The e-document is sent to the configured access point.
• Use the Post and Send action from the document and Service Integration is enabled in the E-Document Service page. The e-document is sent to the configured access point and as an attachment in an email.
• Use the Post action from the document and Service Integration isn't enabled in the E-Document Service page. The e-document is created and ready to download.
• Use the Post and Send action from the document and Service Integration isn't enabled in the E-Document Service page. The e-document is sent by email.

If you accidentally delete a purchase invoice or credit memo, you can't proceed with the e-document connection with the regular purchase document in Business Central. To get yourself unstuck, you can run the Recreate Document action from the e-document. The action creates an unposted purchase invoice or credit memo based on the incoming document type and information in the incoming document and the G/L mapping or item references used.

You have more options to use as access points for electronic invoicing because we've added more electronic document service providers to Business Central. Now, in addition to Avalara and Pagero, you can choose the ExFlow by SignUp connector for your electronic invoicing.

You can choose new options as the service integration endpoints on the E-Document Service page. After you select ExFlow as a service provider and consent to using non-Microsoft systems, you set up the connection. To set up the connection, use the Setup Service Integration action to start your onboarding process and configure the credentials and API URLs.

Integrating the new service provider lets you automate the receipt and delivery of electronic invoices. The provider serves as the endpoint for e-document exchanges. This automation streamlines invoice management, reduces manual processing errors, and accelerates transaction times, significantly enhancing operational efficiency and boosting overall productivity.

Although the E-Document Services page has several global service integrations already, partners can easily add their own to the list by publishing a connector app on AppSource following our technical documentation.

You have more options to use as access points for electronic invoicing because we've added more electronic document service providers to Business Central. Now, in addition to Avalara and Pagero, you can choose the Logiq connector for your electronic invoicing.

You can choose new options as the Service Integration endpoints on the E-Document Service page. After you select Logiq as a service provider and consent to using third-party systems, you set up the connection. To set up the connection, use the Setup Service Integration action to configure the credentials and API URLs.

By integrating the new service provider, you can automate the receipt and delivery of electronic invoices. The provider serves as the endpoint for e-document exchanges. This automation streamlines invoice management, reduces manual processing errors, and accelerates transaction times, significantly enhancing operational efficiency and boosting overall productivity.

Although the E-Document Services page has several global service integrations already, partners can easily add their own to the list by publishing a connector app on AppSource following our technical documentation.

You can mark whether an e-document is fully paid, partially paid, or unpaid. This information is sent (accounts payable) or received (accounts receivable) through access points based on your e-document configuration. The payment tracking feature in e-documents includes details such as:

• Date of payment collection
• Amount collected, including VAT
• Base amount and VAT amount at the time of payment

With the APIs enabled, sharing electronic sales documents from Business Central to other applications or services becomes seamless. By integrating the E-Documents app in Business Central with Power Automate, you can connect to Power Platform tools and other systems for enhanced functionality. This setup allows you to send e-documents as BLOB files through various communication channels beyond the default connectors or email. Additionally, the integration supports automating the receipt of electronic documents in the purchasing process. It transfers them to the E-Documents tables for further processing in Business Central.

A new Power BI app has been added to help you analyze your subscription billing data.

The app contains reports such as:

• Subscription Overview
• Revenue Year-Over-Year
• Revenue Analysis
• Revenue Development
• Revenue by Item
• Revenue by Customer
• Revenue by Salesperson
• Total Contract Value
• Year-Over-Year Total
• Contract Value Analysis
• Customer Deferrals Vendor

To help you track important metrics for your subscription business, the semantic model for the report includes KPIs such as:

• Monthly Recurring Revenue
• Monthly Recurring Cost
• Net Monthly Recurring Profit
• MRR Churn
• MRR Downgrade
• MRR New
• MRR Upgrade
• MRR Change Usage Based Billing
• MRR Overall Change
• Active Customers
• Total Contract Value
• Revenue Forecast
• Customer Deferrals
• Vendor Deferrals

The Power Platform connector for the Business Central Admin Center API enables you to automate various environment management tasks using Power Platform products, including Microsoft Copilot Studio. Tasks include:

• Creating environments
• Copying environments
• Scheduling environment updates
• Integrating environments with other systems

This release wave expands Business Central with powerful Copilot features and tools that boost user creativity and save time. For example, the Sales Order Agent helps SMB organizations improve efficiency and customer relations by automating the process of capturing sales quotes and orders using AI.

Some Copilot and agent capabilities, like the Sales Order Agent, incur charges for using Microsoft Copilot Studio messages. This feature introduces a consumption-based billing model for select capabilities, including the Sales Order Agent and AI features built with Development Tools for Copilot for Business Central.

To use these features, link the Business Central environment to a Power Platform environment from the Business Central admin center.

Once linked, the Business Central environment can consume Microsoft Copilot Studio messages from any prepaid message capacity assigned to the Power Platform environment and use the billing policy for pay-as-you-go billing through an Azure subscription.

Previously, relatively rigid update policies were in place for major and minor updates. This release introduces the following changes for much more flexibility:

• Five-month update periods for major updates: This change gives more time for thorough testing and preparation before implementing the update. Resellers can spread the workload of updating all customer environments over the entire calendar year to avoid peak periods for major updates. Developers have more time to ensure all apps are compatible with the update, and customers with specific testing and preparation requirements have more time to comply with those requirements.

• Optional minor updates: This change allows administrators to choose when and whether to implement minor updates based on their needs and schedule. The default behavior of environments receiving updates every month doesn’t change. Instead, a new environment-level setting makes it possible to opt out of monthly minor updates.

As part of these changes, the grace period after the update period for the next major update shortened to one month. As before, the update will run and can’t be postponed to a later date during this grace period. The update will be forced by uninstalling incompatible extensions once the grace period ends.

Previously, the record links and notes were not automatically migrated to the online tenant as part of the cloud migration process. Instead, you had to use manual means to move the data. Now, the cloud migration setup and replication tooling will automatically migrate the links and notes on records for you with minimal work on your part.

The supply of IPv4 addresses is limited and will eventually run out. Starting in this release wave, Business Central supports IPv6 addresses. The transition to IPv6 not only ensures seamless connectivity for your environments but also enhances the security of your data with IPv6’s built-in security protocols. More importantly, this update prepares your environments for the future as the world moves toward widespread IPv6 adoption.

For each major Dynamics 365 Business Central update, Microsoft organizes a public preview starting a month before the release of the update to enable customers and partners to test and prepare for the new functionality and other product changes using a sandbox environment. Until now, it wasn't possible to update a sandbox environment to a preview version, which has made it difficult to test the next major version using your own data and extensions.

Starting with the public preview, it will be possible to update a sandbox environment to the preview version. This way, customers and partners can:

• Identify and address potential issues caused by environment data or installed extensions before the update is made available to their production environments.
• Test new functionality and the update operation itself using their own data, providing a more accurate representation of how the update will perform in their environments.
• Validate that installed apps and integrations will continue to work seamlessly with the new version earlier, allowing for more time to make any required changes before updating production environments.
• Prepare more effectively. Having a preview environment that closely resembles a production environment allows for earlier user readiness activities such as product training and change communication.

Environment updates might include changes to functionality that installed apps depend on, which, in turn, can break those apps. Until 2024 release wave 2, only notification recipients and registered Application Insights resources received messages about incompatibilities of installed apps with a future Business Central update.

To make it easier to plan for these changes ahead of time and avoid upgrade failures, you can now view app compatibility reports directly in the admin center. You're prevented from scheduling an update to a version that installed apps are incompatible with.

You can add fields from related tables in analysis mode tabs in two ways:

• From the context menu Add columns from on an analysis mode tab. This inserts the fields as new columns at the end of the view.

• From the context menu Add columns from on an analysis mode column. This inserts the fields as new columns to the right.

In both cases, select the related table to choose fields from. If there is more than one relation to the target table, the context menus show via <relation> after the table name. For example, in an analysis mode tab on the Customer list, you can add fields from the Contact table via the relation "Primary Contact No. := No.", where the No. of the Contact matches the Primary Contact No. on the customer.

After you select the table, a dialog appears to choose columns. The dialog shows the source table name and number, as well as the fields in the table. You can only select fields that have already been added to one or more pages. Use the Show available fields from option to select a page, which then populates the available table fields.

You can add multiple fields at once using multiselect. User-defined views are personal and reside in the tenant database.

The following example shows how to add the Email field from the Contact table as a column, using the Contact List page to select fields. Notice the smaller Contact prefix above the E-Mail caption, indicating that this column comes from a related table.

In this release wave, we've significantly improved reporting and analytics for the manufacturing area.

For most things that you can analyze with existing reports, there are new tools for Power BI, data analysis, and Excel.

• You can track new KPIs and scenarios in the updated Power BI Manufacturing app.
• Many existing analytical reports now have an Excel layout that lets you change the report as needed. The datasets are enriched with fields that report extensions often add. The legacy RDLC layouts are deprecated.
• New reports with Excel layouts are available.
• Many existing list reports now have a Word and a simple Excel layout that lets you change a report as needed. The datasets are enriched with fields that report extensions often add. The legacy RDLC layouts are deprecated.
• Many of the existing analytical reports have been marked as deprecated. (Removal date set to 2027 release wave 1.) For each report, we have specified their replacements.
• All existing reports have teaching tips and are documented, including deprecation and replacement options.
• We also added a new Manufacturing analytics section in the documentation.

We've enhanced the financial reporting features with new templates for reports. All country versions benefit from four new column definitions:

• BS Multi-Year Balance Comparison (for balance sheets)
• BS Current Year Balances by Quarter (for balance sheets)
• IS Current Year Net Change by Quarter (for income statements)
• IS Multi-Year Net Change Comparison (for income statements)

The North American (NA) localization has two new row definitions:

• Balance Sheet Audit Lead Schedule
• Income Statement Audit Lead Schedule

The row definitions are part of two new reports:

• The Balance Sheet Audit Lead Schedule report is a balance sheet with the same order as the detailed balance sheet, but with full account details. Use the report for internal or external audits.
• The Income Statement Audit Lead Schedule report is an income statement with the same order as the detailed income statement, but with full account details. Use the report for internal or external audits.

You can set up taxonomies in Business Central using various transactional data sources. The initial setups are prepared for the demo data, but you can adjust them to meet your specific needs. After configuration, you can aggregate existing data based on these taxonomies.

After you aggregate data for a specific reporting period, you can integrate with the ESG Reporting tool to prepare the data for reporting. Because Business Central doesn't contain all the data needed for CSRD reporting, you can switch to the ESG Reporting tool where you'll find a preconfigured CSRD template where you can add any missing metrics so you can generate the reporting file.

In the future, we'll extend this integration to other ESG reporting standards.

You can configure taxonomies in Business Central, drawing from various transactional data sources. The initial setup is prepped for demo data, but you can adjust it to suit specific needs. After configuration, you can aggregate existing data based on the taxonomies. If there's no integration with a reporting tool, you can generate a report layout to serve as a preparation document for CSRD reporting.

We've significantly improved reporting and analytics for our Sustainability features. In addition to the three existing reports with the Excel layout, there are new tools for Power BI and data analysis.

• You can track new KPIs and scenarios in the updated Power BI Sustainability app, such as emissions by category and scope, CO2e analysis, journey to net-zero carbon, realized vs. baseline vs. target, water and waste analysis, and so on.
• You can track new KPIs and scenarios related to social and governance, such as gender or age distribution, qualifications, and so on.
• All reports have teaching tips and are documented.
• You can learn more by going to the new Sustainability analytics section in the documentation.

Leverage Sustainability features to measure environmental impacts such as greenhouse gas emissions, water usage, and waste intensity while maintaining data required for compliance reporting. You can also use features such as statistical accounts to track and measure social and governance effects.

This feature allows you to collect sustainability data and align it with regulatory taxonomies that are required for reporting under various standards, such as Corporate Sustainability Reporting Directive (CSRD) or Business Responsibility and Sustainability Reporting (BRSR). After you collect and aggregate data in Business Central, you can seamlessly transfer it to the Project ESG Reporting (preview) app, where you can add more text or contextual information as needed. The reporting process ends by generating files that comply with regulatory requirements for submission, which streamlines the entire sustainability reporting workflow.

This integration provides a solution for small and medium-sized businesses (SMBs) to meet complex ESG reporting requirements with greater ease. It allows you to access and map sustainability metrics directly from Business Central into Project ESG Reporting (preview).

This solution includes:

• Integration of scope 1, scope 2, and scope 3 emission metrics from Business Central into Project ESG Reporting (preview).
• Ability to map metrics from Business Central to existing concepts in Project ESG Reporting (preview).
• Create metric values and associate them with mapped concepts and an assessment.

To post emissions without a scope, on the Sustainability Account Category page, in the Emission Scope field, choose Out of Scope. Then, either assign the account category to a sustainability account or create a new account and assign the category.

You can use a sustainability account with this setup on a sustainability journal if you configure the sustainability journal batch to use this emission scope, or allow all scopes. After you post the journal, entries marked as Out of Scope are recorded in sustainability ledger entries.

You can use the Sustainability Journals and Recurring Sustainability Journals pages to record water and waste intensity data, based on the existing Chart of Sustainability Accounts, but using new Emission Scopes - Water and Waste. You can use different account groups, subgroups, and formulas to make the collection of water and waste intensity as easy as possible. This feature also uses existing Sustainability Ledger Entries where data is recorded and used for reporting, so you can report both gas emissions and water and waste from the single source.

You can specifically track Water Intensity, Discharged Into Water, and Waste Intensity, using Water/Waste Intensity Type (Withdrawn, Discharged, Consumed, Recycled, Generated, Disposed, Recovered) and Water Type (Surface water, Sea water, Ground water, Third party water, Produced water). Sustainability Goals are also extended to cover water and waste management features.

This feature optimizes screen space usage in the Business Central web client, including:

• Optimized default page size in narrow mode.
• Improved sizing and animation of the FactBox pane in narrow mode. The FactBox pane is added to the page width, so the main content area width remains the same as you expand and collapse the FactBox.
• Better proportions between field labels and values in narrow mode.
• An option to resize the FactBox pane and remember this choice per page and mode. This capability is covered by the Allow adjusting FactBox pane width feature.