0
Category:
STATUS DETAILS

Comments

Adding support for this idea based on a live customer implementation running a 5-4-4 fiscal calendar.Asset leasing derives its schedules from the lease payment and compounding frequency, which supports Monthly, Quarterly, Semiannual and Annual only, and does not reference the legal entity's fiscal calendar. The practical consequence is not simply a date mismatch. On a 5-4-4 calendar, a 5-week period and a 4-week period must carry different interest and lease expense values, and there is currently no way to produce that split. Re-dating the generated journal lines before posting only moves a monthly value to a different date, so it does not address the requirement.The impact is also uneven across the postings. Right-of-use asset depreciation can be aligned where the ROU asset is linked to Fixed assets, since that module does support a fiscal calendar. Interest recognition, lease liability amortization and the short-term liability reclass have no equivalent option. The short-term liability reclass is the most constrained of the three, because the reclass and its reversal share a single voucher.The only approach available today is to post the generated monthly entries and then reclass interest and lease expense into the correct fiscal period manually at period end. That is an accounting workaround rather than a product capability, it carries audit and reconciliation overhead, and it does not scale where an organization is onboarding a high volume of leases across multiple legal entities.Retail, hospitality and manufacturing organizations commonly report on 5-4-4, 4-5-4 or 4-4-5 calendars, and lease accounting is precisely the area where period alignment matters for close and statutory reporting. Allowing batch journal creation to honor the fiscal calendar period start and end dates, in the same way Fixed assets already does, would close this gap.

Category:

Tôi đồng ý với ý kiến của bạn

Category:

Good Idea!

Category:

Timeline view displaying the agent who actually handled the call is crucial to our supervisors, especially when there are more than one phone calls linked to the case.

Category:

This functionality is very important to our business. It will cut down on time spend building a pallet of goods.

Category:

The planned shipment date should definitely be changed.

Category:

Escalation & Feature Request: Third Schedule (FBR) Retail-Price-Based Sales Tax Support in D365 F&O and Commerce

Category:

Agreed, this would be very beneficial. I hope to see this enhancement gain further review and implementation.

Category:

This is a very good idea!

Category:

We are frequently required to prevent the Cost and Price columns from being displayed. While we can achieve this through customization using the HideValue property, there is currently no equivalent way to do so for FieldGroups. This is a significant gap for our customers.

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500