Ivy Yu

Hello everyone, I have a customer in Australia who is financing their leasing through variable rates loan with banks. For example, they have loans with varied interest rates each quarter the 1st year and then another interest rate the 2nd year. It doesn't seem like we should use CPI index to revalue it every year, as there's a defined payment schedule with interest rates in day 1 of the lease agreement.

In AASB 16, we have the following paragraphs:

"Paragraph 43 of AASB 16, in applying paragraph 42 of the AASB 16, a lessee shall use an unchanged discount rate, unless the change in lease payments results from a change in floating interest rates. In that case, the lessee shall use a revised discount rate that reflects changes in the interest rate."

We probably need to use variable interest rates to calculate the NPV value of ROU and link the lease contract to the asset in Fixed Asset module.

Please can we have the function to handle floating interest rates for NPV calculation if there is no existing one.

There are many users complaining about the disposal posting profile. They thought the posting is not intuitive, especially the P&L accounts on disposal of assets.

We’ve created clearing account and used it as both main and offset accounts for Net Book Value configuration in Disposal.

The voucher looks a lot better with this change, but client had to request new main account for this, and this is not just for one customer. Almost every user questioned this posting pattern, so appreciation if Microsoft can make this more intuitive and understandable for Finance professionals. 

We are trying to do beginning balance data migration for some lease schedules with “Ordinary annuity” as the annuity type.

The cut-off date is 1-Feb-2024, and the payment should fall on the 5th of February of each month.

We cannot use Jan 2024 as the start date because in that case the liability schedule will start in Jan instead of Feb, which is incorrect.

Hence, we tried to enter Feb payments as a standalone line with the below 2 methods. However, the result payment schedule generated for these methods both have some unexpected results:

Method 1: First payment schedule line start date on 4-Feb-2024, with Days as period interval and Monthly as Payment frequency. The result payment schedule has the first two payments both fall in March 2024, when we actually expect one in 5-Feb-2024 and another in 5-March 2024.

Method 2: First payment schedule line start date on 1-Feb-2024, with Days as period interval and Monthly as Payment frequency. The result payment schedule has the first payment at the end of Feb, i.e. 29-Feb-2024, when the expectation is 5-Feb-2024.

We've been told by Support this is a system limitation due to the minimum payment frequency that can be selected is month, not day. Hope we can have more flexible payment schedule options for data migration, because "Ordinary annuity" is a quite common annuity type in practice.

We have noticed for some Ordinary annuity, quarterly payment schedules with payment date in the middle of the month, the lease balance forecast report does not capture the lease at the month end of lease start date.

For example, lease commencement date is 13/02/2024, Ordinary annuity with 1st payment due on 13/05/2024. When we run the lease balance forecast report till end of Feb, it doesn't capture the lease. And, only when we run the report on or after 12/03/2024, the lease can be captured. However, in Lease liability amortisation schedule, there's a beginning balance amount on 13/02/2024, and ending balance on 12/03/2024 is a different amount. Apparently, there's movement in balance from Feb to Mar 2024, so there should be some balance at the end of Feb. Once contract is signed and lease started, the liability should be reported even though payment is due much later.

When users process a reversing journal using the Excel Addin, Reversing date is entered but Reversing entry box value is not ticked (default value is No), there is no validation error.

This validation is available in UI, but not in Excel Addin. Please can you add the validation in Excel, as journals are uploaded through Excel more frequently than being entered in UI directly.

It will be great if we can create backdated financial year within the same Fiscal Calendar.

Sometimes, Fixed asset data migration requires to have the historical calendar for the original acquisition date. However, this date may not be predictable until we got the actual data. Calendars are usually created in much earlier stage and it is currently impossible to create historical years.

For field descriptions that are super long, when user hover over the field and then try to move to the field description text box to scroll down, the text box would disappear sometimes. Therefore, it's hard for users to finish reading all the texts. It will be good to stabilize the field descriptions so that users can read longer texts without trying the scroll multiple times. Thanks!

Please can we have data entities for print management import / export.

When we have more than 100 legal entities and print management setups for all major modules such as AR, AP, PMA, etc., it's really time consuming to configure print management manually.

Also, whenever there's a major environment refresh, customers have to reset print management and it is a bit tedious to do it manually every time.

In Expense Management module for Australia legal entity, intercompany GST is not posted to the correct legal entity. The issue happens when the expense is directly charged to the destination legal entity, without project linked to the record.

• The expected results: when General ledger parameter Legal entity for intercompany tax posting is set to Source (Destination option is for the US tax as shown in the description), the GST portion in subledger journal and voucher transaction should be posted to Source legal entity. Also, the Posted GST in Tax module should be recorded in Source company as well.

• The current posting pattern is incorrect: GST portion in subledger journal and voucher transaction is posted to Destination legal entity, however, the Posted GST in Tax module is recorded in Source legal entity.

Fixing the intercompany tax will make this module stand out from competitors and enhance its competitive advantages. I would appreciate it if this could be put on the roadmap.

Sometimes, the column header names can be very long, hence texts are partially hidden. It will be good if there's wrap texts function to automatically adjust the display of texts in column header.