Where RIOMA fits your M3 output
Each row sets a requirement next to what RIOMA can show for it.
Introduction
Requirement
The output does not have to be replaced in one step.
RIOMA Core
You can start with one document type. The other documents stay on the current system until you move them.
Existing print data
Requirement
Existing print jobs should remain the source of the data.
RIOMA Core
RIOMA works with the print XML that M3 already produces.
Layout building blocks
Requirement
Header, footer, logo and legal text should stay consistent across documents.
RIOMA Core
Header, footer, logo and legal text can stay aligned through shared blocks. Each document keeps its own template.
Separate instances
Requirement
Teams should be able to maintain their documents separately.
RIOMA Core
Areas can use their own instances, with their own documents and templates. The number follows the infrastructure.
Change while running
Requirement
A template change should take effect while the system is running.
RIOMA Core
Templates and division rules apply from the next job. Routing, SMTP and the Swiss QR rule need a process restart.
E-invoicing
Requirement
Structured invoice data should come from the existing OIS199 job.
RIOMA Core
For defined OIS199 cases, ZUGFeRD/Factur-X is produced from the print XML. No XRechnung, no Peppol delivery, and no claim to cover every tax case.
Delivery
Requirement
Creation and delivery should be visible as separate outcomes.
RIOMA Core
An OK to M3 means the document was created and output was started. Successful delivery is not guaranteed. SFTP applies only to the archive and is off by default. There is no automatic retry.
Focus
Requirement
The output should fit the XML print jobs of Infor M3.
RIOMA Core
RIOMA is built for the XML print jobs of Infor M3.