Skip to main content

I’ve been digging into some freight margin details lately, and I noticed that some Drop-Shipment Shipments (that are really PO Receipts) have a Freight Cost that is hitting our ARTran table. Does anyone know how that is calculated and why Acumatica automatically applies that (mystery) cost to the Invoice? 
In our scenario, our Drop-Ship POs are truly not drop-ships, we are purchasing services from a vendor, not physical products. There is no freight cost associated to these receipts, so how/why is that calculated?

 

Can you show us a screenshot of the purchase receipt and bill?


@Jeff96 here’s the PO Receipt.

 


I can send you a Bill screenshot too, but I don’t see anywhere on the Receipt or Bill documents that mention freight at all. 


Can you send a screenshot of the totals tab on the order?


@Jeff96 


@Jeff96

Your freight cost is coming from the freight cost field on the SO. I’m guessing your setting on the Sales Order Preference Screen (SO101000) is to allocate it proportionately between the items on the order; that’s why it’s less on the invoice than on the SO since the invoice is only for half of the SO.

 

 

 


@Jeff96 the “Freight Allocation on Partial Shipping” is related to Freight Prices, not Costs. 
Also we have it set to “Full Amount First Time”. I’m concerned with Costs. 

Where is the $75.57 cost coming from on that Drop-Shipment PO Receipt? 
That shows up in our customer margins but is not applicable whatsoever. 


I guess I’ll add this to the list of acu-magical mysteries unless someone else has any thoughts?


Hi @max21 were you able to find a solution? Thank you!


@Chris Hackett not yet. Acumatica support has been investigating for several weeks but nothing yet. 


Hi @max21  is there an update on this from Acumatica Support? 


@max21 -  Hi Max, can you please direct message me, the customer support case#?  

thanks,

Dana


Sorry for the delay — yes Acumatica support got back to me. 
They said that a change request is reported to our analyst team to correct this issue.

They suggested two workarounds that unfortunately weren’t applicable/possible based on our situation. 

@Dana Moffat case #344071


I’ll message to the case about your feedback about the workarounds.


Hi @max21 , just wanted to let you know that there is now a change request with the development team. 


@Dana Moffat - do you have an ETA on this?  I don’t see it on the list of known issues.


Reply