On January 1, 2027, businesses in Germany with annual turnover above €800,000 must start issuing structured e-invoices for their domestic B2B sales. Everyone else follows on January 1, 2028. If your company runs JD Edwards and has a German entity, you are very likely in the first group.
That leaves weeks, not months. The good news is that JD Edwards gets you most of the way there. This guide explains what the mandate actually requires, where JD Edwards output falls short, and what you can still do before the deadline.
Who the mandate applies to
Germany's mandate covers domestic B2B transactions by businesses established in Germany. If your German entity invoices other German businesses, it's in scope. Every in-scope business has been required to receive structured e-invoices since January 1, 2025, so your German customers should already be able to accept them.
The issuing deadline depends on turnover:
| Date | Who must issue structured e-invoices |
|---|---|
| January 1, 2027 | Businesses with prior-year turnover above €800,000 |
| January 1, 2028 | All remaining businesses |
A few points cause confusion. A company with no establishment in Germany that simply exports to German buyers is generally not covered by this mandate. Sales to consumers are outside it too. The turnover test looks at your 2026 figures, so check them now rather than in January. Your tax advisor should confirm scope for your specific entity structure.
What counts as a compliant e-invoice
A German e-invoice must carry its data in a structured format that follows the European standard EN 16931. In practice that means one of two formats:
- XRechnung: a pure XML file, designed for machines. It has no visual layout of its own.
- ZUGFeRD: a hybrid file. It's a PDF/A-3 document that people can read, with the structured XML embedded inside it. Factur-X, used in France, is technically aligned with ZUGFeRD.
Most B2B suppliers prefer ZUGFeRD because both the buyer's AP team and their software can use the same file. It's also where most mistakes happen. Watch for these traps:
- A plain PDF is not an e-invoice. From the deadline on, a PDF on its own no longer satisfies the requirement, however professional it looks.
- A PDF with a separate XML attachment is not ZUGFeRD. The XML has to be embedded inside a PDF/A-3 file, with the right metadata. Two files sent side by side don't qualify.
- Not every ZUGFeRD profile counts. The MINIMUM and BASIC WL profiles don't carry enough data, and Germany's finance ministry excludes them. Use the EN 16931 profile or higher, on ZUGFeRD version 2.0.1 or later.
Where JD Edwards leaves you: two files, one missing step
JD Edwards can produce both halves of a German e-invoice: the invoice print as a PDF, and the structured invoice data as XML. What it hands you is two separate files. That's exactly the combination trap number two describes.
Turning those two files into one compliant invoice takes several steps, every time:
- Match each invoice PDF to its correct XML file.
- Convert the PDF to PDF/A-3 and embed the XML with the required metadata.
- Check the result before it goes to a customer.
- Catch anything that fails without holding up the rest of the run.
- Pass the finished file on for delivery.
Teams can script this themselves, but PDF/A-3 conversion, embedding metadata and validation are specialized work. With the deadline weeks away, it's rarely where you want your developers spending time.
How AventX closes the gap
AventX handles that missing step. Its File System to JD Edwards action picks up the invoice PDFs and XML files JD Edwards produces, and turns each pair into a single hybrid invoice.
- Automatic matching. On a schedule you set, AventX pairs each invoice report with its invoice data.
- One compliant file. It builds a PDF/A-3 hybrid invoice in ZUGFeRD or Factur-X format, with the XML embedded inside, including XRechnung.
- Validation with a safety net. Invoices that can't be matched, or whose data fails validation, are moved to their own folder instead of stopping the run. Each run reports how many invoices went through and how many need attention.
- Clean housekeeping. Source files are archived once the hybrid invoice is produced.
Your delivery process doesn't change. AventX hands the finished file back to JD Edwards or to your downstream delivery tool, so invoices go out the way they do today. There's no new channel to test and nothing to change with your trading partners, which matters when the deadline is this close.
Already using AventX? If you rely on AventX for work orders or other JD Edwards documents, AventX is already connected to your JD Edwards environment and approved by your IT team. Adding German e-invoicing is a configuration project, not a new vendor onboarding.
Your eight-week action plan
There's still time to be ready on January 1 if you start now. Here's a practical sequence:
- Confirm scope. Check which of your entities are established in Germany, which invoices are domestic B2B, and whether 2026 turnover crosses €800,000.
- Check your JD Edwards output. Confirm JD Edwards is producing the XML for German invoices, and that it uses the EN 16931 profile or higher.
- Choose how you'll combine the files. Decide between building the assembly step in-house or using a tool such as AventX.
- Test with real invoices. Run a sample of actual German invoices through the full process and validate the output. Send test invoices to one or two key customers and confirm their systems accept them.
- Plan for exceptions. Decide who reviews invoices that fail matching or validation, and how quickly they're corrected and resent.
- Review archiving. E-invoices must be kept in their original electronic form for the statutory retention period. Make sure the hybrid file, not just a printout, is what gets archived.
Looking ahead: France is next
Germany isn't the only deadline on the calendar. France's mandate began on September 1, 2026: every business must be able to receive e-invoices, and large and mid-sized companies must already issue them. Small and micro-enterprises follow on September 1, 2027. Factur-X, one of France's accepted formats, is built the same way as ZUGFeRD, so the same hybrid invoice approach applies. France does add a requirement Germany doesn't: invoices must travel through a certified platform, a Plateforme Agréée. We'll cover what that means for JD Edwards teams in a follow-up post.
Get ready before January 1
If your German invoices still go out as plain PDFs, the deadline is close but manageable. Contact STR Software to see AventX turn your own JD Edwards invoice output into compliant hybrid e-invoices.
This article is general information, not tax or legal advice. Confirm your obligations with your tax advisor.
