Author: admin

Frankfurt am Main, 2021-12-06

In their coalition agreement the new german government apparently agreed on a
federal reporting system on VAT which will be used for the creation, validation and forwarding of invoices
“ein elektronisches Meldesystem bundesweit einheitlich einführen, das für die Erstellung, Prüfung und Weiterleitung von Rechnungen verwendet wird”.

After Italy introducing mandatory business-to-business e-invoices in 2019 and France set to do so in 2026 (source when this was still planned for 2025) this agreement, together with other documents like a (realtively independent) (german) study, a (german) complaint by the Federal Audit Office, a (german) investigation by the research service of the Bundestag as well as a (german) request by the political liberal party, make it look as if these were preparations to introduce an obligation for e-invoices in Germany as well.

Jochen Stärk
jstaerk@usegroup.de

Mustang 2.3.1 was released on Monday, October 25th 2021, and features an improved and features the document type PARTIAL_BILLING, invoiceReferencedIssueDate, as well as specifiedProcuringProject. It’s now also possible to add multiple referenced documents per line item and the importer has been improved and can now e.g. also act on XML input, not only PDF.

XRechnung 2.1.1 validation is now possible and a PDF issue has been fixed.

Despite it’s only a minor feature this version is also called 2.3.0 to indicate that the changed (internal) PDF upgrade is also a good opportunity to confirm the output PDF/A validity of at least some random samples 🙂

Mustang 2.2.1 adds support for references to orders on line level which was the last required attribute to send XRechnungen to the Deutsche Bahn AG.

Mustang 2.2.0 adds support to validate orders in the Order-X standard and fixes some other issues.

Mustang 2.1.1 fixes

• recipient contacts in XRechnung
• remove outdated dependency
• allow XRechnung without street
• only deploy library and validator to maven central, not core nor cli
• a correction should reference the original invoice via invoiceReferencedDocument, not buyerOrderReferencedDocument
• upgraded CEN Schematron validation (codes 24) to v1.3.4
• added unit tests for ubl conversion and visualization
• and adds the possibility to specify a seller order referenced document

Mustang 2.1.0 was released on 2021-01-19 and contains

• The possibility to convert from CII to UBL (thanks to this library)
• XRechnung now exports as 2.0 (in Mustang 2.0.3 this was automatically switched on 2021-01-01)

Additionally, it

• fixed a charge/allowance rounding error #212
• corrected intra community supply tax exemption category code
• removed Tradeparty.getZip in favor of getZIP (as it’s also setZIP)

Mustang 2.0.3 was released on 2020-12-06 and contains minor bugfixes, namely

• #201 correct embedded files in XRechnung
• don’t write “null” as paymentDescription if no Bank account is specified
• generic and unitcode/categorycode improvements (thanks to weclapp-dev) PR #207

Additionally

• support credit notes (additionally to corrected invoices)
• transaction calculator getGrandTotal now public, allowing to compare XML grant total with own calculations
• programmatically switch to XRechnung 2.0 if invoked after 2021-01-01

Mustang 2.0.2 was released on 2020-11-25 and contains minor bugfixes, namely

• A correction RE file attachments in XRechnung (#197) as well as
• another category code correction (PR #198 Thanks to weclapp-dev)

Additionally

• reverse charge is now supported at all and
• intra community supply is now also supported in the invoice class