Product Updates

We are excited to announce that ecosio's Global E-invoicing Compliance solution is now live for China, enabling enterprises to issue and receive fully digitalised electronic invoices (e-fapiao) in line with the requirements of the State Taxation Administration (STA). Businesses operating in China can now onboard with ecosio and manage their end-to-end e-invoicing flows through a single, globally consistent platform.

With China's clearance-based model already mandatory for VAT-registered entities, this milestone gives multinationals a reliable path to compliance without the overhead of building or maintaining direct integrations with local tax authority systems.

What e-invoicing in China means for your business

China operates a clearance-based Continuous Transaction Controls (CTC) model, administered by the State Taxation Administration (STA) through the Golden Tax System (GTS). Since 1 December 2024, all taxpayers nationwide are authorised to issue fully digitalised e-fapiao, and paper and legacy invoice formats are being progressively phased out. Since 2025, e-fapiao is steadily becoming the standard VAT invoice format for B2B, B2G, and B2C transactions.

Because foreign entities cannot connect directly to the STA, and operational controls such as facial recognition authentication, red-letter corrections, and 10-year in-country archiving apply, running China e-invoicing at scale requires an integrated, compliance-ready approach.

How Global E-invoicing Compliance simplifies China e-invoicing

With Global E-invoicing Compliance, you can meet China's e-fapiao requirements without building or operating direct integrations with Chinese tax authority systems. Our solution provides:

• STA-compliant clearance orchestration, transforming ERP data into compliant XML and managing submission, clearance, and retrieval of official artefacts (invoice number, QR code, digital signature, timestamp).

• Compliant local connectivity covering authentication (including facial recognition), issuance, and archiving in line with STA rules.

• Support for the full document scope, that is: Special VAT e-fapiao, General VAT e-fapiao, and red-letter (credit) invoices for corrections.

• Operational visibility into invoice status, errors, and pending authentications through ecosio Monitor.

• Global coverage, enabling you to manage China alongside every other country where you operate through one single platform.

Ready to connect?

Visit our China country page for detailed technical specifications, or contact our sales team today to start onboarding and ensure your business is fully compliant with China's e-fapiao requirements.

The ecosio Product team

🚀 What’s new

1. Peppol Scenario Support (multi-country)

Partners now have access to support for a set of Peppol-based scenarios that can be activated via the Management API.

Countries included:

• Germany

• Norway

• Belgium

• Sweden

• Netherlands

• Finland

• Estonia

• Denmark

Example: Peppol Belgium scenario payload

{ 
"name": "BELGIUM_EINVOICE", 
"peppolParticipantIds": "2090:BExxxxxxxxx", 
"emailAddressesForValidationErrors": "test@ecosio.com", 
"direction": "BOTH" 
} 

2. Test-only flag (usedForTestOnly)

We introduced the optional parameter usedForTestOnly = true to clearly mark entities created via the Management API as test data.

It can be applied to:

• Companies

• Connectors

• Scenarios

🔍 Why is it important?

This flag helps separate testing activities from real customer configurations, so internal teams can quickly identify non-production objects and handle approvals, visibility, and reporting accordingly.

The ecosio Product team

Slovakia e-invoicing reality is changing and businesses need to plan for it.

Today, Slovakia’s B2G e-invoicing framework is based on the centralised IS EFA (Informačný Systém Elektronickej Fakturácie), Slovakia’s current centralised platform for public sector invoicing.

However, from 1 January 2027, the current B2G model is expected to be replaced. Slovakia’s existing IS EFA framework is also expected to be decommissioned as part of the 2027 transition. From that point, B2G and B2B e-invoicing will follow the same Peppol based model, removing the technical distinction between public sector and private sector invoice exchange. Under this model, VAT-registered businesses established in Slovakia will need to issue, receive and exchange structured e-invoices through accredited service providers, with invoice data reported to the Slovak Financial Administration.

As ever, ecosio is fully preparing for this change and we have already kicked off our implementation for Slovakia. This is part of our broader effort to expand coverage across Europe and ensure our customers can rely on a single platform to manage compliance and business processes across multiple jurisdictions.

