Fintech provides Vendor statements via FTP to Restaurant365. These service statements, which include both charges and refunds, are recognized as invoices in Restaurant365. Below, review the steps of integration, the mapping of a Fintech file to an AP Invoice, and recent updates to this process.



Integration


Once you have created your FTP Site, contact your Fintech Support Representative to notify them that your organization would like to receive their invoices via your FTP site. 



Fintech File to AP Invoice


Fintech files are compatible with Restaurant365 and will directly import as individual AP Invoices when received in the system. While more columns are included in a Fintech file, view how the key columns are mapped to an AP Invoice below.





A) Vendor Name - The name of the Vendor your organization is receiving the items from

B) Retailer Name - The name of the restaurant Location receiving these items

C) Retailer Store Number - The number associated with the restaurant Location. This is an assigned number on the Location record

D) Fintech Process Date - The date Fintech processed the invoice. This is not displayed in the AP Invoice screenshot

E) Invoice Date - Also called 'Document Date', this is the date noted on the top of the invoice

F) Invoice Due Date - The date this invoice needs to be paid

G) Invoice Number - The number associated with the invoice. Even though one file may contain more than one invoice number, individual invoices will be created upon import

H) Invoice Amount - Also called the 'Document Amount', this is the total amount due for the items on the invoice

I) Invoice Item Count - This is the total amount of items requested for the invoice. This is not displayed in the AP Invoice screenshot

J) Product Number - Also called the 'Vendor Item', this is the item number associated with the item

K) Quantity - Noted on the invoice as 'Qty', this is the amount of each U of M bought for the invoice

L) Invoice Line Item Cost - Also called 'Each Amount', this is the cost of one U of M of the item

M) Unit of Measure - The manner in which this item is measured. The Fintech file displays Fintech's U of M while the AP Invoice displays the U of M equivalence as setup in R365

N) Product Volume - The volume of the line item. This is not displayed in the AP Invoice screenshot

O) Case UPC - This is the Universal Product Code per case. This is not displayed in the AP Invoice screenshot

P) Product Description - Also called 'Item', this is the description of the item as noted on the invoice and saved in R365

Q) Extended Price - The total price of the line item (Quantity x Invoice Line Item Cost)

R) Packs Per Case - The amount of packs included in one case



Reasons for Failed Imports


One file contains multiple invoices, so when an invoice is rejected for import, it will often reject all of the invoices with it. The file will then be placed in the 'Error Log' until the necessary invoice is corrected and the whole file is processed successfully. The only time this occurs differently is when Invoice A is a duplicate and Invoice B is unique. Invoice B will be processed while Invoice A will then fail as a duplicate. 




The way to check if this is the case is to login to your FTP site, navigate to the error directory in the R365 folder, and view the html error message that is displayed above the file.