Overview of System Updates

System Update — September 2026

API and integrations

• The API documentation is now available at https://test.postarflowis.sk/api
• X-Account-Id is optional for V1 document listings
  GET /api/v1/sent-documents
  GET /api/v1/received-documents
• The webhook descriptions have been moved to the central documentation at https://test.postarflowis.sk/api-docs/index.html?urls.primaryName=Webhook%20Docs
• The account webhook payload contains a new field, `vpds_token`
  . This is relevant for intermediary and registration webhook flows.
• The Peppol lookup and SMP migration responses contain smp_registrator
  Endpoint: GET /api/v1/peppol-lookup
  SMP endpoints: /api/v1/accounts/{id}/smp-migration

Documents and Onboarding

• A new option has been added to create a new invoice
  UI: Account -> Sent documents -> New document
• The PDF preview includes all the details of the document, not just the BIS required fields
• A default quantity has been added; the supplied company ID is no longer required in selected document flows
• Direct support for card payments for all packages
• The MULTI package has been added, which includes up to 30 legal entities under one roof
• You can now change your selected plan at any time
• Invoices for the package are now available immediately after the bill is paid

Mobile and UI

• Mobile app
• Email 2FA is tied to the specific browser that requested the code
• The links to the self-registration terms have been updated to a direct link to the location on the page
• The ability to lock document headers and footers has been added
• Adding a user with the role of coordinator or secondary owner to the entire billing account

System Update — August 2026

The August release introduced a new self-service onboarding process, expanded API integration capabilities, improved support for intermediaries, stronger security mechanisms, and more tools for both support and developers.

Onboarding and Accounts

• A new self-service registration process for customers, including program selection, confirmation of terms and conditions, and completion of registration.
• The option to select a document mode during onboarding.
• Support for custom plans for customers who need personalized service settings.
• Adjusting prices, limits, and the display order of plans.
• The ability to manage billing account holders.
• A new administrator role in the customer account.
• Move language settings to the user profile level.

API and integrations

• Full management of API tokens directly within the integrations interface.
• Audit history for API access management.
• More robust handling of API requests, including support for text bodies and a fix for the BOM prefix.
• Account event webhooks designed primarily for brokers.
• Addition of ` account_id ` to document webhook payloads.
• Updated API examples and documentation.

Peppol

• Searching for subscribers via SML/SMP.
• Processing of broker registrations through an approval workflow.
• Repeated attempts to deliver documents via Peppol.
• Stop resending if the recipient is not registered.

Documents

• Standardizing the terminology from "invoices" to the more general term "documents."
• The option to adjust the document settings during account verification.
• Notifications for documents that failed to send.
• Reduction in the number of database queries on the dashboard and in document details.

Support and Administration

• A new developer support page with access to API logs, idempotency keys, emails, documentation, MLS responses, and submission attempts.
• Consent-based access to customer accounts for support purposes.
• Overview and audit of system changes via PaperTrail.
• Improved overviews of customer accounts, registration requests, and plans.
• A new "Help" page with a contact form for customers.

Security and Technical Core

• Protection against brute-force attacks and scanning using Rack::Attack.
• Upgrade to Ruby 4.0.6.
• Upgrade Rails to version 8.1.3.1.
• Added strong_migrations for more secure database migrations.
• Dependency updates and security fix releases.
• Removing unused JavaScript code and simplifying the front end.

System Update — July 2026

The July release introduced user role management, a more detailed overview of the document lifecycle, additional API capabilities, and enhanced account security.

API

• A new API endpoint for searching the Peppol Directory and verifying the availability of a Peppol network participant via the API.
• A user API for managing users and their roles within a customer account.
• The document mode in the Accounts API, for example in the requests POST /accounts and PATCH /accounts, including the send and receive mode values.
• Protection of verified accounts against changes to sensitive data, such as the subscriber ID, tax identification number, or country.
• Filter received documents based on whether or not they have already been downloaded.
• The default sort order for received and sent documents is from newest to oldest.

Accounts and Users

• New user roles: owner, administrator, editor, and reader.
• Email invitations for new users.
• Option to deactivate a user through support.