What you must know about Slovakia’s e-invoicing mandate

If your business operates in Slovakia, or sells to Slovak public entities, e-invoicing is moving from a public sector requirement to a broader day-to-day compliance obligation.

Here are the key points to understand:

• The current B2G model is being replaced. Slovakia’s existing IS EFA framework is expected to be decommissioned as part of the 2027 transition. From that point, B2G and B2B e-invoicing will follow the same Peppol-based model, removing the technical distinction between public sector and private sector invoice exchange.

• PDF invoices will no longer be enough for in-scope domestic transactions. From 1 January 2027, domestic B2B and B2G invoices in scope will need to be exchanged as structured electronic invoices. PDF invoices sent by email will not meet the new compliance requirements.

• Invoices must be exchanged through accredited service providers. Slovakia’s new model is based on Peppol and requires businesses to work with an accredited service provider, locally referred to as a “Digital Postman”. This means businesses cannot simply connect directly to the tax authority or exchange invoices through informal channels.

• Tax data reporting happens in parallel. In addition to exchanging the invoice through Peppol, the model introduces a Slovak Tax Data Document, or SK TDD. This document contains invoice-related tax data and must be submitted to the Slovak Financial Administration alongside the invoice process.

• Timing requirements are strict. The Slovak model includes tight reporting timelines, including a 15-minute window for submitting the Tax Data Document in relevant scenarios. This makes automation, validation and reliable process monitoring especially important.

• Customer onboarding will be an important operational step. Customers will need to register through the national onboarding process, provide key identity data such as their 10-digit Slovak Tax Identification Number, or DIČ, and select their accredited service provider before compliant invoice exchange can be enabled.

The risk of underestimating Slovakia is simple: if the structured invoice data, delivery mechanism, reporting process or onboarding setup is wrong, businesses can face avoidable rework, delayed payments and increased compliance exposure.

That is why ecosio’s Global E-invoicing Compliance is built for multi-country reality. Through one integration, ecosio helps businesses manage e-invoice creation, validation, routing, monitoring and compliance handling across jurisdictions. For Slovakia, this helps reduce the effort of managing local requirements while keeping processes consistent, automated and audit-ready.

Timeline

• April 2023: IS EFA fully operational — B2G mandatory.

• 2026: The e-invoicing legislation became legally valid, opening the way for the pilot and voluntary phase. Digital Postman accredited providers list published, businesses must select one for B2B compliance

• 1 January 2027: Mandatory structured e-invoicing and automatic reporting are expected for domestic B2B and B2G transactions involving VAT-registered businesses established in Slovakia.

• 1 July 2030: The mandate is expected to expand to intra-EU cross-border transactions, aligning with the ViDA timeline.

If you do business in Slovakia, or plan to, now is the time to assess whether your transactions fall within the January 2027 mandate. Get in touch to get a customised path to compliance based on your business needs. Or subscribe to our e-invoicing deadlines calendar to never miss any new mandate.

The ecosio Product team

Spain is moving toward mandatory B2B e-invoicing, with the proposed deadline expected in October 2027. While the legislation is still in draft, businesses operating in Spain are already navigating a multi-layered compliance landscape.

With Global E-invoicing Compliance, we are building out Spain support so your business can meet the upcoming requirements without adding new portals or separate integrations.

What makes Spain complex

Spain's e-invoicing framework has evolved over more than a decade, and not every obligation is at the same stage yet. Some requirements are already in force, while others are still planned or in draft. Besides the upcoming mandate affecting B2B e-invoicing, we also have:

• B2G e-invoicing: Public sector e-invoicing via FACE using the Facturae format has been mandatory since 2015 and remains in place.

• SII reporting: The SII system already applies to large taxpayers and requires near-real-time VAT reporting.

• Verifactu: This anti-fraud invoicing-software requirement is a separate obligation and is expected to apply from 2027.

• Other regional requirements: Additional regional obligations may still apply depending on where a business operates.

How Global E-invoicing Compliance helps

