Overview
Our Fintech integration allows you to receive EDI invoice documents for each vendor configured in your Fintech portal. This article will cover how to prepare each vendor's supplier settings in Cloud Retailer.
Procedure
- Log into your back office
- Navigate to Admin > Supplier
- Search for the supplier you want to add to your Fintech integration
- Double-click on the supplier or click and edit the supplier by clicking on the "Edit Selected Supplier(s)" button
- Under Supplier Documents Settings, change the file type to Edi
- Enter the Vendor Id code that Fintech assigned to the supplier in the Vendor Id Number text box
- Note: You can change the Vendor Id in your Fintech portal, just make sure the values match in both systems
- Save the supplier

Setting the Imported Kind
This setting is only available in version 4.12.54 or later. If you do not have this setting, and would like to use it, please contact support@cloudretailer.com to request an update.
There are times when you want some EDI invoice documents to be loaded into Cloud Retailer as a "Regular" purchase order, which lets you receive against and commit the values to inventory, or an "Invoice" purchase order, which lets you compare what was billed with a matching "Regular" purchase order (3-way matching).
Let's look at an example where the purchase orders created from Fintech documents will create "Regular" purchase orders. If your Fintech supplier is configured like the image below:

And your supplier is configured like the image below:

You'll notice in the second image that the "Imported kind" is set to "Invoice", but since the "Use matched kind" setting is disabled, all POs created for Wine Merchants will be a "Regular" PO.
If you want POs for Wine Merchants to be an "Invoice", simply check the "Use matched kind" checkbox, and the system will set the PO's kind to "Invoice" when a PO for Wine Merchants is created from a Fintech document.

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article