First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3619531,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3619531,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3619531,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3619531,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3619531,"resolution":"1","location":"assets","locale":"","width":1280,"height":800},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3619531,"resolution":"2","location":"assets","locale":"","width":1280,"height":800},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3619531,"resolution":"3","location":"assets","locale":"","width":1280,"height":800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3619531,"resolution":"4","location":"assets","locale":"","width":1280,"height":800}},"screenshots":{"1":"The list view shows all issued invoices with date, due date, buyer, gross amount and validation status.","2":"The \"Neue Rechnung\" form has inline hints for every KoSIT-mandatory field (BT\/BR codes).","3":"The single-invoice view shows the generated file, header data, validation report and audit trail.","4":"The Settings page validates seller data against BR-DE-5 to BR-DE-28 on save (contact details, electronic address, VAT ID)."}},"plugin_section":[],"plugin_tags":[15149,247307,12480,263529,263530],"plugin_category":[45],"plugin_contributors":[272517],"plugin_business_model":[],"class_list":["post-343944","plugin","type-plugin","status-publish","hentry","plugin_tags-billing","plugin_tags-e-invoice","plugin_tags-invoice","plugin_tags-xrechnung","plugin_tags-zugferd","plugin_category-ecommerce","plugin_contributors-itdatex","plugin_committers-itdatex"],"banners":{"banner":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/banner-772x250.png?rev=3619531","banner_2x":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/banner-1544x500.png?rev=3619531","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/icon-128x128.png?rev=3619531","icon_2x":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/icon-256x256.png?rev=3619531","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/screenshot-1.png?rev=3619531","caption":"The list view shows all issued invoices with date, due date, buyer, gross amount and validation status."},{"src":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/screenshot-2.png?rev=3619531","caption":"The \"Neue Rechnung\" form has inline hints for every KoSIT-mandatory field (BT\/BR codes)."},{"src":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/screenshot-3.png?rev=3619531","caption":"The single-invoice view shows the generated file, header data, validation report and audit trail."},{"src":"https:\/\/ps.w.org\/itdatex-e-invoice-output\/assets\/screenshot-4.png?rev=3619531","caption":"The Settings page validates seller data against BR-DE-5 to BR-DE-28 on save (contact details, electronic address, VAT ID)."}],"raw_content":"\n
Since 1 January 2025, German businesses must be able to receive electronic invoices under \u00a7 14 UStG. From 2027\/2028 onwards, the issuing<\/em> side becomes mandatory too: B2B invoices must be sent as e-invoices (XRechnung or ZUGFeRD), not as PDFs or Word documents. itdatex E-Invoice Output<\/strong> generates these formats directly inside your WordPress installation.<\/p>\n\n The output of all three builders is accepted by the official KoSIT Validator using the XRechnung 3.0.2 \/ EN 16931 1.3.15 configuration. The plugin includes a test script ( The free version performs all generation locally on your own server. No invoice data leaves your WordPress installation. There is no telemetry, no automatic update check against a third party, no analytics, no external font or asset loading.<\/p>\n\n A separate Pro version (sold via wp.itdatex.support, not part of this free plugin) adds optional cloud-assisted features \u2014 KoSIT deep validation via API, AI-based KoSIT-error explanations in plain German, e-mail dispatch \u2014 and is opt-in only.<\/p>\n\n The plugin supports GoBD-conformant processes through immutable storage, SHA-256 hash chaining and a complete audit trail. As with any tooling: software cannot be \"GoBD-certified\" \u2014 conformity is a property of your<\/em> process. Consult your tax advisor.<\/p>\n\n If you also need to receive<\/em> incoming e-invoices, install itdatex E-Invoice Intake<\/strong> alongside this plugin. The two plugins share the same database schema and upload directory, so incoming and outgoing invoices live in the same hash chain. Either plugin works standalone; if both are installed, the order of activation does not matter.<\/p>\n\n The full source code is released under GPL-2.0-or-later. You can verify, audit and adapt the plugin yourself. Dependencies ( The plugin creates three database tables ( On uninstall, invoice data and files are NOT deleted by default<\/strong> because of statutory retention requirements (8 to 10 years under German tax and commercial law).<\/p>\n\n\n For B2G<\/em> invoices to German authorities (Bund, L\u00e4nder, Kommunen): XRechnung UBL<\/strong> with a Leitweg-ID in the Buyer Reference. For B2B<\/em> invoices: ZUGFeRD-PDF<\/strong> is the most polite choice \u2014 the recipient sees a normal PDF, machine-readable systems extract the XML. CII<\/strong> is useful when the recipient expects the EN 16931 CII payload without a PDF carrier (e.g. via PEPPOL).<\/p><\/dd>\n In the position editor, set the VAT category to It does not. The field is labelled \"Leitweg-ID \/ Buyer Reference\" because BT-10 (BR-DE-15) is XRechnung-mandatory but its content is up to you: in B2G that is the official Leitweg-ID; in B2B you can use a customer- or order-number. The plugin does not<\/em> validate the format against the Leitweg pattern.<\/p><\/dd>\n The free version makes no external HTTP calls. All generation, validation and storage happens locally. You can verify this by inspecting the source \u2014 the only network code path would be the optional Pro upgrade, which is not part of this free plugin.<\/p><\/dd>\n Yes. The plugin creates its own tables and upload directory on activation. If you later install the Intake plugin, both plugins share the existing schema \u2014 no migration needed.<\/p><\/dd>\n Every issued file is hashed (SHA-256) and compared against the file table. Re-running the same draft (same numbers, same VAT, same line items) produces an identical XML\/PDF byte sequence and triggers a duplicate response with the existing invoice id. This is intentional: invoice numbers should be re-used at the invoice level<\/em>, not at the file level. To re-issue a corrected version, change at least one byte (e.g. the issue date or the buyer reference).<\/p><\/dd>\n Yes. The protected upload directory uses both wp ausrg issue --from=draft.json --format=ubl|cii|zugferd-pdf reads a JSON draft and runs the same pipeline as the admin form. Useful for migrations from a different billing system. The seller data falls back to the plugin Settings if not present in the JSON.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat it does<\/h4>\n\n
\n
\n
wp ausrg issue --from=draft.json [--format=cii]<\/code> for scripted issuing<\/li>\n<\/ul>\n\nKoSIT-validated output<\/h4>\n\n
tools\/e2e-validate.php<\/code>) that you can run against a local KoSIT Validator instance to verify this on your own server.<\/p>\n\nPrivacy by design<\/h4>\n\n
GoBD-supporting, not GoBD-certified<\/h4>\n\n
Sister plugin<\/h4>\n\n
Open source<\/h4>\n\n
josemmo\/einvoicing<\/code> for UBL, horstoeko\/zugferd<\/code> for CII\/ZUGFeRD-PDF, setasign\/fpdf<\/code> for the PDF layout) are vendored with prefixed namespaces so they cannot conflict with other plugins in the same WordPress installation.<\/p>\n\n\n\n
\/wp-content\/plugins\/itdatex-e-invoice-output\/<\/code>, or install via the Plugins screen.<\/li>\n*_reing_invoices<\/code>, *_reing_files<\/code>, *_reing_audit_log<\/code>) and a protected upload directory under wp-content\/uploads\/itdatex-e-invoice-{random}\/<\/code>. If the sister plugin \"itdatex E-Invoice Intake\" is already installed, the existing tables and upload directory are reused \u2014 no duplicate storage.<\/p>\n\n\n
Which format should I choose?<\/h3><\/dt>\n
What about Kleinunternehmerregelung (\u00a7 19 UStG) and reverse charge?<\/h3><\/dt>\n
E<\/code> (exempt \u2014 Kleinunternehmer) or AE<\/code> (reverse charge) and the VAT rate to 0. The plugin generates the correct EN-16931 tax breakdown.<\/p><\/dd>\nWhy does the plugin demand a \"Leitweg-ID\" even for B2B invoices?<\/h3><\/dt>\n
Does the plugin send anything to your server?<\/h3><\/dt>\n
Can I use the plugin without the sister \"Intake\" plugin?<\/h3><\/dt>\n
How does the duplicate detection work?<\/h3><\/dt>\n
Does this work behind nginx?<\/h3><\/dt>\n
.htaccess<\/code> (Apache\/LiteSpeed) and a randomized directory name so that path guessing fails. File downloads always go through a capability-and-nonce-checked endpoint, never via a direct URL.<\/p><\/dd>\nHow do I issue invoices from a script?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n