Finance ops, e-invoicing teams and integrators · no signup
UBL invoice XML preflight
Separate malformed XML from unexpected invoice structure before deeper e-invoice validation or remediation.
Start with well-formedness, inspect the document shape, then inspect common UBL invoice fields. The sequence is structural triage only and does not claim EN16931, Peppol or platform acceptance.
The builder stores route slugs only. It does not carry pasted text, uploaded files or generated results between tool pages.
Outcome-first sequence
The order is curated around the job, not around a product feature menu.
Explicit data boundary
Each atomic tool keeps its own runtime and privacy truth. A recipe never silently moves your payload.
Canonical tools only
Every step resolves against the live free-tool catalog, so stale recipe routes fail closed in code.
Recipe · 3 verified steps
- 1Open step
Check XML syntax
XML Syntax Validator
Confirm the invoice is well-formed XML before diagnosing invoice-specific structure.
Developer utilities · fast-xml-parser · MIT
- 2Open step
Inspect document shape
XML Structure Inspector
Review the root element, namespaces and common tags for obvious structural surprises.
Developer utilities · fast-xml-parser · MIT
- 3Open step
Inspect UBL fields
UBL Invoice XML Inspector
Surface common UBL invoice fields before moving into deeper compliance or remediation work.
Business utilities · fast-xml-parser · MIT
When the job repeats
Keep one-off work free. Escalate only when repetition creates value.
If this becomes a recurring workflow that needs monitoring, evidence, team controls or support, compare the paid workflow products instead of paying to unlock the atomic utilities.
Pass the useful route forward
Share this workflow, not visitor data.
Native share sends only this canonical Solarc route plus public page context. It never includes tool inputs, generated results, uploaded files, local presets or builder state.