Suggested by Rekha Thattil – New
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).