Release note 1.5

📢 Communication Platform v1.5 - February 2026

🎯 Goals of the Release

Improve operational autonomy, reliability, and cross-border Peppol readiness by delivering self-service visibility (exports + clearer error messages), adding tenant-level configurability for Peppol outputs, and strengthening platform robustness (file naming, PDF handling, authentication, traffic safeguards) to reduce failed processing and production incidents.

🚀 Feature Highlights

UI export of sent documents

Users can now export a report of sent documents directly from the UI in both:

Sendings UI
Peppol Inbox

Key capabilities

Select a mandatory date range (Start date / End date) based on document creation date (inclusive)
Export format selection: CSV, JSON, XML
Accessible via an “Export” button on top of the grid

No-result behavior

Produces a valid file with headers/structure and 0 records and UI displays a clear “no data” message

Access control

Export is visible and usable for users with at least viewing rights

Improvements

🔐 Auto-submit on 2FA final digit

2FA entry flow is streamlined: the code is auto-submitted when the last digit is entered, reducing friction and login time.

📥 Peppol Inbox — Safe naming for embedded files in UBL

Embedded files received in Peppol inbound UBL documents are now named safely and consistently, preventing invalid characters (e.g., /) from being interpreted as path separators on SFTP and causing unintended folder creation or retrieval issues.
Implementation follows the same strategy as the inbound main UBL renaming approach.

🧾 Show detailed error reasons in “All sendings” view

Improved the “All sendings” view so that when a channel fails, users can see a clear explanation of why it failed (e.g., configuration issue, delivery error, timeout). Where possible, technical errors are shown as user-friendly messages, and a reference code/technical detail is displayed to help with troubleshooting.

🧾 Archive Peppol outbound UBL earlier in the process

Improved Peppol outbound processing so the UBL is archived as soon as it is generated, instead of only at the very end of the flow. This ensures the UBL is still archived even if later validation steps fail, matching customer expectations.

🧾 Make PDF attachment in Peppol UBL optional (tenant setting)

Peppol tenants can now choose whether a PDF should be embedded into the generated UBL. By default, behavior stays the same (PDF embedded when available), but admins can disable it per tenant to match customer or partner requirements.

Fixes

🧾 Fix — Inbound file renaming applied incorrect URI encoding

Fixed an issue where incoming file names were being altered during renaming, changing characters that should have stayed intact (like _). This could lead to unexpected file names for clients, so we updated the logic to keep file names consistent with the agreed naming convention.

🖨️ Fix — pdf-zone-writer crashes on accented/special characters

Fixed an issue where PDF generation could fail when the content included special characters (like é or è). This sometimes caused the processing job to stop and the message to be sent to an error queue.

🧭 Fix — Missing translation key in audit trail

Fixed an issue where one audit trail label wasn’t translated in the UI for the “drop” event, so it now displays the correct, readable text instead of a technical key.

🧾 Fix — Prevent inbound file name truncation when URIEncode is enabled

Fixed an issue where incoming file names with a dot (.) could be incorrectly shortened when URI encoding was enabled. This sometimes caused different files to end up with the same name, leading to overwritten files and invoices not being processed (and hard to recover).

🧾 Fix — Peppol scheme ID for non-Belgian recipients

Fixed an issue where invoices sent to non-Belgian Peppol recipients could fail validation because the Belgian scheme ID (0208) was applied incorrectly. The hotfix now applies 0208 only for Belgian recipients and uses a country-based mapping for foreign recipients.

🧾 Fix — Rate limiting per IP was not applied correctly

Fixed an issue where the platform couldn’t reliably identify the client IP address. As a result, limiting one source from sending too many requests was not properly enforced per IP, which could allow excessive traffic and lead to slowdown or platform stability.

Fixed an issue where admin users with access to many tenants could face login/access problems because the token stored in the browser became too large. We now use a session ID in the browser and keep the full access data securely on the backend for better reliability and security.

UI Impact Summary

✅ New Export action available in Sendings and Peppol Inbox (CSV/JSON/XML + date range)
✅ “All sendings” view now shows clear failure reasons and helpful troubleshooting details
✅ 2FA is faster with auto-submit on the last digit
✅ Peppol configuration now includes a new tenant option: “Embed PDF in UBL” (toggle)
✅ Improved audit trail readability (missing translation fixed)

We hope we support you the best way by having released these items.