APUB - POPAID

Mandate Receiving
Attempts to process payables without a record of receipt will generate a message: either a warning or block. Accounts Payable will not be able to pull PO information unless PO receiving information exists for the given Purchase Order. 

Code Category: APUB

Code Value: POPAID

Short Description: Enter "ON" to block, or "OFF" to deactivate the block. "OFF" postpones the validation of receiving details until proofing the set or invoice(s). Note that the system will always warn unless this description is "ON" to block. If payables are blocked pending receiving, PO items will need to be retroactively received within the PO Receiving (POUPRC) page by an authorized user.

Medium Description: Used to describe the common code.

Long Description: Used to describe the common code.

Associated Numeric Values

1-5: Reserved for future use.

Associated Codes

1: PO type: Limit the receiving mandate to specific PO types or all. Enter the PO type(s) desired in alpha order, and, if selecting multiple types, separate codes using a comma.  PO types are static codes found on the PO Purchase Requests (POUPPR) page within the Details tab.

PO types listed alpha order:

• (blank) - All four PO types will require receiving

• B - Blanket

• C - Contract (Amount)

• P - Standard

• T - Contract (Line Item)

• B,C,T - Blanket, Type C (Amount) and T (Line Item) Contracts

• B,P, - Blanket and Standard

• C,P,T - Type C (Amount) Contract, Standard, and Type T (Line Item) Contract

• B,C,P,T - All four PO Types will require receiving

NU Common Code APBP/POEXCEPTAPBP - POEXCEPTborrows this code's PO Type setup to report exceptions on Set proofs and posting reports.

2: Requisition Codes: Enter the user-defined requisition code that was applied to the purchase order if receiving is needed. For example, "RR" will require receiving for Purchase Orders that contain the requisition code of "RR"). Requisition Codes are added to PO Purchase Requests page on the Req. Codes tab. Requisition Codes are defined in the NU Common Code page with a code category/value of PORC/XX.

3: Association Codes: Association Codes modify PO Types "C" (Contract) for tracking, reporting, or internal purposes. For example, entering "RTPER" requires only items containing the Association Code of "RTPER" be received. Add an Association Code within the Association Codes tab on the PO Purchase Requests (POUPPR) page. Association Codes are defined on the NU Common Codes page with a code category/value of POAS/XXXXXXXX.

4: Fixed Assets: Enter "Y" or "FA" to require receiving for Fixed Assets; use only if using PO to FA interface (AP to FA migration will not enforce this feature as assets are defined in the FA Potential Asset (FAUPPA) page, not POUPRC).

5: Reserved for future use.

Associated Descriptions

1-5: Reserved for future use. Used to describe the Associated Codes. 

The system may display a brief warning (or block when APUB/POPAID is actively blocking) when using PO Extract that says, "No receiving records found; displaying all items. (OH41)." This message is not related to this common code. Also note that the system will always verify an invoice number is unique unless APOHUPGNDuplicate Invoice setting is "N" for that working ledger.