Product Updates

When a message fails, you need to know why, and you need to know quickly. Until now, the reason was only on the message details page, so finding the exceptions that need action meant opening messages one by one. Monitor now shows it where you start your work: the message overview. For France e-invoicing, we've also made business states easier to read and given you direct access to your directory API credentials.

• See why a message failed, straight from the overview. Error category and error details in the table and in your CSV export

• Follow France business states in lifecycle order. The same clear order on every invoice

• Connect your ERP to the France directory. Your API credentials, ready in the Connectors tab

Spot the exceptions that need action

The message overview now has two new columns: error category and error details. The category, for example VALIDATION_FAILED, tells you what kind of problem it is. The details tell you what went wrong. When the error text is long, open it in full and go straight to the message details from there. If you don't need the columns, hide them in your table settings.

Both fields are also in the CSV export, so you can analyse exceptions in your own tools or share them with our support team.

Read France business states in the right order

France e-invoicing creates several business states for each invoice, and they don't always arrive in order. Monitor now always shows Submitted, Received by the platform and Made available first, in lifecycle order, followed by all other business states by time. Inbound invoices have no Submitted state, so their list starts with Received by the platform.

The latest business state you see in the message list and in the action box is the last one in this order. The same order applies everywhere, so what you see in the overview matches the history.

Look up company and tax details in France from your ERP

The official France directory has no direct API, and checking company details on the government website one by one takes too long when you have many companies to check. Our France directory API lets your ERP or business application look up company and tax details automatically, using the SIREN number.

In Monitor, open the Connectors tab to find the France directory connector. It shows the API connection details and the OAuth 2.0 credentials you need to authenticate. Generate or regenerate your credentials whenever you need to. The full values are only shown right after you generate them, so store them securely.

In every country, you now see what needs your attention and can act on exceptions sooner. If you use France e-invoicing, you also follow your invoices in a clear order and automate company checks from your own systems.

Get in touch with our team if you have questions or need help.

The ecosio Product team

Release summary

This release adds e-invoicing scenarios for France and the United Kingdom. It also introduces OAuth2 authentication as the recommended authentication method for Management API integrations.

🌍 New country scenarios

Partners can now activate two additional country scenarios through the Management API:

• 🇫🇷 France

• 🇬🇧 United Kingdom

These scenarios provide the country-specific configuration required for customer onboarding and reduce manual setup.

Endpoint

POST /api/v1/management/companies/{companyUuid}/scenarios

🇫🇷 France example

{ 
"name": "FRANCE_EINVOICE", 
"peppolParticipantIds": ["9957:FRxxxxxxxxx"], 
"emailAddressesForValidationErrors": ["user@company.com"], 
"siret": "xxxxxxxxxxxxxx", 
"siren": "xxxxxxxxx", 
"paAuthorisationContract": true, 
"direction": "BOTH", 
"selfBilling": false 
} 

🇬🇧 United Kingdom example

{ 
"name": "UNITED_KINGDOM_EINVOICE", 
"peppolParticipantIds": ["9932:GBXXXXXXXXX"], 
"emailAddressesForValidationErrors": ["user@company.com"], 
"direction": "BOTH" 
} 

🔐 OAuth2 authentication

The Management API now supports the OAuth2 client credentials flow. OAuth2 is the recommended authentication method for new integrations.

The required credentials are:

• Client ID

• Client Secret

• App key, which remains unchanged and is still required with OAuth2

Authentication options in Monitor

Monitor now provides both authentication methods for Management API connectors:

• Basic Authentication, which still requires IP whitelisting

• OAuth2 client credentials, which does not require IP whitelisting

The OAuth2 credentials are available below the connector information in Monitor. Select the option to generate your new Client ID and Client Secret. Copy the Client Secret when it is generated and store it in an approved credential manager, as it is hidden afterwards.

⚠️Migration period

Both authentication methods are currently available. Basic Authentication is marked for deprecation, but no removal date has been announced. Existing integrations can continue to use Basic Authentication during the migration period. OAuth2 is recommended because it removes the need for IP whitelisting.

✅ Recommended action

• Use OAuth2 for new integrations

• Plan the migration of existing integrations from Basic Authentication to OAuth2

• Keep the existing app key in every request

🔭 Next up

We are preparing additional country features for:

• 🇸🇰 Slovakia

• 🇭🇷 Croatia

• 🇦🇪 United Arab Emirates (UAE)

• 🇩🇪 Germany e-mail scenario

The ecosio Product team

Saudi Arabia is the largest economy in the Middle East and a strategic gateway to the wider Arabic region. It also operates one of the world's most mature and tightly controlled e-invoicing frameworks: for taxpayers brought into Phase 2, standard invoices must be cleared by ZATCA before they are issued to the buyer. This mix of commercial opportunity and technically demanding compliance makes a single-platform approach valuable for companies operating or expanding in the country.

What you must know about Saudi Arabia

Timeline

• Our Saudi Arabia solution is currently fully available since September 2026

How we can help with a managed compliance service

For large organisations, the challenge in Saudi Arabia is running clearance and reporting reliably at volume, integrating those processes with existing systems, and keeping pace with ZATCA's technical and schema updates.

With ecosio's managed compliance service for e-invoicing, we help teams:

• Connect through a single gateway to ZATCA's Clearance and Reporting APIs, with submission visibility in ecosio Monitor.

• Map and transform ERP data into ZATCA-compliant UBL 2.1 XML and validate documents before submission to help reduce rejections.

• Route each document through the correct process: clearance for standard invoices and reporting within 24 hours for simplified invoices.

• Produce a buyer-facing PDF/A-3 representation with embedded XML and the applicable QR code for onward delivery.

• Integrate the Saudi e-invoicing process with existing business systems, including SAP, Oracle and Microsoft Dynamics environments.

• Provide the final invoice artefacts needed for onward delivery and retention. Saudi invoice records must generally be retained for at least six years, subject to the applicable storage and data-residency requirements.

Want to know more about Saudi Arabia? Take a deeper look in our country profile page, where our FAQ answers the questions customers ask most often. And if you are ready to discuss how ecosio can support your business case in Saudi Arabia and many other countries, get in touch today!

The ecosio Product team