By using this website, you agree to our Terms of Use (click here)
We are on the verge of 2019.1 upgrade (annual upgrade from MYOB) and have a pretty serious issue with removal of amount fields from Purchase Receipts. We rely quite heavily on this feature for our standard business processes. Can anyone explain the logic behind this move and how the old functionality provided by Receipt Amount fields could be replicated? We currently can't use Unit Cost * Receipt Qty as in some instances Unit Cost doesn't not contain enough decimals to give the correct result.
They wanted to remove the financial aspect form what was supposed to be a warehouse document. (Page 89 - http://acumatica-builds.s3.amazonaws.com/builds/2018R2/PDF/AcumaticaERP_2018R2_ReleaseNotes.pdf ).
Personally, we suffered very much from this change and saw no benefits. On the one hand, it did not bother anyone that there were extra columns if they weren't adjusting the cost. On the other hand, if a last minute change or verification was required by a purchaser ( say the invoiced amount changed) they could make the change on the receipt directly.
Also, you can no longer create a purchase receipt directly in any currency other than base. This was not clear since we had some import scenarios running and they did not break , so it took time to figure out why our billing was off. Just a heads up.
The stupid thing is they called this change "Purchase Receipt Improvements" whereas for some it is a major step backwards. What it means for us is that the PO needs to be always updated to reflect any changes from delivery and because we have approvals enabled on purchases, if there are any discrepancies between PO and delivery, the PO needs to also get re-approved and the PO Receipt cannot be entered until that is done. So when goods arrive, if there's a discrepancy, the PO receipt cannot be entered immediately. This is stupid!!!
Thanks for the headsup about the currency issue. This will also impact us as well.
Yes, unfortunately for us it was backwards as well.
Good luck with the upgrade.
Grrrr, looks like maybe this was a casualty of Landed Costs getting their own financial document screen. Hopefully Acumatica can add this back in the future.
We had a similar problem because our purchasing team does some re-balancing on the receipt and had issues when the amount field was removed. We ended up adding a new TotalExtCost to the PurchaseReceipt and then a new unbound field on the poreceiptline with the following formula.
[PXUnboundFormula(typeof(Switch<Case<Where<POReceiptLine.tranCost, NotEqual<decimal0>>,
POReceiptLine.tranCost>,
decimal0>),
typeof(SumCalc<POReceiptExt.usrTotalExtCost>))]
@ryan-brown Were you able to add the vendors currency amount when it is different from base currency, or just base currency cost ?
We only use a base currency so we didn't get into scenarios for multiple currencies. Since you are defining the formula to calculate the total extended cost, you should be able to make it more complex to handle currencies.
I guess i can take the currency rate for the doc header, and calculate that.
thanks
I'm doing some testing in a 2019 R2 (19.203.0042) environment and it looks like they added the Unit Cost field back to the Purchase Receipts (PO302000) screen and I can change the value at time of receipt:
But, there is still a problem in that the Unit Cost field on the Bills and Adjustments (AP301000) screen is defaulting the value from the Unit Cost field on the Purchase Orders (PO301000) screen and not the Unit Cost field on the Purchase Receipts (PO302000) screen.
Here's a related Feedback Idea:
https://feedback.acumatica.com/ideas/ACU-I-2400
Also, the unit cost is editable only in Base currency. Meaning you can edit the PO receipt regardless of what currency the PO is in, but it will always just adjust by the base currency value.
I really hope they revert to the old way where users could simply edit the cost on the PO receipt in all cases.
I'm doing some testing in a 2019 R2 (19.203.0042) environment and it looks like they added the Unit Cost field back to the Purchase Receipts (PO302000) screen and I can change the value at time of receipt:
But, there is still a problem in that the Unit Cost field on the Bills and Adjustments (AP301000) screen is defaulting the value from the Unit Cost field on the Purchase Orders (PO301000) screen and not the Unit Cost field on the Purchase Receipts (PO302000) screen.
Here's a related Feedback Idea:
https://feedback.acumatica.com/ideas/ACU-I-2400
@timrodman Has there been a solution to your second point for 2020 R1? Our workflow has always been to change the unit cost on the purchase receipt. you are correct that it doesn't get carried to the Bill. It seems like with this version they want you to either update the cost on the PO or on the bill. The Accounts Payable Preferences reflect this, there used to be more options.
So I am just curious what AP users doing when there is a unit cost change?
Hi @richard
I apologize in advance for how long this became!
Our PO Receipts do not worry about the price. Though, this process will be even more effective if you put the new unit price into the Receipt. *It will make it so the adjustments on the back end don't happen.
(*I am making the assumption that it should work if the unit price you specify on PO Receipt flows into the IN Transaction created by the PO Receipt. You may want to run a test transaction to see what happens.)
We use a Purchase Price Variance (PPV) account. Our Purchase Order Preferences -> Purchase Price Variance Allocation is configured this way:
Setting Allocation mode to Inventory makes the system try its best to allocate the difference back into the Inventory item. Whatever it can't it places into the PPV account. The PPV account is configured via the Reason code. We use Avg costing.
Our process is this:
The PO does its best to accurately represent the unit cost as closely as possible to what it should be. Our receivers don't worry about the costs. Their role is to accurately input what has come in on what PO. When an invoice comes in, Purchasing will create the AP Bills off of the PO Receipt and adjust the price to match the Vendor's Invoice. If they need to argue with the Vendor, they do this before entering the Bill. They hand it to AP to verify and Release. If the Bill comes in before the receipt, they either hang onto it if it should be here soon, or Fwd. to AP to create a Prepayment.
If the price on AP is different than the PO, Acumatica will check the IN transaction and compare it to what the AP Bill says the unit cost should be. It will look at Qty on Hand and apply the difference in unit cost to as much as is on hand and then put the rest in the PPV account.
Cases:
#1)
0 On Hand, 10 Received, 10 On Hand when AP Released.
PO Unit Cost: $100, AP Unit Cost: $120
In this case, during the AP Bill Release, the system sees that there is On Hand Qty and enough to cover all of the Received Qty. It will create an IN Adjust and the final unit cost for the item will be $120, total for 10 would be $1200. IN Adjust impact is +$200 to Inventory from COGS.
#2)
10 On Hand, Avg Unit Cost is $100, 10 Received, 20 On Hand when AP Released.
PO Unit Cost: $100, AP Unit Cost: $120
In this case, during the AP Bill Release, the system sees that there is On Hand Qty and more than enough to cover all of the Received Qty. It will create an IN Adjust for the Qty on the AP Bill to change the Unit Price for that Qty to be $120. When cost is Averaged, the item's AvgCost would end up being $110 (10@100, 10@120) and the total for 20 would be $2200. IN Adjust impact is +$200 to Inventory from COGS.
#3)
0 On Hand, 10 Received, 5 On Hand when AP Released.
PO Unit Cost: $100, AP Unit Cost: $120
(5 units got sold or built into something else, etc. between when the Receipt was released and the AP Bill was released)
In this case, during the AP Bill Release, the system sees that there is some On Hand Qty, but not enough to cover all of the Received Qty. It will create an IN Adjust for the remaining Qty on Hand to change the Unit Price to $120. The leftover is sent into the PPV account. In the end, the Unit Cost will be $120 and the total will be $600. It would have begun with on hand avg cost of $100 and a qty of 5, total would have been $500. IN Adjust impact is +$100 to Inventory from COGS and +$100 to PPV from COGS.
#4)
0 On Hand, 10 Received, 0 On Hand when AP Released. (all of the units got sold or built into something else, etc.)
PO Unit Cost: $100, AP Unit Cost: $120
In this case, during the AP Bill Release, the system sees that there is no On Hand Qty. It will create an IN Adjust to send the difference into the PPV account. There will still be nothing on hand and no value in the warehouse. IN Adjust impact is +$200 to PPV from COGS.
I have tested these 4 scenarios and found that setting the Allocation Mode to Inventory causes this behavior, which is desired for our situation. I feel like if you have the capacity to adjust the PO Receipt to have the appropriate Unit Price, that your situations like Scenario #3 and #4 will not occur. You may have to update the AP Bill again with the correct price, but it will then be matched against the Receipt, so no variance would be found and the PPV would not need invoked. (I mentioned earlier, this is an assumption that should be tested, but I strongly feel the system would behave this way).
@wyatt-erp Thank you for the detailed response. It might be time for a process change. I will test these scenarios.
It was there in 2019.1. They need to revert PO Receipts, they're a mess now. We are still struggling with the 2019.1 upgrade.
@roycelithgo Are you just living without having the amount totals? Or did you find a solution? We just discovered this was missing when we updated today.
@richard We've been struggling with PO Receipts ever since they did this. So far no clear solution. I modified the PO Receipt report to put some amounts on that as a workaround. But there are still gaps in other places, particularly with foreign currency transactions.