Mustang validation report breaks on & in the filename
Separate a broken validation report from an invalid invoice and compare identical contents under a neutral filename.
KAN KAI WORKS · Help
A file can look correct while failing to match the required technical format. For electronic invoices, distinguish the document, its profile and the specific validation rule. For PDF work, check whether a change exists only in the viewer or also in the saved file.
These guides cover technical checks. Passing one rule, producing a PDF or completing an import does not by itself establish complete business or legal compliance.
Separate a broken validation report from an invalid invoice and compare identical contents under a neutral filename.
Read PDF/A, invoice XML and overall results separately when wasCompletelyValid returns true despite a PDF failure.
Locate the exact numeric field and separate XML formatting errors from overly strict importer handling.
Locate the affected allowance or charge in the XML.
Distinguish generation failure from a display issue.
Separate visible-signature font errors from token access and cryptographic signature validation.
Compare the crop preview with saved output on clearly identifiable pages when the selected area shifts.
Check the saved PDF for old text and distinguish editing, covering and permanent removal.
Measure opening, navigation and server processing separately when technical drawings become difficult to use in the viewer.
Compare ID-token claims, UserInfo and supported user mapping when Entra sign-in fails in Stirling PDF.
Reconcile line totals, document allowances, charges and the payable amount separately when import reports an arithmetic difference.
Compare complete rule bundles, scenarios and versions when the same XRechnung passes one check and fails another.
Explore all 100 troubleshooting guides →
Describe the affected system, the visible problem and when it started. That gives us a starting point for the next check.
Describe a different issue →