Running the solution if using folders

Create the chequesFolderPath check folder from the user parameter section.
To start the process, click the Run button to trigger the flow. When the flow is triggered, all documents in the check folder are read.
When the process is triggered, these RPA tasks are performed in the background:
1. Verifies that the ConfigurationFolder exists.
  
  If it does not exist, a directory and subdirectories are created. If the Configuration folder exists, this step is skipped.
2. Accesses the Email Account of the user from the emailAccount user parameter value, and finds the specified emailFolder to download all the unread emails and to process it.
3. Accesses the documents in local Checks folder that is specified in the chequesFolderPath user parameter value.
  - You must provide the details of the email account that is configured in the current system.
  - RPA processes attachments that contain only these formats: PDF, JPG, and PNG.
  - Emails are read based on the numberOfEmails user parameter value.
4. After the attachments are downloaded, all documents are moved to the InProgress folder.
5. This information is extracted from the Document Processor optical character recognition (IDP OCR):
  - Company (Payee name & address)*
  - Customer (Pay to the order of)*
  - Amount box*
  - Amount line
  - Bank information
  - Memo line
  - Rank routing number
  - Checking account number
  - Check number*
  - Bank fractional
  - Payer signature
6. If the remittance advice is received, it must be scanned for these details. The remittance advice contains the invoice numbers that are included in the payment.
  - Check date
  - Check number
  - Invoice date
  - Invoice number
  - Amount
7. The extracted data is verified and validated against predefined criteria to verify accuracy. Sometimes it involves companies and customers that are present in the FSM database and validates discrepancies or errors in the data, and the amount in words with amount in figures. If the data do not match, you are notified.
8. The extracted data is passed on to the RPA bot as input, which creates the Document Payment Interface record. This process results in the creation of Receivable Payments in FSM.
9. The document is uploaded to IDM and attached to the Document Payment Interface record. The user can view the document in the in-context widget called Related Information, and an IDM link is available on the Document Payment Interface screen. When the Document Payment Interface record is interfaced, the IDM attachment is also interfaced into the Receivables Payment.
10. A a success or failure notification is sent to your inbox and your email.