Linux 软件免费装
Banner图

Deklera – E-Rechnung, XRechnung & KSeF for WooCommerce

开发者 ekremtekerek
更新时间 2026年9月18日 22:09
PHP版本: 8.2 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce factur-x ksef xrechnung e-rechnung

下载

0.3.10 0.3.11

详情介绍:

Producing e-invoice XML is the easy part. The hard part is that WooCommerce order data is rarely clean enough for it — and you find out weeks later, when an invoice comes back rejected and you have to work out which of two hundred business rules you broke. Deklera starts at that problem, not at the XML. Install it, open the report, and it tells you in plain language which of your recent orders would be rejected and why. Then it produces the document your country requires — XRechnung in Germany, Factur-X in France, KSeF FA(3) in Poland — and, on the Pro plan, checks it against the official EN 16931 rule set before it is issued. The pre-flight check This is what the plugin is for. It scans your orders and reports, for each problem: what happened, why it matters, the exact rule reference, and where to fix it. No jargon, no "invalid order". Real examples from the report: Findings are grouped by root cause, so a store-wide problem is reported once — not repeated on every order. Other things it catches: When Deklera has to make a judgement call — is this a service or goods? — it says so and marks the order for review instead of guessing silently. You can override it with a filter. Generating documents Deklera maps each order to the EN 16931 semantic model and produces the format your country requires: The tax category (standard, reverse charge, intra-community supply, export) is derived from where the seller and buyer are, not guessed from the rate alone. Where a decision is uncertain, Deklera says so instead of silently guessing. Documents are archived and never overwritten. Regenerating creates a new version; the old one stays, because quietly replacing an issued invoice is not something an audit will forgive. What this plugin does not do It does not transmit invoices, except to KSeF. Deklera produces the document and checks it; delivery goes through your own accredited provider — a PDP in France, a Peppol access point elsewhere. Poland is the exception, because there an unsent file is not an invoice at all. If you are looking for a plugin that sends invoices to a network, this is not it, and you should not buy it expecting that. It also does not guarantee legal compliance. No software can. Whether a specific invoice is accepted depends on your registration, your provider and rules that change over time. What Deklera can honestly promise is narrower and more useful: it tells you when your data will fail the standard, and it checks the finished document against the official rule set before you issue it. Who this is for Shops that already know they need e-invoicing and want to find out, now, whether their order data is ready — rather than discovering it one rejection at a time. France requires e-invoicing from September 2026, small businesses from September 2027. Poland's KSeF already covers most VAT-registered businesses. Germany accepts XRechnung and ZUGFeRD today, and under the E-Rechnungspflicht every business there has had to be able to receive an e-invoice since January 2025.

安装:

  1. Install and activate WooCommerce.
  2. Install and activate Deklera.
  3. Go to WooCommerce → Deklera and enter your VAT number, with the country prefix — FR40303265045, not 40303265045. WooCommerce has no field for this, so Deklera stores it.
  4. Check that your store address is complete under WooCommerce → Settings → General. Street, city, postcode and country are all mandatory on an invoice; if one is missing, Deklera will refuse to produce documents and tell you why.
  5. Read the pre-flight report.
On the Pro plan there is nothing more to set up. Activating your licence switches official validation on; the plugin authorises itself with that licence, so there is no second key to paste. The full guide — what the findings mean, when documents are produced and where they are stored, credit notes, the Polish KSeF flow, and the available filters — is at https://github.com/ekremtekerek/deklera/blob/main/docs/GUIDE.md

屏幕截图:

  • Findings grouped by root cause, each with the EN 16931 rule reference.
  • The e-invoice box on the order screen, with document versions and history.

升级注意事项:

0.3.8 Pro no longer needs a separate validation key: your licence now authorises official validation on its own. If you had pasted a key, it keeps working. The order screen also names the rule when a document is refused. 0.3.2 Adds a user guide and fixes the Pro setup screen, which previously left you with two empty fields and no explanation. Nothing to do after upgrading. 0.3.1 Fixes a Pro-only problem: the first validation of the day could be reported as "service unavailable". Nothing to do after upgrading. 0.3.0 The plugin is now called Deklera. Settings and the archive do not carry over: re-enter your VAT number, your KSeF token, and on Pro your licence. Invoices already registered with KSeF keep their numbers and are unaffected. 0.2.1 Polish stores that issue VAT-exempt invoices should reissue any exempt invoice sent with 0.2.0; the exemption basis was recorded in the wrong field. 0.2.0 Adds Poland (KSeF). Polish stores must enter a KSeF token; other stores are unaffected. 0.1.0 First release.

