A missing field can stop your file from being imported. Compare the file with its rules. The result shows where they differ.
An XSD file sets the rules for an XML file.
A missing field or wrong order can cause rejection.
This tool checks the file against the selected rules.
Correct the reported fields and check again before sending.
One self-written numeric assertion: total equals the sum of items. Good: total 5. Deliberately failing: total 6. Edit your own rules in the existing schema / rule editor.
Loading only replaces the editable source and rules. Each check requires your choice of Validate XML and existing server consent.
Only supplied assertions are checked. No country or package conformity. XPath 1.0 / XSLT 1.0 only; DTDs, external documents and includes are blocked. Missing response context stays unknown.
How to try this rulePractise fixing six file errors →
Load an example or add your own file and rules. Run the check and correct the reported fields.
Keep the original XML export. For an invoice, use the XML from your accounting software, not a scan. Have the recipient’s format instructions ready. For an XSD check, also obtain the matching schema and any files it includes.
An XML check finds broken document syntax. An XSD check tests the structure and values against the schema you supply. For country invoice rules, use the matching country validator under E-invoicing and keep the recipient’s acceptance response.
These screenshots use fictional invoices. Controls are in English; Russian and Ukrainian editions use their existing translated pages.
Bewahren Sie den ursprünglichen XML-Export auf. Verwenden Sie für eine Rechnung die XML-Datei aus der Buchhaltung, keinen Scan. Halten Sie die Formatvorgaben des Empfängers bereit. Für die XSD-Prüfung benötigen Sie auch das passende Schema und eingebundene Dateien.
Die XML-Prüfung findet Syntaxfehler. Die XSD-Prüfung kontrolliert Struktur und Werte anhand Ihres Schemas. Nutzen Sie für länderspezifische Rechnungsregeln den passenden Validator unter E-invoicing und bewahren Sie die Annahmebestätigung des Empfängers auf.
Die Aufnahmen zeigen fiktive Rechnungen und englische Bedienelemente. Die russische und ukrainische Ausgabe zeigt die vorhandene übersetzte Seite.
Conservez le fichier XML original. Pour une facture, utilisez le XML exporté du logiciel comptable, pas une image numérisée. Gardez les consignes du destinataire. Pour le contrôle XSD, obtenez aussi le schéma correspondant et les fichiers qu’il inclut.
Le contrôle XML repère les erreurs de syntaxe. Le contrôle XSD vérifie la structure et les valeurs selon votre schéma. Pour les règles nationales de facturation, utilisez le validateur du pays dans E-invoicing et conservez la réponse d’acceptation du destinataire.
Les captures montrent des factures fictives et des commandes en anglais. Les éditions russe et ukrainienne montrent les pages traduites existantes.
Zachowaj oryginalny eksport XML. Dla faktury użyj pliku XML z programu księgowego, a nie skanu. Przygotuj wymagania odbiorcy dotyczące formatu. Do sprawdzenia XSD potrzebujesz także właściwego schematu i dołączanych plików.
Kontrola XML wykrywa błędy składni. Kontrola XSD sprawdza strukturę i wartości według dostarczonego schematu. Reguły faktur danego kraju sprawdź odpowiednim walidatorem w E-invoicing i zachowaj potwierdzenie przyjęcia od odbiorcy.
Zrzuty pokazują fikcyjne faktury i angielskie przyciski. Wersje rosyjska i ukraińska pokazują istniejące przetłumaczone strony.
Păstrați exportul XML original. Pentru o factură, folosiți XML-ul din programul contabil, nu o scanare. Pregătiți cerințele destinatarului privind formatul. Pentru verificarea XSD aveți nevoie și de schema potrivită și de fișierele incluse.
Verificarea XML găsește erori de sintaxă. Verificarea XSD controlează structura și valorile conform schemei furnizate. Pentru regulile naționale de facturare, folosiți validatorul țării din E-invoicing și păstrați răspunsul de acceptare al destinatarului.
Capturile arată facturi fictive și comenzi în engleză. Edițiile rusă și ucraineană arată paginile traduse existente.
Sačuvajte izvorni XML izvoz. Za račun upotrijebite XML iz računovodstvenog programa, a ne skeniranu sliku. Pripremite zahtjeve primatelja za format. Za provjeru XSD-a trebate i odgovarajuću shemu te uključene datoteke.
Provjera XML-a pronalazi sintaktičke pogreške. Provjera XSD-a ispituje strukturu i vrijednosti prema vašoj shemi. Za pravila računa pojedine države upotrijebite njezin validator u E-invoicing i sačuvajte odgovor primatelja o prihvatu.
Snimke prikazuju izmišljene račune i engleske kontrole. Rusko i ukrajinsko izdanje prikazuju postojeće prevedene stranice.
Сохраните исходный экспорт XML. Для счёта используйте XML из бухгалтерской программы, а не скан. Подготовьте требования получателя к формату. Для проверки XSD нужны также подходящая схема и включённые в неё файлы.
Проверка XML находит ошибки синтаксиса. Проверка XSD сверяет структуру и значения с вашей схемой. Для правил выставления счетов выберите валидатор страны в E-invoicing и сохраните ответ получателя о приёме.
На снимках показаны вымышленные счета и существующая русская страница.
Збережіть початковий експорт XML. Для рахунка використовуйте XML з бухгалтерської програми, а не скан. Підготуйте вимоги отримувача до формату. Для перевірки XSD потрібні також відповідна схема та включені файли.
Перевірка XML знаходить помилки синтаксису. Перевірка XSD звіряє структуру та значення з вашою схемою. Для правил виставлення рахунків виберіть валідатор країни в E-invoicing і збережіть відповідь отримувача про прийняття.
На знімках показано вигадані рахунки та наявну українську сторінку.
Check a document against the structure and data types defined by your XSD. Get specific diagnostics without uploading your XML.
Your data stays yours.
Start with the standard file rules check. Choose an advanced check if your recipient needs other rules. Advanced checks need permission before sending your document. You can save rules projects on this device or in your Pro or Team workspace. Compare the checks and file limits
Check one file free. For repeated work, compare plans for several files, saved rules and shared team work.
Pro from US$9/month. Team from US$29/month.
Save two months with annual billing.
An XSD is a file containing rules for other files. It lists required fields, their order and which values are allowed. For example, a quantity may need a number. Writing “two” is readable text but would fail that rule.
Open your data file in the left editor and its rules file on the right. Keep XML + XSD selected and choose Validate XML. Use the rules version required by the recipient. The included order example shows both a working file and a deliberate mistake.
Two short field names can look the same but have different full names. Compare the full names in your file and its rules. Check the field order too. A missing-field message may mean the field is absent or that another field appears too early.
Developers can add automatic file checks to a project. The setup guide explains which checks run on their own systems and which use the API. XSDHub GitHub Action Copy the CI example
Open your file and all the rules files supplied by the recipient. Choose Validate XML. The check compares required fields, their order and allowed value types. Follow the example to compare a working file with a deliberate error. Follow the XML and XSD example
The rules file must be readable before the data can be checked. A passing result covers those rules only. It does not prove that they include every requirement from your customer. Compare them with the customer’s instructions and test working and faulty examples.
Validate XML syntax in your browser, find malformed tags and read errors with line numbers. Free, no document uploads. UTF-8 XML files up to 10 MB.
Open XML validatorCheck identifiers, code lists and document totals locally. Each result names its rule and source.
The local check sends no document or identifier to a register.
Certificate checks use authenticated EU trust list 398, including France 184 and Italy 225. Ask your signature provider to verify the signed document, revocation and qualified status before relying on the signature. Certificate check details.
The report includes source paths, amounts and certificate fingerprints. Review it before sharing.
When neither limit is stated, the field must appear exactly once. The rules can also allow a missing field or repeated fields. An empty field still counts as present. Its value must meet the field’s own requirements.
Compare the complete examples of missing, empty and repeated fields. complete minOccurs and maxOccurs examples
See validation errors with line numbers where available. Correct your data, check again, and export a JSON result for your records.
Check your XML against an XSD 1.0 schema, or choose XSD 1.1 or Schematron for other rules. Give permission before sending a document for an advanced check. Save schema projects on this device or in your Pro or Team workspace. Compare the checks and file limits.
XML Schema Definition, or XSD, describes the structure a class of XML documents is expected to follow. A schema can require an attribute, restrict an element to a number, define the order of children and limit how many times an item appears. Well-formed XML can still fail its schema: <quantity>two</quantity> is valid XML syntax but fails when quantity is defined as xs:positiveInteger.
Open or paste your XML in the left editor and your XSD in the right editor. Keep XML + XSD selected, then run Validate XML. Use the exact schema version required by the system receiving the document. Start with the included order example; the invalid example deliberately puts text in numeric fields so you can see the resulting diagnostics.
An element called order in a namespace is different from an order element with no namespace. Compare the XML namespace with the schema targetNamespace before renaming elements. For xs:sequence, child elements must also appear in the declared order. Missing child element errors can therefore point to either an absent field or an unexpected field appearing too early.
Open your XML and the complete XSD supplied by your recipient, then choose Validate XML. The result checks required fields, element order and data types against that schema. Follow the XML and XSD example to try a passing document and a deliberate error.
The schema must load successfully before a document can be checked. A passing document shows that it meets that schema; it does not prove that the schema describes every business requirement. Compare the schema with the recipient’s specification and test both accepted and rejected examples.
Both attributes default to 1 when omitted from an element declaration inside a content model. Set minOccurs="0" to allow absence or maxOccurs="unbounded" to allow repetition without a fixed upper count. An empty element still counts as one occurrence and must satisfy its value type.
Paste a document or open a UTF-8 file. Start with the included examples to see what valid and invalid data look like.
An XSD is the rules file your recipient expects. It sets required fields, their order and the kind of values allowed. For broken labels only, choose XML syntax only.
Read the error and its line number when available. Correct the data and check again. Download the result for your records.
Rules and schema references: W3C · XML 1.0 Fifth Edition; W3C · XSD 1.0 Second Edition. Check the result for the exact version used.
A text file with labelled fields, such as an invoice amount. Your software makes it for another computer to read.
Read the full definitionA file that sets the rules for an XML file. It lists required fields and their order.
Read the full definitionThe agreed structure of a file, like a form with fixed boxes.
Read the full definition