RavenClaw
Occasional Member - Level 3

PO Controls

Hi Fab Folks,

 

Got few questions regarding the Invoice module capabilites. I have checked the Admin guides, and KB but nothing seems to satisfy our requirement. Appreciate if some can share their knowledge and best practices. Here are the questions - related to controls and adoption mainly:

1. We wanted to drive users when creating a Purchase Request or PO to not raise a blanket PO and make sure to create appropriate line items. Since our POs do not expire, it's being reused and being uncontrolled (overconsumption). This should be fine as long as there are line items added accordingly for each PO. Now, is there a way to put an expiration to a PO? And can I set conditions for an expiring PO as an Admin?

2. Could we enforce an Additional level of Control for Goods received in the PO Matching Rule? This way the approvers and business can take ownership? Or some sort of a flag or indicator in the system?

 

 

Thanks as always!

1 Solution
Solution
PoojaKumatkar
Super User
Super User

Hi @RavenClaw ,

 

Please find my response below:

 

1. As per my understanding, there is no standard option to set an expiration date for a PO. Even if a custom field is used to capture an expiration date, the system does not provide any control or restriction on the PO based on that date.

Instead, you may consider using the standard system functionality to close the PO. Once a PO is closed by the Purchase Order Processor, users will no longer be able to reference or use that PO on invoices.

 

Attaching settings screenshot for your understanding purposes:

PoojaKumatkar_0-1770709392389.png

Sample screenshot:

PoojaKumatkar_1-1770709426124.png

PoojaKumatkar_2-1770709441036.png


2. Could we enforce an Additional level of Control for Goods received in the PO Matching Rule? This way the approvers and business can take ownership? Or some sort of a flag or indicator in the system?

Pooja - In matching rule section, there is not a much scope for customization. Maximum we can setup some threshold (%) for certain fields such as unit price/quantity/total amount etc. and accordingly warning/hard stop msg can be triggered.

 

If my understanding about your query is wrong then please feel free to provide some example and expected result so that I would be able to understand the scenario and able to guide accordingly.

 

 

If this answers your query, then please mark solution as accepted.

Thanks!
Regards,
Pooja

View solution in original post

2 REPLIES 2
Solution
PoojaKumatkar
Super User
Super User

Hi @RavenClaw ,

 

Please find my response below:

 

1. As per my understanding, there is no standard option to set an expiration date for a PO. Even if a custom field is used to capture an expiration date, the system does not provide any control or restriction on the PO based on that date.

Instead, you may consider using the standard system functionality to close the PO. Once a PO is closed by the Purchase Order Processor, users will no longer be able to reference or use that PO on invoices.

 

Attaching settings screenshot for your understanding purposes:

PoojaKumatkar_0-1770709392389.png

Sample screenshot:

PoojaKumatkar_1-1770709426124.png

PoojaKumatkar_2-1770709441036.png


2. Could we enforce an Additional level of Control for Goods received in the PO Matching Rule? This way the approvers and business can take ownership? Or some sort of a flag or indicator in the system?

Pooja - In matching rule section, there is not a much scope for customization. Maximum we can setup some threshold (%) for certain fields such as unit price/quantity/total amount etc. and accordingly warning/hard stop msg can be triggered.

 

If my understanding about your query is wrong then please feel free to provide some example and expected result so that I would be able to understand the scenario and able to guide accordingly.

 

 

If this answers your query, then please mark solution as accepted.

Thanks!
Regards,
Pooja
RavenClaw
Occasional Member - Level 3

Appreciate your time and sharing your thoughts into this @PoojaKumatkar ! 🙂