The Esquire Bank Document Compliance Automation helps ISOs accelerate the merchant boarding process.
Many ISOs submit compliance documents to Esquire Bank as part of their TSYS onboarding process through TurboApp.
In the past, administrators had to download the necessary data for the batch of merchants they were onboarding, reformat it to Esquire’s requirements for submission, and upload/submit the data manually to Esquire.
If the upload failed or there was an error in the data, they would need to review the entire batch of merchants, detect and fix the cause of the error, and resubmit the documentation to Esquire—once again, entirely manually.
With the Esquire Bank Document Compliance Automation, your CRM takes care of the hard work. No more manual effort, just seamless, automated submissions using data automatically transferred from TurboApp and/or the Lead as part of CRM’s streamlined boarding experience.
How It Works
To get started with the Esquire Bank Document Compliance Automation integration, reach out to our support team and ask for a setup of the Esquire Bank integration.
You will need SFTP credentials from Esquire Bank, as well as the field mappings to transfer the right data from your CRM to the proper places for Esquire Bank.
If you onboard merchants primarily through TurboApp, many of the mappings will be provided for you – but not all.
Two fields are unavailable through TurboApp and require the mappings from the lead page in IRIS CRM – Signer 1 Ownership Pct., and Signer 1 Guarantee (F37 and F52 in the Esquire Bank document).
Data is sourced directly from TurboApp via uploaded files such as an MPA, as well as the Corporate Information entered during the boarding process.
Below, you can see TurboApp’s Upload Files screen where agents and administrators upload merchant MPAs, Voided Checks, and any other additional documents to help with the underwriting process:
Additional merchant data is sourced through TurboApp’s Corporate Information section:
For merchants boarded outside of TurboApp, the data is sourced directly from the lead’s Business Information tab:
Once you are in touch with our support team, we will assist with getting any necessary fields mapped so that the data begins flowing smoothly as soon as possible.
After the integration setup gets completed, you will be able to view the status of your Esquire Bank documentation uploads in a dedicated UI.
Also, a daily task will run in your CRM to upload the proper documentation for the most recent batch of merchants. You can review the uploaded batches, easily identify the reasons for any failed batches, and re-upload documentation when requested by Esquire Bank in just a few clicks!
Esquire Application Uploads
The Esquire Application Uploads page is where you can view all of your batch uploads to Esquire.
A report table on the page shows the source and date range for each batch, along with the .txt file that was submitted to Esquire, the ZIP file with the MPA documents, how many records/merchants were uploaded in that batch, and the status.
You can preview the contents of the .txt file by clicking the small eye icon to the right of the text file name.
This feature enables you to quickly view exactly which merchants were submitted to Esquire Bank for that specific batch:
Here’s a view of the resulting popup:
Under the status column, you will see either Uploaded in green for a successful upload or Failed in red if the batch didn’t upload correctly:
To dive deeper into failed records, we provide a small button in the Records column which opens up a list of the records included in the specific batch:
Next to each record containing any errors, you will see a View X Errors button with X being the number of errors for that particular record:
One such error could be that no documents were found with the specific label.
Each MPA document needs to be assigned a specific label for Esquire in order to be included in the file upload.
If you receive this error, you need to head to the lead and ensure that the MPA documentation has the proper label for uploading to Esquire Bank.
There are a variety of errors that could trigger a Failed mark under Status. Required fields may not be filled out, certain data may not meet requirements, and more.
The Errors popup serves to inform your team of these errors so that they can be corrected and reuploaded to Esquire properly:
Keep in mind that, when re-uploading files that were not mapped through TurboApp, any changes to lead data for leads included in the upload will be reflected in the new submission.
Any files re-uploaded through TurboApp will be static because the data is mapped directly from TurboApp while, if onboarding outside of TurboApp, the data to send to Esquire Bank is mapped directly from the lead file itself.
If the record was deleted, it will not be included in the re-upload. This is also noted on the Esquire Application Uploads page in the tooltip at the top of the Actions column.
You’re able to re-upload the text file, the MPA zip file, or both – but only use this feature as requested by Esquire because otherwise it can cause complications and add unnecessary time to your merchant boarding process: