Regulations in different countries/regions and industries, and customer business practices can cause a need to change the way in which general ledger entries are aggregated during posting.
Feature details
The Invoice Post. Buffer table has been at the center of localizations and partner customizations when changes to G/L posting are needed, or when G/L entries need to be aggregated in a different way when they're posted to the general ledger. The previous design is not extensible because the primary key in that table cannot be changed without introducing breaking change across partner solutions and localizations. There are significant differences in this table across localizations, in particular for APAC, BE, ES, IT, NA, and RU, and this has made it difficult to extract localizations to extensions.
This refactoring makes the posting process for sales, purchase, and service transactions extensible, and enables partners to change the way the posting algorithm aggregates G/L entries—for example, by specific document lines, posting groups, or the tax setup required by local legislation. Partners can replace customizations by using the interface for G/L invoice posting, resolve legacy issues for the Invoice Post. Buffer table, and use their own implementation of G/L invoice posting.
We have removed the dependencies from the Invoice Posting Buffer table in the Base Application and built an Invoice Posting component with an interface and an extensible enum for the implementation setup.
Note
This feature currently is available only for developers and can't be turned on in production environments yet.
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.
Thank you for your idea
Thank you for submitting this idea. We listened to your idea, along with comments and votes, to help us decide what to add to our product roadmap.