Oh, you don't have to tell me. There is / are the extra step(s) while on loading and EOS time. Then, the extra step of taking a pic. of the parcel. Now, there is the extra step in the scenario you have explained. Make no mistake, this is NOT and will NOT be the last extra step we encounter. The PO has , since the inception of carrier pickup scanner documentation, used a benchmarking practice / technique to limit our credit for this task. That's why it cuts us off at 5 parcels. The original language in Pub. 399 stated , " It is not required that the carrier scan each piece if a large quantity of parcels ( 6 or more ) are being picked up." You'll notice that this does not state "prohibited from" or "must not" . Only "not required". Doesn't mean we can't. Kinda' like we are not required to go to the door with a parcel that will fit in the box but WE CAN. And, we are not required to go to the door with a postage due that will fit in the box but WE CAN. All of this rhetoric regarding "scanning integrity" is just that. Hollow words. Yeah, I know many carriers scan as prepaid acceptance while on EOS to account for the parcels as well as increase their actual time through EOS. The thing is this, the customer's insurance doesn't take effect until the parcel is scanned as picked up. One of these days, after a carrier picked up a customer's 10 parcels, that customer is going to check into their pickup and wonder why only 5 of their parcels were scanned as picked up. And they are going to complain. Now, the carrier can do the other 5 as prepaid on the street and the insurance and all of that is good to go. But, that carrier is being shorted on the actual RRECS standard for carrier pickup items because the PO benchmarked / limited the number to 5 under the correct and accurate function. The PO wants the business but they don't want to pay for it. We do need proactive , aggressive, and expeditious representation on all of this. This "wait and see" , "after the damage / harm has been inflicted" , "only if the carrier recorded / documented " , etc. is NOT the way to handle any of this.