Parameters
Challenge
Our Fix
Structured Invoices Received Without a Processing Path
Being able to technically receive an XRechnung or ZUGFeRD file doesn't help if there's no automated way to process it.
Incoming XRechnung and ZUGFeRD invoices are processed automatically into CargoWise, not left as files nobody can act on.
Data Errors Reaching Trading Partners
Incorrect VAT ID, tax codes, or line-item details in a structured invoice get rejected by the receiving system.
Invoice data is validated against CargoWise records before transmission, catching mismatches before they reach the recipient.
Issuing Obligations Phasing In by Company Size
Tracking exactly when your business needs to start issuing structured e‑invoices is easy to get wrong.
Your issuing capability is built ahead of your company-size deadline, so the phase-in date is a formality, not a scramble.
Invoice Formats Not Matching Between Systems
The invoice format CargoWise generates and what XRechnung or ZUGFeRD requires are not automatically the same.
Field mapping keeps your CargoWise invoice and the structured version in sync, with a clear audit trail between the two.
XRechnung and ZUGFeRD Are Not Interchangeable
Different trading partners and government bodies expect different formats, and getting the wrong one causes rejection.
CargoWise generates the correct format, XRechnung or ZUGFeRD, per trading partner or government body automatically.