Bill of Lading Digitization

The M3 Bill of Lading Digitization 2.0 solution is an enterprise automation tool that uses Infor Robotic Process Automation (RPA) to address the challenges of manually processing signed Bill of Lading documents. It automates the collection of signed and scanned Bill of Lading documents from a designated file folder, extracts relevant document attributes, and uploads the scanned documents to Infor Document Management (IDM). By storing these documents in IDM, the solution provides streamlined navigation for customer inquiries, therefore enhances operational efficiency, reduces errors, and eliminates the need for manual intervention.

In a normal setup, a chief financial officer for example, may encounter this process:

  1. The customer signs the paper Bill of Lading document upon receipt.
  2. The signed document is scanned at a recommended resolution of 300 DPI and saved as a PDF in a shared folder.
  3. Store signed receipts digitally using M3 Bill of Lading Digitization 2.0 solution. To do this, start the RPA process called M3BillOfLadingDigitization_2_0 in the Infor RPA Assistant.
    1. The RPA collects the PDF files from the shared folder and extract information including the Bill of Lading numbers.
    2. The same files are uploaded to Infor Document Management (IDM) with Document Type set as Bill of Lading (M3_BOL), along with other relevant attribute values.
      Note: If a PDF file contains several Bill of Lading numbers, the file is divided to ensure each PDF contains only one Bill of Lading number.
    3. After the process is completed, assigned users or user groups receive an ION Notification in the M3 Inbox with the results, including success and failure counts.

The latest version of M3 Bill of Lading Digitization introduces AI-powered data extraction using Infor Document Processor (IDP) flows for improved accuracy, and native RPA activities for splitting and merging PDFs to enhance compatibility and ease of maintenance. Logging and error handling are also improved, offering configurable log levels and clearer feedback for both attended and unattended modes.

You can run this solution in unattended or attended mode. Unattended mode is remote while attended mode is interactive by nature. The process flow steps are mostly similar for both but this documentation focuses on the attended mode.

For information on deploying the unattended mode, contact your system administrator.