We removed the restriction that previously locked a company's country code once set. If a company record synced with an incorrect country code, you can now correct it directly, instead of needing a manual workaround.

We updated the document viewer and the generated PDF to hide any field, or entire section, that has no data. You see a cleaner, more professional document with no empty labels or blank gaps. e updated the document viewer and the generated PDF to hide any field, or entire section, that has no data. You see a cleaner, more professional document with no empty labels or blank gaps.

We added the validity start and end dates from your endpoint request to the document type record created in the SMP. Your endpoint registration now accurately reflects the period during which it's active.

We changed how the portal loads its feature modules, so only the module you're using loads up front instead of the whole application at once. The portal's first page now displays faster.

We added a notification when a document is successfully added to a report, so interested systems know aggregation happened in real time instead of needing to poll or check manually.

We added an Error label to passthrough reports that failed, shown in both the report list and the report details. You can spot a failed report at a glance instead of opening it to check.

We added a search box to the top of the workspace list in User settings. You can now find and switch to a specific workspace by typing its name, instead of scrolling through the full list.

We updated the label and confirmation window for the NF-e cancellation action to follow the same pattern used by the portal's other tax-event actions, with a clear description of what the action does. The cancellation action is now easier to recognize among your other options.

We added a Retry action plus More actions options to check a document's status, so you can retry a failed document or check its status from the portal instead of contacting support.

We reviewed the error messages returned by the France directory and gave each one a unique code and a translated message. When a directory lookup fails, you now see a specific, translated explanation instead of a generic error.

We added a uniqueness check that compares every incoming document against your active and historical reports before it's aggregated. If a duplicate is detected, you get a notification identifying the report it was already included in, so a duplicate document never reaches the tax authority.

We added a limit on how long schematron validation can run and on how many errors it reports, and fixed a case where the same document could be validated twice. Validation now completes reliably instead of running indefinitely on large or heavily invalid documents.

We added an optional migration key to company endpoint creation, in both the API and the portal. If you're migrating your PEPPOL registration from another provider, you can now supply the key at the same time you create the endpoint, instead of needing manual help from Sovos. Learn more at Migrate from another Plateforme Agréée.

We enabled Sovos Intelligence for France clients on Network Services, with automatic submission for every outbound and inbound document once processing completes. You can see your compliance activity in Intelligence without any manual data extraction.

We added the report number to the rejection notification you receive from eReporting, so you can identify which report was rejected without cross-referencing separately.

We aligned the France archive's stored and displayed metadata with the fields your documents actually carry (company code, sender and receiver names, document number, total, and date), removing columns copied from another country's setup that never applied to France. The archive view now shows only fields relevant to your France documents.

We added Norway mandate to Compliance Network. Norway joins your existing country coverage, so you can onboard Norwegian trading partners without a separate integration, and inbound documents are matched to the correct receiver automatically. Learn more about Compliance Network implementation for Norway.

We added Slovakia mandate to Compliance Network UAT. Slovakia joins your existing country coverage, so you can onboard Slovakian trading partners. Learn more about Compliance Network implementation for Slovakia.

We fixed the download endpoint for application-response links so it now returns a 404 with a clear message when the underlying file is no longer available, instead of a misleading 403 that looked like an authorization problem. You can tell the difference between an access issue and content that's simply expired, and handle each case correctly in your integration.

We fixed a problem where reprocessing a document through the API could leave its status stuck on Error even after the retry succeeded, with the file regenerated and the preview unavailable. A reprocessed document's status, file, and preview now correctly reflect the outcome of the retry.

We fixed a problem where a delivery error reported by the receiving network wasn't passed back to update the document's status. A delivery failure now shows as a routing error on the document, instead of leaving it stuck showing "In progress" indefinitely.

We fixed a display problem where a long seller or buyer company name would overflow its field in the document detail view. Long names are now truncated with the full name available on hover, so the layout stays intact.

We fixed inconsistent spacing and alignment between invoice detail fields and their labels in the Metadata, Invoice period, and Document dates sections of the document viewer, and corrected labels that weren't translated. Invoice details are now easier to scan.

We fixed a problem where the correlation ID you provided when submitting an outbound document wasn't kept through every stage of its lifecycle; the "Validated by recipient platform" and "Made available" stages could show a different ID. Your original correlation ID is now kept consistently across every lifecycle stage, so you can trace a document end to end.

We fixed a problem where the seller name wouldn't display if the original file only carried the registered company name and not a separate trading name. The seller name now displays correctly in this case, instead of a blank field.

We fixed a problem where downloading a PDF from an inbound notification link could time out and block the rest of your inbound notification queue behind it. PDF downloads from inbound notifications now complete reliably, so a slow download no longer holds up your other documents.

We fixed a problem where the notification list's pagination counts (total entries and total pages) included notifications the caller wasn't eligible to receive, showing a nonzero count even when the returned list was empty. Pagination counts now reflect only the notifications you're actually eligible to receive.

We fixed a problem where the toolbar search field kept its previous value after you reset the filters, requiring you to press Enter again to see results for the new filters. The search field now clears along with the rest of the filters.

