Skip to main content
Prefer a quick overview? Call us: +49 7222-80 79 002
Contact

E-invoicing in PrestaShop: deadlines and invoice workflows

Law and privacy By Jochen Schmid Reviewed by Damian Rutkowski 3 min read
AI-generated illustration: e-invoicing in PrestaShop — deadlines, processes and implementation.

Which e-invoicing deadlines apply?

According to the German Federal Ministry of Finance FAQ cited in this article, issuers may use other invoice types until the end of 2026; electronic formats such as PDF require the recipient’s consent. Where the issuer’s previous-year turnover does not exceed €800,000, the transition extends to the end of 2027. Certain EDI procedures also have transitional arrangements. From 2028, the general transition period ends for affected domestic B2B transactions.

This does not establish a general B2C obligation from 2028. Exceptions include small-value invoices up to €250 and invoices issued under the German small-business regime. Small businesses must nevertheless be able to receive e-invoices. Discuss application to your transactions with your tax adviser; cross-border sales and public-sector customers require separate consideration.

Why is an ordinary PDF not enough?

An e-invoice contains structured data for electronic processing. XRechnung and suitable ZUGFeRD profiles are commonly used formats. A visually complete PDF alone does not meet that requirement. Check the generated file and how it is processed, not just the store preview.

Which system should create the invoice?

If you already use ERP or accounting software, clarify its role first. It often makes sense to create the authoritative document there and transfer store orders into that system. Two systems independently generating invoice numbers and documents can cause reconciliation problems.

If PrestaShop is to provide the file, assess an extension compatible with your installed version. Use realistic test cases to demonstrate supported formats, corrections and delivery methods. An old compatibility list or announced feature is not proof of what the installed version currently supports.

Which integration tests are needed?

  • Standard order: correct customer details, items, tax and totals.
  • Different addresses: distinguish the invoice recipient from the delivery recipient.
  • Shipping and discounts: transfer both consistently.
  • Partial returns and cancellation: agree correction workflows with accounting.
  • File validation: check structure and required fields with a suitable validator.
  • Delivery and storage: test receipt, retrieval and error handling.

Invoice design, invoice corrections and payment by invoice

These are different requirements. Layout changes concern details such as logos and contact information. A substantive invoice correction must follow the agreed accounting process. Payment by invoice is a payment method and does not automatically generate a valid e-invoice. Keep these requirements separate when choosing an extension or commissioning work.

How can sjmedia help?

We establish which system generates the document, which data PrestaShop supplies and how errors become visible. This defines the technical implementation and testing scope. Tax interpretation remains with your tax adviser. Learn about our PrestaShop support and payment-method planning.

Source and date: Federal Ministry of Finance e-invoicing FAQ, checked for the original article on 7 October 2026. An earlier statement of a general B2C obligation from 2028 was corrected.

For scope, exemptions and transitional periods, consult the Federal Ministry of Finance questions and answers. The source review date for this article is 7 October 2026.