# Validate e-invoices > Check Factur-X, ZUGFeRD and XRechnung invoices you receive with the KoSIT validator and veraPDF, as hybrid PDFs or CII and UBL XML: the verdict, supported formats, errors, limits and billing. > Part of the Dynamic Document API documentation. Index of all pages for agents: [llms.txt](https://dynamicdocumentapi.com/llms.txt), every page in one file: [llms-full.txt](https://dynamicdocumentapi.com/llms-full.txt). `POST /v1/einvoices/validate` checks an e-invoice you received, from any sender: a hybrid PDF (Factur-X or ZUGFeRD 2.x, or a PDF carrying an `xrechnung.xml`) or a standalone XML in UN/CEFACT CII or UBL 2.1. Since 1 January 2025, businesses in Germany must be able to receive e-invoices from other German businesses, so this is the step between your inbox and your accounting system: take the mail attachment, check it, then route it. The check uses the same validators and rules as the [e-invoices Dynamic Document API generates](https://dynamicdocumentapi.com/docs/e-invoicing): the KoSIT validator for the XML, and veraPDF for the PDF. Neither validator is modified. Checks are available on every plan, Free included. > **What a passed check means** > > A passed check means the file conforms to the standard: the schema, the profile's rules and, for a PDF, PDF/A-3b. It doesn't mean the invoice is right. Whether its content is correct for VAT, whether the visible pages match the XML and whether the sender is who they claim to be are for you to check. ## Check an invoice [#check-an-invoice] Upload the file, then pass the upload's ID as the source: cURL: ```bash curl https://api-eu.dynamicdocumentapi.com/v1/uploads \ -H "Authorization: Bearer $DYNAMIC_DOCUMENT_API_KEY" \ -F "file=@R-2026-0042.pdf" curl https://api-eu.dynamicdocumentapi.com/v1/einvoices/validate \ -H "Authorization: Bearer $DYNAMIC_DOCUMENT_API_KEY" \ -H "Idempotency-Key: inbox-2026-11-0042" \ -H "Content-Type: application/json" \ -d '{ "source": { "upload_id": "upl_01J9ZM1X3F7R8K2C4V6B8N0P2Q" }, "reference": "inbox-2026-11-0042" }' ``` Python: ```python import os import requests API = "https://api-eu.dynamicdocumentapi.com/v1" headers = {"Authorization": f"Bearer {os.environ['DYNAMIC_DOCUMENT_API_KEY']}"} with open("R-2026-0042.pdf", "rb") as file: upload = requests.post(f"{API}/uploads", headers=headers, files={"file": file}, timeout=60).json() response = requests.post( f"{API}/einvoices/validate", headers={**headers, "Idempotency-Key": "inbox-2026-11-0042"}, json={"source": {"upload_id": upload["id"]}, "reference": "inbox-2026-11-0042"}, timeout=130, ) if response.status_code == 422: problem = response.json() print("not checked:", problem["code"], problem["detail"]) else: result = response.json()["result"] print("valid" if result["valid"] else "invalid", result["document"]["profile"]) ``` A check reaches one of two verdicts. Both answer `200` with the render object, and the verdict is in `result`: ```json { "id": "rnd_01J9ZM1X3F7R8K2C4V6B8N0P2T", "object": "render", "status": "succeeded", "kind": "einvoice_validation", "input_type": "einvoice", "output_format": "xml", "files": [], "pages": 1, "billed_renders": 1, "reference": "inbox-2026-11-0042", "result": { "valid": false, "document": { "container": "pdf", "attachment": "factur-x.xml", "syntax": "cii", "profile": "EN16931", "specification_id": "urn:cen.eu:en16931:2017" }, "conformance": { "einvoice": { "profile": "EN16931", "syntax": "cii", "status": "passed", "validator": "KoSIT Validator 1.6.3", "scenario": "Factur-X EN 16931 (CII)", "errors": [], "warnings": [] }, "pdfa": { "level": "3b", "status": "failed", "validator": "veraPDF 1.30.2", "profile": "PDF/A-3B validation profile", "errors": [ { "rule": "6.2.11.4.1-1", "message": "The font programs for all fonts used for rendering within a conforming file shall be embedded within that file, as defined in ISO 32000-1:2008, 9.9.", "location": "root/document[0]/pages[0](3 0 obj PDPage)/contentStream[0]/operators[14]/font[0](Helvetica)", "count": 1 } ], "warnings": [] } } } } ``` Here the XML is fine, but the PDF embeds no font program for Helvetica, so it isn't PDF/A-3b and the invoice isn't valid. | Field | Description | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | `result.valid` | `true` when the XML passed and, for a PDF, the PDF passed PDF/A-3b too | | `result.document.container` | `pdf` or `xml`: what you sent | | `result.document.attachment` | The embedded file's name as written in the PDF, such as `factur-x.xml`; `null` for XML | | `result.document.syntax` | `cii` or `ubl` | | `result.document.profile` | The profile the specification identifier names: `MINIMUM`, `BASIC_WL`, `BASIC`, `EN16931`, `EXTENDED` or `XRECHNUNG` | | `result.document.specification_id` | The specification identifier (BT-24), as written in the XML | | `result.conformance.einvoice` | The KoSIT validator's report | | `result.conformance.pdfa` | veraPDF's report, for PDFs only | The reports have the same fields as the [validation report](https://dynamicdocumentapi.com/docs/e-invoicing#validation-report) of a generated e-invoice, with the `status` `passed` or `failed`. An invoice the validator accepts with warnings has passed, and the warnings are listed in its report. `pages` is the PDF's page count, and `null` for XML. A check has no file: `files` is empty, and nothing is delivered. In the dashboard's render log, checks are listed as **E-invoice check** with their verdict. ## Sources [#sources] The `source` takes exactly one of these fields, as for the [PDF tools](https://dynamicdocumentapi.com/docs/pdf-tools#sources): | Field | What it is | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `upload_id` | A file uploaded with `POST /v1/uploads`. Uploads recognise PDFs by their content, and XML when it starts with `