E-Invoice Validator: XRechnung & ZUGFeRD (official KoSIT rules)
Pricing
from $50.00 / 1,000 invoice validateds
E-Invoice Validator: XRechnung & ZUGFeRD (official KoSIT rules)
Validate German e-invoices (XRechnung UBL/CII, ZUGFeRD and Factur-X PDF) against EN 16931 and the official XRechnung 3.0.2 rules with the KoSIT validator. One result and an HTML report per file.
Pricing
from $50.00 / 1,000 invoice validateds
Rating
0.0
(0)
Developer
Daniel Kofler
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 days ago
Last modified
Categories
Share
E-Invoice Validator: XRechnung & ZUGFeRD
Validate German e-invoices against the official rules, without installing Java or the KoSIT validator yourself.
Supported formats
- XRechnung 3.0 in UBL (Invoice, CreditNote) and UN/CEFACT CII
- ZUGFeRD and Factur-X PDF: the embedded XML is extracted and validated
- EN 16931 core invoices
What you get per file
akzeptiert: true or false, the verdict of the KoSIT validatorfehlerandwarnungen: countsmeldungen: every finding with level, rule ID (for exampleBR-DE-15) and the official message textszenario: which rule set matched (XRechnung UBL, CII, Extension, CVD)bericht_url: link to the full HTML report of the KoSIT validatorrechnung_url: link to a readable HTML rendering of the invoice itself (official KoSIT visualization, German labels), useful when you receive XRechnung XML that nobody can readregelwerk: the exact rule version used
Why this matters now
Since January 2025 every business in Germany must be able to receive e-invoices. From January 2027, companies with more than EUR 800,000 turnover in the previous year must issue them, from 2028 all companies in domestic B2B trade. A plain PDF no longer counts.
How it validates
The Actor runs the official KoSIT validator 1.6.3 with the official XRechnung 3.0.2 configuration (2026-08-31), the same rules German public authorities apply. Both are downloaded at build time and checked against SHA-256 checksums. All 86 invoices of the official XRechnung test suite pass.
Input
Links to files:
{ "fileUrls": ["https://example.com/invoice.xml", "https://example.com/zugferd.pdf"] }
Or the files themselves, for example straight from an n8n, Make or Zapier email trigger:
{ "files": [{ "name": "invoice.xml", "contentBase64": "PD94bWwgdmVyc2lvbj0iMS4wIi..." }] }
Up to 100 files per run in total, 20 MB each; links must be http or https. Files that cannot be loaded or decoded are reported and not charged.
Pricing
Pay per event: you pay per validated file. If your spending limit is reached, the run stops and you are not charged for files that were not delivered.
Limits
This Actor checks format and mandatory content according to EN 16931 and XRechnung. It does not judge whether an invoice is correct for tax purposes. Run input, reports and readable copies stay in your own Apify account like any run output and follow your data retention settings; the Actor sends them nowhere else.
Made by HYPEAKZ.IO.