COVERAGE IS PART OF THE RESULT
Know exactly
what was checked.
Every result names its profile, versions and completed stages. A readable view is not validation. An interrupted or partial ruleset never receives a passing conformance value.
| Syntax / profile | Available | Boundaries |
|---|---|---|
| UBL Invoice / CreditNote · EN16931 | UBL 2.1 XSD + EN16931 1.3.16 business rules | Select EN16931 explicitly when the profile identifier is missing. |
| CII · EN16931 | CII D16B XSD + EN16931 1.3.16 business rules | Supported normalized fields remain linked to their XML source. |
| XRechnung · UBL / CII | Official XSD, EN16931 and national rules; configuration 2026-08-31 / XRechnung 3.0.2 | Exact scenario selection. Raw validity and acceptance can differ under official severity overrides. |
| Peppol BIS · UBL | UBL XSD + EN16931 + standalone BIS 3.0.21 (May 2026) | No Peppol delivery or access-point acceptance check. |
| ZUGFeRD / Factur-X PDF | Local embedded XML extraction; CII EN16931 checks | No PDF/A-3, visual/XML equivalence, MINIMUM/BASIC/EXTENDED profile certification or transmission-platform certification. |
| KSeF FA(3) | Published FA(3) 1-0E XSD graph, namespace 2025/06/25/13775 | Schema coverage only. No KSeF submission, authorization or backend business checks. |
Result signals
valid stays null when the selected ruleset has not been fully evaluated. A schema rejection stops later business rules; rawValid: false records that rejection and acceptable: false prevents approval. Completed XRechnung results preserve both the original severity and the effective KoSIT severity. Rule-page arithmetic examples remain partial preflight.
Generation and repair
CSV, XLSX and JSON produce one positive-quantity, positive standard-VAT invoice at a time: XRechnung UBL, Peppol UBL, EN16931 CII XML or ordinary domestic PLN FA(3). Unsupported allowances, prepayments and special tax cases are rejected by the source model. GREEN changes normalize published currency/country codes with exact logging. AMBER scheme changes require a displayed before/after and confirmation. RED commercial edits require your source value and explicit approval. Signed XML is not edited. Every rewritten/generated document revalidates locally.
Valid is not ready
Technical validity is separate from recipient acceptance. Autum8 Ready also checks configured recipient/order rules, syntax, country, source freshness and current-run confirmation. Public baselines are scoped, sourced and freshness-tracked; actual commercial/order values are supplied by the user. READY never guarantees acceptance, tax legality or transmission.
Sources and distribution
Official archives and downloaded build inputs are hash pinned. The ISO Schematron compiler is pinned to a commit. Source files and notices accompany the local build. Legal redistribution approval remains a publication gate; local technical tests do not constitute that approval.