Fill the billing profile
Seller data, bank details and the customer fields the invoice needs are maintained once per project.
Invoicing
Every invoice can produce ZUGFeRD 2.x XML and feed a DATEV-oriented CSV export, with reverse charge and account mapping configured per project instead of hard-coded.
In short
ZUGFeRD 2.x XML generated per invoice
DATEV-oriented CSV export from real invoice data
Reverse charge under § 13b UStG, project-wide
Specifications
Capabilities
UN/CEFACT Cross Industry Invoice in the EN 16931 profile with seller and buyer data, line items, tax indicators and reverse-charge codes, stored per invoice.
Download a DATEV-oriented CSV directly from the billing dashboard, built from stored amounts, tax rates, references, customer and seller data.
A project flag sets VAT to 0 %, adds the reverse-charge note to invoices, uses CategoryCode AE with an exemption reason in the XML and tags rows with [RC] in the export.
Revenue account, contra account and cost centre are configured per project rather than hard-coded, and the CSV carries the extra columns to match.
Customer VAT ID, address lines, postal code, city and country are first-class fields, so the document is complete without manual edits.
A dedicated billing tab collects reverse-charge configuration, DATEV account mapping, the CSV export and ZUGFeRD information in one place.
Invoicing
The export is wired into the existing invoice management and its permissions, so no separate back-office tool is involved. Admin, project and buyer views all read the same invoice records, which is what makes the accounting export trustworthy.
How it works
Seller data, bank details and the customer fields the invoice needs are maintained once per project.
Set the reverse-charge flag if it applies and map revenue account, contra account and cost centre for DATEV.
Invoices are created from real orders with line items, tax rate and references; ZUGFeRD XML is generated per invoice.
Download the DATEV-oriented CSV, or pull ZUGFeRD XML per invoice through its REST endpoint.
Use cases
Business buyers who need a complete invoice with VAT ID and address before they can expense a ticket.
Public-sector reporting where structured e-invoicing is a requirement, not a nice-to-have.
Recurring season revenue that has to land in the right revenue account and cost centre every month.
FAQ
Configure your billing profile once and let every order produce a compliant document.