Laserfiche WebLink
<br />Revised 8/7/06 City of Louisville <br /> Purchasing Policy & Purchasing Card Program Requirements <br />SECTION VII - RECEIVING PROCEDURES AND CHECK REQUESTS <br />Receivinq Procedures: <br />1. It shall be the responsibility of the receiving department/division to ensure that goods and <br /> services are received as ordered and in good condition. Upon receipt of merchandise, <br /> check quantity, quality, and any specifications such as model number, etc. to ensure that <br /> the goods have been received as indicated on the packing slip and as ordered on the <br /> Purchase Order. <br />2. If the goods are faulty or damaged, notify the vendor and Accounts Payable immediately. <br /> If damage is concealed or not noticed at time of delivery, leave all boxes and packing lists <br /> intact and notify vendor immediately. <br />3. It shall be the responsibility of the receiving department/division to inform Accounts <br /> Payable of the delivery and acceptance of an order by submitting the receiving <br /> documents with the check request for payment. <br />4. It shall be the responsibility of the receiving department/division to inform Accounts <br /> payable when full or partial payments are authorized. <br />5. All invoices shall be mailed by the vendor directly to the purchasing department. <br />6. The receiving department shall be responsible for notifying the vendor of any goods <br /> received that are not in compliance with the terms of the Purchase Order and any <br /> damaged goods. <br />7. Receiving documents must be signed off by a departmental manager. <br />Check Requests: <br />Check request forms are used to request payment for materials or services. Check requests will <br />be granted on the following circumstances: <br /> . Checks will be cut in accordance with the Accounts Payable schedule <br /> . Original invoice must be attached <br /> . All receiving documents must be attached <br /> . All requests must be signed by the department director and Finance <br /> . P.O. must be referenced if applicable <br />Effective September 1, 2006 14 <br />