Applies to Product - Dynamics 365 Project Operations
What’s happening?
Customers are experiencing an issue where fee journals created from the invoice proposal screen are being marked as nonbillable but are still showing as fully invoiced in the system.
Customers are experiencing an issue where fee journals created from the invoice proposal screen are being marked as nonbillable but are still showing as fully invoiced in the system.
Reason:
The underlying cause of this is that when creating a fee journal from the invoice proposal screen, there is no option for the user to indicate whether the fee is billable or nonbillable. As a result, the fee journal defaults to nonbillable, yet it is still processed as fully invoiced.
The underlying cause of this is that when creating a fee journal from the invoice proposal screen, there is no option for the user to indicate whether the fee is billable or nonbillable. As a result, the fee journal defaults to nonbillable, yet it is still processed as fully invoiced.
Resolution:
This has been reported to product team. Upon further investigation of product team, we have determined that the issue you reported is not a bug but rather a feature that was designed to work in a specific way.
The original design of fees on the invoice proposal were meant to be a quick way to add fees in a simple quick manner while invoicing. The consideration of a non-chargeable default project with chargeable fees wasn't considered. There is no line property available to override the default.
To avoid this issue, users should create fee journals using the normal fee journal process from the project instead of the invoice proposal screen.
The product team is currently reviewing the functionality. Here you can find more details on product team answer: Details for issue 970385
Additionally the following script updates the status of existing fee journals that were incorrectly marked as nonchargeable to "Fully Invoiced.:
select TRANSDATE as TransDate1, LINEPROPERTYID, SBSCUSTACCOUNT, * from projrevenuetrans T1
join PROJPROPOSALREVENUE T2 on T2.DATAAREAID = T1.DATAAREAID and T2.PARTITION = T1.PARTITION and T2.TRANSID = T1.TRANSID
where T1.DATAAREAID = 'into' and T1.LinePropertyId = 'NonBill' and (T1.SBSCUSTACCOUNT = 'CUST-000000998' or T1.SBSCUSTACCOUNT = 'CUST-000002674')
order by T1.TRANSDATE desc
update PROJREVENUETRANS set LINEPROPERTYID = 'Billable' where TRANSID in (
select T1.TRANSID from projrevenuetrans T1
join PROJPROPOSALREVENUE T2 on T2.DATAAREAID = T1.DATAAREAID and T2.PARTITION = T1.PARTITION and T2.TRANSID = T1.TRANSID
where T1.DATAAREAID = 'into' and T1.LinePropertyId = 'NonBill' and (T1.SBSCUSTACCOUNT = 'CUST-000000998' or T1.SBSCUSTACCOUNT = 'CUST-000002674')) and DATAAREAID = 'into'
This has been reported to product team. Upon further investigation of product team, we have determined that the issue you reported is not a bug but rather a feature that was designed to work in a specific way.
The original design of fees on the invoice proposal were meant to be a quick way to add fees in a simple quick manner while invoicing. The consideration of a non-chargeable default project with chargeable fees wasn't considered. There is no line property available to override the default.
To avoid this issue, users should create fee journals using the normal fee journal process from the project instead of the invoice proposal screen.
The product team is currently reviewing the functionality. Here you can find more details on product team answer: Details for issue 970385
Additionally the following script updates the status of existing fee journals that were incorrectly marked as nonchargeable to "Fully Invoiced.:
select TRANSDATE as TransDate1, LINEPROPERTYID, SBSCUSTACCOUNT, * from projrevenuetrans T1
join PROJPROPOSALREVENUE T2 on T2.DATAAREAID = T1.DATAAREAID and T2.PARTITION = T1.PARTITION and T2.TRANSID = T1.TRANSID
where T1.DATAAREAID = 'into' and T1.LinePropertyId = 'NonBill' and (T1.SBSCUSTACCOUNT = 'CUST-000000998' or T1.SBSCUSTACCOUNT = 'CUST-000002674')
order by T1.TRANSDATE desc
update PROJREVENUETRANS set LINEPROPERTYID = 'Billable' where TRANSID in (
select T1.TRANSID from projrevenuetrans T1
join PROJPROPOSALREVENUE T2 on T2.DATAAREAID = T1.DATAAREAID and T2.PARTITION = T1.PARTITION and T2.TRANSID = T1.TRANSID
where T1.DATAAREAID = 'into' and T1.LinePropertyId = 'NonBill' and (T1.SBSCUSTACCOUNT = 'CUST-000000998' or T1.SBSCUSTACCOUNT = 'CUST-000002674')) and DATAAREAID = 'into'