German freelancers
Freelancers often receive XML from external accounting tools and need a fast pass-or-fail check before sending it on to a buyer or archive.
Validation-only endpoint
XRechnung validator online
German e-invoicing deadlines make malformed XML expensive because failure often appears late, after an export step or customer upload.
If you already have XML from another system, the fastest safeguard is a validation endpoint that tells you whether the document is usable before it goes downstream.
Raw XML inputBase64 inputStructured errors
01QuoteCash
Accepted input
POST /api/v1/validate accepts both raw XML and xml_base64, which works well for direct API clients and queue-driven automation.
02QuoteCash
Stable response shape
The endpoint returns valid, received_as, and a structured validation object rather than human-only output, so automation can decide what to block or retry.
03QuoteCash
Same auth model
The route plugs into the same business-scoped API key model and plan quotas used elsewhere, making it easy to automate after manual validation succeeds.
API details
How QuoteCash handles free XRechnung XML validation
QuoteCash exposes validation at POST /api/v1/validate for teams that want checking without generation. The endpoint accepts a target format and either raw XML in the xml field or base64 data in xml_base64.
The response returns valid, received_as, and a structured validation object instead of a free-form message. It returns 200 when the document was accepted for validation, so callers inspect validation.valid rather than only the HTTP status code.
The same endpoint also supports PEPPOL and ZUGFeRD checks, which makes it useful as a shared validation layer during migrations or multi-format billing imports.
Audience fit
Who is this for?
Belgian SMBs
Teams validating several invoice formats from different upstream systems can use one endpoint instead of maintaining separate validators for each workflow.
SaaS developers
Developers need structured error handling, not only a browser-only validator. JSON output makes it easier to wire failed documents into retry and exception flows.
Agencies and resellers
Agencies often inherit XML from systems they do not control. A validation-only endpoint adds diagnostics without forcing a full generation migration on day one.
ERP integrators
Integrators need to separate payload acceptance from business acceptance. The route helps isolate malformed XML, wrong format selection, and upstream mapping errors.
Search intent
Frequently Asked Questions
- How do I validate XRechnung XML online before sending it?
- QuoteCash exposes POST /api/v1/validate for validation-only checks. You submit a format and either raw XML or base64-encoded XML, and the response returns valid together with a structured validation object.
- 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 the same validator endpoint check ZUGFeRD or PEPPOL documents?
- Yes. The format field supports xrechnung, peppol, and zugferd, and the zugferd validator also accepts factur-x, facturx, and cii as aliases.