My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council Work Session - 07/25/2017
Ramsey
>
Public
>
Agendas
>
Council Work Session
>
2017
>
Agenda - Council Work Session - 07/25/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2025 3:36:32 PM
Creation date
7/21/2017 8:39:01 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council Work Session
Document Date
07/25/2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
The City of Ramsey uses various processes in making payments for goods and services. <br />(1) Standard purchase orders. Purchase orders are used when required by the vendor to <br />acknowledge the city's request for goods and services. A copy of the purchase order will be sent <br />to the vendor when requested. <br />a. Obtain purchase order numbers from finance department. <br />b. The completed purchase order will be attached when invoice is received and submitted to <br />respective department to authorize payment. <br />(2) Check requests/immediate pay. The finance department policy is for bills to be paid from the <br />accounts payable bills list submitted bi-weekly to city council for approval. For certain exceptions, <br />check requests/immediate pay may be used under the following guidelines: <br />a. Immediate pay is for payments that need to be made prior to council meeting approval date. <br />Such items include taking advantage of discounts, avoiding late charges, purchases <br />requiring payment with order, etc. <br />b. Immediate pay checks will be issued upon one day notice. Exceptions to the one day notice <br />is for investments and emergency purchases. <br />c. Checks will be issued, mailed, or returned to appropriate department. <br />Invoices. Invoices, purchase order, or expense reimbursement forms must be returned to the <br />finance department with proper authorization and account coding to be processed on the bills list <br />for city council approval. <br />(4) Account coding. All requests for payment including invoices, check request, purchase order, or <br />expense reimbursement forms must have an eight digit code to process payment. Responsible <br />department head will indicate the fund/department and object number from which payment will <br />be expensed. Reference should be made to departmental budget(s) for department and object <br />numbers. <br />(3) <br />(5) Petty cash. <br />a. Receptionist shall be the custodian of the petty cash. <br />b. Petty cash shall not exceed $100.00. <br />c. Used for reimbursement to employees for items $20.00 or less for expenditures made on <br />behalf of the city. <br />d. Receipt and/or expense reimbursement form must be submitted with proper departmental <br />authorization obtained prior to reimbursement. <br />(6) Payment processing. <br />a. Invoices, check request, purchase orders or employee expense reimbursement forms must <br />be submitted to the finance department. <br />b. Detailed receipts, stating reason for public purpose expenditure, must be submitted with <br />employee expense reimbursement forms. <br />c. Immediate pays are due to the finance department at least one day in advance of the <br />payment day. <br />d. Department heads must have fund/department and object codes to process payment. Refer <br />to departmental line item budget for proper coding. <br />e. Checks may not be made out to cash or bearer. <br />(7) Electronic funds transfer. Electronic funds transfer may be required in some cases to complete a <br />business transaction. The funds are transferred electronically between the city's bank account <br />and the respective business party's bank account. <br />Page 8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.