Suggestions for avoiding double counting accruals and commitments

Hi Gurus

We are planning a custom solution to import month-end reversing accruals resulting from goods received not invoiced from P2P into Projects (for a variety of reasons, the standard perpetual accruals method was not acceptable).  We are on R12.1.3

 

The transactions will be brought in to Projects as miscellaneous transactions on the last day of the period, and reversed out on the first day of the following period, and therefore shown in the project reporting views at month-end as "Actual" costs.. Of course they are also included in committed costs, and hence could be misunderstood by users due to these costs being included in 2 places.