Methods for the City to identify, specify, and develop required custom City reports during the implementation. Integrations and Interfaces (Section 6.6) It is expected that information generally would need to be entered only once into the system. Modules within the system should be integrated in real-time with each other such that batch processes are not required to transfer information from one area of the system to another unless that is the preference of the City. Existing City interfaces between core modules that may currently exist (e.g., AP posting to GL) or shadow systems that will likely be replaced are not included as they are assumed to be included in an integrated ERP System. The following tables contain a listing of current and/or desired City application interfaces and their likely need in a future integrated software environment. Data Data Flow Source Target Currently Needed in Flow Description Application Application Exists new ERP Item Environment # 1 Send Positive Pay Accounts Bank of X X files to bank Payable Oklahoma 2 Yearly 1099 & W2 Accounts US Treasury X X submission Payable 3 Vendor Payment Accounts Bank of X X ACH file export / Payable Oklahoma import 4 Online Payments Authorize.net Cash Receipts X X 5 Upload/download Badger Utility Billing X X of read information 6 Import bank Bank of Bank X X statement Oklahoma Reconciliation electronic file 7 Daily lockbox Bank of Cash X X transfers Oklahoma Receipting / Miscellaneous Receivables / Utility Billing / General Ledger 8 Traffic citation Brazos Cash Receipts X X receivable status / General routed from Brazos Ledger to the ERP system to maintain a
Methods for the City to identify, specify, and develop required custom City reports during the implementation. Integrations and Interfaces (Section 6.6) It is expected that information generally would need to be entered only once into the system. Modules within the system should be integrated in real-time with each other such that batch processes are not required to transfer information from one area of the system to another unless that is the preference of the City. Existing City interfaces between core modules that may currently exist (e.g., AP posting to GL) or shadow systems that will likely be replaced are not included as they are assumed to be included in an integrated ERP System. The following tables contain a listing of current and/or desired City application interfaces and their likely need in a future integrated software environment. Data Flow Item # Data Flow Description Source Application Target Application Currently Exists Needed in new ERP Environment 1 Send Positive Pay files to bank Accounts Payable Bank of Oklahoma X X 2 Yearly 1099 & W2 submission Accounts Payable US Treasury X X 3 Vendor Payment ACH file export / import Accounts Payable Bank of Oklahoma X X 4 Online Payments Authorize.net Cash Receipts X X 5 Upload/download of read information Badger Utility Billing X X 6 Import bank statement electronic file Bank of Oklahoma Bank Reconciliation X X 7 Daily lockbox transfers Bank of Oklahoma Cash Receipting / Miscellaneous Receivables / Utility Billing / General Ledger X X 8 Traffic citation receivable status routed from Brazos to the ERP system to maintain a Brazos Cash Receipts / General Ledger X X
RFP%201617-24%20ERP%20Software%20Suite.docx