Technical e-invoice integration
XRechnung API: what existing systems need
An XRechnung API is an integration task. The key questions are data structure, export route, validation and controlled handover.
Start with the data
Check whether supplier, recipient, invoice number, line items, tax information, payment terms and references are available in structured form. A PDF export alone does not answer that question.
Possible integration routes
Depending on the system, an API, XML export, SQL query, CSV handover or controlled middleware may fit. The route should be traceable, testable and proportionate to invoice volume.
Validation and feedback
An interface needs a checkpoint before handover. Errors should return to the process with clear feedback and an assigned owner.
Start the analysis
The free Compatibility Check collects technical facts and shows which information is still needed for a credible effort estimate.
Test cases and operations
Plan tests for new customers, corrections, credit notes, multiple tax rates, missing fields and retries. Record input, result, error and approval so the workflow remains traceable in operations.
Align with accounting
The interface does not end at XML. Align naming, handover, archive, feedback and ownership with the team that actually reviews and sends invoices.
Questions before fixed pricing
A credible technical assessment benefits from an anonymised example, the current process description, data format, recipient groups, monthly volume and available exports. We separate technical work packages from open business or legal questions.
Result of the technical assessment
The assessment names a likely integration route, missing capabilities, data-quality and operational risks, and the next tests. Implementation starts only after scope, ownership and a fixed-price proposal are agreed.
Keep your existing ERP
Send one sample invoice or process description. We assess a technical integration route for XRechnung or ZUGFeRD without promising legal compliance.
Open the Compatibility Check →