Documents

• A document timeline showing its creation, queuing for sending, delivery attempt, MLS response, and completion of processing.
• More detailed information about errors resulting from failed delivery.
• Protecting the production environment from sending a document to the same participant.

Peppol

• Processing MLS reports on the acceptance or rejection of a document.
• Searching the Peppol Directory is available both through the user interface and via the API.

Safety

• Preparation for penetration testing, including test accounts, the scope of testing, authorized addresses, contacts, and restrictions.
• The foundation for stronger user verification and two-factor authentication.
• Permission checks when managing users and customer accounts.

User Interface

• SAPI information page with an example of how to use an endpoint.
• Improved filters in the customer account management system for support.
• Filters shared across different views.
• A clearer view of the available actions for a document.

Technical Core

• Refactoring classes for searching, filtering, and sorting data.
• Enum string values for more stable data models.
• Organizing models into separate namespaces.

System Update — June 2026

In June, we expanded the verification of Peppol network participants, refined document status information, and added new tools for users as well as customer support.

API

• Updated API documentation with clearer descriptions and links to the API and SAPI sections.
• Unified API responses in Swagger and Postman scenarios.
• The " invoice_mode " field in the account's response, for example, at GET /account.
• Adjustment of document states in the API and removal of the inappropriate manual transition to the " ready_to_send" state.
• More precise API messages when a recipient is unavailable on the Peppol network.

Peppol

• Search the Peppol Directory by name, company ID, VAT ID, tax ID, or Peppol ID.
• Check the recipient's availability before sending the document.
• Improved data submission via Oxalis, featuring higher-quality provider data, request identifiers, and error logging during submission.
• Revised order processing via Oxalis, including the recording of sender and provider data for reporting and status responses.
• More understandable error messages during delivery.

Documents

• PDF preview and export with supplier information, such as BT-33, legal form, or additional supplier details.
• Display of units of measurement in the PDF preview, such as piece, kilogram, meter, liter, hour, package, or pallet.
• The ability to use MLS responses for document types other than standard invoices, such as TDD documents.
• Document state transitions, such as ready_to_send → sent, sent → accepted, and sent → rejected.
• Daily notifications of received invoices, including a summary of unresolved documents.

User Interface

• Clickable items on the dashboard that link directly to the details of a sent or received document.
• Updated profile and security sections.
• A more independent and organized view of subscriptions in the left-hand menu and account settings.
• Visually distinguishing between the test, development, and production environments.

Support

• Advanced document diagnostics, including filter settings, sorting, number of results, and information about the sender and recipient accounts.
• Overview of individual attempts to send the message.
• Recording email correspondence and tracking the delivery status of messages.

Technical Core

• Organizing models into namespaces to ensure more stable future development.
• A separate data model for TDD documents.
• Refactoring of document line items, tax summaries, and supplementary data.
• Setup of the production environment, including the application, database, Redis, Oxalis services, and the validator.

System Update — May 2026

The May release laid the groundwork for processing additional types of documents, registering Slovak participants in the Peppol network, and achieving more reliable system automation.

API

• Webhook data for billing accounts: webhook_slug, encrypted webhook_secret, and mapping the incoming webhook to the correct customer account.
• Processing a new customer's webhook after selecting "Digital Mailman" in the external registration process.
• Extended API error responses for issues in the Peppol network, such as when the recipient is unavailable or cannot be found on the network.
• Support for multiple document types in the parser: invoice, credit memo, customer-issued invoice, and customer-issued credit memo.

Documents

• Support for credit memos and documents issued by customers during processing and validation.
• A collection of documents intended for support and diagnostics.
• Clear indication of the document's direction: sent or received.

Peppol

• SMP configuration for Slovakia.
• The basis for registering Slovak participants in the Peppol infrastructure.

Accounts and Users

• Subscription information in the user profile.
• Basic information about the package: service type, validity, term, and participation in the registration program.

System Operation

• Processing background tasks using Sidekiq.
• Sending system emails.
• Technical cleanup of the system following the evaluation of the MVP version.