A document can be readable, mathematically consistent and still contain evidence of alteration. Ultiwrite Forensics examines the file itself, with metadata always included.
Examine applicable font, glyph and text-placement inconsistencies, including differences in identity-critical fields, monetary columns and repeated page elements. Fine-grained differences can matter even when the extracted words look right.
Inspect the original PDF’s construction, retained revisions and applicable local editing evidence. A later export or a single-revision file can limit what history survives; absence of a trace is not proof of integrity.
Read available file properties, creation tools and timestamps. Examine inconsistencies between recorded history and the document’s internal timeline. Ordinary metadata edits and later exports are not automatically manipulation.
Apply supported checks to statement layout, printed figures, dates and document structure. Reconciled totals answer an arithmetic question; they do not settle whether a submitted statement was altered.
Receive findings linked to source-bound evidence, an original-byte hash, examination time and actual engine/profile versions. The web result and downloadable forensic PDF come from the same published snapshot.
See which checks completed, were partial, failed or could not be assessed for your file. Scanned or flattened pages can limit text and layout evidence. Visible-text comparison examines at most two rendered pages. A failed or skipped comparison stays incomplete; it is not filled in as a clean result.
Document extraction and verification tools vary in scope. Ultiwrite adds a forensic examination of the supplied file to the questions below; it does not claim every other service lacks forensic checks.
| Approach | What it can establish | The question still open |
|---|---|---|
| OCR / text extraction | The words and figures a system reads. | What construction, typographic or retained editing evidence is lost in the extracted text? |
| Arithmetic reconciliation | Whether available numbers and totals agree. | Was a plausible, internally consistent document altered? |
| Identifier / name matching | Whether an identifier or name meets the service’s matching rules. | Is this uploaded copy genuine, and is the exact legal entity the intended one? |
| Ultiwrite document forensics | Applicable document-level findings, with evidence and explicit coverage. | Issuer confirmation, legal-entity ownership and any examination limitations still need independent resolution. |
Stricter EIN name matching has a practical cost. A legitimate applicant may type “L.L.C.” where the name recorded when the EIN was issued uses “LLC.” Increasing strictness can reject ordinary input errors and formatting variations; relaxing it can overlook a materially different legal name.
Punctuation variation is different from “LLC” versus “Inc.” A verification process needs to accommodate the former without treating different legal entities as interchangeable. Simply turning up a matching threshold is not a complete solution.
CP575 document forensics provides another route to assess the submitted evidence. Ultiwrite examines the letter’s construction, typography, layout, metadata and retained editing traces for applicable inconsistencies. This adds evidence that an extracted identifier or name comparison alone cannot supply, with source-bound findings, examination coverage and limitations you can inspect.
Start with one unencrypted PDF, up to 3 MiB and 40 pages. Metadata is included in every examination. Exact original bytes are preserved through intake. There is no selector for investigation tiers, no separate metadata fee and no charge to reopen or redownload a retained report.
Choose a document → sign in → confirm usage or purchase → analyze → inspect findings → download the forensic PDF.
