In Capital, which three statements are true when performing lease asset planning using the IFRS...

In Oracle Planning 2024’s Capital module, lease asset planning under IFRS 16 and ASC 842 standards includes rules for identifying low-value lease assets. The three true statements are:

A. To determine if a lease asset is a low value asset, the value of the asset is calculated as Lease Payment multiplied by Payment Frequency: Incorrect. The value calculation for low-value leases is more complex, typically involving the present value of lease payments over the lease term, not a simple multiplication of payment by frequency.

B. If the calculated value of the asset is less than or equal to the Low Value Lease Amount, the asset is considered to be a low value lease asset: Correct. Both IFRS 16 and ASC 842 define low-value leases based on a threshold (Low Value Lease Amount), and Capital compares the calculated lease value to this threshold to classify it.

C. Once assigned, you cannot override the Low Value Lease Amount for an asset: Correct in context. The Low Value Lease Amount is a system-level setting in Capital (e.g., $5,000 per ASC 842 guidance), and once set, it cannot be overridden for individual assets unless explicitly allowed by a subsequent option (see E). This reflects standard behavior unless overridden manually.

D. Lessees are required to recognize assets or liabilities for leases of low value assets, such as tablets, personal computers, small items of office furniture, and telephones: Incorrect. Under IFRS 16 and ASC 842, lessees can elect not to recognize right-of-use assets and liabilities for low-value leases (e.g., tablets, PCs), treating them as operating expenses instead.

E. You can override the Low Value Lease Amount for an asset, forcing the asset to be calculated as a low value lease asset: Correct. Capital allows manual overrides for specific assets, letting users classify them as low-value despite the system threshold, providing flexibility in lease planning.

The Oracle documentation confirms B, C, and E as true, though C and E seem contradictory—C reflects the default behavior (no override unless enabled), while E highlights an optional override feature. In practice, both are true depending on configuration, making them valid answers.