Comments
we need this for our production environment. Once we purchase dataverse storage, we don't want the space to be utilised by other environment belonging to other country team or by our citizen developers. We don't have centralised admin and we cannot enforce limit on other countries environment
With clients having to move to new platforms from GP, it is beneficial to MS to keep these clients in the MS world. To do so requires clients to maintain the features they have in GP that they know and love along with giving them greater flexibility in a new system. Since users currently have the functionality to close out statistical accounts in GP, these would be a good selling feature and beneficial to clients to have this option in BC. Currently the options available to them are cumbersome or expensive.
This functionality is essential for organizations using statistical accounts in Business Central. Dynamics GP has a built-in year-end reset for statistical accounts that clears balances while preserving historical data—a feature that many businesses rely on for accurate reporting and smooth year-end processes. Business Central currently lacks this capability, forcing users into manual workarounds like configuration packages or statistical journals, which are time-consuming and error-prone.While there is a ‘Reverse Entries’ option in the Statistical Ledger Entries table, it is not ideal because it posts reversals using the original posting dates. This means balances do not reset cleanly at year-end, and reporting across fiscal periods becomes confusing.Adding a proper year-end reset feature would:Streamline closing processes and reduce manual effortMaintain audit integrity by preserving historical data without deleting entriesImprove adoption for GP customers moving to BC by retaining a critical capabilityThis is not just a convenience—it’s a fundamental requirement for accurate operational and statistical reporting. Please prioritize this enhancement to bring Business Central in line with GP’s robust functionality.
I completely agree. MR has functionality that core BC financial reports does not. The BC reports need users to polish the report when exported as well as dynamic dates need to be fixed. MR has this functionality. For smaller clients that already user MR for GP, migration of those reports would be simple
The period closing process for the project module is useless if it doesn't block all postings. If additional transactions can be posted after the closing, inconsistent data is created in reporting tools. Closing vendor/customer periods is not a solution, as these are independent and should still be used for transactions that are not project-related.