Managing Spain's overlapping mandates (different formats, platforms, and reporting obligations) creates real overhead for internal teams. GEC is designed to handle that complexity centrally:

• Multi-format support: We cover the full range of EN16931-compliant formats required in Spain, so invoices reach their destination correctly regardless of which platform your trading partner uses.

• E-signature handling: Digital signatures might be included in scope for B2B e-invoicing. ecosio is ready to apply them automatically where required for platform-to-platform exchange.

• Unified flows for B2B and B2G e-invoicing: Whether you are invoicing government entities via FACE or exchanging B2B invoices across platforms, everything runs through a single integration.

Start preparing now

Our piece advice? Don’t wait until next year. Visit our Spain e-invoicing page for a full regulatory overview, or contact our sales team to get started.

The ecosio Product team

Poland’s KSeF follows a clearance-style model, which means invoicing operations depend on the availability of a government platform.

When KSeF is temporarily unavailable, an offline issuance approach can help you keep critical processes moving and avoid avoidable delays.

That’s why we’re introducing offline mode support in the Monitor for Poland.

What problem does this solve?

When KSeF is temporarily unavailable, you still need a controlled way to keep issuing invoices without creating chaos for finance teams, customers, and downstream processes.

Our offline mode flow is designed for time‑critical invoicing scenarios, such as:

• end of month billing runs

• high volume invoicing

• industries where invoicing blocks shipping or service delivery

• teams that need a predictable customer experience (even in disruption)

How it works

When KSeF is unavailable:

1. You send invoice data to ecosio

2. ecosio maps and validates the invoice as usual

3. ecosio keeps the invoices in the Monitor and generates a PDF in offline mode that can be shared with the buyer

4. The PDF contains two QR codes: one for the customer certificate and one for the invoice representation

5. Once KSeF is available again, ecosio submits the pending invoices to KSeF (in batch), and KSeF assigns the KSeF number as part of the clearance process

Why this matters

Offline mode is a regulated contingency path (not a workaround) and it’s most valuable when invoice delays translate directly into operational or cash flow risk.

What you should prepare

Offline mode works best when it’s set up before you need it. In Poland, that preparation includes certificates.

Monitor’s Poland connector setup supports:

• online authentication (token or certificate based), with certificates being the long term approach as KSeF moves forward

• an optional offline certificate, which enables local signing during outages and helps avoid invoice delays when KSeF is down

If you operate in Poland and want to reduce disruption risk, offline mode is the safety net you’ll be glad you tested before the first outage.

Discover how ecosio simplifies global e‑invoicing compliance at ecosio.com or or get in touch with our experts today.

The ecosio Product team

We are happy to announce that ecosio is now an accredited Peppol Access Point in Japan, which means we can now officially support you in exchanging structured e‑invoices via Peppol as part of our Global E‑invoicing Compliance (GEC) solution.

Japan’s Qualified Invoice System (QIS) has been in effect since 1 October 2023, and it sets clear requirements for how businesses issue and retain invoices when claiming input tax credits. While electronic invoicing isn’t mandated as of today, Japan is actively promoting structured exchange through Peppol, with a local specification called JP PINT.

What this means for businesses in Japan

Japan combines tax compliance obligations with a flexible delivery model:

• Qualified invoice requirements (QIS): to claim input tax credits, buyers must retain invoices that meet QIS content requirements.

• Peppol is voluntary, but strategic: Japan supports exchanging qualified invoices electronically via Peppol. Adoption is encouraged for efficiency and standardisation across B2B and B2G flows.

• Local Peppol specification (JP PINT): Japan uses JP PINT, a localised Peppol format aligned with QIS requirements.

• Electronic archiving rules apply (ERRL): regardless of the exchange channel, electronic invoices and records must be stored in line with the Electronic Record Retention Law (ERRL).

How ecosio supports you

Instead of stitching together local providers, formats, and archiving processes, you can keep one global setup and extend it to Japan with confidence:

• Use one trusted connection: leverage our accredited Peppol Access Point capabilities for Japan for compliant transmission.

• Comply seamlessly with the local specification: create, validate, and exchange structured invoices and credit notes in the JP PINT format.

