Split of PDF with multiple invoices

Process behavior

RPA creates one invoice record per invoice number listed in the PDF. For each invoice, these items are automated:

• A single correlation ID is generated.
• A separate BOD is created and sent to M3.

When a PDF contains multiple invoices, the system processes each invoice independently after splitting.

Naming of newly created PDFs

When PDF splitting occurs, the system names the generated PDF using this convention:

<OriginalFileName>from<pageNumber>to<pageNumber>.pdf

This naming convention indicates which pages from the original document are used for the invoice.

Invoice content in IDM

Only the pages containing invoice details are retained and displayed in IDM. Supporting documents such as purchase orders, delivery notes, or other documentation that are included in the same PDF are excluded.

As a result, IDM shows only invoice-relevant pages, not the full original document.

Handling of single-invoice PDFs

If the incoming PDF contains only one invoice, splitting is not performed. In this case the original PDF is attached directly to IDM. File name and content remain unchanged.

Supporting documents limitation

Supporting documents included within a multi-invoice PDF are not preserved in IDM.

The system does not provide a mechanism to retain or re-attach supporting documents once splitting is performed.

Accessing the original PDF

If PDF splitting is performed, the original combined document is not available in the tenant.

To retrieve the original PDF, perform any of these actions:

• Check the original email received from the supplier.
• Check the success or output folder where the raw file is initially stored.

Workaround and recommendation

Best practice is to receive one PDF per invoice from the supplier.

Alternatively, implement a separate PDF-splitting process as a pre-step before the standard Invoice Processing flow if preserving supporting documents is required.