LucadenFree online toolsBrowse toolsZero-upload treasury utility
Extract local CII XML from a Factur-X or ZUGFeRD PDF and inspect its declared profile, version, and key invoice fields.
Bank statements and payment files expose account numbers, counterparties, balances, and references. This workspace reads them only in browser memory and creates downloads locally, so none of that bank data is sent to Lucaden or a third party.
Loading tool workspace…
How it works
Important
A local validator can prove structural checks, but it cannot confirm a bank's implementation rules, account status, sanctions controls, or settlement. Keep the source file, review every result, and test generated output with the receiving bank before production use.
These tools provide local technical checks and transformations, not banking, legal, compliance, or accounting advice. Formats and bank usage rules vary. Always verify output with your bank before submitting, keep the original file, and use a bank test or sandbox channel where available.
Deep explainer
Factur-X and ZUGFeRD are hybrid PDF/A-3 invoices with an embedded UN/CEFACT Cross Industry Invoice XML file for machine processing.
Accounts payable, e-invoicing integration, tax, audit, and supplier-support teams diagnosing hybrid invoices.
A PDF containing factur-x.xml is opened locally; the embedded invoice number, seller, buyer, currency, totals, guideline profile, and XML are displayed without uploading the PDF.
Practical details
Extract local CII XML from a Factur-X or ZUGFeRD PDF and inspect its declared profile, version, and key invoice fields.
Every byte of input is parsed in this browser tab. Downloads are created with Blob URLs; the suite has no upload endpoint, server action, edge parser, or content-bearing telemetry.
Questions
No. These treasury routes read local files through browser ArrayBuffers, parse them in this tab, and create downloads with local Blob URLs. There is no file upload request.
No. A base-format check cannot cover every bank implementation guide, bilateral agreement, local scheme rule, or compliance control. Always test and confirm the output with the receiving bank.
Keep the original, use the reported row, tag, line, or path to correct the source system, and run the complete file again. Lucaden does not silently drop malformed financial records.
Open-source foundations
Lucaden documents its standards sources, architectural references, and permissive runtime dependencies while keeping this workspace consistent with the Lucaden interface.