Invoice Processing for PDF files with embedded XML

As an extension of M3 Invoice Processing, use this solution to process structured eXtensible Markup Language (XML) e-invoices.

When you receive an e-invoice, the solution extracts invoice data from:

  • A PDF/A-3 file that contains embedded XML, such as ZUGFeRD or Factur-X
  • A standalone XML attachment, such as UBL 2.1 or KSeF

When you process an invoice that contains structured XML, the Robotic Process Automation (RPA) identifies the invoice format by reading the XML root element and XML namespace (xmlns). The RPA compares the values against supported invoice standards to determine how the invoice should be processed.

If the XML matches a recognized format and a corresponding File-based Message Processing (FBM) mapping is available, the RPA sends the XML together with a Correlation ID to Infor Enterprise Collaborator (IEC). IEC uses the XML data to register the supplier invoice in M3 through 'Supplier Invoice. Batch Entry' (APS450). Because the XML contains structured invoice data, invoice processing bypasses optical character recognition (OCR), which can improve processing speed and data accuracy.

If a supported FBM mapping isn't available, XML processing can't continue. In that case, the solution processes the invoice from the PDF file and generates a warning message indicating that the XML file couldn't be processed.

The solution also uploads the original PDF invoice to Infor Document Management (IDM) and stores the document with attributes that include the same Correlation ID assigned to the XML file. Using the same Correlation ID helps APS450 program update the document with the correct supplier and invoice information. You can access the PDF invoice from relevant Accounts Payable and General Ledger programs in M3 through the IDM integration.

The solution supports e-invoice formats used in Germany, France, Belgium, Colombia, Denmark, and Poland. FBM performs business validations, while the RPA identifies the invoice format and routes the invoice to the appropriate processing path.