Imane Ait Allal

Filtering by Invoice status on Project posted transactions form should show accurate data for on-account transactions

The Project ID contextual filter in all forms that include ID project information for example all project list page shows NO project IDs in the drop-down list.

Users are trained to use these contextual filters and while it is working as expected for the customers list page, it does not work for projects list page and forms that include ID project information.

The project ID contextual filter should have the same behavior as the customer ID contextual filter.

In a contract based on billing rule,the system doesn't allow changing a Fee Billing rule percentage for new transactions or for existing invoices.

The solution needs to provide an option to modify the Billing rule fee percentage or make it disabled for new invoice creation.

When a timesheet is created, submitted(workflow) and posted from a lending company to a borrowing company with project type used “internal”, and checking the borrowing company project(type “internal”) pending transaction, we noticed that the sale price valued as zero.

However, when the same is repeated using a project type "Fixed-price, we have the sale price valued on the borrowing company project(type “fixed-price) pending transaction.

There is a discrepancy of behavior between intercompany timesheet(Internal project type) posted with sales price valued as Zero while that of a normal posting on a single entity shows a valued sales price,

The system should have the same beahvior for a posted hours in an internal projet .

It will be useful that the attached file to billing schedule line will be retrieved in generated sale odrer line then in invoice proposal line.

the system's behavior does not support conditions that differentiate the workflow implementation on intercompany invoice and a free text invoice.

The current workflow should allow a condition that can mange that.

When a project of type Fixed Price is created then system generates the revenue recognition project and link it with the main project with the initial project name . Revenue recognition project description can be changed on the revenue recognition form even the name project is updated and same is reflected while executing the revenue recognition process.

the system should allow the update , because the project can be created with an empty description or a wrong descrption then it can be updated , in this case the recognition revenue description remains with inial project descrption and it doesn't reflect the correct description.