Process flow

This sequence outlines the process flow:
  1. Extract invoices and receipts.
    1. In 'Acc Receivable Display' (ARS200) program in M3, add the Unallocated_Receipts H5 script as a button.
    2. To start the process, click the Unallocated_Receipts button.
    3. Select the bank identifier to use for payment receipt creation. Then, click OK.

      The script uses the ARS200MI API to verify payment receipts and invoices. The process continues only if both payment receipts and invoices exist; otherwise, the process stops.

      After successful validation, the script triggers the M3UnallocatedReceiptsOnDemand process in RPA.

      1. RPA uses ARS200MI to retrieve data related to open invoices and unallocated receipts for the selected payer. Unallocated receipts may be identified as credit notes, on account payments, etc.
      2. Data is exported and formatted into Excel.

        Creates a separate section to list invoices and unallocated receipts.

      3. RPA retrieves the payer’s email address using the API CRS111MI.
      4. The Excel file is emailed to the payer. Text document uploaded to IDM containing the email body information, along with the respective PID configured in the script arguments, is retrieved and used as the email body for the customer mail.

        A copy of the sent attachment in Excel is stored in IDM.

      5. Infor OS and email notifications are sent.
  2. Customer matches payment receipts against invoices and replies with the updated Excel file.
    1. A customer manually matches the unallocated receipts to the corresponding invoices with these details:
      • Invoice number
      • Matched amount
    2. Updated file is attached and sent.
  3. Run the M3UnallocatedCashReceipts process in RPA using either attended or unattended mode. During the process, RPA reads the customer response from email, extracts the required values, and uses them to create a bank statement in M3.
  4. RPA populates the Load.bankstatement BOD with this information:
    • Bank identifier
    • Invoice numbers and amounts
    • Currency
    • Payment date
    • Correlation ID
  5. The BOD is published to Infor M3 and payment receipts are created (ABS100).
  6. All inbound customer documents are saved in IDM.
  7. Infor OS and email status notifications are sent to defined user or group.