Why doesn't an Expense Claim push the Unit Rate to the Project Transaction?

Hello @jmcclelland95 !

Can you try looking at a couple of places first:

1. Configuration Settings - Is your Expense Claim setup to push the Unit Rate to the Project Transaction? Check the Project Setup and Non-Stock Item Settings to verify that the Unit Rate is set to be included.
2. Project Costing Rules - Acumatica uses a ton of different rules to determine how costs are calculated. Check the Project Costing Rules to make sure that the Unit Rate is included.
3. Billing Rules - If the Billing Rules doesn’t include - you guessed it: the Unit Rate, it might not be included.

Here’s a couple of help articles that goes into more depth about Unit Rates and configuring them:

https://help.acumatica.com/(W(4))/Help?ScreenId=ShowWiki&pageid=fce5bf02-bdfc-46d6-96cc-3d7ad15f9820

https://help.acumatica.com/(W(5))/Help?ScreenId=ShowWiki&pageid=c12cd234-2ac9-2147-a687-fa3ccdaa1e29

Let me know if this helps, thanks!

Thank you for the suggestions. The configuration settings are correct. The Unit Rates cannot be standardized for the nonstock expense items because they will all be different.  For example, if the expense is an airfare, one consultant will pay one price and another a different price, etc. There is a Unit Cost on an Expense Claim. I am questioning why that Unit Cost does not show in the Project Transaction automatically created by releasing the Expense Claim.  This is a screenshot of the Expense Claim that created the Project Transaction (an AP PM).  The Unit Cost is pushed to the AP Bill, but not to the PM Transaction.

Here’s the AP Bill:

I think this may be a data or a mapping issue within Acumatica.

You have made a good point.  When considering Billable Quantity may be different from the Quantity on the transaction, the formula to calculate billable amount might look like this:

=([PMTran.Amount] / [PMTran.Qty]) * [PMTran.BillableQty]

What if the transaction has Zero quantity and only contains amount?  We may need an IF statement too, to avoid Divide by 0 error, something like:

If ([PMTran.Qty] <> 0,([PMTran.Amount] / [PMTran.Qty]) * [PMTran.BillableQty], [PMTran.Amount])

Laura