Skip to main content

EFR 2.10.0

efsta Team
efsta Team
efsta IT Services GmbH

What's new?​

The Swedish Skatteverket journal export now covers the full article-registration lifecycle — registering, changing, deleting, parking, and moving articles — and its output has been hardened against invalid data types. With that, the Swedish EFR officially leaves beta state.

Networking and configuration also got sturdier: outgoing HTTPS connections to the fiscal recorder are now reused via keep-alive instead of being re-established per request, SSL certificates are decoded and validated before they are stored (including password-protected certificates and the EFSTA_EFR_SSL_CERT / EFSTA_EFR_SSL_CERT_PASSWORD environment variables), and if a certificate cannot be loaded, the middleware now falls back to HTTP instead of starting without any server. A CORS preflight issue that broke browser requests is fixed, and log overflow protection is now speed-based, allowing larger log files for analysis.

Country-specific fixes round it off:

  • Polish KSeF handling accepts the new E2/E3 tax groups without validation errors, and the seller address is now taken from the company level (which more closely reflects the meaning of these fields in the specs). New tax groups now also works in Z reports with POSNET printers.
  • In Hungary, the ping command is disabled after a Z report to prevent needless timeouts; Portuguese PDF receipts no longer show duplicated 0% tax reason descriptions.

What this means for our users?​

Swedish merchants get a compliant, complete journal export without beta caveats. Everyone benefits from faster, more resilient connections, safer certificate handling, and fewer stuck transactions — less time chasing printer errors and retry queues, more receipts flowing.