XRechnung Validator Online – Check XML for Free
Upload an existing XRechnung XML file and review errors and warnings in seconds, without registration.
Drag and drop your XRechnung XML file here
or to select a .xml file
Maximum file size: 5 MB · No permanent storage
How your file is processed
The file is sent to the QuoteCash backend and the configured validation service for checking. The QuoteCash application does not permanently store the XML as a file or in its database and does not log raw XML or Base64 content. The application does not retain the content after the request completes. See our Privacy Policy (section 8f) for details.
How the free XRechnung validator works
Select an XML file, submit it for validation, and review whether the configured validator accepted it. Errors and warnings are shown with their rule identifiers and messages so you can trace the problem back to invoice data or generation logic.
QuoteCash does not repair or replace the uploaded file. Keep the original XML in your own archive and regenerate it in the source system after correcting customer data, tax details, references, or totals.
What the XRechnung validator checks
QuoteCash sends the XML to a configured KoSIT-compatible validation service and parses its structured report. The versions and rules executed depend on that service’s configuration.
The report can cover format and profile recognition, schema and Schematron checks, and business rules for mandatory fields, code lists, references, tax data, and arithmetic consistency. QuoteCash displays the rule identifiers, errors, and warnings returned by the service.
How to read the validation result
“Valid” means the configured validation service completed the executed rules without returning an error. An invalid result lists errors, and the interface can also display warnings.
Errors should be reviewed and corrected in the source system before delivery. Warnings need review in the context of the specific rule and recipient process. The current response and interface do not expose a separate notice category.
Typical errors: required fields, references, and totals
Common messages concern missing buyer references, incomplete address or tax data, unsupported codes, and totals that do not match line or tax amounts. The configured rule set determines which messages actually appear.
Correct the source customer or invoice data, recalculate totals and rounding, and then generate a new XML file. The validator does not alter the original.
- Add the buyer reference or Leitweg-ID in the source system.
- Correct the VAT ID, tax category, or exemption reason.
- Recalculate net, tax, gross, and rounding amounts.
- Review country, currency, unit codes, and addresses.
What a valid result means
A successful result confirms that the file satisfies the technical and business rules executed by the configured service. It does not confirm the commercial truth of invoice data or replace tax, legal, or accounting review.
Recipient-specific fields, portal rules, and contractual data may still apply. Successful XML validation therefore does not guarantee recipient acceptance, payment, or business approval.
Who the validator is suitable for
- Businesses checking incoming XRechnungenReview individual XML files received from suppliers or exported by another accounting system.
- Accounting and finance operationsUnderstand errors and warnings before a file is forwarded to an archive, portal, or recipient.
- SaaS developers and agenciesTest files produced by integrations and translate validator feedback into useful customer actions.
- ERP integratorsCheck mappings, required fields, codes, references, and totals before automating delivery.
API validation for developers
POST /api/v1/validate accepts a target format and existing XML in xml or base64-encoded XML in xml_base64. It uses business-scoped API keys and returns valid, received_as, and a structured validation object.
HTTP 200 confirms that QuoteCash processed the request. Integrations must inspect the top-level valid field or validation.valid together with returned errors and warnings before deciding whether delivery can continue.
The endpoint also supports PEPPOL and ZUGFeRD; factur-x, facturx, and cii are accepted as aliases for the ZUGFeRD target.
Last reviewed: July 24, 2026
A technical check with clear limits
A passing result confirms the rules executed by the configured validation service. It is not tax or legal approval and does not guarantee that every recipient portal will accept the file without additional requirements.
API example: validate existing XML
Automation flows can validate XML before it is delivered to a customer portal or marked as archived.
POST /api/v1/validate
Authorization: Bearer <api_key>
Content-Type: application/json
{
"format": "xrechnung",
"xml_base64": "<base64_encoded_xml>"
}- Use validation.valid, not only the HTTP status, before allowing delivery.
- Review warnings against the applicable rule set and recipient process.
Validation checklist for production teams
- 1Validate sample XML during development and QA.
- 2Run validation before every production delivery.
- 3Map errors to clear UI messages.
- 4Classify issues by customer data, invoice logic, tax logic, or recipient requirement.
- 5Archive the original XML and any required validation evidence in your own system.
Related QuoteCash pages
Official sources and standards
Frequently Asked Questions
How do I validate XRechnung XML online before sending it?
Upload an existing .xml file to the free validator. QuoteCash sends it to the configured validation service and shows whether validation passed together with any errors or warnings.
Does the validator generate a new invoice file?
No. The validation endpoint is designed for existing XML documents and does not generate a new XML or PDF artifact.
Can I send raw XML instead of a file upload?
Yes. The endpoint accepts raw XML in the xml field and also supports xml_base64.
What response code means my XML failed validation?
The validation endpoint returns 200 OK when the XML was accepted for checking. Success or failure comes from validation.valid or the top-level valid field in the JSON response.
Can I validate ZUGFeRD or PEPPOL with the same endpoint?
Yes. The format field supports xrechnung, peppol, and zugferd, and the zugferd validator also accepts factur-x, facturx, and cii as aliases.
Does the validator store my XML file permanently?
No. The QuoteCash application processes the file only for validation and does not permanently store it in a database or as a file. The XML is transmitted to the configured validation service and is not retained by the application after the request completes. Keep the original XML in your own archive for legal and operational retention needs.
Does validation replace accounting review?
No. Validation checks technical and structured-data rules. Finance and tax review may still be needed for business correctness.
Why can a PDF look correct while the XML fails?
The PDF is visual. Validation checks structured fields, calculations, codes, and references that may not be obvious in the visual document.