Process flow

This sequence is followed when you run the Bank Statement Scanning solution in RPA:

1. Bank statement attachments are automatically identified and downloaded from two preconfigured sources:
   • Outlook folder: Only unread emails are scanned to extract attachments.
   • Local drive folder: All files within the specified folder are processed.
2. Key financial data is extracted from the attachments through Optical Character Recognition (OCR).

   This table shows the key financial values:

   Note: If the items with asterisk are not read by OCR, the process fails.

   Key value	Description	Sample value
   Bank Identifier*	IBAN / BABN/ Bank Account Number	ABCD12345
   Invoice Number	Serial number of the invoice	000123
   Statement Number*	Bank Statement Number	BS12345678
   Opening Balance	Opening Balance Amount	100
   Opening Balance Type	Type of transaction	Debit, Credit
   OB Date*	Opening Balance Date	2025-02-26
   Closing Balance	Closing Balance Amount	100
   Closing Balance Type	Type of transaction	Debit, Credit
   CB Date*	Closing Balance Date	2025-02-26
   Currency	Statement Currency	USD
   Total Credit	Total Amount Credit	100
   Total Debit	Total Amount Debit	100
   Transaction Date	Line level transaction date	2025-02-26
   Transaction Summary	Line level transaction Summary	Cheque 001
   Transaction Value	Line Level transaction Value	100
   Transaction Type	Type of transaction	Debit, Credit

3. The availability of the bank identifier is verified in M3 by using the Infor ION API (ABS100MI).

   If the bank identifier is not available in M3, the process stops, and the file is saved to the Failed folder of your local configuration folder.

4. If the bank identifier is available, these details are extracted through the API (ABS100MI) with a GetBankIdent2 transaction:
   • Company
   • Division
   • Bank statement type
   • Bank statement number
5. The extracted file data and the details retrieved through API are used to prepare BOD (Load.bankstatement), then processed in ION.
6. Documents processed by the system are uploaded to Infor Document Management (IDM) under M3_BankStatement document type and linked to corresponding records in ABS100 through a Correlation ID. These items are supported:
   • Seamless traceability between processed data and source documents.
   • Improved auditability and document lifecycle management.
   Note: You can use the Related Information widget in M3 to view the full attached document from IDM directly in the contextual panel.
7. Upon a successful job run, subfolders are created in your local configuration folder.

   This table shows the subfolders:

   Folder	Description
   Failure	Contains bank statement files that failed to process. These factors can be the reason for failure: File type is not supported. Bank Identifier is not available in M3. Issues encountered while sending BOD to IMS API. File is unreadable due to formatting or corruption issues. If an email contains multiple files and one of them is corrupted, all files are not processed. These items are not read by the Optical Character Recognition (OCR): Bank Identifier Bank Statement Number. If the number type is set as 1-According to Bank Opening Balance Date Closing Balance Date
   InProgress	Contains bank statement files that are currently being processed.
   Logs	Stores all log information.
   Success	Contains bank statement files that are successfully processed.

8. If the BOD processing is successful, these items are completed:
   • A bank statement is created in 'Bank Statement. Open' (ABS100).
   • The original attachment is saved in the Success folder of your local configuration folder.
9. After the RPA process is completed, a notification is sent to the OS Portal inbox and email of the designated user or user group.