Magento 2 E-Invoice Implementation Checklist

The safest E-Invoice project starts with recipients and data, not an extension setting. Use this checklist to turn a format requirement into an operating Magento process.

1. Define the invoice populations

Separate domestic B2B, public-sector, consumer, cross-border, marketplace, and exempt flows. Record who issues the legal invoice in each case. A single Magento installation can contain transactions with different requirements.

2. Collect recipient requirements

For major customers, record accepted format and version, delivery channel, endpoint identifier, buyer reference, purchase-order reference, contact, and test procedure. “Please send XRechnung” is not a complete interface specification.

3. Choose the Magento format scope

SoftwareSilo supports five invoice outputs, but the default is configured per store. Decide whether each store can use one default. If customers in the same store need different formats, plan a controlled customization or separate delivery layer.

4. Clean seller and buyer master data

Verify legal name, address, VAT ID, tax number, registration data, bank details, contact, and relevant electronic identifiers. Decide where Leitweg-ID, GLN, DUNS, or Peppol endpoint values are stored. Add ownership so stale data is corrected.

5. Map commercial data

Review SKU, description, unit, quantity, line price, discounts, shipping, payment method, payment terms, purchase-order number, buyer reference, and line accounting reference. Confirm whether values come from the order, invoice, customer, address, or product.

6. Test tax scenarios

Include standard and reduced rates, mixed rates, zero-rated lines, exemptions, reverse charge, intra-community supply, exports, and outside-scope cases that actually occur. Test rounding across line, tax, shipping, discount, and grand totals. Do not create fictional cases solely to fill a matrix.

7. Design invoice and credit memo workflows

Choose creation or payment as the trigger and immediate, queued, scheduled, or manual processing as the mode. Test partial and full refunds. Remember that SoftwareSilo credit memo output is currently limited to ZUGFeRD, XRechnung, and PEPPOL BIS Billing.

8. Set validation and failure handling

Use a validation level appropriate to rollout and decide whether errors block the business process. Configure notification recipients and retry policy. A failed invoice needs an owner, a useful message, and a safe way to regenerate without creating duplicates.

9. Design delivery and retention

Decide between email attachment, customer download, REST handoff, and external network delivery. PEPPOL BIS generation needs a separate Access Point for Peppol transport. Preserve the original structured file according to the merchant's retention policy.

10. Run acceptance tests

Test successful and rejected invoices with the actual receiver. Verify PDF and XML attachments, customer access, admin ZIP export, API authorization, queue workers, cron, retries, and monitoring. Record accepted sample files as future regression fixtures without using real customer data.

Go-live evidence

A responsible go-live file contains the requirement matrix, configuration export, sanitized accepted samples, validation results, recipient acceptance, operational owner, failure procedure, and update plan. This evidence is more valuable than a screenshot of a green status badge.

Sources

Last reviewed: August 9, 2026.