Day: August 10, 2023

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The first of the new functionality in the Copilot and AI innovation section is complete bank account reconciliation faster with Copilot.

Bookkeepers in SMB organizations need to import bank statements and reconcile transactions with their bank ledger entries, making sure customer payments, refunds, and purchases are all accounted for. While Business Central already reduces effort through automated transaction matching, the residual work to process the unmatched transactions every week remains cumbersome and quickly accrues to lost workdays. Copilot reduces bookkeeping effort through improved transaction matching and natural language explanation of any proposed matches.

Enabled for: Users by admins, makers, or analysts
Public Preview: Oct 2023
General Availability: Jan 1900

Feature Details

The bank account reconciliation feature in Business Central has been enhanced with:

• AI-powered transaction matching that further improves automation and reduces the remaining unmatched transactions that require human oversight.
• AI-generated explanations for how remaining transactions could be matched, making it easier for bookkeepers to complete the account reconciliation task by simply reviewing and approving matches.

My Opinion

There was an announcement about Copilot in Business Central a while ago, but I’ve not seen any further details. This may be the first feature to use it? It will be interesting to see how useful an accurate it is in reconciling transactions.

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The fourteenth of the new functionality in the Application section is use General Ledger Allocations to distribute costs and revenue more efficiently.

To make data entry efficient and reduce errors for recurring types of posting, you can use allocations to predefine how to distribute revenue for transactions or cost amounts across G/L accounts and dimensions. You can use allocation keys on document and document lines, and in most journals.

Enabled for: Users, automatically
Public Preview: Sep 2023
General Availability: Oct 2023

Feature Details

You can use customized allocation keys to automate the distribution of revenue or cost transactions in journals, sales documents, or purchase documents. Allocation keys can trigger automatic G/L entry postings and allocations across different accounts and dimensions.

For example, allocation keys can automate postings related to payroll overhead. When posting total salary expenses at the end of the month, you can use automatic account codes to assign a percentage of the total salary to automatically post as overhead expenses. Or, you can use headcount per department to distribute the cost to the department-related dimension.

You can define your allocation keys based on:

• Fixed amounts.
• Variable amounts (balance, net change).
• Statistical accounts (non-financial quantities you track through the Statistical Accounts feature).

My Opinion

I’ve worked with another system in the past that had allocation accounts and the fixed ones were very useful. There variable one was used very little, but in combination with statistical accounts could be useful for splitting costs. For example, splitting based on headcount or number of virtual servers.