Skip to content

Documents and reports

These programmes are implemented in RIOMA. Further documents are added in the project, with their own mapper and template. This page is not a catalogue of every M3 programme.

Supported documents

  • OIS199

    Invoice

    Invoice and supported credit note. ZUGFeRD/Factur-X only for the defined domestic case. Collective invoices only when the field structure matches.

    Technical detail

    Credit notes are recognised from the credit flag. Collective invoices only where the field structure matches the invoice. ZUGFeRD is produced by the shipped rule when issuer and invoice address are in Germany. The Swiss QR payment part is separate and, as shipped, applies to Switzerland and CHF, plus amount and IBAN. A change to that QR rule applies after a process restart.

  • MMS480

    Delivery note

    Delivery note with the base lines of the Item, Package, generic, Order and Style variants. The size matrix and the order-detail table are not included.

    Technical detail

    One mapper reads the base lines of the Item, Package, generic, Order and Style variants. The style size-and-colour matrix and the extra order-detail table are not rendered.

  • OIS606

    Order confirmation

    Order confirmation with its own mapper and template. No e-invoice.

    Technical detail

    Its own mapper, not derived from the invoice. No e-invoice.

  • PPS601

    Purchase order

    Purchase order with its own mapper, not derived from the order confirmation. No e-invoice.

    Technical detail

    A separate mapper, not derived from the order confirmation. No e-invoice.

  • MWS630

    Pro-forma invoice

    Pro-forma invoice for shipping and customs. No e-invoice.

    Technical detail

    Its own document. No e-invoice.

  • MWS450

    Put-away label

    Put-away label as ZPL, not PDF. A send to a Zebra printer only when a host is set.

    Technical detail

    Rough 4×6 inch layout, no PDF. Print writes the file without SMB. A send to a Zebra printer only when a host is set. If only that connection fails, the file remains.

  • MWS485

    Package and logistics label

    Package and logistics label as ZPL. No PDF.

    Technical detail

    The Package and Logistics variants share one mapper. No PDF and no SMB print.

Each document has its own template. Shared building blocks keep the header, footer, logo and legal text consistent across documents.

Supported reports

RIOMA processes matrix and list reports generically when the export structure fits. Columns, groups and subtotals come from the report data.

Mail or archive can produce an xlsx file. Print stays PDF. Excel applies in this report context, not to business documents. GLS512, FAS551 and TXS501 have been checked. That is not a sign-off of every M3 report.

  1. 01

    M3 report data

  2. 02

    RIOMA Core

  3. 03

    PDF / Excel

Checked examples

  • GLS512 – General Ledger
  • FAS551 – Fixed Assets
  • TXS501 – Tax
Technical detail

The class is M3OutReport. It does not depend on the individual form code where the export structure fits.

Excel is produced when mail or archive asks for Excel or CSV. The file is xlsx, not a CSV text file. Print stays PDF.

The three modules named above have been checked. That is not a sign-off of every report in the M3 standard.

Internal reference, not the product scope

An internal list holds 585 form and report codes. It helps place possible cases. That number is not the number of supported document types.