Amendments to Professional Services Agreement - Reductions and Expansions to Scope of ERP System

Home Browse Search

3. Invoice Journals from enQuesta (Utility Billing) Source: enQuesta Target: Dynamics 365, Accounts Payable Frequency: As needed Direction of Integration: One-way Summary: The City needs the ability to send Invoice Journals from their new utility billing system (enQuesta) to Dynamics to be processed and paid. Below is a summary of the expected interface: • Crowe assumes that the City will provide a flat file that will conform to the Dynamics format. • Crowe assumes that no mapping tables are required in Dynamics. Crowe assumes all values in the flat file will match applicable values in Dynamics. • Crowe will develop an interface that passes invoice transactions from enQuesta to Dynamics 365 as an AP Invoice Journal within Dynamics. • Crowe assumes that enQuesta will send Dynamics 365 the following information: Valid vendor ID, Invoice ID, method of payment, transaction date, quantity, unit price, remittance information, and all applicable accounting information (valid account segment values). • Crowe will write additional logic in the interface to systematically create a new vendor in Dynamics if a new vendor ID comes over from enQuesta that doesn't exist in Dynamics. Note: It is assumed that the enQuesta file will include the vendor remit -to addresses, method of payment, and payment terms. Please note, Crowe will treat this as one interface. • This interface will be implemented after cutover. Crowe and the City will mutually agree on the timing of implementing this interface — based on the timing of the City's enQuesta implementation. Please note, it is anticipated that this interface will leverage some of the code developed for interface #2 above (Inventory Invoice Journals from Faster to Dynamics 365. It is also assumed that the Faster interface will be developed and implemented before the one with enQuesta. Should the enQuesta interface be implemented first, we would flip the costs associated with Interfaces #2 and #3. 3. Assumptions: 1. The City will make resources available to assist in the development and testing of any changes that were added to scope. 2. The City will make resources available to review and approve the functional designs associated with the new changes being added to scope. 3. It is assumed that the new interfaces included in this SOW will be delivered post cutover. Crowe and the City will work together to determine the timing. It is assumed that the fixed asset customization will be delivered by the end of conference room pilot so it can be tested prior to cutover. The City will communicate the timing of the changes to all functional area owners impacted. 4. City functional area owners will be responsible for signing off on their respective changes at the end of conference room pilot testing (or after cutover, if the item will be delivered post- cutover). Crowe Page 5