Archiving and long-term compliance
Produce and verify archival PDF/A, and prove it
Convert, validate and archive documents to a conformance level you can name in an audit.
The problem
A retention policy says "PDF/A", and the documents arriving from a dozen systems are not. Converting them is one problem; being able to show that the result conforms is the harder one.
The approach
Convert to the conformance level you need, embed the fonts and colour information that level requires, and check the result rather than assuming it.
How you can check it
The conformance surface is documented and counted on the PDF/A capability page, and the engine's own output is validated against an independent PDF/A validator in the SDK build.
- PDF/A & Conformance (52 APIs)
- Fonts (82 APIs)
- Import & Output APIs (75 APIs)
The capability areas behind it
Prove it on your own documents
Public download, no account. Run it against the files you actually have before anyone signs anything.