常见问题:

Does it work without a PDF invoice plugin?

Yes. Deklera includes a plain fallback template. If you already use a PDF invoice plugin such as WooCommerce PDF Invoices & Packing Slips, Deklera embeds the XML into that plugin's PDF instead, so your own design and branding are kept. The built-in template embeds its own font, so it writes any European alphabet and the finished Factur-X passes PDF/A-3 validation, which France requires. When another plugin produces the PDF, PDF/A conformance is up to that plugin.

Will my invoices be accepted?

Deklera produces documents that conform to EN 16931 and, on the Pro plan, verifies them against the official rule set before they leave your site. Whether a specific tax authority accepts a specific invoice also depends on your registration, your provider and rules that change over time. No plugin can promise that, and any that does is not being honest with you.

Does it send my invoices anywhere?

If your store is in Poland, yes: FA(3) invoices are submitted to KSeF, because there an invoice does not legally exist until KSeF has accepted it. That is the whole point of the Polish system. Everywhere else, no. On Pro, the document is sent to the validation service described under External services, and only if you enable it.

How is this different from the other invoice plugins?

Most WooCommerce invoice plugins already produce the file, and several produce it for nothing. So does Deklera: the entire free version is the format work — pre-flight report, Factur-X, XRechnung, credit notes, versioned archive — and nothing in it is switched off. That is the entry ticket, not the product. Producing a file is easy. Knowing whether the data behind it will survive the rules is not, and that is the part that costs you weeks when it goes wrong. So Deklera does the part nobody else checks. The report tells you which orders would be rejected before you issue them. Pro runs the finished document through the official rule set — the one that compiles to XSLT 2.0, which PHP cannot execute, which is why it runs as a service rather than on your site. If you already pay to send invoices over Peppol, this does not replace that. It is the check you run first, so that what you send comes back accepted.

Which countries are supported?

France (Factur-X, facture électronique), Germany (XRechnung, E-Rechnung) and Poland (KSeF FA(3)) are fully supported, and each one is measured against that country's own official validator before a release goes out. Other EU countries receive EN 16931 CII output, the common semantic standard behind all of them. Read that as the European baseline, not as your national profile. Several member states run their own mandatory format and their own platform — Italy's FatturaPA through the SdI is the clearest example — and Deklera does not produce those. If your country runs its own system, confirm that EN 16931 CII is accepted there before you rely on this plugin for it. Poland is supported, and it works differently from the others. KSeF is not just a format: an FA(3) invoice does not legally exist until KSeF has accepted it and assigned a number. So for Poland, Deklera does send: it submits each invoice to KSeF, waits for the number and records it against the order. This is the one case where the plugin transmits, because producing the file without sending it would leave you holding something that looks like an invoice and is not one. You need a KSeF token from your KSeF account. Start in the test environment — invoices sent there have no legal effect — and switch to production when you are satisfied. One limit worth stating plainly, because you would rather read it here than find it out later. The FA(3) document itself is generated against the Ministry's official XSD and validated against it. The submission client is written to the Ministry's own API specification — authentication, the encrypted session, the upload and the status polling — but it has not yet been exercised against a live KSeF account, because even the test environment needs a token issued from a Polish taxpayer's account. If you run it and something does not match, open an issue with what came back and it will be fixed. One thing to check if you issue VAT-exempt invoices: KSeF requires the legal basis for the exemption and keeps three separate fields for it — a Polish act, an EU directive, or another basis. Deklera reads your exemption reason and picks the matching field; if the text names no recognisable provision, it uses "other". That is a best effort, not a legal opinion, so have your accountant confirm the basis you record is the right one.

Is the free version actually usable?

Yes, and not in the "crippled demo" sense. The free version does everything the plugin itself is capable of: it scans your orders, reports every problem it finds, generates real Factur-X and XRechnung documents, produces credit notes for refunds, archives every version with a hash, and generates a document automatically when an order completes. Nothing in the code is switched off by a licence. Pro adds one thing, because it is the one thing the plugin cannot do on its own: validation against the official EN 16931 rule set before a document is issued. That rule set compiles to XSLT 2.0 and PHP's XSL extension only supports XSLT 1.0, so the check runs on a hosted service instead of on your site. See External services above.

更新日志:

0.3.11 0.3.10 0.3.9 0.3.8 0.3.7 0.3.6 0.3.5 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.2.1 0.2.0 0.1.0