Skip to content

Output for Infor M3

Your M3 output. Reimagined.

Document output for Infor M3, built on the print data you already produce. Start with one document and add others when you are ready. Your current output system can keep running.

Explore RIOMARequest a demo

From print job to output

Infor M3

Print XML

RIOMA

Core

  • E-invoice
  • PDF
  • Email
  • Print

Start with one document.

You do not have to replace the current system in one step. One M3 document can be the first case. Further documents can follow later. You route them in the M3 output configuration, for example in MNS204.

Example routing

Infor M3

  • OIS199InvoiceRIOMA Core
  • MMS480Delivery noteExisting output system
  • OIS606Order confirmationExisting output system
  • PPS601Purchase orderExisting output system

The routing shown is an example. An introduction includes configuration, testing and alignment.

Consistent documents. Less duplicated upkeep.

Shared building blocks keep the header, footer, logo and legal text aligned across documents. Each document still has its own template. Divisions switch company details and conditional text. Field labels can follow the language of the document.

Templates apply on the next job

RIOMA rereads template changes and part of the configuration on the next matching print job. Not every setting applies without a restart.

Shared header

OIS199

Invoice

MMS480

Delivery note

PPS601

Purchase order

Shared footer

Same template, different division

  • Logo ADivision 100100

    Company A

  • Logo BDivision 200200

    Company B

One template. Different companies and languages.

Different requirements. Kept apart.

Sales, logistics and finance can each use their own document types, templates and settings. Each instance stays separately configurable. How many instances run depends on your infrastructure. One container is enough to start.

One possible split

Infor M3

  • Container 01 – Sales

    Its own document types, templates and configuration.

  • Container 02 – Logistics

    A separate instance for logistics documents.

  • Container 03 – Finance

    Its own instance for invoices and other finance documents.

From the M3 document to the right output.

Format and channel follow the document and the job. Not every document produces every format.

Formats

  • PDFBusiness documents and reports
  • ExcelReports only, as xlsx for mail or archive
  • ZPLLabels MWS450 and MWS485

Channels

  • PrintWhen the job asks for it
  • EmailWhen the job asks for it
  • ArchiveWhen the job asks for it
  • SFTPArchive only, off by default

All capabilities

Same M3 document. The format that fits.

A rule chooses PDF, ZUGFeRD or a UBL file from the OIS199 print XML. That does not require a separate M3 print process for each format. Which format is valid stays limited to the supported cases.

Infor M3

OIS199 print XML

RIOMA rule control

Format choice from configurable rules

The rule selects one of these formats

  • PDF

    A conventional invoice

  • ZUGFeRD

    PDF with embedded invoice data

  • UBL

    XML file, not printed and not XRechnung

Existing RIOMA output channels

Email · Archive · SFTP

Email and archive follow the job. SFTP only when it is configured for the archive.

Print

For PDF and ZUGFeRD, as specified in the job. A UBL XML file is not sent to a printer.

E-invoicing from the M3 data you already have.

For defined OIS199 cases, the print XML becomes a PDF/A-3 with ZUGFeRD/Factur-X. M3 does not have to supply a separate e-invoice file. This does not cover every invoice case.

  1. 01

    Print XML

    The invoice job you already have.

  2. 02

    Model

    Mapped for this document.

  3. 03

    CII

    EN 16931, COMFORT profile.

  4. 04

    PDF/A-3

    ZUGFeRD/Factur-X in the same run.

Scope and limits

Start with one M3 document.

Tell us which document you want to modernize. We'll explore how RIOMA can use your existing M3 print data.

Request a demo