Kieran Sweeney D365BC Developer/Consultant

Just looking at the GL Journal, allowing different selections and arrangements of fields would streamline each batch template. Users who select a batch template with a number series and balancing account specified don't necessarily need to see those fields in data entry. A stock GL Journal Entry likely won't need VAT/Posting Group information if the user just wants to issue a debit and credit for a document. I noticed that changing the layout within one batch affected the layouts in other batches, when BC would benefit from separating layouts for each batch.

Service Contract revenue is driven solely based on the Service Contract Accounting Group Code; therefore, all revenue or prepaid liability for a given Service Invoice falls in only one bucket. Users want the ability to have multiple items each with their own distinct revenue/prepaid accounts. For example, users want to lease a piece of equipment to Subscription Revenue while simultaneously booking monthly Protection Plan premiums to Protection Plan Revenue.

After opening a ticket with Microsoft (Ticket 120060324007419), it appears that VAT can be calculated/settled but not reported/uploaded in the United States/North American release of Business Central. As the EU becomes more strict when it comes to collecting VAT internationally, it will be come important to accommodate both US Sales Tax and VAT in all of its facets: Withholding, Settling, and Transmitting/Remitting. I requested the update of Tax documentation for the US Release; so, others are aware of the current VAT limitations here: https://github.com/MicrosoftDocs/dynamics365smb-docs/issues/378