Check the e-invoice before sending: stop faulty invoices automatically

An incorrect e-invoice is worse than none at all: it can be rejected, jeopardise the input tax deduction, and create correction work. The best protection is to stop faulty invoices before they are sent.

> Quick answer: A good conversion checks every e-invoice against EN 16931 (KoSIT) and verifies the mandatory fields. If something is missing or validation fails, generation is blocked and the invoice is flagged for review – the file is only created once the data is complete and actively confirmed.

Two levels of checking

1. Formal validation: the generated XML is checked against the official KoSIT schemas and the business rules of EN 16931 (incl. CIUS DE). Violations do not result in a silent, faulty file but in a stop.
2. Mandatory-field check: if the invoice number, a date, the seller or buyer name, or an amount is missing, this is detected and shown before anything is generated.

Stop and flag instead of waving through

The decisive difference from a plain „convert button“: faulty or incomplete invoices are automatically stopped and flagged for review. This way, no non-compliant invoice ends up in the outbox by accident.

Why manual confirmation counts

Software can check plausibility, but it cannot assume tax responsibility. That is why a deliberate confirmation of the reviewed details makes sense – especially the tax classification (standard taxation, reverse charge, small-business scheme …). This creates a traceable review record and prevents an assumption from slipping through unnoticed.

Conclusion

Check e-invoices before they go out: EN 16931 validation plus a mandatory-field check, combined with a deliberate confirmation. That way you stop faulty invoices instead of having to fix them at the recipient's end.

---

TaxLayer blocks generation on missing mandatory fields or validation errors and requires a deliberate review. Questions to info@landauer.de.