We fixed a problem where changing one dropdown filter (for example, application or operation) would clear the other filters you'd already set. Changing one filter now leaves your other filter selections in place.

We fixed a problem where a client with company-level access restrictions could see transactions belonging to companies outside their assigned access. The transactions page now correctly honors your company-level access restrictions.

We fixed a problem where a workspace admin couldn't update a user's group assignment or other settings on the User Management page, even though they should have the same access as a Sovos admin within their own workspace. A workspace admin can now update any attribute on a user in their organization.

We fixed a problem where outbound NF-e documents could be saved with empty metadata (sender and receiver tax IDs, invoice number, access key, dates, and totals), leaving the Invoice Monitor unsearchable for these documents. Outbound NF-e documents now save their metadata correctly, so you can find and review them in the Invoice Monitor as expected.

We fixed a problem where import declaration details (DI/adi) on an NF-e weren't carried into the generated Canonical Invoice for outbound documents, even though the same details already worked for inbound documents. The Canonical Invoice for outbound NF-e now includes these import details, matching inbound behavior.

We fixed a problem where an NFCom document containing certain optional IBS/CBS tax fields could fail validation with a generic XML error before any business rule ran. Valid NFCom documents with this field configuration are now accepted instead of failing with an unclear error.

We fixed a problem where querying the status of a non-authorized NF3e document could fail because part of the document's key was cut off during the request. Querying a non-authorized NF3e document now returns the expected result.

We fixed a problem where a lifecycle response field exceeding 2,000 characters was rejected by the public portal. Longer lifecycle responses are now accepted.

We fixed a problem where the issuer's registration number was missing from the generated lifecycle response. The issuer's registration number is now included as expected.

We fixed a problem where converting an extended CII invoice to extended UBL could produce an invalid document when it carried line-level order or delivery references. This conversion now produces a valid UBL document in this case.

We fixed a problem where the delivery location identifier and its scheme were dropped when generating an invoice. The delivery location identifier is now kept in the generated invoice.

We fixed a problem where the "OptinNotRegistered" error from the optin-authorization API was incorrectly shown as "OptinNotAuthorized." You now see the correct, more accurate error when an opt-in registration is missing.

We fixed a mapping problem affecting UBL EXTENDED invoices where the payee has only a name and no identifier: the mapper was inserting the seller's SIREN into a field reserved for a different identifier scheme, which caused the invoice to fail validation. These invoices now map correctly and pass validation.

We fixed a mapping rule so that a UBL scheme ID of SEPA maps only to the bank account identifier field (BT-90), instead of also affecting other fields. Invoices using the SEPA scheme now map correctly.

We fixed a problem where the inbound KSeF date format changed unexpectedly. We restored the previous, correct format.

We fixed a problem causing a growing backlog of stuck Poland invoices in transmission. These invoices now complete processing normally instead of remaining stuck.

We fixed a caching problem in the Poland inbound polling process where an invalid authentication token could be kept in cache for 24 hours, well past its actual 15-minute validity in KSeF. Polling now uses a fresh token as soon as the previous one expires, instead of repeatedly failing until the 24-hour cache cleared.

We fixed a workflow throttling problem that could cause Saudi Arabia documents to be permanently discarded after being deferred too many times when a high volume of documents arrived at once. High-volume Saudi Arabia submissions are now processed without documents being silently lost.

We fixed a problem with how duplicate documents were handled: bundle configuration and legal code review now apply the correct status precedence. Duplicate documents now receive a consistent, predictable status.

We fixed a problem where the Libros de Registro de Operaciones Económicas (LROE) resend workflow was missing an archiving step. Resent LROE documents are now archived as expected.

We added the five Factur-X formats to the list of formats accepted for validation on French inbound and outbound invoicing. An incoming Factur-X document is now validated using the Factur-X rules that apply to it, instead of being re-mapped to UBL or CII and validated against the wrong rule set.

We deployed the Flux 10 XSD schema, enabling schema-level validation of French e-reporting documents for the first time, and turned on schematron enforcement for Flow 2 (UBL, CII) and Flow 6 (CDAR) invoices processed during e-reporting consolidation. These documents are now validated against the full rule set before being included in a report.

We updated the French PPF Flow 1 validation rules to the tax authority's latest schematron version. Among other corrections, a buyer VAT identifier is no longer required in a case that previously blocked valid submissions, a rounding issue that could cause a false validation failure is fixed, and the Greek country code EL is now accepted.

We added a rule requiring a specific endpoint identifier scheme for French documents, and fixed a gap in how the rule handled CII agent-endpoint references. This closes a validation gap ahead of the rule's wider rollout.

We updated the Saudi Arabia PDF template to add fields required by ZATCA's E-Invoice Data Dictionary: the original invoice date on credit notes, the ZATCA clearance timestamp, and the ZATCA-issued invoice reference number, and corrected several Arabic field labels to match ZATCA's official terminology. Your Saudi Arabia PDFs now include the fields ZATCA requires, with the correct Arabic terminology.