Prices not populating on an A/P invoice

SUGGESTED

If I try to create an A/P invoice for a part (without first opening a PO), then the default cost for that part won't automatically populate into the invoice.

We would enter parts directly in 4-2 if we had a quick order and wanted to skip the PO step (or if they didn't give us a PO# in the first place).

I would like the price to populate so that I can see if there are any changes to the cost of the item, because so far as I can tell that is the only way I will know if the vendor has changed the price.  Or am I missing something??  Shouldn't there be some sort of warning if the price of the item in the invoice (or PO) is changed from the default price? 

I tried setting the Over PO Warning, which works great if you receive the entire PO.  But if you only receive partial amounts, and even if those parts are now costing WAY over what your PO was, you may not get the warning if that partial total is still less than the original.  Kind of doesn't make any sense. You could have two items take up 99% of your total PO cost, and still have twenty items left on the PO, and you wouldn't get the warning.

Is there some way to set a "per part" overage warning... or to at least have the default price populate 4-2?  Any help would be appreciated!

Parents
  • 0
    SUGGESTED

    You are correct, adding a part # directly to an AP invoice without a PO does not bring in that part's default cost.  I don't believe the system was designed to that.  I can see how that could create issues with people skipping the PO field, or creating new invoices even though inventory receipts have been posted.

    Using parts on a 3-2 invoice does bring in the billing info.

    You didn't mention whether your company uses inventory.  

    As for Purchase Order tracking, the system's primary tracking is the qty field (not the price).  If get invoiced for a part at a different price than the PO, that invoice should not be processed until someone has approved the price variance.  This will then be reflected on a PO audit report.   Note:  The automatic close a PO feature works when all of the qty's have been received, not the price.  

    So if you have PO's where you only care about the total price and not the total quantity, then you might consider setting up those PO's a little differently.  You could set the quantity at the lump sum value, and then the price column would always be $1.00.  This would allow you to receive partial invoicing against the value, and still allow the system to technically be tracking the qty behind the scenes.  However, if you do, then you will need to create a custom PO form with those columns re-labeled when issuing lump sum PO's.  I recommend creating a PO type of lump sum for those instances, depending on how your PO types are structured.

    Hope this clarifies it for you.

Reply
  • 0
    SUGGESTED

    You are correct, adding a part # directly to an AP invoice without a PO does not bring in that part's default cost.  I don't believe the system was designed to that.  I can see how that could create issues with people skipping the PO field, or creating new invoices even though inventory receipts have been posted.

    Using parts on a 3-2 invoice does bring in the billing info.

    You didn't mention whether your company uses inventory.  

    As for Purchase Order tracking, the system's primary tracking is the qty field (not the price).  If get invoiced for a part at a different price than the PO, that invoice should not be processed until someone has approved the price variance.  This will then be reflected on a PO audit report.   Note:  The automatic close a PO feature works when all of the qty's have been received, not the price.  

    So if you have PO's where you only care about the total price and not the total quantity, then you might consider setting up those PO's a little differently.  You could set the quantity at the lump sum value, and then the price column would always be $1.00.  This would allow you to receive partial invoicing against the value, and still allow the system to technically be tracking the qty behind the scenes.  However, if you do, then you will need to create a custom PO form with those columns re-labeled when issuing lump sum PO's.  I recommend creating a PO type of lump sum for those instances, depending on how your PO types are structured.

    Hope this clarifies it for you.

Children
No Data