Process flow for Customer Remittance Advice

This is the process flow for Customer Remittance:

  1. Customer sends payment allocation document in the form of PDF to the user with remittance details and the PDF can be stored in a local folder.
  2. The RPA monitors the configured email account and folder, and set the email as read after processing.
  3. The email moved to ProcessedEmailFolder if processing is succeeded.
    Note: If the processing is failed, the email is moved to UnProcessedEmailFolder.
  4. The PDFs are uploaded to Infor Document Management (IDM).
  5. The OCR extracts header level and line level details using the IDP GEN AI.
    Note: If the extraction is succeeded, RPA generates the Process.CustomerRemittanceAdvice BOD using the IMS endpoint.
  6. The BOD is sent to the Remittance Advices (tfcmg0121m000) session and LN responds with an Acknowledge.CustomerRemittanceAdvice as a confirmation. The automation supports remittance creation with both header and line details.
  7. The scanned PDF is uploaded to IDM. The users can access this PDF for in-context information.
  8. RPA validates for missing information. If the information is missing, user is notified through inbox alert and email with a drill-back link to IDM.
    Note: User can manually specify remittance in LN or modify the PDF and reprocess if processing is failed.
  9. The remittance is created in LN and the user is notified through inbox alert and email if the processing is succeeded.
    Note: If LN rejects the BOD, a Confirm BOD is received in ION, and the user is notified through inbox alert and email.
Note: 
  • The bank account details must be specified for the Pay-by-BP.
  • The BOD is generated only if the PDF includes information related to Payer Name, Payment Date, Invoice Number, Amount and Bank Account. If the required details are specified, RPA sends the BOD to LN.
  • The Remittance is created only if LN master data is configured.