• Reduce compliance risk: support QIS-aligned invoice content and help you stay audit-ready with processes built for QIS + ERRL requirements.

• Scale without extra vendors: if you already use ecosio GEC, simply add Japan to your existing configuration and we’ll handle the local Peppol and compliance specifics.

Next steps

If you operate in Japan, now is the time to align on QIS invoice content, JP PINT readiness, and archiving requirements.

For more context on Japan’s requirements and key dates, feel free to check out our Japan country page and contact our sales team today.

The ecosio Product team

How good documentation helps ecosio customers get more value, faster.

In B2B communication, small details have big consequences. You manage multiple partners, formats, systems, and changing regulations, so documentation becomes the backbone for consistent execution.

When you adopt a new platform or when a new feature is rolled out, speed to clarity matters. You need to know what changed, why it matters, what to do next, and how to do it right the first time.

That’s why our documentation portal is part of ecosio’s service delivery. It helps you get answers fast, and helps your teams keep moving as requirements evolve.

What is our documentation portal?

Our documentation portal is ecosio’s expert-curated, customer-facing source of truth for product documentation and updates. It brings documentation, practical guidance, recipes, and a complete changelog into one place, so you can find what you need quickly, act with confidence, and keep momentum.

It covers four core areas:

• Global e-invoicing compliance: country-specific implementation guidance from ecosio’s in-house experts, with links to our country pages for deeper regulatory context

• Monitor: guides that help you track EDI traffic and manage connections with confidence

• API and connectors: technical documentation to support ERP and partner integrations through the ecosio API

• Recipes: best-practice, step-by-step guidance for common use cases and integration scenarios

The ecosio difference: why documentation is mission-critical for B2B communication

Some providers might automate e-invoicing, but then leave you to figure out the rest when requirements change. ecosio goes further.

Our teams actively monitor 200+ regulatory and market sources every day, and that expertise is distilled into actionable guidance and published in the portal, so you have clarity at the moment you need it.

As a living extension of ecosio’s expert service, the portal helps you:

• Reduce implementation risk with clear, repeatable configuration and processes

• Move faster with fewer tickets because teams can self-serve answers when they need them

• Improve reliability over time as integrations scale across partners, formats, and internal stakeholders

• Stay resilient through change when features, regulations, and business needs evolve

A living resource that grows with ecosio

The portal is designed to stay current. As ecosio’s products and country coverage expand, the documentation expands too.

This is your tool, so your feedback helps us improve and prioritise the right content.

To share feedback:

• Use the buttons on the right-hand side of each page to let us know if the content was useful or not:

  

• Or share feedback the usual way on Featurebase

Explore our documentation portal now!

The ecosio Product team

🚀 What’s new

Poland country scenario (enablement for existing customers)

Partners can now enable the Poland scenario for an existing customer created via the Management API.

Notes:

• Scenarios can only be added to companies that were created via the Management API.

• Two activation options are supported: KSeF token or certificate.

• Update functionality will be provided in a later release.

Endpoint: POST /api/v1/management/companies/companyUuid/scenarios

Request (KSeF token):

{ 
"taxNumber" : "TAX ID xxx", 
"ksefToken" : "xxx", 
"name" : "POLAND_EINVOICE" 
} 

Request (certificate):

{ 
"taxNumber" : "TAXIDxxx", 
"digitalCertificate" : { 
    "certificate" : [ xxx ], 
    "privateKey" : 
       { "key" : [ xxx ], 
         "passphrase" : "xxx" } 
}, 
"name" : "POLAND_EINVOICE" 
} 

Detailed documentation about the mandate in Poland: Compliance for Poland

🔁 What’s changed

Connector create endpoint field rename

To reduce confusion, we renamed the connector create field:

• apiKey → userKey

Applies to: POST /api/v1/management/connectors

If you create connectors via the API, update any client-side parsing and mappings that read or write the old field name.

Reference: Create connector endpoint

⏳Coming soon

• Monitor user scenario

• Peppol scenario

• Italy scenario

• Germany scenario

• Poland Update scenario

The ecosio Product team