Customer Knowledge base

RC-26.2

Release date: 11/08/2026

Major features

Reporting module

New module to help customers comply with e-reporting mandates (such as France), where an aggregated report must be delivered to a compliance platform on a set schedule. Two approaches are supported:

  • Direct e-reporting — the customer sends Routty the final, pre-built report; Routty forwards it to the compliance platform as-is, with no scheduling or aggregation involved.

  • Indirect e-reporting — the customer sends individual partial reports (e.g. per transaction or payment event) as they occur. Routty stores these, aggregates them according to a configured schedule, and submits the final report to the compliance platform on the customer's behalf — including automatic retries on delivery failure and the ability to reprocess a report if configuration changes after the fact.

Both the generated aggregated reports and the underlying partial reports remain fully searchable and auditable as regular Routty Cloud documents.

Manual lifecycle actions

Two mandatory lifecycle updates required for the French mandate are now available as user actions directly on documents:

  • Payment received: For outbound documents in France, users can now confirm receipt of payment from the interface.

  • Refused: For inbound documents in France, users can now formally refuse a document that doesn't match expectations, directly from the interface.


Minor features

  • Auto-assign for more error types: XSLT errors and invalid XML errors are now automatically assigned to the appropriate level (partner or tenant).

  • New Routty XML metadata fields: ChannelUsesLifecycles, ReceivedOn and IsTest are now available in the enriched XML output.

  • Reworked channel management: Channels are no longer purely string-based. Channels can now be configured to use lifecycle statuses and to define which rejection reasons apply.

  • MLS support for Peppol: Added support for sending and receiving MLS messages, in preparation for Slovakia and ViDA.

  • Connector API - company identifiers: You can now specify company identifiers when uploading a document, to control which company it's matched to.

  • Extended PDF/A support: Attachments beyond the XML are now extracted from PDF/A files and imported into Routty.

  • Added the E-Számla ID as a clearance reference on the document details page.

  • Added the Coupa ID as a booking reference on the document details page.

  • "Company not found" audit logs now include the identifiers used in the search.

  • New email config option, PdfForwardEmailAddress, to auto-forward PDF-only emails.

  • Added tracking for the status of emails sent from Routty: Sent, Received, and Opened.


UI/UX improvements

  • Split dashboard charts: Dashboard charts now separate inbound and outbound data.

  • Added a copy button for document errors, making them easier to share.

  • Added a loading indicator when changing dashboard filters.

  • Reworked the Tenant > Features tab for clearer configuration.

  • Received on the platform is now Received on platform.


Bugfixes

  • Dashboard population now uses documents' receivedOn timestamp instead of lastUpdatedOn, for consistency with other document views.

  • Fixed a timestamp issue in our error notification emails.

  • Fixed incorrect UTF-8 encoding of customer names (e.g., special characters).

  • Renamed routty → Routty for consistent casing in audit logs.

  • Removed the option to select Lifecycle document types for route creation.

  • PDF generation timeouts have been resolved.

  • Document reference with extreme length made detail page render incorrectly.


Technical Improvements

Infrastructure rework complete

As announced in previous release notes, we've completed the major refactor of our document-processing infrastructure. This sets Routty up to scale reliably going forward.