Validating XRechnung against EN 16931: schema, Schematron, rejects
Three validation layers, one validator, five recurring rule failures: how SaaS teams check XRechnung before sending instead of after the customer complains.
Expert articles on EU billing, compliance and SaaS invoicing in the European market.
5 posts on E-invoicing. Show all posts
Three validation layers, one validator, five recurring rule failures: how SaaS teams check XRechnung before sending instead of after the customer complains.
Receiving since 2025, issuing from 2027 or 2028: which capabilities e-invoicing software for SaaS needs, when, and what to test in the vendor demo.
Germany's GoBD principles applied to a SaaS billing stack: locking, versioned master data, deletion dates from year end, and process documentation that keeps up with releases.
Peppol is a delivery network, not a format. When SaaS vendors need it, how access points and participant IDs work, and what your billing system has to store.
Seats, prorated add-on seats and API usage as an XRechnung: the fields your billing data model has to supply, and where the Leitweg-ID comes from.