Laserfiche WebLink
Interface Descriptions <br />1. Dynamics Vendors to Faster (for Inventory Purchases) <br />Source: Dynamics 365 <br />Target: Faster <br />Frequency: As needed <br />Direction of Integration: One-way <br />Summary: The City needs the ability to integrate vendor information from <br />Dynamics 365 to Faster. This is needed to support purchasing <br />processes that will be performed in Faster. <br />Below is a summary of the expected interface: <br />• Crowe assumes that the vendor export file from Dynamics to Faster will be three flat <br />files. <br />• Crowe assumes that no mapping tables are required in Dynamics. Crowe assumes <br />that Faster will accept all values in the flat file from Dynamics. <br />• Crowe assumes that vendor information, vendor addresses, and vendor contact <br />information will be included in the flat file interface. <br />• Crowe assumes that the interface will flag inactivated vendors for Faster. <br />• Crowe assumes that the interface will pass a complete list of all vendors, vendor <br />addresses, and vendor contacts. <br />• This interface will be implemented after cutover. Crowe and the City will mutually <br />agree on the timing of implementing this interface — based on the timing of the City's <br />Faster implementation. <br />2. Inventory Invoice Journals from Faster to Dynamics 365 (Fleet management) <br />Source: Faster <br />Target: Dynamics 365, Accounts Payable <br />Frequency: As needed <br />Direction of Integration: One-way <br />Summary: The City needs the ability send Invoice Journals from their fleet <br />management system (Faster) to Dynamics to be processed and paid. <br />Below is a summary of the expected interface: <br />• Crowe assumes that the City will provide a flat file that will conform to the Dynamics <br />format. <br />• Crowe assumes that no mapping tables are required in Dynamics. Crowe assumes <br />all values in the flat file will match applicable values in Dynamics. <br />• Crowe will develop an interface that passes invoice transactions from Faster to <br />Dynamics 365 as an AP Invoice Journal within Dynamics. <br />• Crowe assumes that Faster will send Dynamics 365 the following information: Valid <br />vendor ID, Invoice ID, method of payment, transaction date, quantity, unit price, remittance <br />information, and all applicable accounting information (valid account segment values). <br />• This interface will be implemented after cutover. Crowe and the City will mutually <br />agree on the timing of implementing this interface — based on the timing of the City's <br />Faster implementation. <br />Crowe <br />Page 4 <br />