Aditya Patwari

As per IFRS 16, in case any Security deposit is given for the lease without any consideration then the present value of the

Generally, in a lease agreement a security deposit is payable at the beginning of the lease term. This security deposit is generally refundable. As per Ind AS 109, Security deposit meets the definition of financial asset. As per Ind AS 109, security deposit should be recorded at its fair value on initial recognition. The difference between the actual amount of security deposit and fair value of security deposit should be amortized over the tenure of security deposit. User will enter the relevant details of security deposit in the lease summary. The system will create an amortization schedule of interest income and prepaid expenses. The system will automatically create and post the amortization of interest income and prepaid expenses.

In Fixed Asset Transfer local taxation applies. The Transfer Order Functionality should be extended to include fixed asset transfers. Also inline the Transfer of Fixed asset can be improved across also.

Currently once a negative sales order is posted, the account picked by the system from item posting profile is of type "sale", however at many instances everyone wants to report their returns differently which becomes an issue, thus an option to be given in the system that when enabled a new posting type option appears in the item posting profile wherein user can define the posting for Sales return/credit note or negative invoice.

Currently in the Statement Posting batch job the tasks are in a sequential manner and if one leg is not complete the task does not move to the next stage. So if there in an inventory error in statement, the sales order posting is stuck and due to that the payment posting cannot take place since it is in the later steps.

Thus MS should think of an option to have 3 batch jobs instead of 1 in which

1. Batch Job 1 will only process the Sales Order & Inventory
2. Batch Job 2 will only process the Payment
3. Batch Job 3 will Link and settle the Payment & the Sales Invoice

Currently in In the Subscription Billing module, there's an issue with the revenue split template: a stocked item cannot function as both a parent and a child. When used this way, inventory is deducted twice—once from the parent line and again from the child line—upon posting the sales order.

Ideally, the parent line should act purely as a dummy, regardless of whether the item is stocked or non-stocked. Its sole purpose is to structure the revenue split; only the child lines should drive inventory and posting movements.

Example:

Suppose Item A is a stocked item. If it's set as both the parent and a child in the revenue split template, posting the sales order will reduce inventory for Item A twice—once from the parent line and once from the child line.

Ideally, the parent line should act as a dummy, regardless of whether the item is stocked or non-stocked. Its role is only to structure the revenue split and generate child lines. It should not trigger any inventory or financial postings.

Correct behavior example:

• Item A (stocked) is used only in child lines.
• Parent line is a non-stocked or dummy item (or the same item marked in a way that prevents inventory movement).
• Only the child lines drive inventory and posting movements.

This approach ensures accurate inventory tracking and aligns with the intended use of the revenue split template.