Deklera – E-Rechnung, XRechnung & KSeF for WooCommerce

Changelog

0.3.11

• The pre-flight screen no longer contradicts itself. On a fresh install with
  no VAT number — that is, when every invoice would be rejected — the summary
  said in green that all recent orders would be accepted, while the same
  screen listed two store-level problems as “Would be rejected” three lines
  below. It now leads with the store-level blockers, and “Ready to invoice”
  reads zero, because nothing is.
• The plugins list now links straight to the pre-flight report. Until now the
  only way in was a submenu at the bottom of the WooCommerce menu, and
  activating the plugin left no sign it was there at all.

0.3.10

• Packaging only, no functional change. A command-line tool that came with a
  bundled library is no longer included, and the Factur-X metadata schema is
  now shipped as an .xml file. French invoices are produced exactly as
  before.

0.3.9

• Packaging only, no functional change. The download no longer carries build
  and continuous-integration files from the bundled libraries — Schematron,
  XSLT and CI configuration that nothing in the plugin reads. The WordPress.org
  review asked for this, and the download is a good deal smaller for it.

0.3.8

• When the official rule set refuses a document, the order screen now names
  the rule and quotes what it said. Before, it said only “Invalid” and the
  reason sat in the database where nobody could see it — which is unhelpful
  exactly when it matters most.
• Pro no longer needs a separate validation key. The plugin authorises itself
  with the licence you already activated, so there is nothing extra to paste,
  and a cancelled or lapsed subscription now stops validation on its own.
• An existing validation key still works and still wins, for shops running
  their own copy of the validation service.
• Two settings — the invoice contact name and telephone number — were left
  behind when the plugin was uninstalled with “delete my settings” turned on.
  They are removed now. Invoices, archived documents and the key that verifies
  them are kept, as before.

0.3.7

• Packaging only, no functional change. The free download no longer carries
  compiled translation files: they were never read, because the translation
  loader only runs in the premium build, and on WordPress.org translations
  come from translate.wordpress.org anyway. The download is smaller for it.
• The upgrade notice for 0.3.0 was longer than the 300 characters the plugin
  directory allows, so it was shortened.

0.3.6

• Clearer about what is and is not covered. France, Germany and Poland are
  measured against each country’s own official validator before a release
  goes out; everywhere else you get EN 16931 CII, which is the European
  baseline and not a national profile. Some member states mandate their own
  format and their own platform — Italy’s FatturaPA through the SdI is the
  clearest example — and Deklera does not produce those. Better to know that
  before you buy than after.

0.3.5

• Your customer now actually receives the invoice. The attachment feature was
  wired to the order-completed email, but that email is sent before the
  document exists — generation runs in the background so the customer never
  waits for it. The result was an attachment that never attached. Deklera now
  sends WooCommerce’s Invoice email once the document is archived, with the
  file on it.
• Regenerating an invoice does not email the customer again, and a credit note
  is not sent under an “Invoice” heading. Both would tell the customer
  something you did not mean to say. Use the order screen to send those.
• The new email can be switched off with the deklera/email_after_generation
  filter if you deliver invoices your own way.

0.3.4

• German, French and Polish translations. This matters more than an admin
  screen: the invoice is written in the buyer’s language, so a German
  customer was until now receiving a PDF labelled in English. They now get
  Rechnung, Nettobetrag and USt-IdNr., a French customer Facture and
  Total HT, a Polish one Faktura and Razem netto.
• The legal wording follows each country’s own convention rather than a
  literal translation — reverse charge appears as Steuerschuldnerschaft des
  Leistungsempfängers, autoliquidation, odwrotne obciążenie; a credit note
  as Rechnungskorrektur, facture d’avoir, faktura korygująca.
• A new pre-flight check warns when an invoice would go out in the wrong
  language. WordPress can only switch to a language it has installed, so
  without the language pack the document quietly falls back to your store
  language — and you would not find out.

0.3.3

• Invoices now pass the national validators, not only the EU baseline. This
  release began as a question — would a real tax authority accept what we
  produce? — and the answer, measured against the official rule sets, was
  no in two places.
• Germany: the output failed the official XRechnung 3.0.2 rules on six
  counts. Every one of them is a field the EU standard leaves optional and
  Germany makes mandatory: the seller contact name and phone, the seller and
  buyer electronic addresses, and the payment means. All six are now filled,
  and the same document passes the official rule set with nothing left.
• A new pre-flight check tells a German store when its billing phone number
  is missing, because that one cannot be filled in for you — and if it is
  missing you would only find out when the invoice is refused.
• France: the Factur-X PDF failed PDF/A-3 validation. The cause was a single
  line in the specification — every font used must be embedded in the file —
  and the built-in template used fonts that, by design, are not. The template
  now embeds its own font, and the finished document passes.
• The same change lifts the old Latin-1 limit. The built-in template writes
  any European alphabet: Polish, Czech, Hungarian, Romanian, Greek, Cyrillic.
  It no longer refuses to produce a PDF because of a customer’s name.
• Pro: validation now checks German documents against Germany’s own rules,
  not just the EU baseline. Other countries are unaffected.

0.3.2

• A user guide, linked from the settings screen and the readme: what the
  pre-flight findings mean, when documents are produced and where they are
  stored, credit notes, the Polish KSeF flow, and the available filters.
• Pro setup no longer asks you to guess. The validation service address is
  filled in by default, and the screen says where the validation key comes
  from and that it is not the licence key that activated the plugin.

0.3.1

• Pro: the first validation after the service has been idle is no longer
  lost. The hosted validator sleeps when unused and takes longer to answer
  the request that wakes it; that request now gets a second attempt instead
  of being reported as unreachable.

0.3.0

• The plugin has been renamed. The previous name turned out to conflict with
  a trademark, so it had to change everywhere: the plugin name, the settings,
  the hooks and the database tables.
• Because the tables are renamed, a site upgrading from 0.2.x starts with
  empty settings and an empty document archive. The old rows are left in the
  database untouched, but the plugin no longer reads them. See the upgrade
  notice.
• Pro licences must be activated again after upgrading. The licence record is
  stored under the plugin slug, and the slug changed with the name, so the
  plugin cannot find the old one.
• The built-in PDF template now uses FPDF 1.9.0 instead of 1.8.2.
• The free version no longer calls load_plugin_textdomain(). WordPress loads
  translations for wordpress.org plugins on its own; the call remains in the
  Pro version, which ships its own translation files.

0.2.1

• Poland: the legal basis for a VAT exemption now goes to the field KSeF
  expects — a Polish act, an EU directive, or “other” — instead of always
  “other”.

0.2.0

• Poland: KSeF FA(3) generation and submission. Invoices are sent to the
  national platform, the KSeF number is recorded against the order and shown
  on the order screen.
• Documents that have been sent are never sent twice, even if a retry happens
  after a timeout or a crash.
• Settings for the KSeF token and environment; the test environment is the
  default and invoices sent there have no legal effect.

0.1.0

• First release.
• Pre-flight check with five rule groups covering seller identity, customer
  identity, VAT categories, invoice totals and required fields.
• EN 16931 mapping with tax category resolution for domestic, OSS, reverse
  charge, intra-community and export scenarios.
• Factur-X (PDF/A-3) and XRechnung 3.0 output.
• Document archive with SHA-256 integrity checks, versioning and an audit trail.
• Optional validation against the official EN 16931 Schematron rule set.