E-invoice automation means generating XRechnung and ZUGFeRD directly from your inventory-management, ERP, or invoicing system, validating them against EN 16931 standard before sending, and automatically routing them to customer, portal, or Peppol network. NordFlux builds this outbound path for you and optionally integrates inbound receipt as well. You see each invoice and approve onward yourself.
Everyone must receive e-invoices from 2025 already—that's known. In outbound, most businesses keep sending PDFs, and the switch to structured formats gets pushed to later.
We don't automate a single export but the journey of the invoice from your system to the customer's inbox. We combine these five building blocks to fit your workflow.
The structured file emerges automatically from inventory, ERP, or invoicing software: XRechnung as pure XML or ZUGFeRD as PDF with embedded XML, in the profile per EN 16931. Your office staff creates the invoice as usual; the format arises in the background.
Savings 2–5 h per weekEvery invoice is automatically validated against EN 16931 before sending, including mandatory fields and arithmetic consistency. So no invoice goes out that the customer rejects for a format error, and you learn of mistakes before the customer does.
Effect no format errorRouting path ID for public clients, buyer reference, correct tax rates, and payment details are drawn from your master data and set correctly per customer. This saves you manually entering fields that otherwise stay blank in the XML and invalidate the invoice.
Effect complete invoiceThe finished e-invoice automatically goes where the customer needs it: via email, into a supplier portal, or over the Peppol network. The channel hangs on the customer master record; nobody needs to remember who expects which format over which path.
Savings no manual uploadThe structured original of every e-invoice is stored in a GoBD-compliant, immutable way, not just a PDF printout. In an audit, you retrieve the machine-readable file exactly as sent, including proof of sending.
Effect audit-ready filedThere's no single right tool. We choose based on what already runs at your end and which systems need to be integrated.
Flexible & self-hostedn8n connects your invoicing system, format generation, validation, and sending into one path and can run on a German server if you wish. Good if data sovereignty matters to you or many systems and customer channels come together.
Since 2025, all domestic businesses must receive e-invoices; issuing mandates kick in staggered in 2027 and 2028 (Source: German Federal Ministry of Finance). We clarify what applies to your business concretely before building anything.
Outbound and inbound invoices run through the same automation base with us, so no second tool and no duplicate effort emerge. If more than just invoice sending is broken at your end, look at total process automation.
From first conversation to running e-invoice path in 30 days, fixed price instead of open timesheets.
60 minutes, no obligation: we look at which system your invoices come from, which formats your customers need, and what the law means for you.
You get a concrete proposal: which path we build, which formats and channels we connect, and what it costs. A number, no surprises.
We build the automation and test it with your actual outbound invoices, validate the generated XRechnung against EN 16931, and trial-send to a test channel. You see every milestone.
Your team learns the path, gets documentation, and knows where to intervene. If a format or customer channel changes, we adjust as needed.
If not outbound but the flood of inbound invoices is your bottleneck, look at the inbound path: capture, validation, approval, and handoff to accounting. Both directions run through the same base with us.
In the free initial analysis, we clarify when the issuing mandate applies to you and how your invoice outbound becomes format-compliant. 60 minutes, no obligation, no sales pressure.
Since 1 January 2025, all domestic companies in the B2B sector must be able to receive e-invoices. Transitional periods apply to issuing them: companies with more than 800,000 euros in prior-year revenue must issue e-invoices from 1 January 2027, all others from 1 January 2028 (source: Federal Ministry of Finance). This is not legal advice; if in doubt, your tax advisor will clarify the exact deadlines for your case.
XRechnung is a pure XML format, ZUGFeRD from version 2.0.1 is a hybrid of a PDF with an embedded XML file. Both meet the European standard EN 16931 and thus count as an e-invoice within the meaning of the obligation (source: Federal Ministry of Finance). Which format makes sense depends on the customer: public sector clients usually require XRechnung, many business customers accept ZUGFeRD because they also see the invoice as a PDF.
In most cases yes, without having to change your invoicing program. We build the format generation either on an existing interface of your system or on the exported invoice data and convert it into XRechnung or ZUGFeRD. Whether a direct connection is possible or an intermediate step is needed, we clarify in the initial analysis on your specific system.
After the free initial analysis, you get a fixed price that depends on your source system, the required formats and the sending channels. A pure ZUGFeRD export by email is something different from a setup with several formats, Peppol and portal submission. The fixed price is set before you decide and does not change during the project.
Yes, the obligation to receive e-invoices has applied to all domestic companies since 1 January 2025 already (source: Federal Ministry of Finance). In practice, however, receiving alone is not enough; the invoices also need to be read, checked, approved and booked. We build this receiving side on the same basis, so that outgoing and incoming match up.
E-invoicing obligation 2025-2028 explained clearly: ZUGFeRD vs. XRechnung and how n8n automatically processes incoming e-invoices.
Receive from 2025, issue from 2027 or 2028: which e-invoice deadline your business faces and what the threshold depends on.
How the KoSIT Validator checks XRechnungen, what Schematron errors mean and how to automate validation.
How the KoSIT visualization turns an XRechnung into a readable HTML or PDF view without replacing the original.
