Business file tools
A focused cluster for invoice inspection, format detection, and structured invoice workflows. Built to stay useful without pretending to be a full compliance platform.
Upload XML or PDF invoice files and identify whether they look like UBL, CII, Factur-X, ZUGFeRD, or an unknown structure.
Open detectorOpen UBL or Peppol XML invoices in a readable summary with supplier, buyer, totals, and line items.
Open viewerScan a PDF invoice for embedded XML and export the extracted payload when a hybrid invoice is actually present.
Open extractorWhat this cluster is for
The value here is in the workflow: identify the format, inspect the XML, and verify the important fields before you decide what to do next. That is more useful than another generic "what is Peppol" article on its own.
It helps with the first step of invoice handling: detection, reading, and extraction. Those are practical, repeatable tasks users actually search for.
It does not pretend to validate legal compliance, send invoices, or replace live registry access where a reliable lookup is not available.
Most converter sites stop at files changing format. This cluster also explains what the file is and what the invoice data actually means.
If an invoice arrives as a file you do not recognize, use the detector first. If the detector shows a structured XML family, open the file in the viewer and confirm supplier, buyer, totals, dates, and line items. If the invoice is a PDF that should contain machine-readable data, run the extractor and then inspect the XML result.
Start with the detector when you do not know the file type. Use the viewer when you already have UBL or Peppol XML. Use the extractor when a hybrid PDF should contain structured XML behind the scenes.
If a supplier sends a PDF and claims it is a structured invoice, the extractor is the fastest way to confirm whether machine-readable XML is actually embedded.
If an ERP or billing platform exports XML, the detector helps identify the family first and the viewer helps confirm the visible invoice fields before handoff.
If users are unsure whether they are looking at UBL, CII, Factur-X, or ZUGFeRD, the comparison guides explain the differences without forcing them into registry or network tooling.
Best-effort extraction only works when the PDF contains plain-text XML markers or a clearly readable embedded invoice payload. If the file is compressed or protected, the tool should tell you that instead of guessing.
These pages explain the differences between common invoice formats and the workflows around them, so the cluster gives users both a tool and the context needed to use it properly.
Who is this cluster for? People who receive invoice files, need to inspect structured invoice data, or want to understand what kind of invoice file they were given.
Does Tooltensor claim the files are legally compliant? No. The tools inspect file structure and displayed content, but they do not certify legal, tax, or accounting compliance.
Why include guides as well as tools? Because structured invoice workflows are easy to misunderstand if a site only returns raw data without explanation.
Why is this different from a generic converter site? Because the cluster is built around invoice inspection workflows, not just file extension changes.