Req to Check Documentation

dechevar

Does anyone have standard operating procedures for a buyer they are willing to share? We lost a lot of our internal knowledge and I am finding that the documentation created for training 3 years ago does not address the needs. I just recently found out that we haven't been reviewing the PO136 because the buyers were never trained.

I am looking for documentation around the following reports and who should be responsible for managing them (AP or Purchasing):

PO135 - RNI Received Not Invoiced
PO136 - MNR Matched Not Received
MA126 - Auto Match
MA236 - INR Invoiced Not Received
PO278 - RNI Aging Report
PO254 - PO Inquiry Repot
PO231 - Return Status Report
PO222 - Remaining PO Balance Report
AP252 - Unmatched Invoice Listing
MA231 - Unmatched Receipt Listing

Any assistance would be greatly appreciated.

Dan

jon-athey

I don't have any official documentation but I can tell you who reviews each report at MidMichigan.

PO135 - RNI Received Not Invoiced (Buyers and AP, but the buyers use a Crystal report that mimics PO135 but arranges the data the way we want it.)
PO136 - MNR Matched Not Received (Buyers)
MA126 - Auto Match (AP)
MA236 - INR Invoiced Not Received (Buyers)
PO278 - RNI Aging Report (Finance, but we have a Crystal report for the buyers to review as well)
PO254 - PO Inquiry Report (Used by anyone that needs the info)
PO231 - Return Status Report (Buyers and AP)
PO222 - Remaining PO Balance Report (not used)
AP252 - Unmatched Invoice Listing (AP)
MA231 - Unmatched Receipt Listing (not used; same info as PO135?)

We also have Crystal report that mimics PO223 and MA236 that is worked regularly by the buyers. We look at PO lines that are 10 or more days past the delivery date and shows whether there's an unmatched invoice entered against the PO line.

To be honest, only PO223 and PO135 are worked proactively. We're more reactive with the others when it becomes an issue. Coincidentally, we just began an effort to bring INR down last week because it was getting out of hand.