Hello Alexis

Did you find the root cause of this issue, as I am experiencing this too?

Unfortunately, No.

We can see the issue occur each week, but we can’t make it occur on demand.  We continue to monitor and manually update. 

Only one additional detail has been discovered. I believe that when no valid reason for the 0 Internal Price is evident then the User entered in the Registered By field often does not have access to enter data for the Employee the Project Transaction is connected to. But since we cannot make the error occur on demand we are stuck at the moment.

Noticed this has been awhile so it might be fixed already -

How do you enter project transactions? If it’s manual, make sure that the resource is selected correctly as it’s a known bug on earlier versions of Cloud that it has to be selected so the internal price pulls through. As it is not mandatory, it lets you save the record.

If it’s through time registrations earlier cloud versions also have the problem - under additional details on entering time sometimes it pulls through the resource, and sometimes it doesn’t.

I’ve just found this and logged with IFS and it’s possible this is fixed in later versions.