› Changes in behavior

Changes in behavior

The following summary lists product behavior that differs from the previous version of Tungsten e-Invoice Connect.

  • Country-specific enhancement: Poland

    The deliveryNoteReference is now repeatable. Previously, a discrepancy existed between the mapping document (cardinality [0..1000]) and the ESXML2 schema/implementation (cardinality [0..1]).

    Changes implemented:

    • The ESXML2 schema and mapping have been updated to align with the mapping document.

  • Self-Billing (Routing Logic Update)

    This follow-up release builds on the previous self-billing redesign. In that release, self-billing was supported for the Peppol flow and worked only when both the Buyer and the Supplier are registered on TeC.​ This follow-up extends this with the following additions:

    • Supplier lookup in the Peppol Directory

      • Ability to look up the Supplier in the Peppol Directory when the Supplier is not known within TeC (not available in TeC registry)

    • Original file support

      • The exchanged original will be stored alongside the transaction for both the Buyer and the Supplier (available in UI)

  • Self-Billing (Routing Logic Update)

    Self-billing document handling has been redesigned so that the Buyer acts as the submitter of the invoice and the Supplier acts as the recipient (identified via invoicingMode = SB). Previously, self-billing invoices were incorrectly routed back to the Buyer (landing in Received). With this change, the Buyer sends the invoice via the applicable network to the Supplier, and each party sees the transaction once in the correct list.

    Availability: In the 06.22.2026 release, self-billing works when both the Buyer and the Supplier are registered on TeC.

    Listing

    • The transaction appears once in the Buyer's Sent list, marked as self-billing (previously, self-billing invoices incorrectly landed in Received).

    • The transaction appears once in the Supplier's Received list, marked as self-billing.

    • The document is excluded from the Buyer's Received list.

    • The exchanged original is stored alongside the transaction for both parties.

    Member Opt-In Settings

    • New self-billing send intention for the Buyer (the Buyer must be registered to send invoices; for FR mandate, onboarded to FR services and registered as sender).

    • New self-billing receive setting for the Supplier (TeC member).

    Peppol/SMP Requirement

    • When delivery goes over Peppol to a Supplier registered on TeC, the Supplier must have a profile that allows self-billing document types, published in the SMP.

      Look up of suppliers not registered on TeC, via the Peppol Directory or external networks, is delivered in the 6/27 follow-up.

    • Removed Requirement: The previous requirement that a Buyer with the send setting enabled must also be a registered self-billing recipient in Peppol has been removed from both the UI and the API. Being a self-billing recipient is a property of the Supplier, not the Buyer.

    Rejection Handling

    • If the recipient is not configured for self-billing, the incoming invoice is rejected with the message The recipient is not configured to receive self-billing documents.

    Mapping Updates

    • Updated outbound mappings for PEPPOL and FR: For a self-billed invoice or credit note (document type 389/261), the SBDH Receiver is taken from the supplier endpoint and the SBDH Sender from the customer endpoint.

    These updates are aligned with the latest clarifications from the Peppol community and tax authorities (e.g., FPS Finance Belgium). As clarified by the authorities, for self-billing to function correctly via Peppol, the supplier must be registered as a recipient for self-billing document types, and a bilateral agreement (opt-in) must be in place. For more details, refer to the official FPS Finance - E-invoicing FAQ: How does self-billing via Peppol work.

  • Country-specific enhancements: Poland

    Updated the PDF template to provide a more clear and user-friendly view of the invoice information by changing the placement of certain fields and adding tabular view of grouped information.