[{"data":1,"prerenderedAt":924},["ShallowReactive",2],{"locale-routes":3,"page-\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd":184,"insights-author-\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd":730},{"home":4,"privacy":7,"framework-focus":10,"framework":13,"framework-principles":16,"imprint":19,"contact":22,"shopware-agency-b2b":25,"shopware-agency-electronics":28,"shopware-agency-development":31,"shopware-agency-geo":34,"shopware-agency":37,"shopware-agency-pricing":40,"shopware-agency-migration":43,"shopware-agency-seo":46,"shopware-agency-support":49,"location-hamburg":52,"location-munich":55,"about":58,"about-mission":61,"about-partners":64,"services-consulting":67,"services-development":70,"services":73,"services-optimization":76,"services-growth":79,"insights-ai-sales-channels-shopware":82,"insights-b2b-shop-starten-checkliste":85,"insights-ecommerce-deadlines-2026-27":88,"insights-e-invoice-b2b-shopware-xrechnung-zugferd":91,"insights-handelskoenig-b2b-quotes":94,"insights-shopware-5-eol":97,"insights-shopware-6-7-release":100,"insights-shopware-6-8-outlook":103,"insights-shopware-6-plans-pricing-2026":106,"insights-shopware-6-migration-noetig":109,"insights-shopware-gmv-2026":112,"insights-shopware-vs-shopify-2026":115,"insights-shopware-maintenance-retainer-development":118,"insights-withdrawal-button-shopware-6":121,"whitepaper-agentic-commerce-b2b-beschaffung":124,"whitepaper-compliance-2026-27":126,"whitepapers":129,"whitepaper-kanalverbund-marktplatz-shop-agentic":132,"whitepaper-shopware-6-boutique-vs-grossagentur-tco":134,"case-comspot-focus":136,"case-converge-focus":139,"case-framily-focus":142,"case-handelskoenig-focus":145,"case-lupa-focus":148,"case-shifter-focus":151,"case-topi-focus":154,"case-xucker-focus":157,"talks-beyond-seo-scuc-2026":160,"talks":163,"talks-shopware-container-hosting-hitc-2026":166,"talks-symfony-cli-docker-scuc-2025":169,"webinars":172,"team-alex-jank":175,"team-benedikt-rillox":178,"team":181},{"de":5,"en":6},"\u002F","\u002Fen",{"de":8,"en":9},"\u002Fdatenschutz","\u002Fen\u002Fprivacy",{"de":11,"en":12},"\u002Fframework\u002Ffocus","\u002Fen\u002Fframework\u002Ffocus",{"de":14,"en":15},"\u002Fframework","\u002Fen\u002Fframework",{"de":17,"en":18},"\u002Fframework\u002Fprinzipien","\u002Fen\u002Fframework\u002Fprinciples",{"de":20,"en":21},"\u002Fimpressum","\u002Fen\u002Fimprint",{"de":23,"en":24},"\u002Fkontakt","\u002Fen\u002Fcontact",{"de":26,"en":27},"\u002Fshopware-agentur\u002Fb2b","\u002Fen\u002Fshopware-agency\u002Fb2b",{"de":29,"en":30},"\u002Fshopware-agentur\u002Felektronikhandel","\u002Fen\u002Fshopware-agency\u002Felectronics-retail",{"de":32,"en":33},"\u002Fshopware-agentur\u002Fentwicklung","\u002Fen\u002Fshopware-agency\u002Fdevelopment",{"de":35,"en":36},"\u002Fshopware-agentur\u002Fgeo","\u002Fen\u002Fshopware-agency\u002Fgeo",{"de":38,"en":39},"\u002Fshopware-agentur","\u002Fen\u002Fshopware-agency",{"de":41,"en":42},"\u002Fshopware-agentur\u002Fkosten","\u002Fen\u002Fshopware-agency\u002Fpricing",{"de":44,"en":45},"\u002Fshopware-agentur\u002Fmigration","\u002Fen\u002Fshopware-agency\u002Fmigration",{"de":47,"en":48},"\u002Fshopware-agentur\u002Fseo","\u002Fen\u002Fshopware-agency\u002Fseo",{"de":50,"en":51},"\u002Fshopware-agentur\u002Fsupport","\u002Fen\u002Fshopware-agency\u002Fsupport",{"de":53,"en":54},"\u002Fstandorte\u002Fhamburg","\u002Fen\u002Flocations\u002Fhamburg",{"de":56,"en":57},"\u002Fstandorte\u002Fmuenchen","\u002Fen\u002Flocations\u002Fmunich",{"de":59,"en":60},"\u002Fueber-uns","\u002Fen\u002Fabout",{"de":62,"en":63},"\u002Fueber-uns\u002Fmission","\u002Fen\u002Fabout\u002Fmission",{"de":65,"en":66},"\u002Fueber-uns\u002Fpartner","\u002Fen\u002Fabout\u002Fpartners",{"de":68,"en":69},"\u002Fleistungen\u002Fberatung","\u002Fen\u002Fservices\u002Fconsulting",{"de":71,"en":72},"\u002Fleistungen\u002Fentwicklung","\u002Fen\u002Fservices\u002Fdevelopment",{"de":74,"en":75},"\u002Fleistungen","\u002Fen\u002Fservices",{"de":77,"en":78},"\u002Fleistungen\u002Foptimierung","\u002Fen\u002Fservices\u002Foptimization",{"de":80,"en":81},"\u002Fleistungen\u002Fwachstum","\u002Fen\u002Fservices\u002Fgrowth",{"de":83,"en":84},"\u002Finsights\u002Fai-verkaufskanaele-shopware","\u002Fen\u002Finsights\u002Fai-sales-channels-shopware",{"de":86,"en":87},"\u002Finsights\u002Fb2b-shop-starten-checkliste-shopware","\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist",{"de":89,"en":90},"\u002Finsights\u002Fe-commerce-fristen-2026-27","\u002Fen\u002Finsights\u002Fe-commerce-deadlines-2026-27",{"de":92,"en":93},"\u002Finsights\u002Fe-rechnung-b2b-shopware-xrechnung-zugferd","\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd",{"de":95,"en":96},"\u002Finsights\u002Fhandelskoenig-b2b-angebotsanfragen","\u002Fen\u002Finsights\u002Fhandelskoenig-b2b-quote-requests",{"de":98,"en":99},"\u002Finsights\u002Fshopware-5-eol","\u002Fen\u002Finsights\u002Fshopware-5-end-of-life",{"de":101,"en":102},"\u002Finsights\u002Fshopware-6-7-release-update-vorteile","\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits",{"de":104,"en":105},"\u002Finsights\u002Fshopware-6-8-ausblick-roadmap-vorbereitung","\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation",{"de":107,"en":108},"\u002Finsights\u002Fshopware-6-lizenzen-kosten-2026","\u002Fen\u002Finsights\u002Fshopware-6-plans-pricing-2026",{"de":110,"en":111},"\u002Finsights\u002Fshopware-6-migration-noetig","\u002Fen\u002Finsights\u002Fshopware-6-migration-necessary",{"de":113,"en":114},"\u002Finsights\u002Fshopware-gmv-berechnung-1-million-grenze","\u002Fen\u002Finsights\u002Fshopware-gmv-calculation-one-million-threshold",{"de":116,"en":117},"\u002Finsights\u002Fshopware-vs-shopify-vergleich-2026","\u002Fen\u002Finsights\u002Fshopware-vs-shopify-comparison-2026",{"de":119,"en":120},"\u002Finsights\u002Fshopware-wartung-retainer-weiterentwicklung","\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development",{"de":122,"en":123},"\u002Finsights\u002Fwiderrufsbutton-shopware-6","\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6",{"de":125},"\u002Fwhitepapers\u002Fagentic-commerce-b2b-beschaffung",{"de":127,"en":128},"\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27","\u002Fen\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27",{"de":130,"en":131},"\u002Fwhitepapers","\u002Fen\u002Fwhitepapers",{"de":133},"\u002Fwhitepapers\u002Fkanalverbund-marktplatz-shop-agentic",{"de":135},"\u002Fwhitepapers\u002Fshopware-6-boutique-vs-grossagentur-tco",{"de":137,"en":138},"\u002Fcase-studies\u002Fcomspot-focus","\u002Fen\u002Fcase-studies\u002Fcomspot-focus",{"de":140,"en":141},"\u002Fcase-studies\u002Fconverge-focus","\u002Fen\u002Fcase-studies\u002Fconverge-focus",{"de":143,"en":144},"\u002Fcase-studies\u002Fframily-focus","\u002Fen\u002Fcase-studies\u002Fframily-focus",{"de":146,"en":147},"\u002Fcase-studies\u002Fhandelskoenig-focus","\u002Fen\u002Fcase-studies\u002Fhandelskoenig-focus",{"de":149,"en":150},"\u002Fcase-studies\u002Flupa-focus","\u002Fen\u002Fcase-studies\u002Flupa-focus",{"de":152,"en":153},"\u002Fcase-studies\u002Fshifter-focus","\u002Fen\u002Fcase-studies\u002Fshifter-focus",{"de":155,"en":156},"\u002Fcase-studies\u002Ftopi-focus","\u002Fen\u002Fcase-studies\u002Ftopi-focus",{"de":158,"en":159},"\u002Fcase-studies\u002Fxucker-focus","\u002Fen\u002Fcase-studies\u002Fxucker-focus",{"de":161,"en":162},"\u002Fvortraege\u002Fbeyond-seo-scuc-2026","\u002Fen\u002Ftalks\u002Fbeyond-seo-scuc-2026",{"de":164,"en":165},"\u002Fvortraege","\u002Fen\u002Ftalks",{"de":167,"en":168},"\u002Fvortraege\u002Fshopware-container-hosting-hitc-2026","\u002Fen\u002Ftalks\u002Fshopware-container-hosting-hitc-2026",{"de":170,"en":171},"\u002Fvortraege\u002Fsymfony-cli-docker-scuc-2025","\u002Fen\u002Ftalks\u002Fsymfony-cli-docker-scuc-2025",{"de":173,"en":174},"\u002Fwebinare","\u002Fen\u002Fwebinars",{"de":176,"en":177},"\u002Fteam\u002Falex-jank","\u002Fen\u002Fteam\u002Falex-jank",{"de":179,"en":180},"\u002Fteam\u002Fbenedikt-rillox","\u002Fen\u002Fteam\u002Fbenedikt-rillox",{"de":182,"en":183},"\u002Fteam","\u002Fen\u002Fteam",{"id":185,"title":186,"author":187,"body":188,"citations":691,"description":706,"draft":707,"extension":708,"image":709,"meta":712,"navigation":713,"ogImage":714,"path":93,"publishedAt":715,"readingTime":716,"robots":714,"schemaOrg":714,"seo":717,"sitemap":721,"stem":722,"tags":723,"translationKey":728,"updatedAt":714,"__hash__":729},"insights_en\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd.md","E-invoices in B2B commerce: XRechnung and ZUGFeRD with Shopware","benedikt-rillox",{"type":189,"value":190,"toc":656},"minimark",[191,203,206,209,212,217,220,235,238,242,245,302,307,310,313,317,320,324,344,347,350,354,375,384,387,391,394,398,401,404,429,432,436,445,448,471,474,478,481,484,491,495,498,522,525,529,532,536,539,543,546,550,553,557,560,564,571,575,578,582,585,589,592,596,599,603,606,610,613,617,620,626,630],[192,193,194,195,202],"p",{},"A PDF invoice sent by email is easy to read, but it is not a structured\ne-invoice under ",[196,197,201],"a",{"href":198,"rel":199},"https:\u002F\u002Fwww.gesetze-im-internet.de\u002Fustg_1980\u002F__14.html",[200],"nofollow","section 14 of the German VAT Act\n(UStG)",". Since 1\nJanuary 2025, domestic German businesses must be able to receive e-invoices,\nand from 2028 issuing them becomes mandatory for domestic B2B transactions —\nwhile Shopware 6 generates ZUGFeRD documents natively since version 6.6.10.0.\nXRechnung requires an extension or ERP integration depending on the target\nprocess.",[192,204,205],{},"For the recipient, a plain PDF still means extracting, checking and\ntransferring its data into an ERP. An e-invoice stores invoice data in a\nstructured format that software can process directly.",[192,207,208],{},"For a B2B store operator, this is not only a file-format decision. The invoice\nmust be created from correct order, customer, tax and payment data, generated\nfor the right business event, pass a technical validation and reach the\nrecipient reliably.",[192,210,211],{},"Shopware can support this process. The right solution depends on the Shopware\nversion, B2B process, ERP, target format and the requirements of business\ncustomers. This article explains XRechnung and ZUGFeRD, the German transition\ndeadlines and three ways to implement them with Shopware 6.",[213,214,216],"h2",{"id":215},"what-is-an-e-invoice","What is an e-invoice?",[192,218,219],{},"An e-invoice is not simply any invoice sent digitally. A PDF is a “different\ninvoice” unless it also contains a structured data part. An e-invoice must\ntransmit invoice information in a structured electronic format that can be\nprocessed automatically.",[192,221,222,223,228,229,234],{},"In Germany, permitted formats are based on the European EN 16931 standard.\n",[196,224,227],{"href":225,"rel":226},"https:\u002F\u002Fxeinkauf.de\u002Fxrechnung\u002F",[200],"XRechnung"," is a purely structured XML format.\n",[196,230,233],{"href":231,"rel":232},"https:\u002F\u002Fwww.ferd-net.de\u002F",[200],"ZUGFeRD"," combines a human-readable\nPDF with embedded structured XML data. With ZUGFeRD, both parts belong to one\nfile.",[192,236,237],{},"The structured data has priority: if the XML and the visual PDF part of a\nhybrid invoice differ, the XML is authoritative. Invoice generation and\nvalidation must therefore be designed together.",[213,239,241],{"id":240},"xrechnung-and-zugferd-compared","XRechnung and ZUGFeRD compared",[192,243,244],{},"The core difference: XRechnung is pure, machine-oriented XML based on\nEN 16931 with German business rules; ZUGFeRD combines a readable PDF\u002FA-3 with\nembedded XML in one file. Both qualify as e-invoices — which standard fits is\ndecided by recipient requirements and the ERP processes on both sides.",[246,247,248,267],"table",{},[249,250,251],"thead",{},[252,253,254,258,261,264],"tr",{},[255,256,257],"th",{},"Format",[255,259,260],{},"Structure",[255,262,263],{},"Human readability",[255,265,266],{},"Typical use",[268,269,270,287],"tbody",{},[252,271,272,278,281,284],{},[273,274,275],"td",{},[276,277,227],"strong",{},[273,279,280],{},"XML based on EN 16931 and German business rules",[273,282,283],{},"Not directly readable; a viewer is needed",[273,285,286],{},"ERP and public-sector processes, automated inbound processing",[252,288,289,293,296,299],{},[273,290,291],{},[276,292,233],{},[273,294,295],{},"PDF\u002FA-3 plus embedded XML",[273,297,298],{},"PDF is readable, XML is machine-readable",[273,300,301],{},"B2B invoices where people and systems use the same file",[303,304,306],"h3",{"id":305},"xrechnung-structured-and-machine-oriented","XRechnung: structured and machine-oriented",[192,308,309],{},"An XRechnung does not contain a PDF view. That is consistent for automated\ninvoice intake, but changes the human workflow: the recipient needs an XML\nviewer or an ERP. A B2B customer can therefore explicitly request XRechnung\neven if ZUGFeRD would also be technically valid.",[192,311,312],{},"In B2B, an invoice generally does not need a Leitweg-ID. That routing\nidentifier belongs to B2G invoices addressed to public authorities. Buyer\nreferences, purchase order numbers or customer numbers can still be required\nby the recipient and must be available in the data model.",[303,314,316],{"id":315},"zugferd-pdf-and-xml-in-one-file","ZUGFeRD: PDF and XML in one file",[192,318,319],{},"ZUGFeRD is a pragmatic starting point for many B2B processes: the recipient\nopens the PDF as usual while the ERP processes the XML. To qualify as an\ne-invoice under the applicable rules, the ZUGFeRD profile must meet EN 16931.\nThe MINIMUM and BASIC-WL profiles are not sufficient for that purpose; an\nEN-16931-conformant profile such as COMFORT or its current equivalent is\ntypically used.",[213,321,323],{"id":322},"which-deadlines-apply-in-germany","Which deadlines apply in Germany?",[192,325,326,327,331,332,337,338,343],{},"The deadlines in brief: Since 1 January 2025, domestic businesses must be\nable to receive e-invoices — an email inbox is sufficient in principle, and\nthere is no general receiving exemption for small businesses. For issuing,\ntransition rules apply: other invoice formats remain permitted until the end\nof 2026, or until the end of 2027 where the previous year's turnover was no\nmore than €800,000; from 2028, e-invoices are mandatory for domestic B2B\ntransactions in the normal case. The legal basis is\n",[196,328,330],{"href":198,"rel":329},[200],"section 14 UStG",";\nthe details are set out in the\n",[196,333,336],{"href":334,"rel":335},"https:\u002F\u002Fwww.bundesfinanzministerium.de\u002FContent\u002FDE\u002FFAQ\u002Fe-rechnung.html",[200],"Federal Ministry of Finance FAQ","\nand the\n",[196,339,342],{"href":340,"rel":341},"https:\u002F\u002Fwww.bundesfinanzministerium.de\u002FContent\u002FDE\u002FDownloads\u002FBMF_Schreiben\u002FSteuerarten\u002FUmsatzsteuer\u002FUmsatzsteuer-Anwendungserlass\u002F2025-10-15-einfuehrung-obligatorische-e-rechnung.pdf",[200],"BMF application letter",".",[192,345,346],{},"The rules concern transactions between domestic businesses; exceptions such as\nsmall-value invoices need separate review. Transition periods are not a reason\nto postpone preparation: customers, ERP and accounting need time for testing\nand process changes.",[192,348,349],{},"The current legal assessment should always be confirmed with a tax or legal\nadvisor. This article describes the technical implementation and is not tax\nadvice.",[213,351,353],{"id":352},"what-does-shopware-6-provide-natively","What does Shopware 6 provide natively?",[192,355,356,357,362,363,368,369,374],{},"Shopware has added e-invoicing to its document workflow in stages.\n",[196,358,361],{"href":359,"rel":360},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Forders\u002Foverview",[200],"According to\nShopware",", the\ncore supports ZUGFeRD documents from\n",[196,364,367],{"href":365,"rel":366},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.6.10.0",[200],"Shopware 6.6.10.0",". The\nstructured data can be provided as a separate XML file or embedded in the PDF.\nFrom ",[196,370,373],{"href":371,"rel":372},"https:\u002F\u002Fgithub.com\u002Fshopware\u002Fshopware\u002Freleases\u002Ftag\u002Fv6.7.9.0",[200],"Shopware 6.7.9.0",",\nadditional document types can be created in ZUGFeRD,\nincluding credit notes and cancellation documents.",[192,376,377,378,383],{},"The normal Shopware documents remain the basis: invoice, cancellation invoice,\ncredit note and delivery note. The\n",[196,379,382],{"href":380,"rel":381},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fsettings\u002Fdocuments",[200],"Shopware document settings","\nconfigure\nbusiness data, layout and the order information displayed. ZUGFeRD variants\nuse these data sources.",[192,385,386],{},"This does not mean that every installation immediately generates every desired\nXRechnung. The native document workflow particularly covers ZUGFeRD. For\nXRechnung, the appropriate route may be an extension, an ERP or a custom\nintegration. The important question is not the plugin name, but whether it\nsupports the required Shopware version, profile, correction and cancellation\ncases, tax logic and B2B data.",[213,388,390],{"id":389},"three-implementation-routes-for-xrechnung-and-zugferd","Three implementation routes for XRechnung and ZUGFeRD",[192,392,393],{},"Three routes lead to e-invoicing with Shopware: the core route for ZUGFeRD\n(from 6.6.10.0), an extension for XRechnung and mixed requirements, or an\nERP-led or custom integration where the ERP is the system of record for\ninvoices. Which route fits depends on the Shopware version, target format and\nsystem landscape.",[303,395,397],{"id":396},"_1-zugferd-with-the-shopware-core","1. ZUGFeRD with the Shopware core",[192,399,400],{},"For a B2B store on a current Shopware 6 version, the core route is the smallest\nstep if ZUGFeRD is sufficient. The invoice is generated from the existing\norder process; the appropriate ZUGFeRD variant is added, either embedded or as\nseparate XML.",[192,402,403],{},"Before production, verify at least:",[405,406,407,411,414,417,420,423,426],"ul",{},[408,409,410],"li",{},"complete seller and buyer addresses,",[408,412,413],{},"VAT ID and tax category,",[408,415,416],{},"invoice number and date,",[408,418,419],{},"line items, quantities, prices and tax amounts,",[408,421,422],{},"payment terms, method and due date,",[408,424,425],{},"purchase order number or other buyer reference,",[408,427,428],{},"shipping costs, discounts, credit notes and cancellations.",[192,430,431],{},"A visually correct PDF is not proof of a valid e-invoice. The XML must be\nvalidated against the relevant business rules and tested with real-world\nbusiness cases.",[303,433,435],{"id":434},"_2-an-extension-for-xrechnung-and-mixed-requirements","2. An extension for XRechnung and mixed requirements",[192,437,438,439,444],{},"If customers explicitly request XRechnung or you need additional profiles,\ndocument types and automated delivery rules, a Shopware extension is often the\nright route. The ",[196,440,443],{"href":441,"rel":442},"https:\u002F\u002Fstore.shopware.com\u002F",[200],"Shopware Extension Store","\noffers solutions for XRechnung and ZUGFeRD. They extend the document process,\ngenerate XML and can vary output by customer, country, tax case or order\nstatus.",[192,446,447],{},"Choosing one is an architecture decision, not a simple installation task.\nCheck:",[405,449,450,453,456,459,462,465,468],{},[408,451,452],{},"supported Shopware version and upgrade path,",[408,454,455],{},"XRechnung and ZUGFeRD profiles,",[408,457,458],{},"automatic or manual document generation,",[408,460,461],{},"PDF\u002FXML email delivery and customer-account downloads,",[408,463,464],{},"credit notes, partial cancellations and corrections,",[408,466,467],{},"buyer references, Leitweg-ID fields and international tax cases,",[408,469,470],{},"validation, logging and retry behaviour after delivery errors.",[192,472,473],{},"Test an extension in staging with anonymised or synthetic orders first. This\nprotects against more than format errors: it also exposes side effects in\nnumber ranges, order states and email automation.",[303,475,477],{"id":476},"_3-erp-led-or-custom-integration","3. ERP-led or custom integration",[192,479,480],{},"In complex B2B stores, the ERP is often the system of record for invoices.\nShopware transfers the order, the ERP creates and posts the invoice, and the\nERP or a specialised e-invoice service sends XRechnung or ZUGFeRD. Shopware\nthen makes the invoice available in the customer account or links it to the\norder.",[192,482,483],{},"This avoids duplicating invoice logic. It does require a robust state machine:\nwhat happens after a failed transfer, a correction, a partial cancellation or\na delayed response? A unique external invoice ID, idempotency, error logging\nand a manual retry path matter more than another admin button.",[192,485,486,487,490],{},"Our ",[196,488,489],{"href":33},"Shopware development"," service covers\nthese interfaces and custom document processes. For an existing store, the\nright starting point is a system audit, not immediately installing a plugin.",[213,492,494],{"id":493},"the-technical-flow-in-a-b2b-store","The technical flow in a B2B store",[192,496,497],{},"Whichever route you choose, a reliable flow follows seven steps: from\nidentifying the business customer, through generating invoice and XML from\nthe same source data and validating against EN 16931, to delivery,\naudit-proof logging and linking in the customer account. Simplified:",[499,500,501,504,507,510,513,516,519],"ol",{},[408,502,503],{},"The store identifies the business customer and provides customer, tax and\nreference data.",[408,505,506],{},"The order is checked and posted in Shopware or the ERP.",[408,508,509],{},"The system of record creates the invoice and XML from the same source data.",[408,511,512],{},"The file is validated against EN 16931 and the selected profile.",[408,514,515],{},"XRechnung or ZUGFeRD is sent through the agreed channel.",[408,517,518],{},"Document ID, status and delivery errors are logged for audit and retry.",[408,520,521],{},"Invoice, credit note or cancellation is linked in the customer account and,\nwhere appropriate, the ERP.",[192,523,524],{},"Do not convert a PDF into XML after the fact if the original line-item and tax\ndata are still available. The structured invoice should be generated directly\nfrom the business data model.",[213,526,528],{"id":527},"common-implementation-mistakes","Common implementation mistakes",[192,530,531],{},"Five mistakes dominate implementations: confusing PDF and XML, testing only\nthe standard case, ignoring recipient requirements, validating only after\nsending, and treating the Shopware version and its extensions separately.\nEach of them surfaces only in live operation — and then expensively.",[303,533,535],{"id":534},"confusing-pdf-and-xml","Confusing PDF and XML",[192,537,538],{},"A PDF emailed to a customer is not an e-invoice. A PDF with a QR code is not\nautomatically an EN-16931-compliant invoice either.",[303,540,542],{"id":541},"testing-only-the-standard-case","Testing only the standard case",[192,544,545],{},"Tests must cover discounts, shipping, multiple tax rates, tax-exempt items,\nintra-community supplies, credit notes and cancellations—not only normally\ntaxed goods with one delivery address.",[303,547,549],{"id":548},"ignoring-recipient-requirements","Ignoring recipient requirements",[192,551,552],{},"A customer may require XRechnung, a specific profile, a purchase order\nreference or a particular delivery channel. Before rollout, create a small\nrecipient profile with format, profile, channel, mandatory fields and an error\ncontact.",[303,554,556],{"id":555},"validating-after-sending","Validating after sending",[192,558,559],{},"The recipient's ERP is not a test environment. Validate before delivery and,\nideally, as part of automated document generation.",[303,561,563],{"id":562},"treating-version-and-extensions-separately","Treating version and extensions separately",[192,565,566,567,570],{},"E-invoicing touches documents, taxes, orders, status flows, email, customer\naccounts and often the ERP. Changes in one area can alter another. ",[196,568,569],{"href":51},"Shopware\nsupport and maintenance"," with staging tests and\ncontrolled releases reduces that risk.",[213,572,574],{"id":573},"a-practical-introduction-plan","A practical introduction plan",[192,576,577],{},"The introduction plan follows five steps: collect recipient requirements,\nchoose the system of record, close data gaps, test formats and integration,\nand monitor delivery and archiving. The order is deliberate — starting with\nthe plugin instead of the recipients means testing past the actual need.",[303,579,581],{"id":580},"_1-collect-recipient-requirements","1. Collect recipient requirements",[192,583,584],{},"Which customers require XRechnung? Is ZUGFeRD sufficient? Which profiles,\nreferences and delivery channels are expected?",[303,586,588],{"id":587},"_2-choose-the-system-of-record","2. Choose the system of record",[192,590,591],{},"Is the invoice created in Shopware, the ERP or a specialist e-invoice service?\nTwo systems must not independently generate invoice numbers and tax data.",[303,593,595],{"id":594},"_3-close-data-gaps","3. Close data gaps",[192,597,598],{},"Check company name, addresses, VAT ID, customer number, purchase order\nreference, tax logic, payment terms and product master data. Missing data is\nusually the real e-invoice project.",[303,600,602],{"id":601},"_4-test-format-and-integration","4. Test format and integration",[192,604,605],{},"Generate both formats, validate them and have the most important recipients or\ntheir ERP check test files. Include corrections and cancellations.",[303,607,609],{"id":608},"_5-monitor-delivery-and-archiving","5. Monitor delivery and archiving",[192,611,612],{},"Record generation, validation, delivery, retry and failure. An e-invoice is a\nstable process only when exceptions are handled as deliberately as the happy\npath.",[213,614,616],{"id":615},"conclusion-shopware-can-produce-e-invoicesthe-architecture-decides","Conclusion: Shopware can produce e-invoices—the architecture decides",[192,618,619],{},"Shopware 6 now provides a native basis for ZUGFeRD. XRechnung, complex\nrecipient profiles and ERP-led invoicing require an extension or custom\nintegration depending on the setup. In every case, the file is only the visible\npart. Correct B2B master data, tax-consistent cases, validation, error handling\nand clear ownership determine whether the process works.",[192,621,486,622,625],{},[196,623,624],{"href":12},"F.O.C.U.S. system"," starts with Facts: What data and\nsystems actually exist? We then define the objective, expose integration\nconstraints, implement the right route and operate it in a controlled way.\nThat turns e-invoicing into a reliable part of B2B commerce rather than an\nisolated plugin.",[303,627,629],{"id":628},"official-sources","Official sources",[405,631,632,638,644,650],{},[408,633,634],{},[196,635,637],{"href":334,"rel":636},[200],"German Federal Ministry of Finance: E-invoice FAQ",[408,639,640],{},[196,641,643],{"href":340,"rel":642},[200],"German Federal Ministry of Finance: E-invoice application letter",[408,645,646],{},[196,647,649],{"href":359,"rel":648},[200],"Shopware: Orders and ZUGFeRD documents",[408,651,652],{},[196,653,655],{"href":380,"rel":654},[200],"Shopware: Configure documents",{"title":657,"searchDepth":658,"depth":658,"links":659},"",2,[660,661,666,667,668,673,674,681,688],{"id":215,"depth":658,"text":216},{"id":240,"depth":658,"text":241,"children":662},[663,665],{"id":305,"depth":664,"text":306},3,{"id":315,"depth":664,"text":316},{"id":322,"depth":658,"text":323},{"id":352,"depth":658,"text":353},{"id":389,"depth":658,"text":390,"children":669},[670,671,672],{"id":396,"depth":664,"text":397},{"id":434,"depth":664,"text":435},{"id":476,"depth":664,"text":477},{"id":493,"depth":658,"text":494},{"id":527,"depth":658,"text":528,"children":675},[676,677,678,679,680],{"id":534,"depth":664,"text":535},{"id":541,"depth":664,"text":542},{"id":548,"depth":664,"text":549},{"id":555,"depth":664,"text":556},{"id":562,"depth":664,"text":563},{"id":573,"depth":658,"text":574,"children":682},[683,684,685,686,687],{"id":580,"depth":664,"text":581},{"id":587,"depth":664,"text":588},{"id":594,"depth":664,"text":595},{"id":601,"depth":664,"text":602},{"id":608,"depth":664,"text":609},{"id":615,"depth":658,"text":616,"children":689},[690],{"id":628,"depth":664,"text":629},[692,694,696,698,700,702,704],{"name":693,"url":198},"Section 14 UStG: issuing invoices (German VAT Act)",{"name":695,"url":334},"German Federal Ministry of Finance: e-invoice FAQ",{"name":697,"url":340},"German Federal Ministry of Finance: e-invoice application letter",{"name":699,"url":225},"XRechnung: standard of the German IT standards coordination office",{"name":701,"url":231},"ZUGFeRD: Forum elektronische Rechnung Deutschland (FeRD)",{"name":703,"url":359},"Shopware: orders and ZUGFeRD documents",{"name":705,"url":380},"Shopware: configure documents","XRechnung or ZUGFeRD for a B2B store? We explain the differences, German deadlines and three ways to generate and send structured e-invoices with Shopware.",false,"md",{"src":710,"alt":711},"\u002Fimages\u002Finsights\u002Fe-rechnung-b2b-shopware-xrechnung-zugferd.png","Benedikt Rillox presents the Shopware process for XRechnung and ZUGFeRD in B2B commerce",{},true,null,"2026-08-17",11,{"title":718,"description":719},"B2B e-invoices with Shopware: XRechnung & ZUGFeRD",{"Implement e-invoices in a B2B Shopware store":720},"XRechnung, ZUGFeRD, German transition deadlines, Shopware core, extensions and ERP integration.",{"loc":93},"en\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd",[724,725,726,727],"B2B Commerce","Shopware","B2B","E-invoice","insights-e-invoice-b2b-shopware-xrechnung-zugferd","aRP7ktUVmpUergpPlImk6dUuz16-2BORXX_bjvS_lP4",{"id":731,"title":732,"alternateName":714,"bio":733,"body":734,"description":904,"events":905,"extension":708,"heroIllustration":907,"image":909,"meta":912,"name":911,"navigation":713,"ogImage":714,"path":180,"projects":714,"publishedAt":714,"robots":714,"role":913,"sameAs":914,"schemaOrg":714,"seo":918,"sitemap":919,"slug":187,"socials":920,"stem":921,"talks":714,"translationKey":922,"updatedAt":714,"__hash__":923},"team_en\u002Fen\u002Fteam\u002Fbenedikt-rillox.md","Benedikt Rillox — Founder & Strategist","Benedikt is managing partner of nuonic Digital, e-commerce consultant, and developer. Since 2009 he has been designing, building, and guiding digital platforms — from code through product ownership to strategic leadership.",{"type":189,"value":735,"toc":895},[736,740,746,749,752,755,759,762,765,768,771,774,778,781,784,787,810,813,817,820,823,826,843,847,850,853,859,862,866,869,872,875,879,882,885],[213,737,739],{"id":738},"about-benedikt-rillox","About Benedikt Rillox",[741,742,743],"blockquote",{},[192,744,745],{},"To me, technology is not a cost item — it's a competitive advantage.",[192,747,748],{},"I'm Benedikt Rillox, managing partner of nuonic Digital, e-commerce consultant, and developer.",[192,750,751],{},"Since 2009 I have been designing, building, and guiding digital platforms. My path led from hands-on software development through product ownership and technical team leadership into entrepreneurial responsibility.",[192,753,754],{},"That's why I know e-commerce from very different perspectives: from the code, from product development, from budget responsibility, and from strategic leadership. Today I combine these experiences to build commerce systems that don't just work technically, but measurably move businesses forward.",[213,756,758],{"id":757},"my-path-in-e-commerce","My path in e-commerce",[192,760,761],{},"I started out as a developer for web and e-commerce projects using technologies like Shopware, TYPO3, PHP, and Symfony. During that time I delivered solutions for smaller companies as well as for well-known brands and corporations — including Unilever, Paul Hewitt, and Framily.",[192,763,764],{},"At A-Z Gartenhaus my role evolved from Shopware developer to product owner. There I helped build and lead a ten-person development team and was responsible for the strategic evolution of the commerce platform and its connected third-party systems.",[192,766,767],{},"For the Legero United group I took on budget responsibility as product owner and coordinated the technical development of the Superfit, legero, and Think! shops.",[192,769,770],{},"As tech lead for ByteClub I planned and built the commerce platforms of the group with brands like COMSPOT, Shifter, GfBD, and IM.F.B. Further projects included ongoing support and the Shopware 6 rebuild for Xucker, as well as the design and development of a Shopware payment plugin for topi that digitizes B2B leasing and buy-on-invoice.",[192,772,773],{},"These stations taught me that successful commerce projects never consist of technology alone. They combine architecture, processes, people, and clear business goals.",[213,775,777],{"id":776},"from-development-to-strategy","From development to strategy",[192,779,780],{},"I am a developer, a strategist, and a problem solver.",[192,782,783],{},"I can dive deep into technical details without losing sight of the actual goal: What impact should a solution have for the company, its people, and its customers?",[192,785,786],{},"Today my focus is on designing, building, and continuously evolving demanding Shopware systems. Among other things, that includes:",[405,788,789,792,795,798,801,804,807],{},[408,790,791],{},"technical and strategic e-commerce consulting,",[408,793,794],{},"software and Shopware development,",[408,796,797],{},"architecture and system integration,",[408,799,800],{},"product ownership and project management,",[408,802,803],{},"performance and stable operations,",[408,805,806],{},"automation and process optimization,",[408,808,809],{},"technical team leadership and collaboration with agencies.",[192,811,812],{},"Across more than 25 client projects I have seen what makes digital initiatives fail — and what makes them succeed. Good technology needs a clear direction, realistic requirements, and the courage to make decisions.",[213,814,816],{"id":815},"i-dont-build-shops-just-so-theyre-online","I don't build shops just so they're online",[192,818,819],{},"A shop can work technically and still be too slow, too complicated, or economically ineffective. That's why at nuonic we don't just look at individual features. We look at the whole system: architecture, processes, integrations, performance, customer journey, and the ability to grow in the future.",[192,821,822],{},"I don't believe in best practices when they merely mean copying what everyone else is already doing. I believe in solutions that fit a company's business model, its team, and its actual goals.",[192,824,825],{},"That also means asking uncomfortable questions:",[405,827,828,831,834,837,840],{},[408,829,830],{},"Does this feature really need to exist?",[408,832,833],{},"Does it solve a relevant problem?",[408,835,836],{},"Will the system remain manageable in the long run?",[408,838,839],{},"Does the investment support a concrete business goal?",[408,841,842],{},"Can the platform grow without collapsing under its own complexity?",[213,844,846],{"id":845},"responsibility-begins-after-go-live","Responsibility begins after go-live",[192,848,849],{},"To me, go-live is not a success. It's the beginning of responsibility.",[192,851,852],{},"Only in day-to-day operations does a platform prove whether it truly holds up: whether it stays stable, whether the team can work with it efficiently, and whether it can evolve without unnecessary friction.",[192,854,855,856],{},"That's why my work doesn't end with the handover. That's where the real value creation begins: ",[276,857,858],{},"Optimize. Automate. Scale.",[192,860,861],{},"I don't think in short-term projects, but in commerce systems that carry their weight for the long run. Technology shouldn't just cover today's needs — it should open up new possibilities.",[213,863,865],{"id":864},"clarity-is-part-of-working-together","Clarity is part of working together",[192,867,868],{},"Good results don't come from saying yes to every idea. That's why I also say no — to bad requirements, to short-term thinking, and to projects without a discernible direction.",[192,870,871],{},"I prefer working with decision-makers who take ownership. With teams that are ready to genuinely change things instead of merely managing existing problems. And with companies that see technology as an investment — not as a necessary cost item.",[192,873,874],{},"That's not always comfortable. But it creates clarity, protects budgets, and leads to better results.",[213,876,878],{"id":877},"what-i-stand-for","What I stand for",[192,880,881],{},"I don't want to simply be busy. I want to create impact.",[192,883,884],{},"With nuonic we build commerce systems for companies that want to grow — faster, more stable, and more profitable.",[192,886,887,888,891,892,894],{},"Others talk about digitalization. We deliver it.",[889,890],"br",{},"\nOthers plan. We build.",[889,893],{},"\nOthers wait. We go.",{"title":657,"searchDepth":658,"depth":658,"links":896},[897,898,899,900,901,902,903],{"id":738,"depth":658,"text":739},{"id":757,"depth":658,"text":758},{"id":776,"depth":658,"text":777},{"id":815,"depth":658,"text":816},{"id":845,"depth":658,"text":846},{"id":864,"depth":658,"text":865},{"id":877,"depth":658,"text":878},"Projects, references, talks and events by Benedikt Rillox — founder and strategist at nuonic Digital, e-commerce consultant and developer since 2009.",[906],"omr-festival-2026",{"src":908,"alt":657},"\u002Fimages\u002Fteam\u002Fdefender.png",{"src":910,"alt":911},"\u002Fimages\u002Fteam\u002Fbenedikt-rillox.jpg","Benedikt Rillox",{},"Founder & Strategist",[915,916,917],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fbenedikt-rillox-4122b183\u002F","https:\u002F\u002Fgithub.com\u002Fbenediktrillox","https:\u002F\u002Fwww.xing.com\u002Fprofile\u002FBenedikt_Rillox",{"title":732,"description":904},{"loc":180},{"linkedin":915,"github":916},"en\u002Fteam\u002Fbenedikt-rillox","team-benedikt-rillox","rs5NE-Gj2TvYOV7llmWFwl6akstrUYU27E9kzJqG1aM",1787227067325]