Rekha Thattil

When setup with a progress type billing rule, we noticed that when the invoice proposal is created it correctly assigns the billing rule.

But if you create a fee journal manually using the same category and bringing it in, billing rule is not associated correctly. Same happens if you try to use the 'Create Fees' on a current open invoice proposal.

Billing rules populating correctly on these transactions is essential because the Progress billing contract is tracking the contract & invoiced values against billing rule ids'. So if there is a data mismatch, the expected fee in the next round of billing is incorrectly calculated.

We are using resource/category validations and within an expense report can use different projects on the expense lines. When creating an expense report line first the category needs to be selected. But all the categories are listed despite the resource/category validation. Only when a project ID is populated does the expense report filter down to the validation group.

This was logged and deemed to be a design issue. -https://fix.lcs.dynamics.com/Issue/Details?bugId=980271&dbType=3&qc=73a8e27e34afe6eb922f5a54366954af580385be91236df6051b3d3e195ce5ff)

We need this fixed so the system does cater to resource/category validations on expenses.

There is a legacy field called 'Status' on the projects form. This field is not used in PMA solutions, the project stage field is the one that is used to control the lifecycle of the project. i.e. Created/In process/Finished. This legacy 'Status' field however is still available and if it is 'Finished', while the project stage is 'in Process', the system creates customer retention transactions that cannot actually be processed.

We had examples of when creating invoices with retention, while on the invoice it appears there are retention amounts, the actual invoice voucher & customer balances did NOT reflect the retention deductions expected. This was due to this legacy field being set to 'Finished', even though the project stage was active and we could raise an invoice.

The other part to this problem was when you try to release the retention on a project, it generates a transaction but never gets into the invoice proposal.

This was logged as a support issue but has been deemed as a design limitation of the system.

Request to fix this solution so that the logic looks to the project stage (as with other parts of invoicing that is done).